Running a focused software engineer job search
A good engineering job search is a filtering problem more than a volume problem. Decide what you want, read postings for the real requirements, and put your effort into roles you can win.
Job search4 min readUpdated
On this page
Most engineers start a search the same way: open a job board, search for senior software engineer, and apply to anything that looks roughly right. A week later they have thirty applications out, no clear sense of which ones fit, and a few recruiter emails about roles they don't remember applying to.
This guide lays out a more deliberate approach for mid-level through staff engineers across mobile, backend, frontend, platform, and full-stack work. It takes a little more thinking up front and much less wasted effort later.
Define the target before you search
Write down, in one place, what you are looking for. Be literal. Interesting problems isn't a filter. These are:
- Role family: backend, iOS, Android, frontend, platform or infrastructure, full-stack.
- Level: the title you're targeting and the scope you want, such as owning a service or setting technical direction across teams.
- Stack: languages and systems you want to work in, and ones you'd rather avoid.
- Location and work mode: remote, hybrid, on-site, and which time zones you can work in.
- Work authorization: where you can work without sponsorship, and where you'd need it.
- Compensation floor: the number below which you won't move, stated as base or total, in one currency.
- Hard no's: on-call load, industries, company size, or anything else that would make you decline an offer.
Alex Rivera, a backend engineer with six years of Go, might write: senior or staff backend, Go or Rust, remote within US time zones, no sponsorship needed, base above a set floor, no ad-tech. That fits in two lines and eliminates most listings before any reading starts.
Read job postings for the real requirements
Job descriptions mix three kinds of statements, and treating them the same is where most mismatched applications come from.
| Kind | Example | How to treat it |
|---|---|---|
| Hard requirement | Must be authorized to work in the UK. 5+ years building backend services. | If you clearly don't meet it, skip |
| Core skill | Strong experience with Go and PostgreSQL. | Meet most of these, or have close equivalents |
| Nice to have | Familiarity with Terraform a plus. | Useful signal, not a filter |
Watch for blockers hidden in the middle: security clearance, a required on-site location, a specific time zone, or a legal requirement you can't meet. One blocker outweighs ten matching skills.
Shortlist with reasons, not scores
For each promising listing, write down why it's on the list: which requirements you meet, which you don't know about, which are gaps. A note like Go ✓, PostgreSQL ✓, Kafka ?, 8+ years ! (I have 6) tells you far more than a 78% match. Percentage scores hide the reasoning. Two roles with the same score can be a near-certain fit and a hard no.
Sort the shortlist into three buckets: strong fits where you'd apply today, possible fits where one or two things are unclear, and skips. Put most of your effort into the first bucket. For possible fits, a short note to a recruiter or a look at the team's engineering blog often resolves the unknowns.
Be honest with the possible bucket. If a posting asks for eight years and you have six, that's a gap, not a disqualifier, and many teams flex on years for the right experience. If it requires on-site work in a city you won't move to, that's a blocker, and no amount of skill overlap changes it. The difference between the two decides where your evening goes.
Where to look
- Company career pages. Many listings appear here before they are syndicated elsewhere, and applying directly avoids third-party redirects.
- Your network. A referral from someone who has worked with you is still one of the strongest ways into a process.
- Engineering-focused boards and community hiring threads. Often higher signal than general boards.
- Recruiters. Useful when they specialize in your area. Be clear about your target up front.
Apply carefully, in batches
Batch your applications into two or three sessions a week instead of trickling them out daily. In each session, go through the good fits, fill each form, write the narrative answers properly, and check everything before submitting. Tools can take the typing off your hands. They shouldn't take the judgment. The guide to choosing a job application tool covers what to watch for.
Track outcomes and adjust
Record every application: company, role, date, CV version, and status as it moves through screen, interviews, offer, or rejection. After three or four weeks, patterns show up. If platform roles at mid-size companies lead to screens and product-backend roles at large companies don't, adjust your targets. If nothing leads to screens, the problem is usually role selection or the CV, not volume.
Keep the search sustainable. A steady, well-targeted search over six to ten weeks usually beats a burst of mass applications followed by burnout. The application tracker guide has a structure you can copy.