Job Hunting After Redundancy: Running the Campaign

What it is

Redundancy produces two separate problems and most advice only addresses the smaller one. The smaller problem is how you explain it in a room: what you say when an interviewer asks why you left, how you talk about a gap, how you avoid sounding either bitter or evasive. That problem is real, it is solvable in about an hour of preparation, and it is not this page. The larger problem is that you now have to run a months-long project with no manager, no colleagues, no deadline anybody else cares about, and a bank balance that is going in one direction. Almost nobody has ever run that project before, and the ones who have run it badly.

This page is about the campaign. Not the CV line, not the interview answer, but the thing that produces the interviews in the first place: how you decide where to aim, how many applications to send and how targeted they should be, what a week of searching should contain hour by hour, how you get a network you have not touched in three years to be useful without feeling like a hustler, how you keep yourself interview-sharp with no daily work to draw on, how you negotiate from what feels like a position of nothing, and how you tell the difference between a hard market and a wrong plan.

The framing that helps most is that this is a campaign with a burn rate and a pipeline, not a period of waiting punctuated by applications. A campaign has a budget you can count, a shape you chose deliberately, activities allocated against that shape, and a review cadence that tells you whether the shape was right. A period of waiting has none of those, which is why it feels the way it does. Almost everything that makes a long search miserable comes from running it as the second thing while telling yourself it is the first.

The loop looks like this, and the branch is the part that matters.

flowchart TD
  accDescr: The search loop from agreeing runway and target, through building the pipeline, applying and networking, and interviews and screens, to a weekly review, which sends you back to applying while the pipeline is moving but, when you are stuck at one stage, changes targeting or materials and resets the plan.
  RUN[Runway and target agreed] --> PIPE[Pipeline built]
  PIPE --> ACT[Apply and network]
  ACT --> INT[Interviews and screens]
  INT --> REV{Weekly review}
  REV -->|pipeline moving| ACT
  REV -->|stuck at one stage| ADJ[Change targeting or materials]
  ADJ --> RUN

Look at the edge from the weekly review back to the top rather than back to the activity. Most people loop forever between applying and reviewing, doing more of the same thing harder, because the review only ever asks "did I do enough this week". The review that changes outcomes asks a different question, which is whether the evidence from the last three weeks says the plan itself is wrong, and if it does, the loop has to go all the way back to runway and target rather than to another Tuesday of applications.

What redundancy changes about a search that a voluntary move does not

It is worth being precise about this, because the differences are the reasons the standard job-search advice, which is written for the employed candidate, misfires.

You have a clock. An employed candidate can wait eight months for the right role because the cost of waiting is boredom. You are spending savings, and the spend is the single input that constrains every other decision on this page. This is not a psychological point, it is an arithmetic one, and treating it as a feeling rather than a number is the first mistake.

You have time, which is a genuine asset and is almost never used. Forty hours a week is a large budget. Most people out of work spend it worse than they spent their working week, because the working week had structure imposed on it and this one does not.

You have less positional leverage in a negotiation, or more precisely you believe you do, which turns out to be almost the same thing and is addressed at length below. This is where redundant candidates lose the most money in the entire process, more than they lose from a slightly slower search.

You have a story to tell that you did not choose, and you will tell it forty times. How to tell it well is genuinely a separate discipline and is covered end to end in career gaps, layoffs and short tenures, along with explaining an employment gap or short tenure and was leaving your last role your decision. Read those once, get the answer to a settled state, and then stop thinking about it, because the answer is a five-minute problem and the campaign is a five-month one.

And you have an emotional load that degrades your judgement in specific, predictable ways: it makes you apply too broadly, accept too quickly, negotiate too little, and interpret ordinary market noise as information about your worth. Naming those four distortions in advance is most of the defence against them.

The three phases, and how long each should take

A campaign has a shape over time even though it does not feel like it from inside.

The setup phase runs roughly one to two weeks and produces four things: a runway number in weeks, a target definition specific enough to reject roles against, a small set of materials that will not need rewriting every time, and a list of people to contact. It produces no applications, or very few, and the discipline to hold that is the subject of the next section.

The running phase is the long middle. It is a repeating week with a fixed shape, a pipeline you can see, and a review every Friday. Most of the campaign is this, and the skill in it is consistency rather than intensity.

The adjustment points are not a phase but they are scheduled. Roughly every three to four weeks, and at any point where the runway crosses a threshold, you stop and ask whether the target is still right. The evidence for that question accumulates in the weekly reviews, which is the whole reason to run them.

Why we need it

The case for structure is not that structure is virtuous. It is that an unstructured search produces worse outcomes and feels considerably worse while producing them, and the two are connected.

Start with the outcome. An unstructured search allocates effort by mood: you do the thing that feels tolerable today. Applications feel productive and are mostly not, because the marginal application to a role you are a moderate fit for has a low chance of anything and costs an hour. Network conversations feel exposing and are the highest-yield hour in the week. Preparation feels premature until you have an interview and then feels rushed. Left to mood, almost everybody over-invests in the low-yield activity and under-invests in the high-yield one, and then concludes after two months that the market is impossible. The market may well be impossible. You will not be able to tell, because you did not run the experiment properly.

Then the feeling, which matters more than advice pages usually admit. The distinctive misery of unemployment is not the money, at least not in the first months. It is the loss of a structure that used to answer, every day, the question of whether you had done enough. In a job that question is answered by other people and by the day ending. Out of work, nothing answers it, so it runs continuously and the answer is always no. You can spend eleven hours at a laptop and go to bed feeling you did nothing, because there was no definition of enough. A week with a shape supplies that definition. It is a slightly artificial one, and it works anyway.

There is a third argument, which is about evidence. A search that cannot be reviewed cannot be corrected. If you do not know how many applications went out, at what level of tailoring, to what kind of company, and where each one stopped, then when things are not working you have no way to tell whether the problem is your CV, your targeting, your interviews, or the market. You will guess, and the guess will be the most self-critical option available, which is almost never the right one. Structure exists so that after six weeks you have something to look at other than your own feelings.

Why the first fortnight is the highest-leverage part

Every decision later in the campaign is downstream of decisions made in the first two weeks, and those decisions are made worst because that is when you are least able to think.

The runway number determines the campaign shape, which determines the volume-versus-targeting ratio, which determines how you spend forty hours a week for the next several months. Get the runway wrong by a factor of two and you will run the wrong campaign for its entire duration. Most people do not compute it at all; they have a vague sense of "a few months", which is not a number and cannot be reasoned with.

The target definition determines what you apply to, and more importantly what you decline to apply to. Without one, the answer to "should I apply to this" is always yes, because there is no basis on which to say no. That is how people end up with four hundred applications and no interviews.

References are the one thing that decays with time and cannot be recovered later. Your manager remembers what you did this month. In seven months they will have had two reorganisations and a new team, and the reference will be warm but generic. Getting this agreed in week one is twenty minutes of work with a several-month expiry date on it.

And the pause is what makes the other three possible. There is no version of this where you do the thinking properly while also sending sixty applications, because sending applications is what you do instead of thinking.

The first fortnight

Work out the runway in weeks, not in a feeling

Do this on the first day you can face it, before anything else. It is arithmetic and it takes half an hour, and every decision on this page depends on the output.

You want a single number: how many weeks you can cover before something has to change. Build it from four inputs. Your accessible cash, meaning what you can reach without penalty, not your pension. Any redundancy payment, after tax and after any part of it that is already spoken for. Any benefits or state support you are entitled to and will actually claim, which many people do not investigate out of embarrassment and should. And your monthly outgoings at two levels: the number as things stand today, and the number after you cut what you would cut if things got tight.

Two numbers come out of that, and you need both. The comfortable runway is cash divided by current outgoings. The stretched runway is cash divided by reduced outgoings. The first is when the search stops being calm. The second is when it stops being possible. Most people know neither, and the gap between them is frequently three or four months of decision-making room they did not know they had.

Express both in weeks rather than months, because weeks are the unit the campaign runs in, and because "nineteen weeks" is a number you can plan against in a way that "about four or five months" is not. Then subtract a notice-and-onboarding tail: an offer accepted in week fourteen does not pay you in week fourteen. Between offer and first salary there is frequently a month, sometimes two. Take that off the front of your usable runway, because the deadline you are actually working to is the date you need an accepted offer, not the date you run out.

Write the number somewhere you will see it. Recompute it monthly, not weekly, because weekly recomputation is a form of anxiety rather than a form of planning.

Decide the target shape

A target is not a job title. It is a set of constraints tight enough that you can look at a posting and say no, and loose enough that more than a handful of things pass. Five dimensions are usually enough.

The role band. Not just "senior engineer" but where in the band, and whether you are willing to go a level down. Have that answer in advance rather than discovering it at the offer stage, because being offered a level below what you interviewed for is a decision that goes badly when it is made under pressure and reasonably when it was pre-decided.

The domain or sector. Where your experience compounds, and where it is merely transferable. These are different and the difference shows up in how hard the application is. A domain where you compound gets a tailored application; one where you are transferable needs a story about the transfer, which is more work per application and lower yield.

Company shape. Size, stage, whether it is a product company or a consultancy or in-house at a non-technology business. This matters more than most people weight it, because the same job title at a two-hundred-person product company and a thirty-thousand-person bank are different jobs with different hiring processes and different time-to-offer.

Non-negotiables. Location, remote arrangement, right to work, anything medical or caring that fixes your hours. Be honest about which are genuinely non-negotiable and which are strong preferences that would bend for the right offer, because a list of eleven non-negotiables is a list of preferences with a stern label. If your right to work is part of this, it belongs in the first conversation and not the fifth, for the reasons set out in visa sponsorship and right to work.

The floor. The lowest total package you would accept, computed rather than felt, and computed against the runway rather than against your last salary. This number is the single most useful thing you can decide while you are still calm, because the pressure to accept below it arrives exactly when you are least able to evaluate it.

Write the target down in five lines. It exists to be applied, and it will be applied roughly two hundred times.

Get references agreed while people still remember you

This is the cheapest high-value task in the whole campaign and the one most often deferred until it is expensive.

In the two weeks after a redundancy, the people you worked with are sympathetic, available, and still have your work in their heads. Six months later they are sympathetic, busy, and remember that you were good without remembering what you did. A reference given from memory of a specific project is a different instrument from a reference given from a general impression, and the difference is visible to whoever takes the call.

Ask three or four people, not one. A former line manager, a peer who saw you work closely, and if you can, somebody who was your internal customer, because the last of those speaks to impact in a way peers cannot. Ask directly and give them an easy out, because a reluctant reference is worse than no reference and you want the reluctance now rather than at the offer stage.

Hi Dan, you will have heard my role went in the restructure. Before everything scatters, could I ask you to be a reference for me? No rush and no obligation, and if you would rather not for any reason that is completely fine and I will not ask again.

If you are happy to, it would help enormously if you could jot down two or three lines while it is fresh about the migration work and how the platform handover went. I will send you the role details each time so you know what is being asked, and I will always check with you before giving your name out.

Two things in that message are deliberate. The explicit out means a yes is a real yes. And asking for two or three written lines now, rather than only for permission, converts a vague willingness into an artefact that survives the next six months. If they write it, you have it. If they do not, you have still got the permission.

Do the same thing with your own record while it is fresh. Write down, in a private document, the six or seven things you did in the last two years that you would tell a story about: what the situation was, what you specifically did, what changed, and the numbers if you have them. You will not remember the numbers in November. This is also the raw material for every behavioural round you will sit, and it makes preparing stories without sounding rehearsed considerably easier, because rehearsal sounds rehearsed mostly when the underlying memory is thin.

The case for a deliberate pause

Every instinct says apply on day one. Applying feels like control, and after a redundancy the shortage is of control rather than of activity. It is worth resisting for a week or two, and here is the case rather than the platitude.

Applications made in the first week are made with materials that have not been revised, a target that has not been defined, and a story that has not settled. They go to roles chosen by what appeared on a job board that morning rather than by fit. They are, in a fairly literal sense, spent inventory: the roles you most wanted are frequently the ones you applied to worst, because you applied to them before you were ready and you cannot apply again.

There is also a state-of-mind argument that does not require any therapeutic framing. Applications written in the first week after a redundancy carry the tone of the first week after a redundancy. Covering notes come out either defensive or over-eager, and both are legible. Two weeks later the same person writes a better note about the same role.

The pause is not a holiday and should not be sold to yourself as one. It is a fortnight of setup work: the runway arithmetic, the target definition, the references, the story document, the CV rewrite, the network list. That is genuinely two weeks of work. If it helps to have permission, the permission is that the setup fortnight is the highest-return work in the campaign and the applications you did not send in it were mostly going to be wasted.

There is one exception worth naming. If a specific role you have been watching for a year opens in your first week, apply to it. The rule is about the default, not about a rare good opportunity, and treating it as a rule you cannot break is its own kind of rigidity.

Volume against targeting

This is where campaigns are won or lost, and where the standard advice is right in a way that makes it useless.

The standard advice is that fifty tailored applications beat five hundred generic ones. It is true. Generic applications to roles you are a moderate fit for convert at close to nothing, and a hundred of them produce a hundred rejections, which costs you three weeks and a considerable amount of morale for no information. If somebody has to choose one of the two extremes, they should choose the tailored fifty.

But almost nobody is choosing between extremes, and the honest version of the advice has a variable in it. The right ratio of volume to targeting depends on your runway. A candidate with twelve weeks and a candidate with fifty weeks should not run the same campaign, and telling both of them to send fifty beautifully tailored applications is telling one of them to run out of money while polishing.

The logic is straightforward once it is stated. Tailoring raises the conversion rate per application and lowers the number of applications per week. Volume does the reverse. Which combination maximises your chance of an offer before your money runs out depends on how many weeks you have, because a high-conversion low-volume strategy needs time to produce enough attempts to be reliable, and a short runway does not have that time. A short runway therefore has to buy attempts, accepting a lower rate per attempt, because the alternative is a small number of high-quality attempts and no second chance if they miss.

The reverse case is just as real. A candidate with a long runway who sends volume is wasting the one thing they have. They can afford to wait for the roles they would be a strong fit for, prepare properly for each one, and let the network work slowly, because the network works slowly and produces the best roles.

Deciding the ratio

Here is a concrete way to do it rather than a principle to hold.

Read the columns together rather than picking a row and only reading the second column. The point of the short-runway row is not that low-quality applications are good; it is that with ten weeks you cannot run a strategy whose feedback loop is longer than your money, so you buy attempts and you take the interim work conversation seriously from week one rather than week eight.

Two adjustments to whichever row you land in. First, if your target market is small, meaning there are only twenty employers in your city who do the thing you do, volume is not available to you at any runway and the answer is targeting plus network plus a widened target. Volume is only a lever when there is enough to apply to. Second, "deep tailoring" does not mean rewriting your CV from scratch. It means a genuinely specific covering paragraph, the CV reordered so the relevant three years are at the top, and enough reading about the company to make the note non-interchangeable. That is thirty to forty minutes, not three hours, and people who think tailoring takes three hours are usually rewriting things that did not need rewriting.

The third adjustment is the one most people miss: the ratio should move as the runway shortens. A campaign that starts at twenty-eight weeks and is at eleven weeks in month four should have changed shape at some point, and the weekly review is where you notice that it has not.

What a week should actually contain

A search week with no shape defaults to about eleven real hours spread across seven days, with a permanent low-grade sense of not doing enough. A search week with a shape uses thirty to thirty-five and finishes on Friday. Here is a shape for a full-time search, to be scaled down honestly if you have caring responsibilities or interim work.

The proportions matter more than the totals. Notice that applications are under half the week even at the volume end, and that network conversations get a serious allocation despite being the activity people most avoid. Notice also that preparation is allocated in advance rather than only when an interview appears, because the alternative is three days of panic before every first round and no capacity to run two processes at once.

The last row is not padding. A search run at fifty hours a week for six weeks ends in a collapse, and the collapse costs more weeks than the extra hours bought. Thirty-five hours sustained for five months beats fifty hours sustained for six weeks followed by a fortnight of nothing.

Fix the shape to days rather than leaving it floating. Applications in the morning when you are sharpest, because a tailored covering note written at nine is meaningfully better than one written at four. Network conversations booked into fixed slots so that you are not deciding each day whether you feel up to one. Friday afternoon for the review, and then stop. A search that has no end to the day never has an end.

Treating the search as work

The pipeline

Keep a single sheet. It does not need to be a system and the people who build elaborate ones are usually avoiding applying. Columns that earn their place: company, role, date applied, route in (advert, recruiter, referral, direct approach), tailoring level, current stage, date of last movement, and the next action with a date.

Two of those do more work than the rest. Route in is the column that tells you, after six weeks, whether your applications or your network are producing your interviews. Almost everybody is surprised by this number, and it is the single most useful piece of evidence for reallocating your week. Date of last movement is what turns a pipeline into something you can act on: anything that has not moved in ten days needs either a chase or to be marked dead, and a pipeline with fourteen live-looking rows that are all silently dead is why people believe they have more in flight than they do.

Mark things dead. A pipeline that only ever grows is a comfort object rather than an instrument. A role that went quiet three weeks ago after one screen is not live, and continuing to count it means you are not applying to the thing that would replace it.

The weekly review

An hour on Friday, at the same time, with the sheet open. Five questions, answered in writing, because answering them in your head produces a mood rather than a record.

How many applications went out, and at what tailoring level. How many network conversations happened, not how many were intended. What moved forward, and what died. Where in the funnel things are dying: no response at all, rejection after a screen, rejection after a first round, rejection at final stage. And what one thing will be different next week.

That fourth question is the one that carries the page. The stage at which things die is the diagnostic, and it points at different problems: no responses points at targeting or CV; death after the recruiter screen points at how you are presenting the story or the salary conversation, which is where the recruiter screen and ATS screening and the recruiter call earn their reading; death after first rounds points at interview performance; death at final stage in a competitive market frequently points at nothing you did, which is a genuinely different situation and should be treated as one.

Write two lines. Not a journal. The record exists so that in week nine you can look at weeks three to eight and see a pattern rather than remembering the worst day of each of them.

Why unstructured searching feels worst

Because the working day used to contain its own verdict. You went in, things happened, you came home, and the question of whether you had done enough was settled by the day ending. Job searching contains no verdict. There is always another application you could have sent, another person you could have messaged, another hour you could have worked, and no point at which anybody says that is enough for today.

A defined week supplies the missing verdict. Twelve applications was the target, twelve went out, that is the week. It is artificial in the sense that you invented the number, and it works anyway, because the mechanism was always external and arbitrary and you are simply supplying it yourself now. This is the practical reason to write the week down rather than hold it in your head: a target you can move is not a target, and an unwritten target moves every evening.

The second mechanism is that structure converts an ambient fear into a bounded task. "I need a job" is not something you can do anything about at three in the afternoon. "Send the two applications and message Priya" is. The work is identical. The experience of it is not.

Reactivating a network you have not used

Most people have a network they have not touched in years and a strong reluctance to touch it now, because the first contact in three years being a request for help feels like exactly what it is. That instinct is right about the diagnosis and wrong about the conclusion. The answer is not to avoid the contact; it is to make the contact honest about its own timing, because what makes these messages feel grubby is the pretence.

The pretence is the fake warm-up. A message that opens with two paragraphs of how-are-you-and-the-family before arriving at the ask reads worse than one that arrives at the ask in the second sentence, because the recipient can see the structure and now knows the warmth was instrumental. People are considerably more tolerant of a direct ask than of a disguised one.

Three other things make this work. Be specific, because a vague request for help is work for the recipient and a specific one is a yes-or-no. Be small, because most people will do a ten-minute thing for a former colleague and will hesitate over an open-ended commitment. And give them a graceful exit, because the exit is what makes the yes real.

The message to somebody you last spoke to three years ago

Hi Rachel, this is out of the blue and it comes with an ask, so I will get to it.

My role at Meridian went in a restructure last month and I am looking for the next thing. You are one of the people whose judgement I trusted most at Kestrel, so I wanted to ask you two questions rather than the whole world.

First, is there anything happening at your place, or anywhere you have visibility of, in the platform engineering space? Second, if not, would you have twenty minutes on a call in the next couple of weeks? I would find your read on where that market has gone genuinely useful, and I am not going to use it to ask you for a job.

Either way it has been good to see what you have been up to, and no problem at all if the timing is bad.

The opening line is doing the most work. Naming the awkwardness removes it, because the thing that was going to be awkward was the pretence that this was a social message. The two questions are specific and answerable. The explicit "I am not going to use it to ask you for a job" is not throat-clearing; it is a real commitment that makes the twenty minutes a much easier yes, and you have to keep it.

Send these in small batches. Six a week, personalised, beats forty on a Sunday, and forty on a Sunday is detectable because people talk to each other.

Asking for a referral

Different message, different ask, and it needs more from you rather than less. A referral puts the referrer's name against you, so the job of the message is to make that cheap and safe.

Hi Sam, I saw Northgate are hiring a senior data engineer, the London one, and I am going to apply. Before I do, would you be willing to refer me internally?

Completely fine if not, and I mean that. If you have not seen me work recently enough to feel comfortable putting your name to it, a no is genuinely the right answer and it will not be weird.

If you are up for it, I have attached the CV and here are three lines you can paste or ignore:

Worked with Priyanka for two years at Meridian, where she owned the ingestion platform end to end. She took our nightly batch to streaming without an outage and was the person the analytics team went to when something looked wrong. Straightforward to work with and good at saying when something will not fit.

Happy to answer anything about the role or my situation first if that helps.

The three pasteable lines are the part that changes the response rate. You have converted a task that takes twenty minutes of writing into one that takes ninety seconds, and you have controlled what gets said about you. The explicit permission to decline is doing the same job as in the reference request: it means the yes carries weight and the relationship survives a no.

Asking somebody to keep you in mind, without asking for a job

This is the most useful message of the three and the one people never send. Most roles are filled through somebody remembering somebody at the right moment, and the whole game is being the person who is remembered. That requires being specific enough to be memorable and asking for nothing, so there is nothing to decline.

Hi Tom, no ask attached to this one, just putting a marker down.

I left Meridian in the March restructure and I am looking for a senior platform role, ideally London or hybrid, in a product company somewhere between fifty and five hundred people. The things I am best at are data platform work and taking a team through a migration without stopping delivery.

If something crosses your desk that fits, I would love you to think of me. If nothing does, that is completely fine and this needs no reply.

Hope things are good at Ardent.

Four sentences and an exit. The specificity is the mechanism: "let me know if you hear of anything" is unmemorable and therefore useless, whereas "senior platform, London, fifty to five hundred people, data platform and migrations" is a pattern somebody's brain can match against when a colleague mentions a vacancy nine weeks from now. The "this needs no reply" line raises the response rate rather than lowering it, because it removes the obligation that makes people leave a message unanswered for a fortnight and then feel too awkward to answer at all.

Send this one widely. It costs the recipient nothing, so the usual restraint about volume does not apply in the same way, though it should still be individually written.

On the coffee chat that is not a coffee chat

If you promised not to ask for a job, do not ask for a job. The conversation is still enormously valuable and the value is not the favour, it is the information: what is happening in that market, which teams are growing, which of your assumptions about your own positioning are wrong, and who else you should talk to.

End with that last one. "Is there anybody else you think I should be speaking to?" is the single highest-yield sentence in networking, because it turns one conversation into two and it asks for an introduction rather than a job, which is a much smaller thing to give.

And follow up when something happens. A short note two months later saying you took their advice about the sector and here is how it went costs you three minutes and is the entire difference between a network you burned and one you built. It is also how you avoid the position of only ever contacting people when you need something, which is the thing you were worried about at the start.

Negotiating when you feel you have no leverage

This is where laid-off candidates lose the most money, and the loss is usually not a small one. It compounds: the accepted number sets the base for the next raise, frequently anchors the next employer's offer, and follows you for years. A candidate who accepts eight per cent under because they felt they could not push is not making an eight per cent mistake in one year.

The general mechanics of negotiating are covered in salary negotiation and offers, and everything there still applies to you. This section is only about the specific case: what changes when you are out of work, believe you have nothing to trade, and are frightened of losing the only offer you have.

What you believe against what is true

The belief is that being unemployed makes your offer worse, because they know you need it and will therefore pay less. It feels obvious. It is mostly wrong, and understanding why is the whole of the defence.

An offer is constructed from three things: the internal band for the level, what the market is paying for the skill set, and what it would cost the hiring manager to go back and start again. Your bank balance is in none of them. The compensation team producing the number frequently does not know your employment status; the recruiter may, and the hiring manager may, but the band was set before you applied and the approval process for exceeding it does not have a field for candidate desperation.

What is true is narrower and worth stating precisely. Being out of work removes exactly one piece of leverage, which is the credible competing pressure of a current salary and a job you would have to be persuaded to leave. That is one input among several, and it is the one you can most easily replace. It does not remove the band, the market, the cost of restarting the search, or the fact that they have chosen you over the other finalists and would rather not undo that.

The genuine risk is not that they lower the offer because you are unemployed. It is that you accept a normal offer without asking, or accept a low one without testing it, because you have talked yourself out of the conversation before it starts. The money is lost by you, not taken by them, in the great majority of cases.

The leverage you still have

The last row is why the floor mattered in the first fortnight. A floor computed while calm is a real boundary. A floor computed the evening an offer lands is whatever you can bear to say out loud, which is lower.

The sign-on bonus row deserves its own note because it is under-used and it is the closest thing to a free move for a candidate in your position. Companies guard the base salary because it is permanent and it sets internal precedent. A one-off payment does neither, which means it comes out of a different budget with a shorter approval chain. If the base genuinely cannot move, a sign-on can frequently be found, and for a candidate who has been out of work for months and drawn down savings, cash now is worth more than the same money spread over a year.

Not signalling urgency

You do not have to conceal that you are out of work. Concealment is unnecessary and it fails. What you are managing is not the fact but the register, and the register is a small number of habits.

Do not volunteer the runway. "I need to be earning by September" hands over the deadline. If you are asked when you can start, the answer is that you are available quickly and can be flexible, not the reason you need to be.

Do not reply to the offer in nine minutes. Thank them warmly and immediately, and ask for the time you need to consider it. Twenty-four to forty-eight hours is normal, unremarkable, and it changes the tone of everything that follows. An instant yes is the loudest urgency signal available, and it is also how people accept offers they had not read. What to read before signing is set out in what to check in the offer letter before signing, and an offer with an artificial clock on it is its own problem, handled in an offer with a twenty-four hour deadline.

Do not apologise inside the negotiation. "I know I am not really in a position to ask, but" is a sentence that concedes before the ask arrives. Ask plainly and without preamble.

Do not answer the expectations question with your last salary. It is the wrong anchor for anybody and a particularly bad one for you, and there are better ways to handle it in what are your salary expectations.

Be honest about other processes without decorating them. Asked whether you are interviewing elsewhere, a truthful answer with a real shape is more useful than either a bluff or a flat no, and the framing that works is covered in are you interviewing elsewhere. A fabricated competing offer is the one move that can destroy the whole thing, because the market is small and the fabrication is checkable.

The words

For an offer that is in a normal range and could be better:

Thank you, I am genuinely pleased and I want to do this. Before I confirm, can I ask about the base? I had been working towards seventy-eight based on the scope of the role and what I have seen for comparable positions, and the offer is at seventy-two. Is there room to move on that, or is seventy-two where the band sits for this level?

If the base is fixed I understand, and in that case I would want to ask about a sign-on to bridge the gap, since I have been out since March. Either answer works for me and I am not going to make this difficult.

That last sentence is not weakness. It tells them the negotiation is bounded, which is what makes a hiring manager willing to go and ask, because the thing they fear is a candidate who will come back three more times.

For an offer that is clearly low:

Thank you for this, and I do want to work with you, so let me be straightforward rather than dance around it.

Sixty-two is below where I can go. I have been out of work since March so I am not going to pretend I have infinite time, but I would be taking a real step back to accept this, and I do not think either of us wants me starting on that basis. Where I can get to is sixty-eight, and I would rather tell you that plainly now than negotiate in stages.

If that is not possible within the band, tell me and I will think properly about whether the rest of the package makes it work. Is there flexibility on a sign-on, on the review date, or on the level itself?

Naming that you are out of work while also naming a floor is a stronger move than hiding it. It says the constraint is real and is not the whole story, and it makes the sixty-eight credible in a way that a bluff never is.

For the case where they cannot move at all:

Understood, and thank you for going and checking rather than just telling me no.

Two things then. Can we agree a review at six months rather than twelve, with the scope we have discussed written into it? And can I ask what would have to be true for me to be at the next level up, specifically, so that I know what I am working towards rather than guessing?

That converts a closed door into a dated commitment, and a dated commitment written in an email is worth considerably more than a verbal assurance about the future.

When the answer is to take it

Sometimes the honest answer is that the offer is under where you should be and you should take it anyway, and a page that will not say so is not being useful. If your runway is short, the offer is the only live one, and the work is reasonable, take it. That is not a failure of nerve. It is a correct decision under the constraints you actually have, and the alternative of holding out on principle with eleven weeks of money is a considerably worse decision dressed as a stronger one.

What matters is how you take it, because the difference between taking a low offer well and taking one badly is entirely in what you set up on the way in.

Get the review date in writing. Not "we review annually", but a date, with the scope of the role written next to it. Ask what the criteria are for the next level, specifically enough that you could tick them off, and put the answer in an email back to them so it exists. Ask about the sign-on, once, since it is the easiest thing for them to say yes to. And ask what the internal path looks like, because in some organisations the fastest route to being paid correctly is an internal move at nine months rather than a review at twelve.

Then set your own twelve-month plan on day one, before the job absorbs you. Diarise a check at six months against the criteria you were given. Understand that the correction may have to come from a move rather than from a review, and that a move from employment is a completely different negotiation from the one you just had, because next time you have the leverage you were missing. Keep the network warm rather than letting it lapse the moment you sign, which is what everybody does and what makes the next search start from cold again.

The resentment question is worth addressing directly, because a low starting salary is the kind of thing that quietly poisons a job. The thing that turns it toxic is not the number, it is carrying an unstated grievance into the work. You made a decision with the information and the runway you had, and it was the right decision at the time. Say that to yourself in those terms, put the review date in the diary, and then do the job properly, because the strongest position you can be in at the six-month conversation is having been visibly excellent. A person who accepted a low offer and then withheld effort has confirmed the low offer. That is the actual risk, and it is the one thing you fully control.

The question you will be asked for months

At some point past the third or fourth month, an interviewer will ask why you are still looking, and it lands differently from all the other questions because it feels like an accusation with a fact behind it.

Answer it truthfully and without defensiveness, and remember that the person asking has usually hired in this market and knows what it looks like. The structure that works is three parts: name the timeframe without flinching, give a real and unembarrassing reason for the shape of the search, and then show that the time has been used.

Five months, yes. I have been reasonably selective, which has cost me time but I think it was the right call, and I have had two processes reach final stage and go to internal candidates, which was the market rather than anything I would change. In the meantime I have done a contract piece for a logistics firm on their pipeline migration, which kept me current, and I have gone deeper on the streaming side because that is where I think this kind of role is going.

What that answer avoids matters as much as what it contains. It does not apologise. It does not blame the market as a whole while implying the interviewer is part of the problem. It does not oversell what was done with the time. And it does not spiral into detail about how many applications went out, which invites the follow-up nobody wants.

Being selective is a legitimate reason and is generally believed, provided the selectivity is visible in your CV rather than asserted. Final-stage losses are also a good answer, since reaching final stage twice is evidence rather than an excuse.

Two things to avoid saying. Do not say you have been applying constantly with no response, even if that is true, because it invites the reader to wonder what everybody else saw. And do not say you took time out to think about what you wanted unless it is true and you can say what you concluded, because the unfinished version of that answer reads as drift. The related question about your career direction more broadly is handled in walk me through your career, and the specific CV-gap version in there is a year gap on your CV.

Staying sharp with nothing to draw on

Two months out, three things start to erode, and they erode at different rates.

Stories go stale first, and fastest. Everything you talk about in a behavioural round happened at least three months ago and is receding. The specifics go before the shape does, which is why long-unemployed candidates give answers that are structurally correct and evidentially thin: they remember that they led the migration and no longer remember the number that made it impressive. The fix is the document you wrote in week one, reread before every interview rather than rewritten. If you did not write it in week one, write it now, because it gets harder every month.

Confidence in the register goes second. Talking about your work fluently is a practised skill and it decays without practice. This is not about self-belief, it is about fluency: the sentences come out slower and more hedged when you have not said them for six weeks. The remedy is saying them out loud, to somebody, on a schedule. A friend in the industry doing a mock round once a fortnight is worth more than any amount of reading, and if you cannot get one, saying the answers aloud to yourself is a distant second that still beats thinking them.

Technical currency goes third, and slowest. Slower than people fear, and the fear does more damage than the decay. Six months out of a codebase does not make you unable to write code. It makes you slower for a week. The genuine risks are narrower: specific tooling that has moved, a language version with new features you cannot discuss, and interview-specific formats that need practice regardless of how good you are at the job.

Whether side projects are worth it

Honestly: sometimes, and considerably less often than the internet suggests. The test is whether the project does a job that nothing else in your campaign is doing.

A project earns its place when it fills a stated gap in your target roles, when it gives you something current and specific to talk about in an interview, or when it keeps your hands in during a long search for reasons that are mostly about your own state of mind. Those are three good reasons and the third is legitimate on its own.

A project does not earn its place when it exists to prove you were busy. Nobody is impressed by a repository, and an interviewer who asks about it will ask about the interesting decisions in it, so a project you built without making any is a liability rather than a credential. It also does not earn its place if it eats the hours that should be going into network conversations, which it very often does, because building is comfortable and messaging people is not.

Keep it small enough to finish and specific enough to describe in two sentences. Two weeks of evenings on something that works beats four months on something at forty per cent, and the second one is also the thing that quietly stops you applying.

Study is a similar calculation with one addition: a certification is worth doing when it is a filter you keep failing rather than when it is a credential you would like to have. If postings in your target keep naming a specific cloud certification and you keep not getting responses, that is evidence. If you simply feel you should be learning something, that is anxiety with a curriculum, and the hours are better spent on the pipeline.

Contract, interim and part-time work

Somewhere around the point where the runway crosses into the uncomfortable band, the question of taking something temporary arrives. It is worth thinking about earlier than it arrives, because deciding it under pressure produces the worst version of the decision.

What temporary work costs is real. It takes hours out of the search, and not proportionally: a three-day-a-week contract does not leave you sixty per cent of your search capacity, it leaves you rather less, because the search work that gets cut first is the network conversations and the preparation, which were the highest-yield parts of the week. It can also make you harder to schedule for interviews and, depending on the sector, it can raise a question about availability at exactly the wrong moment.

What it protects is also real, and it is more than the money. It stops the runway shrinking, which changes the negotiation position at the end of the search and does so more than the money alone suggests, because runway is the input to the floor. It keeps you current, which solves most of the decay problem in a way no side project does. It gives you something present-tense to say when asked what you are doing now. It supplies structure and colleagues, which matter more at month five than anybody expects. And on occasion it converts into the permanent role, which is not the reason to take it but is not nothing.

The decision rule that works: take it when the runway is the binding constraint, decline it when the search itself is. If you have twenty applications out, three live processes, and eight months of money, a contract is a distraction. If you have eleven weeks and a thin pipeline, the contract is the correct move and the search continues at reduced intensity around it. The mistake is taking one at month two out of anxiety, or refusing one at month six out of a belief that it looks like giving up. It does not look like giving up to anybody except you.

Two practical notes. Negotiate the notice period on the way in; a contract you can leave in a week is a different asset from one that locks you in for three months when the permanent offer lands. And be straightforward about it in interviews. Interim work during a search is completely normal and needs no apology, and describing it plainly as bridging work that also kept you current is both true and sufficient.

The emotional shape of a long search

This section is going to stay practical, because you are not looking for a counsellor and a page that pretends to be one is worse than one that admits its limits.

Rejection volume, and what it is not evidence of

The arithmetic is unpleasant and worth having straight. In a slow market, strong candidates get rejected a great deal. Roles get hundreds of applicants, shortlists are small, and final rounds frequently end with an internal candidate or a role being pulled. You will lose processes you should have won, and you will lose several of them, and each will arrive as a two-line email with no reason attached.

The error that does the damage is treating each rejection as a data point about yourself. It is painful and it is also statistically wrong, for a reason worth understanding rather than just being reassured about. A single rejection is the output of a process with enormous variance in it: who else applied that week, whether the hiring manager already had somebody in mind, whether budget moved, whether the person reading your CV was on their fortieth of the day. The signal about you is real but faint, and it is buried under noise so large that no single outcome tells you anything reliable. Reading one rejection as a verdict is reading noise as signal, which is a mistake you would spot instantly in any other context.

Patterns across many attempts are informative. Individual outcomes are not. That distinction is the entire practical content of this section, and it is also why the weekly review looks at where things die across weeks rather than at what happened on Tuesday. The particular pain of a rejection that arrives with no explanation at all is common enough to have its own treatment in interview rejection and self-diagnosis, which is the page to read when you want to know what a rejection can and cannot tell you.

One practical habit: read rejections once, at a fixed time of day, not as they arrive. Checking email continuously means being available for bad news at every hour, and that is a genuinely different experience from reading four of them on Friday afternoon with the pipeline open in front of you.

Routine

The specifics matter less than that there are any. Get up at a fixed time. Leave the house once a day, for anything at all. Keep a boundary around the day so that the search has an end, because a search with no end colonises the evening and then the weekend and then you are working eighty hours in a state of continuous guilt while achieving about twelve.

Take a full day off a week and treat it as part of the plan rather than as a lapse. The people who search seven days a week are not further ahead in month four, they are further behind, because they burned out in month two and lost a fortnight.

Get dressed for interviews properly even when they are on video, not for the camera but because the transition into a different mode is most of what preparation is for.

Isolation

Isolation is the part that catches people who were prepared for everything else. Work supplies most adults with the majority of their incidental human contact, and it goes overnight along with the salary. The gap does not announce itself; it shows up three months later as a general flattening, and people attribute it to the search when a fair share of it is simply not having spoken to anybody.

The counter is to book contact rather than wait for it. This is the unexpected secondary benefit of the network conversations, which are the highest-yield search activity and also happen to be three conversations a week with people who know your field. Beyond that, anything with other people in it and a fixed time attached. Former colleagues who are still working are worth keeping up with, and the awkwardness of seeing them is smaller than you imagine and shrinks after the first time.

If there are other people around you looking at the same time, and after a large redundancy there usually are, a standing weekly call with two or three of them does more good than it sounds like it should. It also gives you a place to say the parts you are not saying at home.

Telling family

Two failure modes, and they are opposite. Saying nothing, which means managing your own situation and a growing secret at the same time, and the secret costs more energy than the situation. Or narrating every rejection in real time, which turns your household into an audience for a process with a lot of bad days in it and puts them in the position of managing your mood daily.

The middle is a fixed, low-frequency update with a shape to it. Once a week, briefly: here is where things stand, here is the runway, here is what I am doing next week. It is honest, it is bounded, and it stops the question being asked at dinner every night, which is the thing that grinds everybody down.

Be straight about money early, especially with a partner, because the household budget is a joint decision and discovering the runway situation in month five is considerably worse than knowing in week one. And if there are children, they mostly need to know that things are being handled and that the change is temporary, not the details of the pipeline.

Knowing when to change the plan

The hardest judgement in a long search is telling a hard market from a wrong plan, because they feel identical from the inside and the second one is fixable. The distinguishing evidence is where in the funnel things stop, and this is exactly why the weekly review records that.

Read the last row before the others. The commonest reason a search cannot be diagnosed is that it has not generated enough attempts to have a pattern, and changing your CV on the evidence of nine applications is changing it on noise. Get to a volume where the pattern is real, then read it.

What to change, in what order

When the evidence says something is wrong, change one thing at a time and give it three weeks, because changing four things simultaneously means learning nothing from the result.

Change the target first if the failure is at the application stage, because it is the highest-leverage variable and because a wrong target makes everything downstream harder. Widening the band, adding an adjacent sector, or accepting a level you had ruled out are all target changes, and the last one deserves genuine consideration rather than reflexive refusal, particularly if the runway is shortening.

Change the materials second. Get the CV in front of somebody who actually hires for your kind of role and ask them what they would screen it out for. This is uncomfortable and it is twenty minutes that frequently saves two months. Most CV problems are not quality problems, they are legibility problems: the relevant experience is on page two, the current title does not match the target title, or the first six lines say nothing specific.

Change the channel third. If adverts are producing nothing and network conversations are producing interviews, the honest response is to move ten hours a week from one to the other, and to stop feeling that applications are the real work and networking is the supplement. The pipeline's route-in column tells you this and people ignore it for months.

Change the interview preparation if things die after the first round. This is the most fixable category and the one people spend the least time on, because preparation feels like a thing you do when you have an interview rather than a thing you do to get better at them.

Change the timeline last, meaning take the interim work, cut the outgoings, extend the runway. Not because it is a defeat, but because it does not fix a wrong plan and doing it first can disguise one for another three months.

The signals that say do not change anything

There is a failure mode in the other direction, which is rewriting the campaign every fortnight in response to noise. Some patterns mean the plan is right and the market is slow, and the correct response is to keep going, which is much harder advice to follow than a list of changes.

If you are reaching final stages, the plan is working. Final-stage losses are painful and they are also the strongest possible evidence that your targeting, materials and interviewing are all sound. The variable you are missing is volume of finals, and the fix is more of the same rather than something different.

If your pipeline is moving but slowly, and you have runway, hold. Processes have got longer and a slow pipeline is not a stalled one. A role that went quiet for three weeks and then came back with a second round is completely normal now.

And if you have changed something in the last three weeks, wait. You cannot read the result of a change you have not given time to produce one, and a campaign that changes shape every fortnight has no evidence about anything, which is where it started.

What interviewers ask

The questions a visibly out-of-work candidate gets cluster into a small number of archetypes, and each is probing something specific rather than asking for the information on its face. Recognising the archetype tells you what the answer has to contain.

The thread running through all eight is that they are testing composure under a fact everybody in the room already knows. Nobody is trying to catch you out about being unemployed; they can see it on the CV. What they are reading is whether you can discuss it without the conversation changing temperature, because a candidate who becomes defensive about a known fact will be difficult in every other awkward conversation the job contains.

The second thread is agency. Every one of these questions has a passive answer and an active one, and the active one wins even when the underlying facts are identical. "I was made redundant and I have been applying" and "my role went in a restructure and I decided to use the time to move deliberately towards platform work rather than take the first thing" describe the same five months.

Questions

These are phrased the way interviewers put them. Each answer names the signal being graded, because on this subject the graded thing is frequently not what the question appears to be about.

Why are you still looking after five months?

Give the number without flinching, give a real reason for the shape of the search, and show the time was used. "Five months, yes. I have been selective, which cost me time and I think was right. Two processes went to final stage and went to internal candidates, which was not something I would change. Alongside that I did a two-month contract on a pipeline migration, so I have stayed current, and I have gone deeper on streaming because that is where these roles are heading."

Graded on composure first and content second. An interviewer who has hired recently knows the market. What they are watching for is whether the question destabilises you, because if a known fact does, so will a hard question in a stakeholder meeting. The other thing being read is whether the five months has any shape at all, and shape can be selectivity, contract work, study, caring responsibilities, or a deliberate change of direction. Undifferentiated searching is the only answer with nothing in it.

What have you been doing since you left?

Name two or three specific things and be honest about the mix. "The search has been most of it and I will not pretend otherwise. Beyond that, a contract piece for a logistics business on their ingestion pipeline, which was three months and genuinely useful, and I put myself through the streaming material properly because I kept seeing it in the roles I want."

Graded on initiative and on honesty in the same answer. Claiming the whole period was productive study is not believed. Saying only "looking for work" leaves the interviewer nothing. The strong version admits the search took the bulk of it and names the things that were not that. Anything real counts, including caring for a relative, which is a complete answer and needs no embellishment.

Was leaving your last role your decision?

Answer in one clear sentence, then stop. "No, my role was made redundant in a restructure in March. The data platform team went from nine to four and the two most recent hires and my role went with it." No blame, no lengthy justification, no volunteered detail about who survived and why.

Graded on whether the account is straight and whether you can deliver it without heat. The failure is either evasion, which reads as concealment, or a five-minute explanation with a villain in it, which tells the interviewer how you will talk about them one day. Detailed handling of this and its variants lives in was leaving your last role your decision.

Why do you think you were selected for redundancy?

Answer factually about the mechanism, not defensively about yourself. "The whole function was cut back and selection was by role rather than by person. My role was one of three in scope and the other two holders had considerably longer service. I asked at the time and that was the answer I got."

Graded on whether you can discuss an unflattering event without either accepting blame you do not owe or deflecting entirely. Interviewers ask this to find out whether there is a performance story behind the redundancy, and the straightest way to answer it is with the mechanism, which is usually genuinely structural. If it was partly performance-related, a short honest account with what you took from it is survivable and a discovered evasion is not.

How soon could you start?

Be available without being urgent. "I have no notice period, so I could be with you as quickly as suits. A couple of weeks would let me hand over the contract work cleanly, but if you need somebody sooner that is manageable."

Graded on whether availability reads as an asset or as need. The version that costs you money is "immediately, whenever you want", said quickly, which pairs availability with eagerness. Naming a short lead time keeps the same practical answer while framing it as a professional handover. Availability is genuinely worth money to an employer with an urgent gap; give it as a concession rather than as a symptom.

Are you interviewing anywhere else?

Tell the truth with a real shape to it. "Yes, two other processes. One is at second stage and one I have just started, and neither is at offer. I would rather be straight with you about the timing than pretend there is pressure that is not there."

Graded on honesty and on whether you understand your own process. An invented competing offer is the one unrecoverable move here, because markets are small and it is checkable. A flat no is honest and slightly costly, and the way to give it well is to make it about focus rather than about the absence of options. The full treatment is in are you interviewing elsewhere.

What are your salary expectations?

Anchor on the role and the market, never on what you last earned or on what you need. "Based on the scope you have described and what I have seen for comparable senior platform roles, I have been working to seventy-five to eighty-five. Where does that sit against the band you have for this?"

Graded on calibration and on whether the pressure of unemployment has moved your number downwards in a way the interviewer can hear. A number well below the band is read as either not understanding the level or as being in trouble, and both make the offer worse. Handing the question back with "where does that sit against your band" is the move that does the most work, because it converts your answer into a conversation about their range. See what are your salary expectations for the mechanics.

The offer is a bit below what you asked for. Can you work with that?

Do not answer immediately, and do not answer with a yes or a no. "Thank you, and I do want this. Can I ask where seventy-two sits in the band for the level? If there is room I would want to talk about it, and if there is not, I would like to ask about a sign-on and about the review date instead."

Graded on whether you negotiate at all. The commonest outcome for an unemployed candidate is instant acceptance, and hiring managers frequently have room they were never asked for. Asking calmly, once, with a named alternative if the base cannot move, is normal professional behaviour and does not put an offer at risk. Withdrawal over a single polite question is close to unheard of, and where it happens it has told you something you needed to know. More in the written offer is below the number you gave.

Given your situation, I assume the salary is flexible?

This is the one question where the fact is being used as a lever, and the answer needs to be warm and completely firm. "My situation is that I am between roles, and that is true. What I need to be paid for the job is a separate thing, and it comes from the scope and the market rather than from my circumstances. I have been working to seventy-eight, and I would rather agree the right number now than have this conversation again in six months."

Graded on whether you hold a boundary without becoming difficult. An interviewer or recruiter who tries this is testing whether the number was real. Conceding immediately confirms it was not and typically costs several thousand within the next sixty seconds. Separating the circumstance from the valuation, in plain words, is the whole move, and it can be done without any edge in the voice.

This role is a level below your last one. Are you sure about that?

Have a real reason that is not about the runway. "Yes, and I have thought about it rather than just accepting it. The scope here is closer to what I want to do than my last title suggests; I spent most of that role in management and I want to be back on the platform side. The title matters less to me than the work, though I would want to talk about what the path looks like from here."

Graded on whether the step down is a choice or a capitulation, because the interviewer's worry is that you will leave the moment something at your old level appears. A reason grounded in the work is credible. "I need a job" is honest and confirms the fear. If you can name what would make you stay for three years, say it, and if the level genuinely is a compromise for you, say that plainly and say what would need to be true about progression, which is more convincing than a claim of enthusiasm nobody believes. See also being offered a level below what you interviewed for.

If a role at your previous level came up next month, would you take it?

Answer the real worry rather than the hypothetical. "I would not be having this conversation if I were waiting for something else. What I want is to be doing platform work with a team that owns its own systems, which is this. If I were only after the title I would be applying differently, and I would rather tell you what would make me stay than promise I would never look."

Graded on whether you engage with the concern or dodge it. A flat "no, never" is not believed and slightly damages you. Naming what you want from the role, and what would keep you, is a better answer than any promise. The related framing of long-term intent is covered in where do you see yourself in five years.

Are you applying to a lot of these?

Be honest and give the answer a shape. "I have applied to a fair number, yes, though not indiscriminately. There are maybe five companies I have gone after properly and this is one of them, because the platform work here is close to what I did at Meridian and I would rather be somewhere the data problem is the product problem."

Graded on whether you have criteria. Everybody knows an unemployed candidate is applying widely and nobody minds. What they are checking is whether this application was considered or automatic, so the answer needs one specific reason you chose them that could not be copied to another company. "I am applying to everything" is honest and unhelpful. Denying that you are applying widely is neither.

How have you kept your skills current?

Be specific and be honest about the limits. "Two things. The contract work kept me writing production code through the summer, which is the part I was most worried about losing. And I worked through the streaming material properly and built a small ingestion service with it, which is on GitHub. What I have not done is keep up with any large-scale operational work, since you cannot manufacture that on your own, and I would expect to be a bit rusty on the on-call side for the first few weeks."

Graded on realism as much as on activity. The honest limit at the end is worth more than the two accomplishments before it, because a candidate who claims six months out cost them nothing has told the interviewer they do not calibrate well. Naming what has decayed and how long it would take to recover is precise and lands as confidence rather than weakness.

Walk me through this contract role on your CV. Was that a stopgap?

Say what it was without apology and name what you got from it. "It was, in the sense that I took it because I was between permanent roles. It was also genuinely good work: three months on a pipeline migration for a logistics business, and I owned the cutover. I took it because it kept me current and because I would rather be working than not, and I would take contract work again for the same reasons."

Graded on whether you are defensive about it. Interim work during a search is entirely normal and needs no cover story. Candidates who dress it up as a deliberate career choice sound evasive; candidates who apologise for it invite the interviewer to discount it. The straight version, which names both the practical reason and the real content, is the one that works.

You have had time to prepare for this. Have you?

Take the point and show the preparation was targeted rather than exhaustive. "I have, and I will not pretend I had a busy week that stopped me. I read your engineering blog, particularly the piece on the warehouse migration, and I spoke to a former colleague who worked here two years ago. The thing I would most like to understand is how the platform team splits ownership with the analytics group, because the blog post implies one thing and the job description implies another."

Graded on whether the available time was used, and this is one question where the bar is genuinely higher for you than for an employed candidate. It is unfair and it is real. The compensation is that thorough preparation is fully within your control right now, and a specific question drawn from their own material is the cheapest way to demonstrate it. Do you have any questions for us is the place this most often shows.

Tell me about yourself.

Present tense, forward-looking, with the redundancy as one clause rather than the subject. "I am a data platform engineer, eight years, mostly on ingestion and streaming at mid-sized product companies. Most recently I ran the platform at Meridian, where I took the nightly batch to streaming and owned it through a year of growth. That role went in a restructure in March, so I am looking for the next thing, and what I am after is somewhere the data platform is central rather than a side concern, which is why I am here."

Graded on framing and on whether the redundancy dominates the answer it appears in. This is the question that sets the temperature for the whole conversation and most candidates out of work let it become the redundancy answer. One clause, no defensiveness, then straight into what you are looking for. The general treatment is in tell me about yourself.

What is the biggest thing you have learned from the last few months?

Answer with something real and unsentimental, and keep it short. "That I had let my network go completely. I had not spoken to people I worked with for years and I found that uncomfortable to fix, and every useful thing that has happened in this search has come through somebody I knew. I will not let that lapse again."

Graded on whether you can reflect without either performing resilience or airing distress. Interviewers ask a version of this to see how you handle a genuinely difficult period, and the answers that land are concrete and slightly unflattering. Grand statements about what really matters read as prepared. A specific operational lesson reads as true.

We are seeing a lot of strong candidates for this. Why you?

Do not compete on effort or availability. Compete on fit, specifically. "Because the difficult part of this role is the migration without stopping delivery, and that is the thing I have done. At Meridian I moved the whole ingestion path with the analytics team running the whole time, and the thing I learned was that the sequencing of the cutover matters more than the technology choice. If your problem is what the job description implies, I have made those mistakes already."

Graded on whether you can name the hard part of their job and connect it to evidence. The failing answers are "I would work harder than anybody" and "I am available immediately", both of which are about your situation rather than their problem, and both of which are what an anxious candidate reaches for. The related self-presentation is in the work you are proudest of and why that one.

How are you managing financially? Is there a deadline we should know about?

Answer without the number. "I am fine for the time being, so I am not in a position where I need to rush a decision. I would obviously rather move sooner than later, and if there is a timeline on your side I would want to work to it."

Graded on whether you disclose your deadline. Sometimes the question is genuine kindness and sometimes it is information-gathering, and you cannot reliably tell which, so the answer is the same either way. Naming a date hands over the negotiation. A warm non-answer is completely acceptable and nobody presses it, because pressing it would be obviously inappropriate.

You have been out for a while. Would you consider a contract-to-permanent arrangement instead?

Engage with it as a real option and negotiate the terms rather than the principle. "I would consider it. What I would want to understand is what the conversion looks like: is there a defined point and defined criteria, or is it a general intention? And I would want the contract rate to reflect that I am carrying the risk in the meantime rather than being the permanent rate divided by twelve."

Graded on commercial awareness. The instinctive responses are gratitude, which costs money, and offence, which costs the option. The correct posture treats it as a legitimate structure with terms worth negotiating: conversion criteria, a date, and a rate that prices the risk you are absorbing. If they cannot name conversion criteria, that is worth knowing.

What would you do differently if you were doing this search again?

Answer operationally. "Two things. I would have worked out my runway properly in the first week rather than the fifth, because it turned out I had more room than I thought and I spent a month applying more widely than I needed to. And I would have started the network conversations immediately instead of treating them as a fallback, because they have produced almost everything."

Graded on whether you can review your own process, which is a proxy for how you will handle a retrospective on a project. Answers about how you should have been more positive are not answers. Answers naming a specific decision, its consequence, and what you now do differently are the same shape as a good post-incident review, and interviewers hear them that way.

This role is quite different from what you were doing. What is the thinking?

Own the change as a choice rather than presenting it as an adaptation to circumstance. "Partly circumstance and partly not. The redundancy gave me a reason to look at where I wanted to be, and the honest answer was that I had drifted into managing platform work rather than building it. This role is closer to what I was best at three years ago. If I had not been made redundant I might have kept drifting, so in that sense the timing did me a favour."

Graded on whether the change is directional or opportunistic. The interviewer is checking whether you would go back the moment your old kind of role appeared. Acknowledging that circumstance created the opening while the direction was your own is both true and more credible than either extreme. See why this company and why are you leaving.

Tell me about a time you had far more to do than you could deliver.

Use a work example rather than the job search, unless you have nothing else. "At Meridian we had the migration and a compliance deadline in the same quarter with four people. I took the position that the compliance work was fixed and the migration was not, so I sequenced the migration into three cutovers and moved the last one past the deadline. I told the analytics team what they were getting and when, in writing, before anybody had to ask."

Graded exactly as it would be for an employed candidate, which is the point. Under-employment tempts people to reach for the search itself as an example of pressure, and it is a weaker story because it has no stakeholders and no delivery in it. Keep your work examples current in your head; that is what the story document written in week one is for. The full version is in far more work than you could deliver.

Where do you see yourself in three years?

Answer about the work and connect it to this role specifically. "Deep in a platform that I own the shape of, with a couple of people I have brought on. I do not particularly want to go back to pure management. What would make this the right three years is if the platform here is genuinely central to the product, which is the thing I want to test in this conversation."

Graded on whether your answer is a plan or an escape. The specific risk for a recently redundant candidate is giving an answer that sounds like anywhere-will-do, because that is how you currently feel about the next three months. Naming something concrete about the work, and something you want to verify about them, separates the two.

Is there anything about your situation we should know?

Take it at face value and answer briefly. "Nothing that affects the role. I am available quickly, I have a two-week contract obligation to wind down, and I am in two other processes. If anything changes on the timing I will tell you rather than let you find out."

Graded on candour and on whether you volunteer things that hurt you. It is a genuine invitation and the correct response is short, factual and forward-looking. The failure is treating it as an opening to explain the redundancy again at length, which puts the subject back on the table after it was settled. The other failure is a flat no when there is something material, like a competing timeline, that would be better named now.

If we made you an offer today, what would you say?

Be warm, be positive, and do not commit on the spot. "I would be pleased, and I would want to read it properly before I said yes. I am interested and this is the process I most want to work out, so I am not going to sit on it. What I would want is a day or two to look at the whole package and come back to you with anything I want to discuss."

Graded on whether you can express enthusiasm and retain a decision at the same time. Answering "I would accept immediately" gives away the entire negotiation before it starts, which is exactly why the question gets asked in that form. Answering coolly loses goodwill for no gain. Warm and unhurried is the register, and asking for a day is so normal that failing to ask is the thing that stands out. If you are weighing more than one, comparing two offers when one pays more is the framework for the comparison.