Hiring for a Date That Cannot Move: How to Work Back From Launch Day and Know If You Are Already Late
When the launch date cannot move, the question is not how fast you can hire but whether the date is still safe. One subtraction tells you, a backward calendar shows where the weeks go, and an honest list shows when the answer is to cut scope instead of adding people.
How Late Is Too Late to Add Developers to a Fixed-Date Project?
Later than the sum of four things: your decision time, the start lead time, the ramp to useful work, and the integration and test buffer. Add them, count back from the launch date, and the answer is the last safe day to start. Anything after that day trades the buffer for people, which is the trade that usually goes wrong.
Here is an illustrative set of numbers, not a forecast. Suppose a decision takes one week, a start takes up to two weeks (the top of our one to two week range for the first engineers), ramp takes about five weeks, and you want three weeks of integration and testing. That is eleven weeks. With more than eleven weeks to the date, you are on track. With between eight and eleven, you are tight and every line needs an owner. With fewer than eight, which is ramp plus buffer, adding people will not rescue the date and you are choosing between scope and the date.
The ramp figure needs a source. DX, a vendor that measures engineering teams, reported that as of April 2026 the average time for a new engineer to reach their tenth pull request was 33 days, down from 39 days in Q4 2025, in a random sample of 400 companies. That is about five weeks, it is a vendor-measured average, and your codebase may be slower. Our guide to new engineer ramp-up covers it in more depth.
What Does the Backward Calendar Look Like, Week by Week?
One timeline, counted back from launch. Fill the right-hand column with your own dates and write a name next to each row. The weeks in the middle column use the illustrative numbers above; replace them with yours.
| Row | Illustrative length | Your date and owner |
|---|---|---|
| Launch day | T | [your date] |
| Integration and test buffer | 3 weeks before T | [start of buffer, owner] |
| Ramp to useful work | About 5 weeks before the buffer | [date, owner] |
| Engineers start | Up to 2 weeks before the ramp | [date, owner] |
| Your decision | 1 week before the start | [last day to decide, owner] |
Can Adding Developers Save a Late Project?
Only where the work can run in parallel. New engineers also take time from the people who already know the code, because someone has to explain it. If the remaining work is one chain of dependent steps, a second pair of hands waits. If it is several independent areas, a second pair of hands finishes one.
So before you add anyone, list the remaining work and mark what can be done in parallel and what cannot. Our rapid scaling playbook sets out which kinds of work scale quickly and a staged plan for adding people without losing the ability to reverse.
Adding engineers to a roadmap like this? Spec your team in a minute.
Why Is the Buffer the First Thing Teams Cut, and Why Is It the Wrong One?
Because it is the only line that looks empty. Everything else on the calendar has a task attached; the buffer is a block of weeks labelled integration and testing, so it looks like slack. It is where the surprises land: the interface that does not fit, the defect that only shows with real data, the approval that comes back with changes. Cut it and those surprises land after the launch date instead.
Protect the buffer first. If the subtraction fails, shorten the scope, not the buffer.
What Does a Regulatory Date Look Like on the Calendar?
Like any other fixed date, with an owner other than you. The European Commission's page on the Cyber Resilience Act says its reporting obligations apply as of 11 September 2026 and its main obligations from 11 December 2027. The first of those dates has already passed. The second is a little over a year away, which is long enough that the subtraction above leaves room, and short enough that the work has to start soon.
Put the regulatory date at T, add your own compliance work as rows, and run the same subtraction. We do not interpret the legal text here; our Cyber Resilience Act deadline guide covers what the dates mean for software teams, and your counsel owns the reading of the law.
How Do You Cut Scope to the Date?
Sort the remaining work into must, should and could in the first week, and freeze the must list. Everything on the must list ships on the date. Should items ship if the buffer survives. Could items are named, dated for later and not discussed again until launch. The value of the exercise is the decision, not the list: a scope that someone approved in writing stops growing.
Key Takeaways
- Decide the must list in week one, with one named person who can say no
- Write down what ships later and when, so cutting it does not feel like losing it
- Review the list weekly against the backward calendar, not against the backlog
What Should You Decide Before the First Engineer Starts?
Three things, in writing. The pass or fail criteria for the first two weeks, one named counterpart on your side with set hours, and your definition of done. A developer who is not the right fit is replaced free within the first 30 days. Criteria written down turn the first two weeks into a checkpoint, which matters when there is no time to discover a mismatch at week six.
Write the criteria down, and see the guide to putting the start date in the contract for how to make the start date binding.
When Is the Honest Answer That You Cannot Make It?
When the time left is shorter than the ramp plus the buffer. At that point more engineers cannot change the outcome, and the real options are to cut scope, move the date, or narrow the launch to what is already close. Say so early; a date missed with a plan is cheaper than a date missed by surprise.
What we can say is limited to the start: engineers can typically start within one to two weeks of first contact; a full team usually takes two to four weeks. We make no promise about what happens after that, because it depends on your code and your scope.
Is the Date Still Safe to Keep?
Do the subtraction today with your own numbers. If it works, start the decision row now. If it does not, cut scope before you add people. To check your date against ours, send the date, the stack and the scope on our contact page and book a 15-minute intro call; if there is a fit, a 60-minute discovery call follows. We will tell you whether engineers can start in time or what to cut.
Building a team in Eastern Europe?
StepTo builds dedicated nearshore engineering teams in Belgrade, Serbia. Engineers can typically start within one to two weeks of first contact; a full team usually takes two to four weeks. From $4,500 per developer per month.
Related: Open seat calculator
