You Can Get Hired Without CS

Look, I get why people prioritize degrees. Having a formal education is great. It provides a structured foundation that is hard to replicate on your own. If you have the time and money, go for it. But if you think a piece of paper is the only way to get hired, you are mistaken.

I recently tried to debug a simple React app. I kept seeing an “undefined is not an object” error when trying to map over a list of users. I assumed the API call was the problem, so I spent an hour logging the response. Turns out, the data was fine. I just forgot to initialize the state as an empty array. It was a silly, basic mistake. Did my lack of a formal algorithms class cause this? No. My own haste did. (I really should have checked the console error stack first.)

“But companies require degrees in the job description!” Sure, some do. That is a fair point. If you want to work for a legacy firm that treats HR software as the gatekeeper, you might hit a wall. However, plenty of companies care more about what you can actually build.

Here is what you actually need to do instead:

1
function fetchUsers(url) {
2
  return fetch(url)
3
    .then(res => res.json())
4
    .catch(err => console.error("Failed to load", err));
5
}

Show them you can write code that works. Build a project. Deploy it. Document your struggle in a repo. If you can explain why you chose a specific state management library or how you handled an API error, you are already ahead of many graduates who can only talk about theory. (Theory is nice, but shipping code is better.)

I’ll admit, my advice might not help you land a role at a research-heavy lab that requires deep knowledge of math or low-level graphics engines. There, a degree is often a shorthand for the depth of knowledge they expect. But for 90 percent of web development roles, it is about solving business problems.

Are you building things? If you aren’t, start today. Focus on the tools you use every day. Get good at the parts of the stack that actually matter for your daily tasks. If you can show a portfolio of projects that solve actual problems, you won’t need a degree to prove your worth. Does your project have a README that explains the ‘why’ behind your technical decisions?