Staff Engineer Staffing, Screened on the Written Record
Senior ICs who steer technical direction across teams, vetted on the design docs and reviews behind their calls.
KORE1’s staff engineer staffing service finds senior individual contributors who set technical direction across several teams, and screens them on the design docs, reviews and decision records behind their work before you meet them. We place staff engineers on direct hire, contract and contract-to-hire terms across more than 30 U.S. metros, and 92% of KORE1 placements are still in the seat a year later.
Last updated: September 10, 2026
A staff engineer req rarely opens because a team needs more code written. It opens because a decision keeps not getting made. Three teams are building three versions of the same service, the migration has been next quarter’s problem since last spring, and the one person everybody trusted to break a tie left in March. Nobody owns the call.
You need somebody who can settle those calls without a single direct report. They’re hard to spot. Nearly everything a strong staff engineer does happens in writing, and almost none of it survives onto a resume.
Staff and principal searches run out of our software engineer staffing desk, part of the wider IT staffing services practice. Still deciding whether the seat is really staff? Our guide to hiring a staff engineer works through that call, and the staff engineer salary guide carries the bands. What follows is how we find the person, and how we check them.
Staff Work Shows Up in Documents, Not the Commit Graph
Open the Git history of a good staff engineer and you may find less than you expected. Fewer merged pull requests. Some quarters, barely any.
That’s not a red flag. The job moved upstream.
Malte Ubl’s 2020 account of design docs at Google lays out what a big build gets written into before anyone starts it, from context and scope through goals and non-goals to the design itself and the alternatives that lost. Michael Nygard’s architecture decision records, proposed in 2011, cover the other end of the work with one short file per decision, holding its context, the call, the consequences and a status that eventually reads accepted, deprecated or superseded.
They write plenty of both. They review far more. And a resume flattens all of it into one line about driving architecture, a line every candidate has and far fewer can back up with the document that sits behind it.
Read the Margin Before the Proposal
This is the kind of design doc candidates reconstruct for us in the screen, rebuilt here as a composite with the company and the systems changed. The proposal is sound. Watch what three comments do to it.
Publish order events to a shared stream
Written by a senior engineer on the Orders team. Margin notes by a staff engineer on Platform.
Context
Checkout, fulfillment and billing each poll the orders table every thirty seconds. At peak the polling is most of the database’s read load, and every new consumer adds to it.
Proposal
Publish every order state change to a shared Kafka topic, and let each team consume at its own pace1. Retire the polling jobs in Q3.2 Changes to the event schema go through the owning team3.
Review · staff engineer, Platform
- 1Billing reruns invoices after an outage, and topic retention is seven days. What happens to the invoice run after a two-week incident?
- 2Q3 is fulfillment’s peak season. Do we want the cutover then, or both paths running until October?
- 3Which team owns the schema once three teams depend on it? Name one, or it belongs to nobody.
Three questions. No code. The design that shipped was the revision after them, and the engineer who wrote those comments never touched the implementation. On a resume that work is invisible, so our screen goes looking for it on purpose.
How We Screen a Staff Engineer Candidate
Every staff candidate we put in front of you has already spent an hour with a senior engineer from our own bench, someone who has written these documents and argued over them for years. Most of that hour goes to two of them.
The first is one they wrote, whether a design doc, an RFC or a migration plan, as long as it carried a real decision. We don’t want the file. It’s usually under NDA, and a candidate who forwards an employer’s architecture has told us something anyway, so we ask them to rebuild its shape out loud.
The tell is the alternatives. An engineer who wrote the doc can argue the losing option better than its own champion did. One who only read it remembers the winner.
The second is one they reviewed, and it’s where staff engineers pull away from very good seniors. We ask for the comment that changed someone else’s design, and what happened to the author after. Strong answers credit the author. They also admit which of their own comments turned out wrong.
Google’s published standard of code review tells reviewers to approve a change once it clearly improves the health of the system, even if it isn’t perfect. Staff engineers hold whole designs to that same line. Ask where they drew it.
Four Documents That Show Staff-Level Work
Few candidates have all four. Most strong ones can speak to three, and the missing one tends to be whatever their last company never bothered with.
A proposal other teams signed
Proof they can win an argument in writing with teams that don’t report to them.
The call, with its reasons
Written reasons are what stop the next engineer from reopening the same fight two years later.
An outage, told without blame
Good ones fix the system instead of the person, then chase the follow-ups across team lines.
The long move, actually finished
Walking a dozen teams off an old system over several quarters takes patience nobody can assign.
If a candidate has never written an incident review, ask why, and ask twice if the seat sits anywhere near site reliability engineering. Thepostmortem culture chapter of Google’s SRE book is a fair bar for what a good one holds, from impact and root cause to the follow-up work that stops a repeat.
Staff Engineer, Principal, or Engineering Manager?
Some reqs that arrive as staff searches shouldn’t be. We’d rather tell you on the first call than in week five. Every one of Will Larson’s staff archetypes, from tech lead to right hand, assumes a problem bigger than one team, and that’s the first test we run.
If the pain is people, with one-on-ones slipping, a team that needs hiring and coaching, and performance nobody is handling, you want a manager, and our engineering manager staffing desk runs that search. Several managers who need one leader is a director of engineering search instead. Hand a staff engineer a people problem and you tend to get a reluctant manager or a resignation.
A single bet the company will live with for years is a different case, say a platform rewrite or a new product architecture, and it may mean you’re writing a principal job. The principal engineer salary guide shows where that band starts. It isn’t a small step. If nobody owns technology strategy at all, that’s a CTO search instead.
And if the problem sits inside one team, a strong senior with room to grow is often the better hire. Cheaper, too.
| Seat | What they write | Whose decisions it moves |
|---|---|---|
| Senior engineer | Design docs for the system they own | Their own team’s |
| Staff engineer | Proposals and reviews that cross team lines | Several teams’, with authority over none of them |
| Principal engineer | Technical strategy, and the conventions other documents follow | The whole engineering org’s |
| Engineering manager | Hiring plans, team charters and performance reviews | The careers and delivery of the people who report in |
Different documents, different seat. When nobody on the hiring side can say which row the req belongs to, we sort that out before we source anyone.
How a Staff Engineer Search Runs
Four stages. The first one decides how long the other three take.
-
01
Name the cross-team problem
We start from the decision your org keeps failing to make and the teams it crosses. If we can’t name two teams, the seat probably isn’t staff.
-
02
Go where staff engineers are
Nearly all are employed. Few are looking. We work referrals, our own placement history, open-source maintainers and conference speakers before any job board.
-
03
Screen on the written record
A senior engineer from our bench spends an hour on one document the candidate wrote and one they reviewed. You get the notes.
-
04
Close on scope, then stay close
Staff candidates choose on the problem far more than the band, so the offer leads with the problem, the teams it touches and the decisions they will own, and the number comes second. We check in at 30, 60 and 90 days.
Direct Hire, Contract, or Contract-to-Hire
Same bench. Same screen. What changes is how long the problem lasts. Senior contract rates by specialty are in our 2026 tech contractor rate guide.
Direct hire
Most staff seats are permanent. The person gets more useful every quarter they spend inside your systems, and the fee is due once they start.
About direct hire →Contract
A bounded problem with an end date, like a database migration or readying a service for a known traffic spike. When the cutover ships, the contract ends.
About contract staffing →Contract-to-hire
For when the permanent seat is real but you’d like to watch the person run a design review or two before you commit. Both sides get a look.
About contract-to-hire →Common Questions
Is a staff engineer just a senior engineer with a better title?
Not when the title is used properly, because a staff engineer owns technical problems that cross team lines and settles them through writing and review, while a senior engineer owns one team’s system. Some companies hand it out as a retention bump. Plenty do. That’s why we check the scope of the work before we trust the word on a resume.
How do you vet a staff engineer whose best work is under NDA?
We ask for the shape of the documents, never the documents themselves. Candidates rebuild one design doc they wrote and one review they left, out loud, with the proprietary detail taken out. Engineers who did the work can do that easily without breaking any confidence, because the reasoning was theirs to begin with.
Do we need a staff engineer or an engineering manager?
Hire a manager when the problem is people and a staff engineer when it’s a technical decision nobody owns. Most ladders treat the two as peers with similar pay, so the choice comes down to the work, not seniority. If both problems are real you probably need two hires, and our engineering manager staffing team can run the second search.
How long does it take to hire a staff engineer through an agency?
Six to twelve weeks from a settled req is typical. Our 17-day average covers IT roles at every level, and staff runs longer because the people who fit are nearly all employed and weighing other options. The weeks go to finding and moving those people, far more than to screening them.
Can we hire a staff engineer on contract for one project?
Yes, and for a bounded problem it’s often the better buy. A database migration, a platform consolidation or a scaling push with a fixed date suits a contract staff engineer who leaves when the cutover ships. If the problem keeps producing new decisions after that, you have a permanent seat on your hands.
Where do staff engineers come from if they aren’t applying?
Mostly from people who already know their work. Referrals from engineers we’ve placed, former colleagues, maintainers of the open-source projects your stack depends on and speakers at events like KubeCon or LeadDev StaffPlus fill far more of our staff shortlists than job boards do.
What should a new staff engineer do in the first 90 days?
Read, listen, then write one thing that matters. The first month goes to decision records, incident reviews and design reviews, learning who actually decides what. By day 90 they should have written a document that settles a question the org had been avoiding, and that tells you more about the hire than the interview did.
Bring Us the Decision Nobody Is Making
Tell us which call keeps stalling and which teams it touches. We’ll tell you whether it’s a staff seat, and what the search looks like if it is.
Talk to a Staff Search Recruiter →