You Don’t Need a CS Degree to Win in Tech (Here’s Proof)
Let’s talk about a myth that needs to die: You need a computer science degree to break into tech.
Let’s talk about a myth that needs to die: You need a computer science degree to break into tech.
No, you don’t.
In the last year alone, I’ve helped a barista, a product marketing analyst, and an NGO manager land software engineering jobs. None of them had traditional tech backgrounds. But they did have something just as valuable—skills that transferred beautifully into engineering.
Let me tell you how they did it.
How a Barista Became a Software Engineer
If you’ve ever worked in a coffee shop, you know it’s chaos. Lines out the door. Custom orders that make no sense. Customers who swear their oat milk latte isn’t oat-y enough. But you also know how to read people, anticipate needs, and solve problems fast.
That’s exactly what made this barista a great engineer.
They understood customer pain points deeply—because they’d dealt with them firsthand. When they started coding, they naturally built products with real users in mind. That perspective? Invaluable.
How a Product Marketer Became a Software Engineer
Marketing people know how to get a message across clearly and persuasively. They simplify complex ideas and make people care.
Turns out, that’s a superpower in engineering too.
This person picked up coding and quickly became the one who could explain why they were building something, not just how. They wrote clear, well-structured code. They documented their work. And in interviews, they absolutely nailed the “Tell me about a project” question because they knew how to tell a compelling story.
How an NGO Manager Became a Software Engineer
Running an NGO is like running a startup (except with zero budget and constant uncertainty).
You have to plan, prioritize, and navigate ambiguity like a pro.
That’s why this NGO manager crushed it in tech. Software engineering is all about breaking down complex problems, figuring out what matters most, and making things happen with limited resources. They already had those skills. Coding was just another tool to execute them.
What’s the Common Thread?
Each of these people did three things:
They played to their strengths. Instead of worrying about what they lacked, they leveraged what they already had.
They positioned themselves strategically. They didn’t just say, “I’m learning to code.” They said, “Here’s how my past experience makes me a great engineer.”
They built proof. Each of them worked on personal projects that showcased their unique perspective—whether it was user empathy, communication, or problem-solving.
Tech Needs More Than Just Coders
If you’re trying to break into tech but feel like you don’t “fit the mold,” here’s the truth:
Tech doesn’t just need people who can code. It needs problem-solvers, communicators, and people who get things done.
So stop stressing about what you don’t have. Start focusing on what you bring to the table.
You’re closer than you think.
Thinking of making the switch? What’s the #1 skill from your current role that you think would help you in tech? Hit reply—I’d love to hear about it.
— Raphael