Hire a software engineer from the people already shipping code
To hire a software engineer, search for people already doing the work instead of waiting for applicants, judge them on debugging, design trade-offs and code review, and keep the loop to about 4 stages. BLS counts 1,905,400 US software developer, QA and tester jobs, so the pool is deep but mostly employed.
Where are the software engineers worth hiring?
Mostly in jobs. BLS projects about 106,100 openings a year across software developers, QA analysts and testers, against 1,905,400 people already employed. A job post reaches the small slice looking this week. The engineer who rebuilt a billing service last year is not reading it, so you have to go and find them.
Titles help less than you'd hope. O*NET's reported titles for the same occupation include Software Engineer, Software Developer, Software Development Engineer, Application Developer and Systems Engineer. Search on the system someone built, the stack they built it in and the scale it ran at, then let the title break ties.
Which sourcing channels work for software engineers?
Each channel returns a different slice of the market. Most teams that hire well run 3 of these at once and stop relying on the last one.
| Channel | What it finds | Watch out for |
|---|---|---|
| Profile search across public profiles | Employed engineers by stack, system and seniority, including people who never post | Profiles lag reality by months; confirm the current role in the first message |
| GitHub and open source | Real code, review comments and how someone handles a pull request discussion | Most professional work is private, so silence on GitHub proves nothing |
| Hacker News "Who wants to be hired?" thread | A monthly thread of engineers who state stack, location and remote preference themselves | Skews toward startups and US time zones |
| Conference talks and engineering blogs | People who can explain a system well enough to present it | Speakers get a lot of messages; yours has to name the talk |
| Referrals from your own engineers | Pre-trusted candidates with a known working history | The pool looks like your current team unless you widen it on purpose |
| Job posts | Active applicants, fast | High volume, thin signal; the strongest engineers rarely apply cold |
Search strings for a software engineer, Boolean and plain English
The same search 3 ways. Swap the stack and domain for yours. The Boolean misses anyone who described the work in other words; the brief is read as meaning.
BOOLEAN (profile search or LinkedIn)
("software engineer" OR "software developer" OR "software development engineer" OR SDE OR "member of technical staff")
AND (TypeScript OR Node.js) AND (Postgres OR PostgreSQL)
AND (payments OR billing OR checkout)
NOT (intern OR recruiter OR "talent acquisition")
GOOGLE X-RAY
site:linkedin.com/in ("software engineer" OR "software developer") TypeScript Postgres payments -recruiter
GITHUB X-RAY
site:github.com "TypeScript" "Postgres" "billing" location:"Berlin"
PLAIN-ENGLISH BRIEF
Software engineer with 3 to 6 years building web products in TypeScript and Postgres, ideally on payments or billing, at a startup or scale-up. Remote within UTC minus 1 to UTC plus 3.
From a written brief to a ranked list you can check
A plain-English brief is read into filters you can see and edit before any result appears.
In The Cognitive the brief above becomes editable filters, then a search across ~900M public profiles. Each person is judged against your must-haves; anyone who misses one drops below the people who meet them, and nobody is removed. Every card opens with a "Why this match" line traced to the profile.
What does the software engineer market look like in 2026?
US federal figures, the latest BLS published. Use them as the floor of a pay conversation, then check the band against your city and stage.
| Measure | Figure | What it means for you |
|---|---|---|
| Median pay, software developers (May 2025) | $135,980 a year | Half of US software developers earn more than this |
| Median pay, developers plus QA and testers (2025) | $134,040 a year, $64.44 an hour | The group figure most salary pages quote |
| Highest-paying industry listed | Software publishers, $164,550 | Product companies pay above the median; expect to compete with them |
| Jobs in 2025 | 1,905,400 | A deep pool, nearly all of it employed |
| Projected growth, 2025 to 2035 | 10 percent | BLS calls this much faster than average |
| Openings per year | About 106,100 | Includes replacements, not just new seats |
Source: BLS Occupational Outlook Handbook, read 5 October 2026.
What to assess in a software engineer, and what a strong answer shows
5 competencies decide most software engineer hires. Ask about something the candidate personally did, then push one level deeper.
Tell me about the hardest production bug you tracked down. What did you see first?
A path from symptom to root cause they walked themselves, such as heap snapshots that exposed a leak after a deploy, plus the fix and the regression test.
You said the logs pointed to the database. Which query was it, and how did you prove it was the cause?
Pick a datastore decision you made for a real service. Why that one?
The access pattern, the consistency need and what they would revisit at 10 times the load. Postgres over DynamoDB is fine; the reasoning is the point.
What would make you change that decision today?
Describe a pull request you pushed back on. What exactly worried you?
A specific concern, such as a missing index or an unhandled error path, and how they settled it with the author without pulling rank.
Talk me through making a slow piece of code faster.
Complexity reasoning out loud, such as swapping a nested loop for a hash map lookup, and an honest view on when the simple version was good enough.
Name a feature you carried from ticket to production. What happened after launch?
The flag rollout, the metric they watched and the change they made once real users arrived.
What did the metric do in the first week, and what did you change because of it?
Keep one coding round
A conversation shows whether someone did the work and can reason about it. It does not show them typing code. Keep a short pairing or code-reading session with one of your engineers for the finalists.
A software engineer hiring process in 6 steps
4 candidate-facing stages after sourcing. Every extra round costs you engineers who are also talking to other companies.
- Write the brief with the hiring manager Name the system this person will own in the first 6 months, 3 must-haves and what you will accept instead of a degree or a framework name. "Owns the billing service and ships the move off the legacy gateway by Q2."
- Source from 3 channels at once Run a profile search, a GitHub or open-source pass and referrals together. Shortlist on evidence of the system, not on logos.
- Reach out about the problem Name the specific thing in their work that made you write, then the problem they would own. Follow up twice; many engineers answer the second or third message.
- Run a structured first interview Cover the 5 competencies above with a fixed scorecard, so 2 interviewers can compare candidates on the same criteria.
- Pair on real code with an engineer 60 to 90 minutes on a small, realistic task or a code-reading exercise. Score it alone before the debrief.
- Debrief, decide and close in a week Collect independent scores first, then discuss. The hiring manager makes the offer call personally; engineers accept offers from the person they will work for.
How The Cognitive fits a software engineer search
Each criterion scored 1 to 5, with overall written feedback, the transcript and the recording.
We cover steps 2 to 4. Sourcing finds the engineers, then each one you invite takes a live, two-way AI video interview of 10 or 20 minutes at a slot they book. The rubric is fixed for the role and the questions adapt to each answer, probing up to 5 resume claims.
Outreach that software engineers answer
Do
- Open with one detail from their work: a repo, a talk, the system on their profile
- Say what the first 6 months own and who they would report to
- Put the salary band in the first message if you can
- Send a short second note a week later with one new fact
Do not
- Lead with "we are hiring rockstars" or a list of perks
- Paste the whole job description into a first message
- Ask for a CV before a 15-minute conversation
- Stop after 1 message and decide the market is empty
More for hiring software engineers
Software engineer job description · Software engineer interview questions · AI interviewer for software engineers · AI sourcing tool · Best technical recruiting tools · Free Boolean search generator
Frequently asked questions
How much does it cost to hire a software engineer?
Pay is the largest cost: BLS put the May 2025 median for US software developers at $135,980 a year, and software publishers paid a median of $164,550. On top come your sourcing tools, interviewers' time and any agency fee, which is usually a percentage of first-year salary. Sourcing yourself and keeping the loop to 4 stages is what keeps the non-salary part small.
Where can I find software engineers to hire?
Search profiles of people already employed, then add GitHub and open-source contributors, the monthly Hacker News "Who wants to be hired?" thread, conference speakers and referrals. Job posts find active applicants only. In The Cognitive you write the role as a brief and search ~900M public profiles, with an "Open to work" badge and tenure per role on each person.
How long does it take to hire a software engineer?
There's no reliable public figure for software engineers specifically, so plan from your own process. The time goes on 3 things: building the shortlist, waiting for replies and scheduling interviews across several busy engineers. Sourcing from day 1, running a structured first interview the candidate books themselves and deciding within a week of the final round removes most of the waiting.
What should a software engineer interview include?
A structured first interview on debugging, design trade-offs, code review, algorithmic reasoning and ownership, then a pairing or code-reading round with one of your engineers, then a conversation with the hiring manager. Score each stage against written criteria before the debrief, so the loudest interviewer does not decide.
Can an AI interview replace the coding round?
No, and we don't claim it does. The Cognitive runs a live, two-way AI video interview that tests how an engineer reasons and whether they did what their resume says. It is not a coding environment. Use it to decide who reaches your pairing round, so your engineers spend that time on the strongest people.
Should I use a recruiting agency to hire software engineers?
An agency makes sense for a one-off senior search where you have no sourcing time at all. For repeat hiring, the fee recurs on every hire while the work, finding employed engineers and getting a reply, is something an in-house recruiter can run with a sourcing tool and a written brief.
How much does The Cognitive cost for hiring engineers?
AI Sourcing and AI Interview each start at $99/month. Plans are monthly and you can cancel anytime. Each interview plan includes a monthly interview allowance, and extra interviews come from a top-up. Sourcing credits go on candidates returned and on contact reveals, and a reveal is charged only when a value comes back.
Can I try The Cognitive before paying?
Yes. Every account starts with a free trial that includes 100 sourcing credits and 2 AI interviews, so you can run a software engineer search and interview 2 people before choosing a plan. Sign up at app.thecognitive.io/signup.
Explore: AI interviewer for software engineers · Software engineer interview questions · Software engineer job description · Hire backend developers · Pricing