3 TypeScript Offers Lost to a 3-Month Notice — the 7-Step Singapore Timeline I Use Now

Three strong TypeScript engineers, three signed acceptances, three roles that stayed empty. None of them left because of money, the work or the team. They left because we treated the notice period as an administrative detail rather than as the longest and riskiest phase of the hire.

Why notice is the phase that decides Singapore hires

Most hiring processes are designed around the part that is visible: sourcing, screening, technical assessment, decision. Teams measure that and optimise it, sometimes obsessively.

Then the offer is accepted and everybody relaxes — at exactly the moment when the longest and least controllable phase begins. In Singapore, engineering contracts commonly specify one, two or three months of notice, with three months increasingly common at senior levels and in larger organisations. Statutory minimums under the Employment Act apply where a contract is silent, and are shorter, but very few engineering contracts are silent.

The arithmetic is unforgiving. A four-week hiring process followed by a twelve-week notice means the notice is three times longer than everything you optimised. It is also the phase where you have the least contact, the least information and the most competition — because a resigning engineer is, for those twelve weeks, the most actively courted person in their current company.

The seven steps below are what we changed after the third loss. They have not eliminated the risk, but they have moved it from something that happens to us to something we plan for.

Step 1 — Ask about notice on the first screening call

Not at offer stage. Not at final interview. On the first call, in the same breath as availability and salary expectations.

The question is simple: “What notice period does your current contract specify, and has your employer been flexible about it in the past?” The second half matters as much as the first, because contractual notice and practical notice are frequently different numbers.

Asking early does two things. It stops you discovering a twelve-week gap after four weeks of interviews, when your only remaining option is to accept it. And it lets you sequence candidates deliberately: if two are comparable and one can start in four weeks, that is a legitimate factor to weigh — provided you weigh it consciously rather than discovering it too late to matter.

One caution: notice length correlates with seniority and with employer size, not with candidate quality. Treating a long notice as a negative signal about the person is a mistake we made once and will not repeat.

Step 2 — Plan backwards from the date the work must start

Most hiring plans run forwards from today: post the role, screen, interview, offer. That produces a start date nobody chose.

Run it backwards instead. Fix the date the work genuinely needs to begin — tied to something real, a product deadline, a contract, a departure — then subtract the expected notice, then subtract your own process. If the result is in the past, you have learned something important before spending a month on interviews.

When the arithmetic does not work, there are only four honest responses, and it is far better to choose among them deliberately:

• Move the deadline. Sometimes possible, rarely popular, always worth asking about.
• Widen the pool to include candidates with shorter notice, accepting the trade-off consciously.
• Bridge the gap with contract capacity for the intervening weeks.
• Budget for a buy-out — which is step four, and it should be a decision rather than a reflex.

Step 3 — Separate contractual notice from negotiable notice

A contract says three months. That is the starting point, not the answer. In practice three distinct routes shorten it, and they have very different costs and implications.

The first two are far more common than employers assume and cost nothing to explore. A candidate leaving on good terms, with a clean handover, frequently gets several weeks back simply by asking. Encourage them to ask before you reach for the chequebook.

One thing to avoid entirely: pressuring a candidate to leave in breach of their contract. It is a poor start to a relationship, it exposes both sides, and in a market as connected as Singapore it becomes known.

Step 4 — Decide your buy-out policy before you need it

The worst time to decide whether you will compensate a candidate for shortening their notice is the moment a candidate asks. Improvised answers are inconsistent, and inconsistency in this area becomes visible inside a team within a year.

Write the policy down in advance, and make it about the role rather than the person:

• Which roles justify it. Usually those with a hard external deadline attached, not simply those you want filled sooner.
• The ceiling. A stated maximum, expressed in weeks of salary, applied consistently.
• The trigger. How many weeks of gap have to exist before it is offered at all.
• The clawback, if any. If the person leaves within a defined period, is any of it repayable? Whatever you decide, decide it before it comes up.

The policy also protects you from a specific failure: paying a buy-out for a candidate who was never going to be released early anyway, because their employer had no intention of agreeing regardless of the money.

Step 5 — Compress the only part of the timeline you control

You cannot shorten someone else’s contract. You can shorten your own process, and most teams have far more room here than they believe.

Where the weeks actually go, in our experience:

• Scheduling gaps between stages. Almost always the largest single loss. Four interviews scheduled a week apart is a month spent on calendar friction rather than evaluation.
• Stages that duplicate each other. Two separate technical conversations covering the same ground, because two teams each wanted their own.
• Approval delays after the decision. The team decides on a Tuesday and the offer goes out ten days later. This is the most damaging gap of all, because it lands precisely when the candidate is most engaged and most likely to be talking to someone else.

Our rule now: a decision on Tuesday means a written offer by Thursday, or the delay is escalated. It costs nothing and it has done more for our conversion rate than any change to the interview content. The same principle applies to how the assessment itself is structured — our comparison of take-home versus paired trial for Singapore TypeScript developers looks at where the calendar time really goes.

Step 6 — Design the offer to survive the counter-offer window

The counter-offer is not a failure of the candidate’s character. It is a rational response by a well-run employer to losing someone they value, and it should be planned for as a certainty rather than treated as a betrayal.

What actually works, in order of effect:

• Make the offer about the work, in writing. A counter-offer can nearly always match money. It very rarely matches a specific, named first project and a clear scope of ownership. Put that in the offer letter, not just in the conversation.
• Have the resignation conversation before it happens. Ask the candidate directly what their manager is likely to say and what they will answer. Candidates who have rehearsed it decline counter-offers far more consistently.
• Name the number they would need to hear to stay. Uncomfortable, and extremely informative. If they can name it, you know exactly what you are competing against.

What does not work: matching a counter-offer with a rushed increase. It resets the relationship around price, and it teaches the person that pressure produces money.

Step 7 — Keep the candidate engaged through the notice period

This is the step we did not have, and it is the one that cost us all three hires.

After acceptance, our contact dropped to a welcome email and then silence until the start date. Meanwhile the current employer had ten weeks of daily contact, a retention conversation, and a team of colleagues making the case for staying. We were absent from precisely the period when the decision was being re-litigated.

What we do now, deliberately and lightly:

• A short call in the first week after resignation. Not a check-in on the process — a conversation about the work they will pick up.
• An introduction to two future teammates within the first month, informally. It converts an abstract employer into specific people.
• One genuinely useful piece of context per month: an architecture document, a product decision, something that makes them feel already partly inside.
• A deliberate touchpoint two weeks before the start date, which is risk peak two. Practical, warm, and specific about day one.

Four contacts across twelve weeks. It is not a campaign, and it is not pressure. It is simply not disappearing during the phase when someone else is present every day.

Three mistakes worth avoiding

Writing a single hard start date into the offer. It depends on a third party you do not control. Write a target date, a latest acceptable date, and an agreed check-in. You will renegotiate either way; do it from a planned position rather than a broken promise.

Treating a long notice period as a red flag. It correlates with seniority and employer size, not with the person. Some of the strongest engineers we have placed came with twelve weeks attached.

Going quiet after acceptance. The single most expensive habit in the whole process, and the easiest to fix. The dynamic is not unique to Singapore — teams hiring in Dubai see the same pattern with visa-dependent start dates, as our colleagues at HireDeveloper.ae describe, and in Tokyo the gap is longer still, which is why the team at JapanDev treats pre-start engagement as part of onboarding rather than as courtesy.

Frequently asked questions