In this guide 6 sections
Hire your own engineers when the need runs past a year, the skill is common in your market and you have a lead with time to manage them. Augment when the gap is short. Augment when the skill is rare. Test both routes against five questions.
How long will you need this person?
Start with the calendar. Not the budget. A payments integration that ends in four months is a project. A second backend developer for the core product is a permanent seat. Write down which one this is.
Short work suits augmentation. Nobody has to be let go afterwards. Long work suits a hire, since you keep everything the person learns about your codebase, from the deploy quirks to the reasons behind old table names. Be honest here. Many founders call a gap temporary for two years running, and by then the work has become part of the roadmap. It happens often.
- Under six months: augment or use a short-term specialist
- Six to eighteen months: either route can work
- Open-ended and tied to the core product: hire
- Seasonal peaks around a launch or audit: augment
Count the ramp-up cost on both routes
Every new engineer reads old code first. A hire spends weeks on laptop setup, repository access, the staging environment and the unwritten rules of your pull requests. An augmented engineer does the same.
The difference is practice. A vendor engineer who has joined many teams usually asks sharper questions on day one. A direct hire stays longer, so the reading pays back across more months of work.
Check how rare the skill is
Some skills sit on every résumé: React, Node.js, Laravel, Flutter. Hiring for them is slow. Not impossible. Others are thin in your city. Think Kubernetes operators, payment gateway certification, embedded firmware or a legacy COBOL batch job.
For rare skills, augmentation shortens the search because the vendor already carries the bench. For common skills, a vendor markup buys you little, and a direct hire is usually the better answer.
- Common stack, steady work: hire
- Rare stack, short need: augment
- Rare stack, permanent need: augment first, then convert to a hire if the terms allow
- Regulated work needing background checks: ask who holds the records
Ask who will manage them each day
Neither route manages itself. Someone reviews pull requests, writes tickets with acceptance criteria and answers questions before standup. If your only senior engineer is already stretched, a new person of either kind will drift.
Augmentation can include a technical lead who reviews code on your behalf. Hiring a lead is the alternative, and it takes longer. Count the hours you can truly give each week, then match the route to that number.
Price the exit before you sign anything
Ending a direct hire means notice periods, local labour rules and a hard conversation. Ending an augmentation means a notice clause and a handover. Read that clause now. Nobody is upset yet.
Whichever route you pick, ask for knowledge capture from week one: a runbook, a diagram of services and a list of credentials owned by your company. Write the exit terms down and keep them on the same page as the start date.
Hire or augment scoring sheet
Worksheet with five rows: length of need, ramp-up, skill rarity, management hours, exit cost. Each row has two columns, hire and augment, where you mark which route fits and note the evidence. A last block records the decision, names who owns it and sets a check-in for month three.
Open a blank worksheet to printQuestions owners ask
Is augmentation always more expensive than hiring?
Not always. The monthly rate looks higher, but you skip recruiter fees, notice periods and idle time between roles. Compare the full cost over the real length of the need.
Can an augmented engineer become a full-time hire later?
Sometimes. Check the contract for a conversion clause and any fee attached to it before the engineer starts, not after.
What if I need a whole team rather than one person?
Then you are choosing between a dedicated team and building your own. The same five tests apply, with management time weighing even more heavily.
Who owns the code an augmented engineer writes?
Your company should, from the first commit, in your repository and under your accounts. Put that in the agreement and check it after the first week.