A practical playbook for running a job hunt that produces interviews — and for turning those interviews into offers.
Applications convert at roughly the same rate as any sales funnel: a small percentage of well-targeted approaches lead to conversations, and a fraction of those to offers. Decide up front how many roles you will approach each week — eight strong, tailored applications beat forty copy-pasted ones — and track every one with its status and follow-up date. When you can see the pipeline, a rejection is a data point instead of a verdict.
Write down the three role titles you are actually going after, the industries you would accept, your salary floor and your non-negotiables on location and working pattern. Everything else — the CV wording, the portfolio, the way you introduce yourself — becomes easier once this is fixed. Vague searches produce vague documents, and vague documents lose to specific ones.
A job advert is a checklist that someone will literally tick. Mark the requirements that appear in the first third of the text: those carry the most weight. Note the exact vocabulary used, because the screening system matches strings, not synonyms. If the ad says “stakeholder management” and your CV says “worked with clients”, you score zero on that line even though you have done the work.
Applications submitted in the first 72 hours of a posting are reviewed while the shortlist is still open. Where possible, find the hiring manager or a team member on LinkedIn and send a short, specific note — three sentences: who you are, the one result that matches their problem, and a question about the role. Referrals and direct approaches convert several times better than portal submissions alone.
Build a bank of eight to ten stories from your career, each written in the STAR shape: Situation, Task, Action, Result — with a number in the result. Most interview questions are variations on the same themes: a conflict, a failure, a deadline, a decision with incomplete information, a time you influenced without authority, a technical problem you solved. Rehearse them out loud until each takes ninety seconds.
Before the interview, read the company's last annual or quarterly report, its recent product announcements, and the LinkedIn profiles of the people you will meet. Prepare three questions that could only be asked by someone who did that reading. Candidates are remembered for the quality of their questions far more often than for the polish of their answers.
Know the market range for the role in that city before the first call, and give a range rather than a single figure when asked, anchoring slightly above your target. If the number comes up too early, it is entirely acceptable to say you would like to understand the scope of the role first. Never invent a competing offer — verify-ability matters more than leverage.
Send a short thank-you note within 24 hours that references one specific thing discussed and restates the single reason you fit. If you are rejected, reply graciously and ask for one line of feedback; roughly a third of interviewers answer, and that line is worth more than another ten applications. Keep the contact — many hires come from the second role a company opens, not the first.