← Qiki · all runs · 📊 leaderboard
r-1788776318396-fm3jk
Write the SOP for onboarding a new engineer in week one — accounts and access, first commit, buddy assignment, and a day-5 checkpoint
model /nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF upstream http://127.0.0.1:8080 harness 127.0.0.1
score 0 / 10
2026-09-07 10:18:38 UTC · total 85s · 1 step
ops-doc · done · 85s
Engineer Onboarding SOP (Week 1)
0 / 10
model /nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF harness 127.0.0.1:8080
validity 0/2
fidelity 0/2
structure 0/2
depth 0/2
cleanliness 0/2
why (1 notes)
- unknown kind
1 LLM call on this step
ok ·
84865 ms · prompt 1960c → resp 3299c ·
t=0.35 max=2800 ·
→ /nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF @ http://127.0.0.1:8080
→ /nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF @ http://127.0.0.1:8080
raw JSON
{
"id": "r-1788776318396-fm3jk",
"prompt": "Write the SOP for onboarding a new engineer in week one — accounts and access, first commit, buddy assignment, and a day-5 checkpoint",
"project": {
"name": "OnboardFlow",
"tagline": "Streamlined 5-day engineer onboarding SOP for seamless integration",
"theme": "clean, structured, and professional documentation with a focus on clarity and efficiency",
"brandColors": [
"#2563EB",
"#10B981",
"#F3F4F6",
"#1F2937"
],
"audience": "Engineering Managers, HR, and New Hires",
"vibe": "organized, supportive, efficient, clear"
},
"steps": [
{
"id": "s1-q67jx",
"kind": "ops-doc",
"params": {
"brief": "Write a Standard Operating Procedure (SOP) for onboarding a new engineer during their first week. The document must cover the following key milestones: 1) Accounts and Access provisioning (day 1), 2) Buddy assignment and introduction, 3) Guiding the engineer to their first commit (day 2-3), and 4) A structured day-5 checkpoint meeting to review progress and address blockers. Use a clear, professional tone suitable for engineering managers and HR.",
"variant": "sop",
"project": {
"name": "OnboardFlow",
"tagline": "Streamlined 5-day engineer onboarding SOP for seamless integration",
"theme": "clean, structured, and professional documentation with a focus on clarity and efficiency",
"brandColors": [
"#2563EB",
"#10B981",
"#F3F4F6",
"#1F2937"
],
"audience": "Engineering Managers, HR, and New Hires",
"vibe": "organized, supportive, efficient, clear"
},
"heroPlanned": false
},
"label": "Engineer Onboarding SOP (Week 1)"
}
],
"results": {
"s1-q67jx": {
"status": "done",
"startedAt": 1788776318399,
"attempt": 1,
"output": {
"html": "<!doctype html><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1\">\n<title>New Engineer First-Week Onboarding SOP</title>\n<style>\n:root{\n --bg:#faf7f2;--surface:#ffffff;--elevated:#f2ede4;\n --text:#171410;--muted:#5d574e;--border:rgba(23,20,16,.14);\n --accent:#10B981;--accent-btn:#10B981;--accent-text:#0b7955;--ink:#0a0a0a;--glow:rgba(16,185,129,0.20);--soft:rgba(16,185,129,0.13);\n /* Foreground for anything painted on --soft. See the derivation above: a token\n computed against --bg is not valid on a tinted surface. */\n --soft-ink:#0b7955;\n /* Minimum comfortable hit area. Referenced by every interactive rule so a\n tap target can never regress below the 44px WCAG/iOS floor. */\n --tap:44px;\n /* Translucent chrome derived from the direction's own background. Hardcoding\n rgba(10,10,11,.62) here put dark text on a dark nav (1.08:1) the moment a\n light direction shipped. */\n --nav-bg:rgba(250,247,242,0.72);--hairline:rgba(0,0,0,.14);\n --font:ui-sans-serif,system-ui,-apple-system,'Segoe UI',Roboto,Helvetica,Arial,sans-serif;\n --font-display:'Iowan Old Style','Palatino Linotype',Palatino,'Book Antiqua',Georgia,serif;\n --w-display:400;--w-body:400;\n --track-display:-.01em;\n --texture:radial-gradient(1200px 500px at 80% -10%, rgba(138,51,36,.06), transparent 60%);\n --maxw:1200px;--r:3px;--r-lg:5px;--ease:cubic-bezier(.4,0,.2,1);\n color-scheme:light;\n}\n\n*{box-sizing:border-box}\nbody{background:var(--bg);background-image:var(--texture);color:var(--text);font-family:var(--font);\nfont-weight:var(--w-body);font-size:16px;line-height:1.6;margin:0;padding:clamp(24px,4vw,64px);-webkit-font-smoothing:antialiased}\n.doc{max-width:50rem;margin:0 auto}\nh1{font-family:var(--font-display);font-weight:var(--w-display);letter-spacing:var(--track-display);\nfont-size:clamp(1.8rem,4vw,2.7rem);line-height:1.15;margin:0}\n.doctype{font-size:.8rem;text-transform:uppercase;letter-spacing:.1em;color:var(--accent-text);font-weight:700;margin:0 0 10px}\n.sub{color:var(--muted);font-size:1.02rem;margin:8px 0 0;max-width:62ch}\nh2{font-family:var(--font-display);font-weight:var(--w-display);font-size:1.18rem;letter-spacing:-.01em;\nmargin:34px 0 12px;display:flex;align-items:center;gap:10px}\n.count{font-size:.8rem;font-weight:600;color:var(--soft-ink);background:var(--soft);border-radius:99px;padding:2px 10px}\np{margin:0 0 14px;max-width:68ch}\n.lede{color:var(--muted);font-size:1.02rem;margin:22px 0 0;max-width:66ch}\n.eyebrow{display:block;font-size:.8rem;text-transform:uppercase;letter-spacing:.09em;color:var(--muted);font-weight:700;margin-bottom:6px}\n.meta{display:flex;flex-wrap:wrap;gap:8px 24px;margin:26px 0 0;font-size:.9rem;color:var(--muted);\npadding-bottom:20px;border-bottom:1px solid var(--border)}\n.meta b{color:var(--text);font-weight:700;margin-right:6px}\n.sub-line{color:var(--muted);font-size:.9rem;margin-top:4px}\n.act{font-weight:700;font-size:1rem;line-height:1.4}\n.chip{display:inline-flex;align-items:center;background:var(--soft);color:var(--soft-ink);\npadding:4px 12px;border-radius:99px;font-size:.82rem;font-weight:700}\n.chip.alt{background:transparent;border:1px solid var(--border);color:var(--muted)}\n.tags{display:flex;flex-wrap:wrap;gap:8px;margin-top:10px}\nol.steps{list-style:none;margin:0;padding:0;counter-reset:none}\n.step{display:grid;grid-template-columns:2.6rem 1fr;gap:14px;background:var(--surface);border:1px solid var(--border);\nborder-radius:var(--r);padding:16px 18px;margin-bottom:10px}\n.num{font-family:var(--font-display);font-weight:var(--w-display);font-size:1.25rem;color:var(--accent-text);line-height:1.25}\n.done{margin-top:12px;font-size:.92rem;color:var(--muted);border-left:2px solid var(--accent-text);padding-left:12px}\n.done b{color:var(--text)}\nul.plain{margin:0;padding-left:20px}ul.plain li{margin-bottom:8px}\nol.plain{margin:0;padding-left:22px}ol.plain li{margin-bottom:8px}\n/* Printable checklist: a drawn box, not an <input>. A real checkbox is a ~20px\n hit target inside a document nobody submits, and it would trip the 44px\n interactive floor. The ROW carries --tap so it stays comfortable either way. */\nul.check{list-style:none;margin:0;padding:0}\nul.check li{display:flex;align-items:flex-start;gap:14px;min-height:var(--tap);padding:11px 0;border-bottom:1px solid var(--border)}\n.box{flex:none;width:20px;height:20px;margin-top:3px;border:2px solid var(--accent-text);border-radius:5px}\nul.cards{list-style:none;margin:0;padding:0}\nul.cards li{background:var(--surface);border:1px solid var(--border);border-left:3px solid var(--accent-text);\nborder-radius:var(--r);padding:14px 16px;margin-bottom:10px}\n.kv{display:grid;grid-template-columns:repeat(auto-fit,minmax(200px,1fr));gap:22px;margin:26px 0 8px}\n.salary{margin:26px 0 0}\ntable{width:100%;border-collapse:collapse;font-size:.95rem;margin-top:8px}\nth{text-align:left;font-size:.8rem;text-transform:uppercase;letter-spacing:.08em;color:var(--muted);\nfont-weight:700;padding:0 10px 10px 0;border-bottom:1px solid var(--border)}\ntd{padding:12px 10px 12px 0;border-bottom:1px solid var(--border);vertical-align:top}\nth.n,td.n{text-align:right;padding-right:0;font-variant-numeric:tabular-nums;white-space:nowrap}\ntfoot td{border-bottom:0;padding:6px 10px 6px 0;color:var(--muted)}\ntfoot tr.total td{color:var(--text);font-weight:700;font-size:1.12rem;border-top:2px solid var(--accent-text);padding-top:14px}\n.org ul{list-style:none;margin:0;padding-left:28px;border-left:1px solid var(--border)}\n.org>ul{padding-left:0;border-left:0}\n.node{display:inline-flex;flex-direction:column;justify-content:center;min-height:var(--tap);\nbackground:var(--surface);border:1px solid var(--border);border-left:3px solid var(--accent-text);\nborder-radius:var(--r);padding:10px 16px;margin:7px 0}\n.node b{font-size:1rem;line-height:1.35}\n.node span{color:var(--muted);font-size:.88rem}\n.obj{display:grid;grid-template-columns:3rem 1fr;gap:14px;margin-bottom:26px}\n.obj h2{margin:0}\nul.krs{list-style:none;margin:14px 0 0;padding:0}\nul.krs li{border-left:2px solid var(--border);padding:0 0 0 14px;margin-bottom:14px}\n.notice{border:1px solid var(--accent-text);background:var(--soft);border-radius:var(--r);\npadding:14px 18px;margin:28px 0 0;font-size:.92rem;color:var(--text);max-width:none}\n.notice b{display:block;color:var(--accent-text);margin-bottom:4px;font-size:.82rem;\ntext-transform:uppercase;letter-spacing:.08em}\n.todo{display:inline-block;background:var(--soft);color:var(--soft-ink);border:1px dashed var(--accent-text);\nborder-radius:6px;padding:2px 9px;font-size:.88rem;font-weight:700}\n.signoff{margin-top:38px;color:var(--muted);font-size:.92rem}\n.rule{display:inline-block;width:220px;border-bottom:1px solid var(--border);margin-top:26px}\n@media print{body{padding:0}.doc{max-width:none}}\n</style></head><body><main class=\"doc\">\n<p class=\"doctype\">Standard operating procedure</p><h1>New Engineer First-Week Onboarding SOP</h1><p class=\"sub\">Following this procedure guarantees that a new engineer has secure access, clear social integration, a verified first contribution, and a structured feedback loop within five business days.</p><div class=\"meta\"><span><b>Owner</b> Engineering Manager</span><span><b>Trigger</b> Offer letter signed and start date confirmed</span><span><b>Review</b> This SOP is reviewed annually by the Head of Engineering and HR Business Partner to ensure alignment with current tools and team structure.</span></div>\n<p class=\"lede\">Applies to all newly hired software engineers from the moment the offer is accepted until the end of the first week. Does not apply to contractors or interns unless explicitly specified in their contract.</p>\n<h2>Procedure</h2>\n<ol class=\"steps\"><li class=\"step\">\n <div class=\"num\">1</div>\n <div>\n <div class=\"act\">Create and distribute login credentials for all required systems (GitHub, Jira, Slack, CI/CD, cloud console)</div>\n <div class=\"tags\"><span class=\"chip\">IT Operations</span><span class=\"chip alt\">Identity Management System</span></div>\n <div class=\"done\"><b>Done when</b> The new engineer successfully logs into GitHub and Jira using the provided credentials</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">2</div>\n <div>\n <div class=\"act\">Assign a buddy and schedule a 30-minute introductory coffee chat</div>\n <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Calendar System</span></div>\n <div class=\"done\"><b>Done when</b> The calendar invite for the buddy introduction is sent and accepted by both parties</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">3</div>\n <div>\n <div class=\"act\">Provide the new engineer with a 'Hello World' or low-risk bug fix task and explain the local development setup</div>\n <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">Local Development Environment</span></div>\n <div class=\"done\"><b>Done when</b> The new engineer has the codebase cloned locally and the application runs successfully on their machine</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">4</div>\n <div>\n <div class=\"act\">Guide the new engineer through creating a pull request and merging their first commit</div>\n <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">GitHub/GitLab</span></div>\n <div class=\"done\"><b>Done when</b> The pull request is merged into the main branch and the CI pipeline passes green</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">5</div>\n <div>\n <div class=\"act\">Conduct a 15-minute check-in to review access, setup, and the first commit experience</div>\n <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Video Conferencing Tool</span></div>\n <div class=\"done\"><b>Done when</b> The meeting takes place and any immediate blockers are documented in the ticketing system</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">6</div>\n <div>\n <div class=\"act\">Schedule a 30-minute structured checkpoint meeting for the end of day 5</div>\n <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Calendar System</span></div>\n <div class=\"done\"><b>Done when</b> The meeting is scheduled on the calendar with the agenda shared with the new engineer</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">7</div>\n <div>\n <div class=\"act\">Review progress against the first-week checklist and address any outstanding blockers or questions</div>\n <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Project Management Tool</span></div>\n <div class=\"done\"><b>Done when</b> The checklist is marked as complete and any open issues are assigned to owners with due dates</div>\n </div>\n</li></ol>\n<h2>If something goes wrong</h2><ul class=\"plain\"><li>I</li><li>If</li></ul>\n\n</main></body></html>",
"variant": "sop",
"label": "Standard operating procedure",
"title": "New Engineer First-Week Onboarding SOP",
"doc": {
"title": "New Engineer First-Week Onboarding SOP",
"purpose": "Following this procedure guarantees that a new engineer has secure access, clear social integration, a verified first contribution, and a structured feedback loop within five business days.",
"scope": "Applies to all newly hired software engineers from the moment the offer is accepted until the end of the first week. Does not apply to contractors or interns unless explicitly specified in their contract.",
"owner": "Engineering Manager",
"trigger": "Offer letter signed and start date confirmed",
"steps": [
{
"action": "Create and distribute login credentials for all required systems (GitHub, Jira, Slack, CI/CD, cloud console)",
"owner": "IT Operations",
"doneWhen": "The new engineer successfully logs into GitHub and Jira using the provided credentials",
"tool": "Identity Management System"
},
{
"action": "Assign a buddy and schedule a 30-minute introductory coffee chat",
"owner": "Engineering Manager",
"doneWhen": "The calendar invite for the buddy introduction is sent and accepted by both parties",
"tool": "Calendar System"
},
{
"action": "Provide the new engineer with a 'Hello World' or low-risk bug fix task and explain the local development setup",
"owner": "Buddy",
"doneWhen": "The new engineer has the codebase cloned locally and the application runs successfully on their machine",
"tool": "Local Development Environment"
},
{
"action": "Guide the new engineer through creating a pull request and merging their first commit",
"owner": "Buddy",
"doneWhen": "The pull request is merged into the main branch and the CI pipeline passes green",
"tool": "GitHub/GitLab"
},
{
"action": "Conduct a 15-minute check-in to review access, setup, and the first commit experience",
"owner": "Engineering Manager",
"doneWhen": "The meeting takes place and any immediate blockers are documented in the ticketing system",
"tool": "Video Conferencing Tool"
},
{
"action": "Schedule a 30-minute structured checkpoint meeting for the end of day 5",
"owner": "Engineering Manager",
"doneWhen": "The meeting is scheduled on the calendar with the agenda shared with the new engineer",
"tool": "Calendar System"
},
{
"action": "Review progress against the first-week checklist and address any outstanding blockers or questions",
"owner": "Engineering Manager",
"doneWhen": "The checklist is marked as complete and any open issues are assigned to owners with due dates",
"tool": "Project Management Tool"
}
],
"exceptions": [
"If access credentials fail to work, escalate immediately to IT Operations with a ticket priority of High",
"If the assigned buddy is unavailable, the Engineering Manager must temporarily assume the buddy role or assign an alternative senior engineer",
"If the first commit fails due to environment issues, pause the timeline and resolve the technical blocker before proceeding to the checkpoint"
],
"review": "This SOP is reviewed annually by the Head of Engineering and HR Business Partner to ensure alignment with current tools and team structure."
},
"accent": "#10B981",
"direction": "editorial",
"needsLegalReview": false,
"warnings": []
},
"produces": {
"siteHtml": "<!doctype html><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1\">\n<title>New Engineer First-Week Onboarding SOP</title>\n<style>\n:root{\n --bg:#faf7f2;--surface:#ffffff;--elevated:#f2ede4;\n --text:#171410;--muted:#5d574e;--border:rgba(23,20,16,.14);\n --accent:#10B981;--accent-btn:#10B981;--accent-text:#0b7955;--ink:#0a0a0a;--glow:rgba(16,185,129,0.20);--soft:rgba(16,185,129,0.13);\n /* Foreground for anything painted on --soft. See the derivation above: a token\n computed against --bg is not valid on a tinted surface. */\n --soft-ink:#0b7955;\n /* Minimum comfortable hit area. Referenced by every interactive rule so a\n tap target can never regress below the 44px WCAG/iOS floor. */\n --tap:44px;\n /* Translucent chrome derived from the direction's own background. Hardcoding\n rgba(10,10,11,.62) here put dark text on a dark nav (1.08:1) the moment a\n light direction shipped. */\n --nav-bg:rgba(250,247,242,0.72);--hairline:rgba(0,0,0,.14);\n --font:ui-sans-serif,system-ui,-apple-system,'Segoe UI',Roboto,Helvetica,Arial,sans-serif;\n --font-display:'Iowan Old Style','Palatino Linotype',Palatino,'Book Antiqua',Georgia,serif;\n --w-display:400;--w-body:400;\n --track-display:-.01em;\n --texture:radial-gradient(1200px 500px at 80% -10%, rgba(138,51,36,.06), transparent 60%);\n --maxw:1200px;--r:3px;--r-lg:5px;--ease:cubic-bezier(.4,0,.2,1);\n color-scheme:light;\n}\n\n*{box-sizing:border-box}\nbody{background:var(--bg);background-image:var(--texture);color:var(--text);font-family:var(--font);\nfont-weight:var(--w-body);font-size:16px;line-height:1.6;margin:0;padding:clamp(24px,4vw,64px);-webkit-font-smoothing:antialiased}\n.doc{max-width:50rem;margin:0 auto}\nh1{font-family:var(--font-display);font-weight:var(--w-display);letter-spacing:var(--track-display);\nfont-size:clamp(1.8rem,4vw,2.7rem);line-height:1.15;margin:0}\n.doctype{font-size:.8rem;text-transform:uppercase;letter-spacing:.1em;color:var(--accent-text);font-weight:700;margin:0 0 10px}\n.sub{color:var(--muted);font-size:1.02rem;margin:8px 0 0;max-width:62ch}\nh2{font-family:var(--font-display);font-weight:var(--w-display);font-size:1.18rem;letter-spacing:-.01em;\nmargin:34px 0 12px;display:flex;align-items:center;gap:10px}\n.count{font-size:.8rem;font-weight:600;color:var(--soft-ink);background:var(--soft);border-radius:99px;padding:2px 10px}\np{margin:0 0 14px;max-width:68ch}\n.lede{color:var(--muted);font-size:1.02rem;margin:22px 0 0;max-width:66ch}\n.eyebrow{display:block;font-size:.8rem;text-transform:uppercase;letter-spacing:.09em;color:var(--muted);font-weight:700;margin-bottom:6px}\n.meta{display:flex;flex-wrap:wrap;gap:8px 24px;margin:26px 0 0;font-size:.9rem;color:var(--muted);\npadding-bottom:20px;border-bottom:1px solid var(--border)}\n.meta b{color:var(--text);font-weight:700;margin-right:6px}\n.sub-line{color:var(--muted);font-size:.9rem;margin-top:4px}\n.act{font-weight:700;font-size:1rem;line-height:1.4}\n.chip{display:inline-flex;align-items:center;background:var(--soft);color:var(--soft-ink);\npadding:4px 12px;border-radius:99px;font-size:.82rem;font-weight:700}\n.chip.alt{background:transparent;border:1px solid var(--border);color:var(--muted)}\n.tags{display:flex;flex-wrap:wrap;gap:8px;margin-top:10px}\nol.steps{list-style:none;margin:0;padding:0;counter-reset:none}\n.step{display:grid;grid-template-columns:2.6rem 1fr;gap:14px;background:var(--surface);border:1px solid var(--border);\nborder-radius:var(--r);padding:16px 18px;margin-bottom:10px}\n.num{font-family:var(--font-display);font-weight:var(--w-display);font-size:1.25rem;color:var(--accent-text);line-height:1.25}\n.done{margin-top:12px;font-size:.92rem;color:var(--muted);border-left:2px solid var(--accent-text);padding-left:12px}\n.done b{color:var(--text)}\nul.plain{margin:0;padding-left:20px}ul.plain li{margin-bottom:8px}\nol.plain{margin:0;padding-left:22px}ol.plain li{margin-bottom:8px}\n/* Printable checklist: a drawn box, not an <input>. A real checkbox is a ~20px\n hit target inside a document nobody submits, and it would trip the 44px\n interactive floor. The ROW carries --tap so it stays comfortable either way. */\nul.check{list-style:none;margin:0;padding:0}\nul.check li{display:flex;align-items:flex-start;gap:14px;min-height:var(--tap);padding:11px 0;border-bottom:1px solid var(--border)}\n.box{flex:none;width:20px;height:20px;margin-top:3px;border:2px solid var(--accent-text);border-radius:5px}\nul.cards{list-style:none;margin:0;padding:0}\nul.cards li{background:var(--surface);border:1px solid var(--border);border-left:3px solid var(--accent-text);\nborder-radius:var(--r);padding:14px 16px;margin-bottom:10px}\n.kv{display:grid;grid-template-columns:repeat(auto-fit,minmax(200px,1fr));gap:22px;margin:26px 0 8px}\n.salary{margin:26px 0 0}\ntable{width:100%;border-collapse:collapse;font-size:.95rem;margin-top:8px}\nth{text-align:left;font-size:.8rem;text-transform:uppercase;letter-spacing:.08em;color:var(--muted);\nfont-weight:700;padding:0 10px 10px 0;border-bottom:1px solid var(--border)}\ntd{padding:12px 10px 12px 0;border-bottom:1px solid var(--border);vertical-align:top}\nth.n,td.n{text-align:right;padding-right:0;font-variant-numeric:tabular-nums;white-space:nowrap}\ntfoot td{border-bottom:0;padding:6px 10px 6px 0;color:var(--muted)}\ntfoot tr.total td{color:var(--text);font-weight:700;font-size:1.12rem;border-top:2px solid var(--accent-text);padding-top:14px}\n.org ul{list-style:none;margin:0;padding-left:28px;border-left:1px solid var(--border)}\n.org>ul{padding-left:0;border-left:0}\n.node{display:inline-flex;flex-direction:column;justify-content:center;min-height:var(--tap);\nbackground:var(--surface);border:1px solid var(--border);border-left:3px solid var(--accent-text);\nborder-radius:var(--r);padding:10px 16px;margin:7px 0}\n.node b{font-size:1rem;line-height:1.35}\n.node span{color:var(--muted);font-size:.88rem}\n.obj{display:grid;grid-template-columns:3rem 1fr;gap:14px;margin-bottom:26px}\n.obj h2{margin:0}\nul.krs{list-style:none;margin:14px 0 0;padding:0}\nul.krs li{border-left:2px solid var(--border);padding:0 0 0 14px;margin-bottom:14px}\n.notice{border:1px solid var(--accent-text);background:var(--soft);border-radius:var(--r);\npadding:14px 18px;margin:28px 0 0;font-size:.92rem;color:var(--text);max-width:none}\n.notice b{display:block;color:var(--accent-text);margin-bottom:4px;font-size:.82rem;\ntext-transform:uppercase;letter-spacing:.08em}\n.todo{display:inline-block;background:var(--soft);color:var(--soft-ink);border:1px dashed var(--accent-text);\nborder-radius:6px;padding:2px 9px;font-size:.88rem;font-weight:700}\n.signoff{margin-top:38px;color:var(--muted);font-size:.92rem}\n.rule{display:inline-block;width:220px;border-bottom:1px solid var(--border);margin-top:26px}\n@media print{body{padding:0}.doc{max-width:none}}\n</style></head><body><main class=\"doc\">\n<p class=\"doctype\">Standard operating procedure</p><h1>New Engineer First-Week Onboarding SOP</h1><p class=\"sub\">Following this procedure guarantees that a new engineer has secure access, clear social integration, a verified first contribution, and a structured feedback loop within five business days.</p><div class=\"meta\"><span><b>Owner</b> Engineering Manager</span><span><b>Trigger</b> Offer letter signed and start date confirmed</span><span><b>Review</b> This SOP is reviewed annually by the Head of Engineering and HR Business Partner to ensure alignment with current tools and team structure.</span></div>\n<p class=\"lede\">Applies to all newly hired software engineers from the moment the offer is accepted until the end of the first week. Does not apply to contractors or interns unless explicitly specified in their contract.</p>\n<h2>Procedure</h2>\n<ol class=\"steps\"><li class=\"step\">\n <div class=\"num\">1</div>\n <div>\n <div class=\"act\">Create and distribute login credentials for all required systems (GitHub, Jira, Slack, CI/CD, cloud console)</div>\n <div class=\"tags\"><span class=\"chip\">IT Operations</span><span class=\"chip alt\">Identity Management System</span></div>\n <div class=\"done\"><b>Done when</b> The new engineer successfully logs into GitHub and Jira using the provided credentials</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">2</div>\n <div>\n <div class=\"act\">Assign a buddy and schedule a 30-minute introductory coffee chat</div>\n <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Calendar System</span></div>\n <div class=\"done\"><b>Done when</b> The calendar invite for the buddy introduction is sent and accepted by both parties</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">3</div>\n <div>\n <div class=\"act\">Provide the new engineer with a 'Hello World' or low-risk bug fix task and explain the local development setup</div>\n <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">Local Development Environment</span></div>\n <div class=\"done\"><b>Done when</b> The new engineer has the codebase cloned locally and the application runs successfully on their machine</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">4</div>\n <div>\n <div class=\"act\">Guide the new engineer through creating a pull request and merging their first commit</div>\n <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">GitHub/GitLab</span></div>\n <div class=\"done\"><b>Done when</b> The pull request is merged into the main branch and the CI pipeline passes green</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">5</div>\n <div>\n <div class=\"act\">Conduct a 15-minute check-in to review access, setup, and the first commit experience</div>\n <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Video Conferencing Tool</span></div>\n <div class=\"done\"><b>Done when</b> The meeting takes place and any immediate blockers are documented in the ticketing system</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">6</div>\n <div>\n <div class=\"act\">Schedule a 30-minute structured checkpoint meeting for the end of day 5</div>\n <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Calendar System</span></div>\n <div class=\"done\"><b>Done when</b> The meeting is scheduled on the calendar with the agenda shared with the new engineer</div>\n </div>\n</li><li class=\"step\">\n <div class=\"num\">7</div>\n <div>\n <div class=\"act\">Review progress against the first-week checklist and address any outstanding blockers or questions</div>\n <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Project Management Tool</span></div>\n <div class=\"done\"><b>Done when</b> The checklist is marked as complete and any open issues are assigned to owners with due dates</div>\n </div>\n</li></ol>\n<h2>If something goes wrong</h2><ul class=\"plain\"><li>I</li><li>If</li></ul>\n\n</main></body></html>",
"opsDoc": {
"title": "New Engineer First-Week Onboarding SOP",
"purpose": "Following this procedure guarantees that a new engineer has secure access, clear social integration, a verified first contribution, and a structured feedback loop within five business days.",
"scope": "Applies to all newly hired software engineers from the moment the offer is accepted until the end of the first week. Does not apply to contractors or interns unless explicitly specified in their contract.",
"owner": "Engineering Manager",
"trigger": "Offer letter signed and start date confirmed",
"steps": [
{
"action": "Create and distribute login credentials for all required systems (GitHub, Jira, Slack, CI/CD, cloud console)",
"owner": "IT Operations",
"doneWhen": "The new engineer successfully logs into GitHub and Jira using the provided credentials",
"tool": "Identity Management System"
},
{
"action": "Assign a buddy and schedule a 30-minute introductory coffee chat",
"owner": "Engineering Manager",
"doneWhen": "The calendar invite for the buddy introduction is sent and accepted by both parties",
"tool": "Calendar System"
},
{
"action": "Provide the new engineer with a 'Hello World' or low-risk bug fix task and explain the local development setup",
"owner": "Buddy",
"doneWhen": "The new engineer has the codebase cloned locally and the application runs successfully on their machine",
"tool": "Local Development Environment"
},
{
"action": "Guide the new engineer through creating a pull request and merging their first commit",
"owner": "Buddy",
"doneWhen": "The pull request is merged into the main branch and the CI pipeline passes green",
"tool": "GitHub/GitLab"
},
{
"action": "Conduct a 15-minute check-in to review access, setup, and the first commit experience",
"owner": "Engineering Manager",
"doneWhen": "The meeting takes place and any immediate blockers are documented in the ticketing system",
"tool": "Video Conferencing Tool"
},
{
"action": "Schedule a 30-minute structured checkpoint meeting for the end of day 5",
"owner": "Engineering Manager",
"doneWhen": "The meeting is scheduled on the calendar with the agenda shared with the new engineer",
"tool": "Calendar System"
},
{
"action": "Review progress against the first-week checklist and address any outstanding blockers or questions",
"owner": "Engineering Manager",
"doneWhen": "The checklist is marked as complete and any open issues are assigned to owners with due dates",
"tool": "Project Management Tool"
}
],
"exceptions": [
"If access credentials fail to work, escalate immediately to IT Operations with a ticket priority of High",
"If the assigned buddy is unavailable, the Engineering Manager must temporarily assume the buddy role or assign an alternative senior engineer",
"If the first commit fails due to environment issues, pause the timeline and resolve the technical blocker before proceeding to the checkpoint"
],
"review": "This SOP is reviewed annually by the Head of Engineering and HR Business Partner to ensure alignment with current tools and team structure."
},
"opsDocVariant": "sop",
"opsDocTitle": "New Engineer First-Week Onboarding SOP"
},
"finishedAt": 1788776403269,
"llmCalls": [
{
"upstream": "http://127.0.0.1:8080",
"modelRequested": "txt2txt",
"temperature": 0.35,
"maxTokens": 2800,
"timeoutMs": 240000,
"startedAt": 1788776318400,
"finishedAt": 1788776403265,
"ok": true,
"promptChars": 1960,
"responseChars": 3299,
"modelServed": "/nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF"
}
]
}
},
"startedAt": 1788776318396,
"fingerprint": {
"ownAiUrl": "http://127.0.0.1:8080",
"harnessHost": "127.0.0.1",
"modelServed": "qwen-image",
"nodeVersion": "v24.18.1",
"capturedAt": 1788776318396
},
"finishedAt": 1788776403272,
"scores": {
"perStep": {
"s1-q67jx": {
"validity": 0,
"fidelity": 0,
"structure": 0,
"depth": 0,
"cleanliness": 0,
"total": 0,
"notes": [
"unknown kind"
]
}
},
"total": 0,
"perKind": {
"ops-doc": 0
},
"axes": [
"validity",
"fidelity",
"structure",
"depth",
"cleanliness"
]
}
}