Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
What a 30-60-90 plan is actually for, and how vague ones fail
Turning a job description into three checkable technical goals
First day accounts, access, and why access is the critical path
First week: environment setup and running the system locally
Reading an unfamiliar repository and its architecture
The first change: a small real ticket from branch to production
Testing and CI setup, and getting to a green pipeline
Code review, team norms and communication channels
The deploy process and understanding where the code goes
The on-call shadow and what to actually do in it
Your first incident and the mistake most new joiners make
Security and compliance training, and why it blocks real work
The 30 day checkpoint and what good actually looks like
The 60 day checkpoint and taking ownership of a component
The 90 day assessment and the probation review conversation
The buddy or mentor arrangement and what makes it work
The stakeholder map and who actually decides
A ramp-up plan for a new team, written from the manager side
Remote and distributed onboarding, and the extra work it creates
International relocation, work authorisation and start-date problems
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
A 30-60-90 plan is an agreement about outcomes at three dates, so every line has to be true or false by the end of that block rather than merely attempted.
A technical goal is falsifiable when a competent stranger could look at the system in sixty days and say yes or no without asking the author.
Access is the critical path, because a pending request quietly blocks reading, running, testing and shipping at the same time.
A setup guide is usable only if a stranger can follow it without asking anyone, which is the test to apply before the next joiner arrives.
Start from an entry point rather than the tree: the request handler, the command entry, the job entry and the scheduled task are where a system actually begins.
A good first ticket is real, small, and has a named requester, because a ticket with no requester gives no feedback and no sense of consequence.
Questions this pack covers
What problem does a written first ninety day plan actually solve?
Which parts of a ninety day plan are boilerplate and should be cut?
How do you turn a job description into three technical goals?
What makes a technical goal falsifiable rather than aspirational?
Which accounts must exist before a new joiner can be useful?
How do you order access requests when approvals take a week?
How do you get a repository running locally within the first week?
What should a setup guide contain to be usable by a stranger?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
