21–30 of 51 posts
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.
Those would be 98% of your staff.
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 pas…
All good FE engineers are happily employed and enjoy doing FE stuff. Source: am a FE engineer.
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.
What? No, the real trick is to find someone who is reliable, honest, consistent and well rounded. Those would be 98% of your staff.
There's heaps here in Australia, G'day!
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?
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.
All good FE engineers are happily employed and enjoy doing FE stuff. Source: am a FE engineer.
I dunno. I'm a FE dev and have been for 20 years. I'm finding more and more that FE jobs are webpack and dependency management jobs. Far from building bespoke user interfaces or developing new patterns. The design side of web development has grown boring thanks to bootstrap and bootstrap influenced design libraries. All the fun challenges of the early aughts are gone and all that's left is figuring out why library A…
But it's not just the library management that kills me. It's the complete lack of any form of respect I see time and again in regard to FE. BE folks say something is hard and will take time? They get all the leeway they need. FE says something is hard and will take time or just flat out want to do it right? Now you have 20 people from the marketing department crying foul and claiming the FE team is just lazy. I tell them the specs are incomplete and I get told to just deal with it and make it work. I ask for clarification of interactions and everyone expects me to tell them how the thing they designed should function for a user. I used to love FE because it was the "fireworks"... but lately it just feels like a lot of people have no respect for the craft at all.
At the end of the day I think my organization would kill to just have a FE they could manage like Wix and do away with us. So on to something new...
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.