Problematic job titles I clarify for recruiters, fellow developers, and curious folks all. While job titles are routinely inaccurately used, one can do a better job of it if one knows their problems:
- Senior Frontend Developer implies I’ve 3+y of reactJS, the only buzzword all frontend roles ask for, regardless of actual use, thus a weeder word but avoid weeder job applications because they’re the types that’ll say they’ll hire immediately when they find the right candidate yet have no idea what candidate they want.
- Senior implies I’m 3-5+y experienced in everything which is untrue. I recommend a more careful reading of my resume for such folks.
- Engineer imples I can or want to do 110% backend or can invent algos to solve the unsolvable, both of which are untrue. Developer is more implementing given algos while an engineer does more algos. Firms need to be careful of how much problem solving they’re asking of developers.
- Fullstack may imply I’ll do the work of 2+ developers when actually I’m still only 1 person. The notion that tech efficiency could eliminate multiple roles in short order isn’t justified per management studies often seen in credible management publications.
Next time, we’ll discuss this 10x phemon which is bunk.