14-day staff augmentation process: from brief to the first interview
Most staff augmentation firms will tell you they can hand you a shortlist "in a week or two." Some can. Most can't. The difference is what happens between the moment you send the role brief and the moment you're sitting across from someone worth hiring.
We're going to walk you through what happens across those fourteen days at Bonapolia — not because the number is magic, but because the failure modes hide inside the process. If you know what a competent process looks like, you can spot a lazy one when you see it.
Days 0–2: The brief, and the questions we ask before we start
Most role briefs are undercalibrated. Not wrong — undercalibrated. The client knows they need a senior React engineer. They don't know they need one who's shipped in a healthcare product, who can join a five-hour daily overlap with Boston, and who can survive a codebase that started life as a WordPress plugin.
We don't fix that with a form. We fix it with one 30-minute call, and one document you send us before it: a real job description if you have it. On the call we go through six things:
Stack, in the order it matters. React first, or GraphQL first? If a candidate is strong in one and weak in the other, which one do we walk away from?
Seniority, but in years shipped, not years employed. A senior engineer who's spent four years maintaining a legacy monolith is different from a senior engineer who's shipped three greenfield apps.
Time zone reality. Not "flexible hours" — the actual meetings the engineer will be expected to join.
Budget, in a range. We'd rather hear "€45–65/hour" than "competitive." Competitive rules nothing out.
The must-nots. Things that would end the engagement in month two. Language barrier? Previous experience with a specific product? Domain background?
Who else is in the loop. If the CTO briefs us but the VP Engineering runs the interviews, we need to talk to both — differently.
We're not doing this to be thorough. We're doing this because many shortlists get rejected downstream simply because the brief failed to capture something everyone assumed was obvious.
By the end of day 2, we've written up a one-page calibration doc and sent it back to you. It says what we heard. If it's wrong, we correct it before we start sourcing. If it's right, you sign off — and we're clear to begin.
Days 3–5: Sourcing
This is the part every agency claims to be good at. Most aren't. A common shortcut is database lookup: running a filter across an existing pool of available engineers and sending whoever appears to match. The candidate isn't calibrated to your role; the candidate is calibrated to the search filter.
Our sourcing is done for a specific brief, not from a pool. That means our recruiters spend the next three days on it: LinkedIn Recruiter, direct outreach, referrals from engineers we've placed before, and — sometimes — the passive candidates who've told us "not now, but talk to me in six months."
At this stage we're not screening. We're building a longlist. If the role is well-defined, that longlist will have 30–60 profiles by end of day 5. If it's a hard role (very senior, niche stack, hard time zone), it might be 15.
Days 6–8: Screening
Screening is where we separate ourselves from firms that send you fifteen CVs for you to filter. We do the filtering. That means:
First-round call, 20–30 minutes, human recruiter. Not automated. Not a form. A conversation. We're testing three things: does the candidate's current situation match what they claim on LinkedIn (departure date, notice period, expectations); can they communicate clearly enough for your standups; and do they actually want this role — not just any role.
Brief match, done by a person. Not a keyword filter, not an ATS score. We compare what's on the CV to what's actually in your six-point brief — the stack order, the years shipped vs. years employed, the domain background — and flag mismatches an automated match would let through. We don't pretend a recruiter can validate every technology as deeply as a specialist in that exact stack. What we can do is read the CV against your specific requirements instead of relying on a generic filter.
Salary and availability confirmed. The number they told LinkedIn six months ago isn't the number they'll accept today. We update both.
By end of day 8, we've cut the longlist to five or six real candidates. Two or three of those will make the final shortlist.
Days 9–12: The shortlist arrives
You get 2–3 profiles. Each with a profile note that says:
Why we think they match — specifically, against your must-haves and must-nots
The one thing they're weak on, and how much that matters
Their expectations (rate, start date, notice period, hybrid preferences)
The one question worth asking in the interview — usually the one that tests the weak point above, not a generic technical screen
The point of the profile note is to save you an hour of reading between the lines. If we send you three profiles and you can't tell them apart from the CVs alone, we've done the sourcing but not the calibration.
Days 13–14: Interviews start
Assuming feedback and interview availability move quickly, the first interviews start on days 13–14. You interview using your process, your standards, your loop. We stay out of it unless you ask us to schedule interviews, coordinate feedback or help resolve open questions on either side.
If all three candidates reach your final round and none receives an offer, that may be a signal that the brief, evaluation criteria or interview process needs recalibrating. We address it on the same call, not through a new statement of work.
The failure modes to watch for in someone else's process
If you're comparing us to another staff augmentation firm, ask them these six questions. The answers will tell you more than any pitch:
Have you personally spoken to every candidate on this shortlist specifically about our role?
If we reject all three, what does your day 15 look like?
How many candidates on this shortlist came from targeted outreach rather than an existing database?
Who wrote the profile note — the recruiter who screened the candidate, a sales rep or a template?
What's your ratio of engineers presented to engineers actually placed?
If our brief has a mistake in it, when do you tell us?
The good firms answer these directly. The mediocre ones will pivot to talking about their "process." The bad ones will send you a case study.
The point
Two weeks isn't a magic number. It's the timeframe we use to move from a calibrated brief to the first client interview. Relevant profiles may surface within three days; the rest of the time is spent verifying fit, expectations, availability and genuine interest before we put anyone in front of you. Speed matters. Sending unqualified CVs faster doesn't.
If someone promises a complete, interview-ready shortlist in three days, ask where those candidates came from and when they were last screened. Sometimes there's a good answer. Sometimes it's the bench.
If your last three shortlists came from firms who took two weeks and still missed — the days aren't the problem. The days between the days are.
About Bonapolia. We're a five-person staff augmentation team based in Lisbon. We build engineering teams for product companies and IT consultancies across Europe and the US. If you have a role that's been open longer than it should have — book a 30-minute call →.
Comments