Engineering onboarding

Welcome. Your first two weeks, in order. Your buddy goes through this with you; tick things off in your onboarding issue in Jira.

Day one

• Laptop, Google Workspace account and Slack (#eng, #ops, #support, #releases).
• GitHub: ask Lukas to add you to our three repositories (Emargen/acme-identity-service, acme-portal, acme-notifier). Turn on two-factor first.
• Jira and Confluence.
• AWS SSO, read-only. Write access comes per change, through an OPS ticket.
• Emargen: Lukas asks Ana for your seat. Make a personal token only when you start building with an agent: Claude Code and Codex with personal tokens.
• The security induction with Mira (one hour): data regions, support access, what never goes in logs.

Read in the first week

1. Architecture overview, then the page for the system you'll work on.
2. Roles and approvals and Single sign-on: what customers actually do with us.
3. How we use Emargen.
4. Coding standards and Release process.
5. Glossary. We say depot, approver, access request, client (in code) and customer (in words).

Set up

Local development and the SAML test IdP. If a step is wrong, fix the page.

First task

Your buddy picks a small task with you: an ENG bug or a task on a slice in Emargen. Aim to have a merge request reviewed and released in your first week.

On-call

Shadow two on-call weeks, then join the rota as primary. Read the runbooks during your first shadow week.

Meet

Rafael (CTO), Lukas, Oskar (production), Mira (security), Hanna (QA), and one person from customer success and one from support. Ask Ana and Ines who has a customer call you can listen to.

Change history

Version	Date	Who	What
10	1 Jun 2026	Lukas	Summer joiners; Emargen seat
11	15 Jun 2026	Oskar	On-call shadowing
12	7 Sep 2026	Lukas	For Jonas: personal tokens, local setup link