Where backend engineer roles are actually advertised

Why the public job boards feel dead

If you're a backend engineer applying through LinkedIn or Indeed and hearing nothing, that's not necessarily about your CV. Those boards work reasonably well for high-volume, low-specificity roles - support, sales, junior generalist positions - where a keyword match is most of the job. Backend roles are the opposite: the requirements are narrow (a specific language, a specific data store, a specific scale problem), and the people who could actually assess a candidate are engineers, not the board's algorithm. Companies know this, so a large public board listing for a backend role is often either a legal requirement (some jurisdictions and some public-sector employers must post publicly even when they already have a preferred candidate), a wide net for a role that's genuinely hard to fill, or a listing that's already stale because someone was hired through another channel before it was taken down.

The practical effect: a backend engineer with five years of Go and distributed systems experience is competing on the big boards against a flood of full-stack and junior applicants using the same search terms, for a smaller number of genuinely open reqs than the listing count suggests.

Where the roles actually surface

Company engineering blogs and careers pages. Most companies with an engineering culture worth working in - the kind that writes about their architecture, their migration off a monolith, their on-call practices - post backend openings on their own site before or instead of the aggregators. If you already have three or four target companies, their careers page plus their engineering blog's RSS feed is worth more than any board.

Hacker News 'Who's Hiring' thread. Posted on the first weekday of each month. It's unmoderated in the sense that any company can post, but the audience is specifically engineers, and comments on listings sometimes surface useful detail (stack, team size, remote policy) that a formal ad won't. Threads are searchable by month, so you can go back and see which companies post repeatedly - that's a signal of sustained hiring, not a one-off.

Stack Overflow's job board was discontinued - worth knowing so you stop checking it. If you still have it bookmarked from a few years ago, it's gone.

Language and framework-specific boards and communities. Backend hiring clusters around stack. Go, Rust, Elixir, and Python each have community job boards or pinned channels (r/golang, r/rust, various Discord and Slack communities tied to specific frameworks or conferences) where companies post because they specifically want someone who already knows the ecosystem's idioms, not just the syntax. These get far less volume than LinkedIn and a much higher hit rate for relevance.

Remote-first boards - We Work Remotely, Remote OK - carry a disproportionate share of backend and infrastructure roles because backend work is one of the easiest functions to do fully asynchronously: no client-facing meetings, deliverables are code and design docs, and on-call can be handled across time zones with a rotation.

Wellfound (formerly AngelList) and Y Combinator's Work at a Startup for anyone targeting early-stage companies. Titles here are often broader - 'Founding Engineer', 'Backend/Infra' - because a five-person startup needs one person to own the database, the API layer, and the deploy pipeline, not a specialist in one layer.

Agencies, internal moves, and referrals

Specialist technical recruiters exist and, for backend specifically, they matter more than for many other engineering disciplines because the screening bar is high (system design rounds, sometimes a take-home involving a real data or concurrency problem) and companies would rather pay a fee than run a bad process themselves. These recruiters tend to specialise by stack or sector - fintech backend, gaming backend, infra/platform - and they often know about roles before they're posted anywhere, because they're briefed by the hiring manager directly. Finding them means looking at who's placing engineers at your target companies now: check the LinkedIn profiles of recent hires at those companies for 'introduced by' mentions, or look at who's active in the same language-specific communities mentioned above, since a decent specialist recruiter shows up there too.

Contract-to-permanent is a real and distinct pipeline in backend hiring, especially in finance and larger enterprises running legacy migrations. A contractor brought in for a six-month project to move a service off a monolith is often the internal candidate when the permanent role opens, because the team already knows their code and their debugging under pressure. If you're open to contract work, it's worth treating it as a route into a company rather than a detour from one.

Internal mobility is bigger than it looks from outside at any company past a few hundred engineers. A backend role advertised externally at a large tech company frequently has an internal candidate already identified - someone moving from a different team, or a new grad rotating out of a generalist programme into a specific backend org. The external posting still has to run, sometimes for legal or process reasons, sometimes because the company genuinely wants to compare, but the odds are different than the headcount number suggests. Referral schemes matter here for a mechanical reason, not a networking-platitude one: most large engineering orgs pay a bonus to the employee who refers a hire, so an internal engineer has a direct financial incentive to push your CV into a real inbox rather than the general queue, and referred candidates are frequently reviewed by a human before the applicant tracking system's filters ever run.

Titles that split the same job

Backend hiring is fragmented across titles that all describe overlapping work: Backend Engineer, Software Engineer (Backend), Platform Engineer, Infrastructure Engineer, and increasingly Site Reliability Engineer for roles that are backend-heavy with an operations slant. If you're only searching 'Backend Engineer' you're missing roles that are functionally the same job under a different label, particularly at companies where the platform or SRE team owns services rather than a pure product feature team. It's worth running your search across all of these and reading the actual responsibilities section rather than filtering on title alone.

Timing and hiring cycles

Backend hiring follows budget cycles more visibly than headline-generating roles do, because backend headcount is usually costed against infrastructure and platform budgets that get set annually. January through March tends to be the strongest window at companies on a calendar fiscal year, once new budgets are approved and last year's projects are either finished or cancelled. A second, smaller window often opens after mid-year planning, around July, particularly at companies re-forecasting against revenue. December and the first half of January are reliably slow - approvals are pending, hiring managers are on leave, and interview panels are hard to assemble. This doesn't mean don't apply in December; roles posted then have often been sitting unfilled and the process can move fast once people are back, with less competition because most candidates have paused their search.

Startups don't follow this pattern as cleanly - they hire when they close a funding round or land a contract that requires scaling the backend, which is why a startup's hiring can spike suddenly outside the usual calendar and then go quiet for months.

What to actually do this week

Pick three to five target companies and put their careers page and engineering blog into an RSS reader or a weekly manual check - this beats scanning aggregators daily. Read the next two Hacker News 'Who's Hiring' threads in full rather than skimming, and note which companies repeat across months. Join one or two communities tied to your specific stack (a language's Discord, a framework's Slack) and treat the pinned jobs channel as a primary source, not a backup. If you're open to it, contact one or two recruiters who specialise in your stack and sector rather than sending your CV to a generalist agency. And check your target companies' current engineers for internal referral possibilities before you apply cold - a referral from someone on the team is a different application than one through the portal.

jobmarket.pro reads adverts across these sources in full and prepares an application from your actual profile without inventing experience you don't have.