DEV Community

Danielle Heberling
Danielle Heberling

Posted on • Originally published at danielleheberling.xyz on

Dear New Code School Grad

Diploma

Photo by RUT MIIT on Unsplash

Over the years, many people have come to me for advice on doing a career change into software engineering. Here are my thoughts written down relevant to doing this in the year 2024 in the United States.

Who am I?

I graduated from a code school in 2016 in the United States and have been employed as a software engineer ever since. I’ve held both formal and informal mentor titles. The formal ones were through side jobs working for code schools or being a mentor for nonprofits that help folks break into tech. The informal ones are via warm intros from network connections with recent code school grads seeking help.

My goal in writing this

I want you to succeed. We need more people in this industry that bring diverse life experiences to make our products truly reflect the public that we serve.

There are a lot of folks on the internet and in real life that want to sell you the idea that a career switch and learning how to code is easy. I’m here to tell you it is not.

Trends in 2024

The hiring market has evolved since I was looking for my first software job in 2016. It is much more challenging now. Here’s a list of trends that I’m seeing in my part of the industry:

  • More code schools exist than did in 2016
  • Most of these code schools teach full stack JavaScript with an emphasis on the frontend (react in particular)
  • Due to higher enrollment in these programs 👉🏻 more people are looking for their first job as a full stack JS or frontend developer
  • Many hiring managers are only interested in hiring people who have experience. It doesn’t seem good enough to be “senior” anymore, lots are looking for “staff” or higher levels (what these levels actually mean can vary from company to company)
  • Due to “macroeconomic conditions” many companies are conducting layoffs including software engineering staff

Unsolicited advice

It is harder than ever to break into tech. Know that a large part of finding a job in any market is about being in the right place at the right time. Part of it is putting in the work to land that position…but if the job doesn’t exist then you don’t have a chance to land it. Be kind to yourself and know some of this is outside of your control.

In my opinion, the most important thing to do is find ways to differentiate yourself. How are you different from the thousands of applications to this one open position and why should they hire you over the other applicants? Due to the high number of career changers seeking jobs, the story of a career change is no longer enough to make yourself stand out.

A good way to start is by looking at job postings and taking note of specific technologies and positions that are in high demand. If you don’t know those things 👉🏻 put in the work to learn it. We live in a golden age where there is tons of content (paid and unpaid) online.

One caveat: there are lots of “influencers” trying to sell you something. Do your homework to investigate that individual or organization’s background before purchasing anything. Try to find some LinkedIn profiles or ask folks in your network for a second opinion. It is possible they lied on their LinkedIn, but if they are qualified there should be artifacts somewhere in public spaces. Just because someone is loud and all over social media, it doesn’t necessarily mean that they are an expert.

Back to in demand skills. This is my highly biased opinion, but in my part of the industry there is high demand for people who work with the cloud. In all of my recent jobs, there were lots of frontend engineers and not enough people to do things on AWS side of our stack. This might look like a software engineer that builds apps that integrate with cloud managed services or it could be more of a “DevOps” type of person. (Side rant: DevOps should never be a job title in my opinion as it is a philosophy that everyone should follow despite their official title, but that could be another post.)

A mistake that I see new graduates do is focus too much on making their LinkedIn profile and resume perfect. It is important to have a good online presence and resume, I’m not debating that. But equally important is finding people (specifically people who are hiring/have influence in hiring decisions) to read your profiles/website/resume. From my experience, the best way to do this is by networking. I know most career advice says this, but it is true. All of my software engineering jobs have come from some form of networking and I’m an introvert. It will be very uncomfortable, but if you want this badly enough you will need to acknowledge that unfortunately we live in a world where this is what you have to do to get people with influence to pay attention to your candidacy.

Ideally this would be done via a warm introduction from a common connection, but don’t worry about sending messages to people you don’t know. As long as you’re directly asking for what you want and respecting people’s time, they will most likely reply and want to help you. Worst case is that they don’t reply. View relationship building as a long term strategy and not as a one time transaction. You never know if you might one day be able to help this individual in return. Anecdotally, there have been many times when people whom I’ve formerly mentored were able to help me out too later on. We’re all in this together as a community and remember to give as much as you take in the long run.

Another mistake that I see new graduates do often is they start a conversation with a hiring manager by stating they’re a beginner or looking for a junior role. In this hiring climate, many hiring managers are seeking people with prior experience (see bullet point above), so starting out the conversation this way will most likely result in them losing interest in your candidacy. I’m not suggesting you lie or misrepresent your experience at all. I’d recommend talking about some things that you’ve built, the the technologies you’ve worked with, what parts of tech you’re excited about, and what type of role you’re looking for. If the question of previous professional experience comes up in conversation then tell the truth. “Junior” and “entry level” can mean different things to different hiring managers. Allow them to make that judgement after getting to know you a bit and hearing about what you’ve been working on.

Closing

Keep in mind that some of these thoughts are very specific what’s going on in the year 2024 in the United States, so if you’re reading this in the future or from a different location some of it might not be relevant.

I am not trying to sell you anything and really want you to succeed. This post is a compilation of my thoughts that many in my network have asked for, so I hope you find me publicly sharing this helpful.

It is totally up to you if you want to follow this advice, because at the end of the day I’m just another random person on the internet with opinions.

Top comments (6)

Collapse
 
efekeremaydin profile image
efekeremaydin

I’ve found points in this article relevant to many geographies! Thanks Danielle! Appreciated the part of being honest but at the same time focusing on the right things while talking to interviewers. Kind of agreed with the DevOps rant too, I think this can depend on the company size though, anyway I agree with the idea ☺️ @deeheber

Collapse
 
deeheber profile image
Danielle Heberling

Thanks! And yeah true sometimes it depends based on the company size.

Collapse
 
corinamurg profile image
Corina: Web for Everyone

This should be a must-read for everyone starting a bootcamp or a self-taught path. Thank you Danielle!

Collapse
 
deeheber profile image
Danielle Heberling

Thanks, Corina! Hope you found it helpful.

Collapse
 
efekeremaydin profile image
efekeremaydin

Agreed!

Collapse
 
vishaldev profile image
vishal

This is a valid points