Newsletter, free, every Tuesday
The Mobile Career Brief
Staff mobile engineer · 500+ technical interviews from the hiring side.
One career fix for mobile engineers, from the hiring side, every Tuesday. Under 5 minutes.
You might not be behind. You might just be unreadable.Feeling behind after years at one company? Sort what job posts ask for into knowledge, experience and evidence gaps, then check the evidence gap in your CV with the Free ATS CV scan.Your interview went well. You still got rejected.Why answering technical questions correctly may still leave a hiring team unconvinced, and how iOS and Android engineers can prepare for the follow-ups that test their engineering judgment.Before you apply, check the roleA practical way to decide whether a job is worth applying to before you spend time tailoring your CV or application.Four lines in a job post you should never skipMost of a job post is the company describing itself. Four lines are not: where you can legally work from, the real level, the one requirement that is not negotiable, and the work model at the bottom. Read those first, and ask the recruiter one question before you apply.I told people there was no Job. They sent me their CVs anyway.I posted a fake €125K mobile job, clearly said there was no vacancy, and people still sent CVs, commented “I’m interested” and tagged friends. This issue is about what that says about job search, why I work candidate-first, and why Career OS is not a spreadsheet of links. Part 2 is coming.You are fixing the wrong thing.Six different failures produce the same rejection email. Here is how to tell which one is yours.Five ordinary questions. Five decisions.A recruiter asks five ordinary questions. Each one is a decision about your level, your fit, your affordability and whether you are worth an hour of someone else's time. What they are assessing, and how to answer.The submission is no longer the evidenceA strong take-home can still expose weak ownership. Stop trying to detect AI and test whether the candidate can explain, challenge and change the work.The number is hiding in the shadowYour best work may look qualitative, but every real improvement casts a measurable shadow you can recover from the systems around it.You cannot proofread your own positioningWhy your strongest evidence stays invisible to you, and the ten second test that exposes it.The confident wrong answer costs more than I don't knowWhy calibrated uncertainty signals stronger engineering judgement than a confident mistake.Recruiters read the top of your profile. Your proof lives at the bottom.Reorder your strongest evidence so the first ten seconds earn the next ten.It depends is a senior answer, if you finish the sentenceSenior judgement starts with the constraints that make a technical choice defensible.The committee can only promote what it can readStaff-level impact only helps at calibration when the evidence survives outside the room.The compiler accepting your code is not evidence it is correctThe most important review question is what enforces every manual safety promise.Make one claim the room can repeatA hiring panel remembers a candidate as a sentence. If the sentence is unclear, strong evidence turns into a vague impression.Fix the two lowest, ignore the restRaising a four out of five to a five changes nothing about the verdict. The twos are what decide it.Nobody is coming to notice youIn a large company, good work is not self-announcing. Being legible is a separate skill from being good.The least prepared conversation is the most expensive oneMonths preparing for the technical rounds, ten improvised minutes on the number that anchors the next five years.Staff is a change of scope, not a change of seniorityBeing very good at senior work for longer does not make you staff. It makes you a senior engineer with more years.Coverage measures lines executed, not risk retiredA number that goes up while the thing it measures stays the same is worse than no number.Hard to test means the design is wrongTesting is a design conversation wearing a testing costume, and the answer that scores says so.A device can propose. Only the server can ratifyEvery value your client computes locally is implicitly a claim about authority.Last-write-wins is a policy, chosen by defaultThe worst incident I know of had no bug in it. The code did exactly what it was designed to do.A retry is a second write until you prove otherwiseRetrying a failed request feels harmless. Without an idempotency rule, it can repeat the action that already succeeded.One bullet, rewrittenThe difference between a task and a decision, demonstrated on a single line.Take the thing nobody ownsEvery organisation has a system with no maintainer. That is the fastest available route to staff scope.The smallest thing on your CV that nobody thinks aboutThe filename is read by a person who has never met you, in a folder with two hundred others.Your CV has two readers and only one forgives youThe first reader is a parser. Whatever it fails to extract does not exist for the next step.The summary survives, the evidence evaporatesTwo engineers with identical experience. One has a record, one has a memory, and they get levelled differently.They are asking why, and you are answering whatThe question type that separates senior candidates, and almost nobody prepares for it.Ask what the round isMost candidates prepare for the wrong interview, and the reason is that nobody tells them which one they are getting.The level you get offered is the level you sounded likeInterviewers answer two questions, and most candidates only prepare for the first.Silence and confusion look identical from the other chairA pause feels like thinking from inside your head, but the interviewer cannot distinguish it from confusion or not knowing what to do next.The follow-up decides the round, not the answerMost preparation optimises for the first thirty seconds of a question. The round is decided in the sixty seconds after.
