Day-1 Checklist
Day 1 has one goal: the new hire runs the project locally, gets a green build, and opens one tiny PR. Everything below serves that.
flowchart TD A["Identity created<br/>email + SSO"] --> B["Azure DevOps access<br/>org + project + team"] B --> C["Repos cloned<br/>read/write on assigned repo"] C --> D["Dev environment<br/>per track"] D --> E["Linter + build green<br/>local run passes"] E --> F["Buddy assigned<br/>first small task opened"] F --> G["First PR<br/>tiny change, squash-merged"]
The checklist
Section titled “The checklist”| Step | What | Owner |
|---|---|---|
| Identity | Company email, SSO, MFA | Nidal Mohammad |
| Azure DevOps | Add to org, project, team; Boards + Repos + Pipelines access | Firas Alhawasli |
| Repos | Clone assigned repo; confirm read/write; read the repo AGENTS.md and ADRs |
Team lead |
| Dev environment | Set up per track (below) | Buddy |
| Coding standards | The linter is the standard — run it locally, it must pass in CI | Team lead |
| Buddy | Named buddy for the first 2 weeks | Team lead |
| First task | One tiny, real work item with a linked branch | Team lead |
See Tools & Access for how to request each account and where secrets live, and the Org Chart for who everyone above is.
Dev environment per track
Section titled “Dev environment per track”- Backend (.NET): SDK, local DB/containers, secrets from Key Vault (never committed), run the API + tests.
- Frontend (Angular + PrimeNG): Node LTS,
npm ci, run the app against a dev API, lint passes. - Mobile (native Android + iOS): platform SDK/toolchain, run the app on a simulator/emulator against dev.
- QA: test-plan access in Azure DevOps, access to
qa/uat, the bug-report template.
First PR
Section titled “First PR”Pick something real but tiny: a copy fix, a small test, a lint cleanup. Follow Branching & PRs — short-lived branch, one PR, squash-merge, delete. Shipping on day 1 proves the whole pipeline works for the new hire.
Next: 30 / 60 / 90.