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:
The first ninety days and the expectations nobody told you about
Working hard versus working well
Asking for help without burning your credibility
Code review as a two-way conversation
Why estimates are always wrong, and what to do about it
Saying no and negotiating what you take on
The deadline you cannot make
Documentation as a career skill, not a chore
Quality versus delivery speed, and how to decide
Your first production incident
On-call reality and how to survive it
Your relationship with your manager
The performance review cycle and the self-assessment trap
The promotion conversation and what a ladder actually looks like
Changing team or company without resigning
Resigning well, and the counteroffer you should probably refuse
Telling burnout apart from ordinary difficulty
The impostor feeling and the one behaviour that helps
Remote work and the time zone tax
Is engineering still the right career for you
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
Ramp-up is a curve rather than a switch, so a manager expecting full speed in week one has misunderstood onboarding rather than found a weak hire.
Hours are the easiest thing to count and the least correlated with output, so a team that reviews effort is reviewing the wrong variable.
A good question names what you tried, what you expected and what happened, because without those three a senior engineer has to reconstruct your work before answering it.
A review comment is a claim about the change rather than about you, and separating those two things is most of the skill required to take feedback well.
The systematic bias runs the same way in both directions: teams underestimate what is known and overestimate what is familiar, so the error is predictable and therefore negotiable.
A yes without a stated trade is a silent promise, and the trade surfaces later as a missed date or a lower quality result that you will be asked to explain.
Questions this pack covers
What should you actually do in your first week at an engineering job?
Why does the first month feel slower than the work actually deserves?
How do you tell working hard from working well as a new engineer?
Why does staying late at the office often mean the work was badly chosen?
How do you ask a question that actually gets answered?
What should you try before you ask anybody for help?
How do you read a review comment without taking it personally?
What should you fix before pushing a change for review again?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
