Career strategy
Two pieces of writing decide your offer, and you write one of them
After the loop, interviewers write notes and meet to decide your level. After the offer, your one written reply sets what you accept. How to feed the first and write the second.
By Mike Salari. Staff mobile engineer · 500+ technical interviews from the hiring side.
6 min read
Audio is currently recording.
After your last interview round, a decision gets made in a room you are not in.
At companies that run a structured loop, each interviewer writes up a score and the evidence for it. Then they meet. Some companies call it a debrief, some a hiring committee. The exact system varies, but the task is the same: turn what people saw into a hire or no-hire, and a level. The level sets the pay band before a recruiter says a number to you. What reaches you is the output, an offer or a template rejection.
I have run 500+ technical interviews from the hiring side of that table. I have written the notes afterwards and sat in the debrief where those notes became a decision.
Two pieces of writing shape what you are paid: the notes written about you, and the reply you write when the offer arrives. You cannot write the first. You can decide a great deal of what goes into it. The second is entirely yours.
What happens in the debrief
A good interviewer does not trust a gut feeling. They score you against a rubric with named dimensions, write down evidence, and then defend it against the other interviewers.
The notes are short. I am filling each dimension with a rating and one line of evidence. An empty box reads as weak. If you go silent, I have nothing to write.
In the room, each interviewer presents a score and the evidence behind it. A specific piece of evidence wins an argument. A vague impression loses one. One brilliant round and three confusing ones reads as a risk. Four clear rounds reads as a safe hire.
The room also decides a level, not only a yes or no. If it concludes senior and you were aiming at staff, good negotiation can move the package inside the senior band. It rarely turns the panel's evidence into a different level. A forceful counter cannot repair a weak debrief.
What feeds the notes
So the job in every round is to leave the interviewer a sentence they can repeat.
A good answer compresses without losing its value. It holds the constraint, the decision and the reason: she chose a local source of truth because writes must survive connectivity loss, then defined reconciliation. State the constraint before the choice. Name your own action instead of hiding inside "we". Close with the result and what changed. The interviewer can then write a faithful receipt instead of rebuilding one from memory.
Before the final round, write the one sentence you want the debrief to retain. Then support it with different evidence in each relevant round.
Do not claim what you cannot defend. A confident bluff that I catch can sink an otherwise strong candidate by itself, because I stop trusting the true parts too. "I'm not sure, here is how I would find out" helps you. I write it down as a strength.
What the CV hands the room
The notes start earlier than the interview. The first scan of a CV takes seconds. It is a decision about whether an engineering assessment should use anyone's time.
The CV also chooses the interview. A skills list produces questions about knowledge. A claim of ownership produces questions about judgement. Whatever you put first is what gets tested.
A senior Android engineer bought my CV audit. On paper, he was the kind of engineer companies say they cannot find. He was getting no recruiter responses.
His CV did not name the products he had shipped. His headline claimed a technology his experience never mentioned. His most valuable specialisation, payments, sat in a skills list between Google Maps and MATLAB. His LinkedIn ended by asking for an opportunity to grow.
None of that was a skills problem. Every fix was mechanical: name the products, attach the numbers, lead with the specialisation, delete the claims he could not defend. He applied the whole rebuild within two days of reading it.
Read your own CV the way two readers do. A recruiter asks whether you can be placed. A hiring manager asks which claim to test. If a stranger cannot tell in seconds what you own and at what scale, the interview you get will be built on guesses. Write down your five strongest claims and the evidence for each before you interview.
The second piece of writing: your reply to the offer
Suppose the notes go your way and an offer lands. The number is a starting position. Companies expect a counter and build a band into the offer. I have sat in the rooms where offers get approved, and a polite counter backed by data is treated as normal. What leaves an impression is how you do it.
Two replies cost people money. One is accepting at once out of relief. The other is reacting to the number on the spot. My book Leverage opens its script with the opposite move: do not react to the number.
First, thank them, say you are excited, and ask for the full offer in writing: base, bonus, equity, sign-on, relocation and level. Ask for a couple of days.
Second, do the preparation before you write. Find three comparable data points for your level, company and city. Decide your target and your walk-away floor. Confirm the level and what the role owns, because level and scope come before money. A staff title on a senior band is a downlevel in a costume.
Third, send one written counter. The order is enthusiasm, then data, then specific numbers, then a commitment. Ask for the whole package, not only base. If base is capped, ask about sign-on, equity or level. The shape from my iOS Engineer Playbook looks like this:
"I'm excited and want to make this work. Based on my research at this level, I would like to ask for a base closer to $[target] and a sign-on of $[amount] to bridge the equity I am leaving. If we can get there, I am ready to sign this week."
Make one clear ask and stop. Do not name a number first when someone asks for your expectations before an offer. Ask about the role, the level and the range budgeted for it.
Use a competing offer only if you hold one. Never bluff. The recruiter may ask you to forward it, and with nothing to forward your position ends in one message.
Know when to close. The first counter is rarely the last, and one more calm round often finds a little more. A fourth and fifth round chasing a token amount spends the goodwill you need for your first year. When the number is right, ask for the updated offer, and get the final package in writing before you resign anywhere. A verbal offer is not binding.
How much can this move? Leverage puts a typical negotiation at 5% to 25%, and labels that medium confidence. It is a pattern, not a promise.
Decide both before they are tested
Both pieces of writing get made whether you prepare or not. The notes are built from what you hand each interviewer. The final number is shaped by what your first reply hands the recruiter.
Before the loop, decide the one sentence you want the debrief to keep, and make your CV carry the same claim. Before the offer, decide your target, your floor and your one ask. Do both in advance, while nothing is at stake.
If you want help with the first, Engineer Career Rebuild tests your target, then rebuilds your CV and LinkedIn around it. It includes a committee report on how a hiring panel would read you. It is written work, and you apply yourself.
For the second, the scripts and the worked offer are in Leverage.
I do this work one engineer at a time in Engineer Career Rebuild: your target first, then the CV, LinkedIn and search around it.
