Where are all the senior front end engineers?

I'm a senior FE engineer in Singapore, been doing FE since 2000, here's what I think:

1. Job descriptions and interviews now are skewed towards "full-stack" or backend. Most interviews are lacking or outdated due to the fast and volatile nature of FE.

2. Literally no career progression if you're specialised in FE. Most BE or "full-stack" devs will be given a chance to become principal engineers, tech leads, engineering managers, CTOs, etc. I've seen folks with "FE Team Lead" titles but never goes beyond that.

3. FE is a subconsciously looked-down field. Neither a designer nor an engineer. Product/design team won't involve you in meetings (but will treat you like a code monkey). BE/"full-stack"/API engineers will think your job is easy and keep throwing business logic stuff to FE.

I wouldn't say it's just FE - many of my recruiter friends have this problem with ANY senior developer. It's low supply and low turnover.

Additionally, it could be your job posting not being enticing enough to get hits. I'm a senior FE dev and I saw some pretty bad job postings (hostile programming assessments, unpaid take home assignments, a circus of interviewing rounds). If you don't have your salary listed, that could be the issue too.

I can't speak for everyone here, but I'll take 2nd or 3rd best in compensation if the interviewing process isn't a 3-ring circus. ie, I will actively drop out to protect my time from bad interview pipelines.

My last two gigs were less than 2 hours of total conversation before a contract got signed, as an anecdote. Hell, I had one that was a 23 minute phonecall (it was awesome!). Some people just know how to hire someone after they look at a good LinkedIn or GitHub profile.

Just my 2 cents. As a selfish plug, you could talk to freelancers who have the expertise you need so stuff gets done in the meantime. It's not ideal, but at least you'd have the help...

They have jobs already. I don't know if you're US-based, but our company is having the same issue with off shore devs.

I've been banging my head for the past few weeks trying to get our management team to understand off shoring is by no means an easy solution any more. We've traditionally hired off shore with good success, and management thinks it's still easy. However, our recruiters have been fairly quiet these past few months, and the candidates that we're getting are a lot less experienced than what we want. You absolutely cannot just waltz into a developing country with a US job posting and expect candidates lining up. Everyone did that, and now we're in a situation where the competition is insane. Off shore costs have skyrocketed, and, addressing your second point, you have to have interesting work for them.

I qualify as a senior FE engineer but the last time I was looking finding open positions for that exact title was difficult. I don't really mind full stack (I guess it would depend on the backend) so I normally take those jobs as I'm more flexible to the company that hires me. Also I prefer smaller companies <100 overall and <10 developer so finding overlap with a small company that also wants someone only focused on the frontend is hard. But, like I said, I don't mind full stack so it's worked out well for me and I get a good amount of frontend work (a lot of it greenfield).

Also if you aren't posting a salary you might be losing people who gloss over the posting since FE isn't always respected/paid well. I think that factors into my gravitating to full stack work, I absolutely love FE work but finding a company that will let me do that and pays well AND is small has been... challenging.

It's hard to give more advice without seeing something like a job posting. I will say, don't limit yourself by framework (but DO say what you use, if it's not greenfield). I prefer Vue but I've built sites/apps in Angular and I have no doubt I could pick up React if I needed to. A "real" senior FE developer isn't going to balk at any of the big 3 frameworks (or minor ones but be ready to explain why you picked something other than Angular/React/Vue).

Most senior level hackers are being hired through very shortened interview cycles. Often a phonecall and that's it. The old school way of a recruiter reaching out, then a screening, then a tech round is falling behind.

Low supply of talent, low supply of companies worth working on their product.

Usually the existing frontend is a mess and the company has no intention of scrapping it.

Why shoot yourself in the foot with such a ball of stress? Current FE's are happily married.

If an enticing startup came along, maybe. But in this environment it better be REAL enticing.

I'm a full stack dev that's also somehow excel at react (who also don't mind frontend jobs at all), and also have some interviews for senior front end openings in recent weeks.

The job title senior front end is too broad IMO. Since most of the time at early 2000, if we're talking about front end we'll usually deal with complex css, design, and ui/ux. What's worse is usually that skillset is not in align with react at all, since react is more into programming than design.

IMO, it's easier (and more accurate) to search for fullstack nodejs programmer who also know react (or vue, etc).

I'm surprised at some of the responses suggesting senior FE engineers are in demand, because I've noticed that most job postings these days seem to be full stack. My current job is full stack, but like some others have said, the focus seems to be on the back end.

I think it doesn't help that a lot of places follow FAANG interview style and go for algo/data structures and system design questions.

I think as you grow in your career you'll tend to specialize rather than generalize. You get really good at a few things, rather than somewhat good at lots of things. The "Senior FE" roles are fewer but more specific. Now and then I see listings for "Performance Engineer", "Accessibility Engineer", and "Infrastructure Engineer", but on further inspection these are actually Senior Front End roles, but not in title.

Recently I went through a generic Sr FE interview at Google (still waiting to find out if I've been ghosted after). There were 5 or 6 rounds, and I feel I totally bombed one of them, excelled at one, and did okay at the others. I think that's acceptable at this level. I went through a "Performance Engineer" interview loop at another company, and the rounds were all specific to the role. I had a much better experience in that interview.

> Most companies don't have interesting FE work

While true, I think it's a bit more nuanced than that.

The most attractive companies have at least 2 of 3 qualities that make front-end work significantly easier:

  - engineering permission to use sensible tooling (typescript, openapi type generation, etc)
  - strong / focused product team (stable roadmap for project requirements)
  - modern ux designers (able to design a component library & can easily communicate changes (Figma))

I've noticed that companies that get this right tend to have healthier work cultures & deliver on expectations without stress.

Companies that don't tend to have front-end work defined by a sense of impermanence, lingering technical debt, and pain.

All good FE engineers are happily employed and enjoy doing FE stuff. Source: am a FE engineer.

Management in my case. I lead a few teams now after having been mostly responsible for just the FE portion of things. I’ve always been a full stack dev but being the lead for FE team meant working a lot with business and presenting things, taking feedback and communicating back to devs etc. So moving up was a natural thing for me. Just a lot of meetings now, unfortunately.

I’ve had no problems hiring senior devs across the board - FE, BE, DBA, DevOps, etc etc. The existing ones recommend their friends so I imagine it’s a company culture thing as well.

Blame this on the low bar to entry. HTML, CSS & JS are relatively easy to learn. So you have everyone applying for these jobs and we’ve reached peak front end candidates.

The real trick is to find those who use that tech in new and interesting ways. Those who push the envelope.

Maybe try check the recruiting funnel/pipeline. It's possible majority of them got dropped at the initial interview stage where they were asked questions not relevant to their expertise, so by the time the funnel reaches you it's just drips.

I would be considered a senior FE engineer, and I do interviewing at my employer. I recently interviewed an individual for a L6 role (senior engineer) who didn't know how to listen for clicks on a . What's going on?

Senior FE is high demand, low supply position. In a similar boat for hiring, but I think it helps when you are able to present your company as one that values FE (a good website for starters).

probably no one wants to deal with all the headache that comes with it tbh. my experience, management just always fucks it up. the first org i ever did FE at didn't even have daily standup or any kind of scrum or agile processes... no jira. no version control. no separate environments. no nothing. and then they blamed devs for not delivering when business/ownership couldn't even define what we were supposed to be delivering.

> Where are all the senior front end engineers?

There's heaps here in Australia, G'day!

I've been tinkering with the idea of switching to FE, preferably, full stack second.

I'm a founder of CIS Force - freelance platform for pre-vetted high quality software devs. We have lots of great FE engineers, happy to recommend you some great matches - please contact me dlazarev@cisforce.com

i think it’s more of the second point you mentioned. additionally, pay seems stagnant for senior frontend positions as opposed to backend.

We all got promoted, sorry.

Hello, someone calling?

Because senior engineers realize what a dumpster fire the modern web is and then don't want to work on it since they can make more doing backend feature dev just as easily if they learn another skill set / language.

There is also a limit to what you can do in a browser. Many folks get tired of working in this environment and want to branch out and explore more areas of programming / application development.

Also, the constant churning of overengineered tooling, libraries, and frameworks in the modern web ecosystem is another big turn off for a lot of folks.