Skip to content

A free guide

Why you didn't get the offer

Seven reasons I saw from the hiring side, and nobody tells you any of them.

Rejection emails are written to tell you nothing. But there is a document with your name on it, containing the specific reason, written by people who watched you for an hour. You never see it.

This is what is usually in it. 34 pages, free.

Delivered instantly, and you can download it on the next page. You will also get the Tuesday Brief, one specific career fix each week. Unsubscribe anytime.

Cover of Why you didn't get the offer

What is inside

Seven reasons. Fourteen days. Real output.

Each reason includes what it cost me before I understood it, what it looks like from the other side of the table, the common mistake, and an exercise with a deadline and a real output.

  1. 01

    Your CV was read by software first

    It lost the argument with a parser before a human opened it.

    Days 1 to 2.
  2. 02

    You were invisible before anyone evaluated your code

    The filter that decides whether you are worth an hour measures legibility, not ability.

    Days 3 to 4.
  3. 03

    Your answer was correct and your reasoning was invisible

    The interview does not start when they ask the question. It starts when they challenge your answer.

    Days 5 to 6.
  4. 04

    You went quiet instead of thinking out loud

    From the interviewer's chair, silence and confusion look identical.

    Days 7 to 8.
  5. 05

    You described responsibilities because you never kept the evidence

    The summary survives. The evidence evaporates.

    Days 9 to 10.
  6. 06

    You sounded one level below the role

    Level is measured by the size of the thing you talk about owning.

    Days 11 to 12.
  7. 07

    You got the offer and left money on the table

    The least prepared conversation in the entire process is the most expensive one.

    Days 13 to 14.

Who this is for

For the engineers who need a reason, not another pep talk.

iOS, Android, React Native and Flutter engineers who are interviewing, or about to be.

Engineers who have been applying for months and getting silence rather than rejections.

Anyone who has read a rejection email and had to guess at the reason.

Not for you if you want encouragement. The guide tells you what is weak, because that is the only version worth reading.

Why trust this

I have watched the decision get made.

Fifteen years building production mobile software. More than five hundred technical interviews conducted from the hiring side: screening calls, technical rounds, live coding, system design, debriefs.

That is the only credential that matters here. Not that I am a good engineer, which you cannot verify, but that I have spent years watching the decision get made and writing the document you never see.

Get the guide

Start with the reason.

Delivered instantly, and you can download it on the next page. You will also get the Tuesday Brief, one specific career fix each week. Unsubscribe anytime.

34 pages. Fourteen exercises. No cost.