Where frontend engineer roles are actually advertised

Why searching "frontend engineer" on LinkedIn undersells you

A lot of frontend hiring happens under titles that don't contain the words "frontend" or "engineer". Companies building design systems — Shopify's Polaris, Atlassian's design system, GitHub's Primer — hire specifically for that team, often under "UI Engineer" or "Design System Engineer". Vercel, Linear, Stripe and a growing list of product companies use "Design Engineer" for a role that sits between frontend engineering and product design: someone who can ship a React component and also judge whether the spacing is right. Other reqs say "Product Engineer" and mean a full-stack-leaning frontend role where most of the work is still UI. "Web Engineer" and "JavaScript Engineer" turn up too, usually at companies that don't separate frontend from backend cleanly.

If your saved search is just "frontend engineer", you're missing all of these. Search separately for the title variants that match your actual stack — React, Vue, Angular, Svelte — and for "design system", "UI platform" and "frontend platform", which are their own sub-specialism with less competition than generalist frontend roles.

Where the postings actually live

Generic boards (LinkedIn, Indeed, Glassdoor) carry frontend roles, but a meaningful share of what you see there is a repost of a requisition that's already progressed internally, or one an ATS is required to keep visible for a set period regardless of pipeline status. Neither of those facts is something a board discloses, so treat a listing's age and the "applicants" count as weak signals at best.

The more useful places are narrower:

• Company careers pages, direct. Frontend-heavy companies — those with public design systems or component libraries — often list frontend and design-engineering roles on their own site before or without syndicating to boards. If there's a company whose product you use and admire the frontend of, check their careers page directly rather than waiting for it to surface elsewhere.
• Hacker News "Who is hiring" — a monthly thread, first weekday of each month, where companies post roles directly and candidates reply publicly or by email. It carries a genuine mix of frontend roles, particularly from smaller product companies and startups that don't want to pay board or agency fees. Searching the thread archive for "React", "Vue" or "frontend" by month is a real, low-friction source.
• Framework- and stack-specific boards. Vuejobs.com lists Vue-specific roles. Awwwards Jobs skews toward frontend and creative-development roles where visual craft matters as much as engineering. Remote-focused boards like We Work Remotely and RemoteOK carry frontend and JavaScript tags that are worth filtering on directly rather than browsing the general feed.
• Stack Overflow Jobs no longer exists — it closed in 2022 — so if you're following an old list of "where developers look for jobs", drop it.

None of these will have as much volume as LinkedIn. That's the point: lower volume, higher relevance, and postings that haven't already been seen by everyone else with your exact skill set.

Agencies, and what they're actually doing

Frontend hiring, especially contract work, runs through specialist tech recruitment agencies more than most engineers assume. Two mechanisms matter here.

First, contingency recruiters work a requisition alongside the company's own pipeline and only get paid if their candidate is hired. They tend to work broad frontend reqs — React, Angular, general JavaScript — and will often approach you before the role is posted publicly, because their commercial incentive is to fill it fast, not to make it competitive. If a recruiter contacts you about a role you can't find posted anywhere, that's not unusual — it may not be public yet, or may never be.

Second, contract and interim agencies specialise in short, defined pieces of frontend work: a framework migration (Angular to React, or a jQuery-era codebase to a modern SPA), a design-system build, a performance remediation ahead of a product launch. These roles rarely appear on general boards because the client wants someone who can start in weeks, not after a multi-stage interview process advertised for a month. If you have migration or design-system experience specifically, registering with agencies that handle contract frontend work is a more direct route than public boards for that kind of engagement.

Neither type replaces applying directly. But if your CV doesn't surface for contingency recruiters at all — no LinkedIn presence, no GitHub, nothing searchable — you're cut off from a channel that moves roles before they're public.

Internal movement, and how frontend engineers actually get noticed

A fair number of frontend hires are not external hires at all — they're backend or QA engineers moving into a frontend team internally, or a contractor converting to permanent after a migration project. That reduces the number of genuinely external openings relative to what the public sees, and there's no published figure on how much, so take this as a reason to expect fewer live external roles than headcount growth would suggest, not as something you can quantify.

Where external hiring does happen through something other than an application, it's usually visibility-driven, and frontend has specific visibility channels other engineering disciplines don't:

• Open source contribution to the frameworks and libraries themselves. A merged PR to React, Vue, Svelte, or to a widely used component library, is a concrete, checkable signal that hiring managers at companies using that stack do look at. Your GitHub activity on a project the team depends on carries more weight than a generic portfolio repo.
• Conference and meetup talks. React meetups, VueConf, CSSConf, SmashingConf and similar events are small worlds — speakers and active attendees get approached directly by engineering managers who were in the room. This isn't networking advice in the abstract; it's that hiring managers in this field specifically attend these events looking for people, and a talk or a well-argued conference-hallway conversation about, say, hydration strategy or Core Web Vitals functions as an interview you didn't apply for.
• A visible portfolio that demonstrates judgement, not just code. For frontend specifically, a live site with clean Lighthouse scores, sensible accessibility (WCAG 2.2 conformance, not just an aria-label sprinkled in), and a component built with Storybook or a similar tool tells a hiring manager more in five minutes than a CV bullet point does.

Timing and seasonality

Frontend hiring follows the broader tech hiring calendar rather than having its own separate rhythm, but a few patterns are worth knowing. New budget typically lands in January, so postings pick up from late January through to around May. Hiring slows in the run-up to and during major holiday periods — late November through the New Year in the US, and July–August across much of Europe when teams are down to skeleton staff and hiring managers are on leave. September, where you are now, is usually one of the stronger windows: budgets are known for the rest of the fiscal year, teams are back from summer, and there's a push to fill roles before the next slowdown in December. That doesn't guarantee anything about a specific company or team, but it's a reasonable reason not to assume a quiet week reflects your own application quality.

What to do with this

Set up separate saved searches for "design engineer", "UI engineer" and "frontend platform" alongside "frontend engineer", on whichever boards you use. Check the Hacker News "Who is hiring" thread on the first weekday of the month and search it by your stack. Go directly to the careers pages of two or three companies whose frontend you rate. If you do migration or design-system work, look at contract agencies that specialise in it rather than only general tech recruiters. And keep something a hiring manager could actually find — a merged PR, a talk, a live site with good performance and accessibility scores — because in this field that's a channel in its own right, not just a nice-to-have on a CV.

If what's slowing you down is the sheer number of near-miss titles and adverts to read closely for fit, jobmarket.pro reads each advert in full against one candidate profile and says where the fit is and isn't, before an application goes out.