I'm a senior front-end developer at my current job. I'm tired of working here but having trouble finding a new job. I have 8 years of experience, which includes having done some fullstack stuff with PHP in the past. I'm obviously qualified to be a senior front-end dev because uh.. I AM one... Problem is I don't have a CS degree and the interviews that I go on ask me questions about algorithms and data structures that I have trouble with. It seems a bit silly to me since these questions usually don't have much to do with frontend development (do backend devs get asked about how they would implement a mobile-first responsive design using CSS3 and HTML5?) but whatevs... it is what it is.<p>I'm planning on hitting the books (and coursera ) to brush up on this stuff, but I'd love to know if anyone else out there running into this same issue? If so, how are you coping with it?
Same here. 9yr of front-end dev/design experience and no luck. Applied for over 120 jobs (between 2015 & Today), and not 1 single interview. Nothing.<p>I have the education (Bachelors in Digital Design & Masters in HCI)...I have the experience & diversity of project work..... yet, I can't seem to land an interview out of 120 applications. What gives?<p>Perhaps it's my resume, perhaps it's my skill set, or the places I am applying, or maybe the market it flooded with dudes like you & me...I'm not sure.<p>It is very frustrating. I don't know what to do about it. Maybe get another degree....?
This is a problem in general. There were so many instances where the candidates were turned down because they couldn't write an algorithm from text book. The famous example being the guy who made Homebrew.<p>Reasons are below:
1) The existing assessment methods being used have been working for companies except in some cases.
2) There's no new way(yet) to assess candidates apart from the experience related questions. some companies use pair programming interviews which is by far the only different way which seems to be working.
3) Companies don't have time/resources to screen every candidate over phone, so they end up sending a link to hackerrank or some other programming questions site. And there are no custom assessments generated based on the candidate profile, rather these are very generic aptitude/algorithmic questions.
Don't look for a job, look instead for people you can help.<p>Get out of your bubble-- start attending meet-ups, conferences, industry trade events. Make new friends and contacts. Ask around who's doing interesting work? Who's struggling with technologies in your area of expertise? Who might need dev help?<p>That's the Old School informal search approach where you uncover those famous 'hidden jobs'. And it still works!
As a hiring manager I see a lot of resumes and I am frequently shocked at how poorly many candidates come across on their resume. There may actually be nothing wrong with your skillset or experience, but many can't make it show on their resume.<p>If for every position you did:<p>1. Feature enhancements in HTML, CSS and JS
2. Bug fixes and debugging
3. Wrote scripts, created new layouts etc etc<p>...then sorry, I am not even interviewing you because you don't seem to be thinking very critically about your job and what you are really here to do for the company.<p>Always express your resume in terms of accomplishments and what change you produced that affected the ultimate goal of the business.<p>So no, you didn't do "feature enhancements', you "Increased conversion rate by 5% after acting upon A/B test results. Streamlined the customer on-boarding experience by reducing clutter, pre filling forms, and cutting page latency."<p>After 8 yeas of experience and a brief listing of technologies you frequently work with somewhere on your resume, I don't really care what technology you used to accomplish the above. The fact that this is how you think about your role at the company is what matters to me. Any deficiencies or strengths will come out during the interview but I'll definitely invite you for a conversation.<p>And I agree, interviewing front end devs using algorithm puzzles are bullshit. A clear sign the company hiring doesn't know what it actually needs in a person but just do it because it's what Google does (or did).