DEV Community

Discussion on: 5 Tips On Landing Your First Developer Job

Collapse
innercitypressure profile image
InnerC#ity

I'm really sorry, and I know this will be unpopular but I hire for a major and if I saw someone who is basically a React/Vue.Js front end developer with little experience calling themselves a "Software Engineer" I would move to the next resume in about 5 seconds. Rude and mean, yes, but true. Again, not trying to trash your post.

Collapse
emmabostian profile image
Emma Bostian ✨ Author • Edited on

I have a degree in computer science/software engineer so I'm more than qualified to list Software Engineer on my resume. Not to mention that a Software Engineer is not an accredited profession like a doctor or lawyer. So really not sure why you feel the need to gatekeep but.

Collapse
stereoplegic profile image
Mike Bybee • Edited on

Then it's probably not a very good environment for a junior (or any) dev to apply to. If that's the first impression you give, chances are not very high that the second, third, or fiftieth will be much better... But this is a teachable moment for both sides of the equation.

Candidates, it's true that you need to be more specific/accurate with your terms. It is also true that a lot of the crap you put up with in the hiring process is a sign of the company's overall culture. The first impression they make is likely the best you'll see from them. Make note of every red flag, and think long and hard about whether or not the job is worth it.

Recruiters, hiring managers, tech leads, architects, CxOs, etc.: If you truly believe you're working at a super-amazeballs company, you'd damn well better be able to prove it in your words and actions. If you're making candidates jump through pointless hoops, being unforgiving of rookie mistakes, and generally treating them like crap this early on, why should they believe a word you say about your "awesome culture"/"great place to work"/[insert generic amazing thing every company says about itself]?