Ask HN: How many of you are working in tech without a STEM degree?
15 zebproj 21 7/23/2025, 11:58:08 AM
As someone without a STEM degree and who is largely self-taught, I'm interested in hearing about similar experiences. What is your story? What are you doing now? How long have you been doing it? etc, etc.
My kids (two with degrees, one went to a vocational program) all have jobs, but none of them work in tech or software. I can't imagine trying to get a job today as a junior, especially without a STEM degree. Plenty of employers (or freelance customers) will overlook credentials if the candidate has experience and a reputation, but young people fresh out of school don't have any of that.
Employers seem completely unwilling to take a chance on young people eager to work and learn. I get the impression that very few employers put any resources into training or mentoring their programmers, instead they want to hire people who exactly match some checklist or "skill set" and fob the screening and interviewing off to HR, recruiters, and now AI.
I dropped out of uni after it kept holding me back. I think I have around 50% of credits left to finish. I was already working as a developer and I had many things to learn career wise. I had to choose between going ahead or staying on place while finishing a degree.
I don't regret my choice but I wish I had a degree. While I have superior studies in the field (2 years instead of the 4 of a degree) it doesn't feel the same.
After 10 years working and with many more years ahead (I hope) I don't think I'll ever find the motivation to finish it. And most recruiters that contact me are more interested in the experience I have than anything else.
But 2008 hit, job market was terrible and I ended up working at a computer repair store chain while trying to pay my way through college until 2011, where I got a LAMP dev job for a large travel website. I dropped out of college at that point and haven't looked back.
I got to program for a bit over 10 years before moving into leadership, selling two startups along the way.
I did a Media Studies (theory) degree, but all the way through university I was making websites for fun and for profit (badly), and managed to get into web 'producer' roles before moving to 'Product Owner' type roles. Though I am non-technical, I took the time to learn about the technologies we use, likely more than my peers.
These days I work in IT strategy and support the CIO - though most of the leadership team I work with do have engineering backgrounds, many of people my level do not.
I got pigeonholed quickly into enterprise development, mostly at non tech companies of various sizes.
I knew I never wanted to work as a software dev professionally. I had other plans initially that fell through. However I found myself in a situation where my choices were to struggle off of a low skill job or try and break into the industry have a reasonably comfortable life.
Of course, even that didn’t work out as expected. I was significantly underpaid (even with local COL/salary data in mind), still at least it was a foot in the door and a full time job. My salary came more in line with what someone would expect in a small city around the time, but still barely at the bottom of that range.
Around the time of the COVID glut, I finally landed a six figure job, as well as the closest thing I’ve had to a job ”in tech”. It was pretty decent, but half the company was dumped a year or two later.
I didn’t expect to have much of an issue in the market, ignorant of how bad it really was and with the understanding that with my experience I couldn’t be a total pariah. Instead it took over a year to find a new job and that was solely due to nepotism.
A little bit into my current job, I realized my career was dead. I don’t keep up with the industry outside my day to day anymore, I’m certainly not keeping up with newer fresher people and to some extend miss that enthusiasm. But it really does not interest me anymore. Rarely the tech and never the product.
I’ve thought about leaving before that happens, but I have yet to see a path to something else that I wouldn’t hate just as much.
I figure I’ll either die of from stagnation or AI will replace me or lower that value of my work to the point where the money is no longer worth staying
I started learning how to code from trying to make game mods around age 10. This was mostly UnrealScript + Lua for SecondLife.
Got an internship at a web dev shop when I was 18. They primarily did SaaS startup launches. There was a lot of trial-by-fire. Picked up frontend + backend + DevOps skills there.
To answer your question: I got into computers and programming when I was 8 years old in the 1970s, and haven't stopped.
During interviews my lack of degree is often brought up - usually asking if I accidentally forgot to add it to my CV.
At first it was tough but now I'm two decades deep into a career in Ops.
Have done almost every job, found system administration/DevOps/SRE stuff the most interesting. Security stuff is cool but also too product-oriented for my tastes.
While it was always possible for me to find work before the degree, I have to admit that the work offered was vastly incommensurate with both my actual skill level and my desired compensation. This is much less the case post-degree. In fact I now regularly have to turn down work I frankly feel like I couldn't do as good a job on because I have a language to learn and a citizenship to clinch.
I do think this effect would have faded out gradually either way, markets are going to reach equilibrium. But the degree made it happen much faster for me even despite relocating to an entirely foreign job market. I would say get the degree in almost all cases.
https://news.ycombinator.com/item?id=44599228
Here is almost the exact same comment but specifically in the context of WASM and tree structures receiving the maximum number of downvotes:
https://news.ycombinator.com/item?id=44657549
It’s weird but apparently insecurity among software developers is super common. It’s why I left a career writing JavaScript and refuse to go back.
At the moment, I'm running a program for self-directed CS education[1] and end up talking to a lot of people who were self-taught. Part of the motivation for the program was that we found that people we hired who had a lot of self-directed experiences were much better engineers. It wasn't that degrees were necessarily bad, but it seemed like the thing that made them good was not the degree.
From my experience talking to people who were also mostly self-taught, the outcomes are a mixed bag. In retrospect, I think I was quite lucky in that I had the right support structures (mentors, etc) in place throughout my life. Some I worked towards, others kinda fell in my lap. In addition, some of my earlier career/life decisions based on hunches have worked out so far (pivoting from medicine to ML in 2012). Not everyone I talked to had the same experience. Some really languished because they really had no support / positive influences. Others think it's one of the best decisions they've made, in both time/money saved and agency.
If I had to summarize, one of the major negatives is that self-directed education frontloads a lot of the problems early on. You're in total control, but also exposed to all your mistakes. If you don't have the right environment, you can flounder in the sense that you don't even know what you're missing. This is compounded by our terrible K-12 education system, which does not prepare you for self-direction. If you don't have other sources of support, it could lead you to a vicious cycle of failure begetting failure. You'll also be "marked" [2] and mistakes/setbacks will be attributed to your lack of degree, whether justified or not. From a career perspective, some hiring managers are not incentivized to take risks on non-degree holders. Ie. it could blow back on them if you don't work out. You'll have to work harder on signaling and networking, etc. You're not going "fit", esp in a degree-heavy culture, and that could lead to social isolation.
The positives is that, at the moment, there's never been a better time to self-direct your education. You end up learning things that interest you, at your pace at the right time, so the problems/work is always relevant. You can go really deep really fast. The people that you want to work for/with don't care about your degree. Self-directed education is inevitable, esp in tech. Every one of us eventually have to take control of our education. The problems you have to work through early on are also inevitable (ex. signaling to others that you are competent). The agency and sense of control is great for your mental well-being and developing accountability. Your team can count on you to take the initiative, figure things out, and learn the things you need to learn. Uncertainty is not paralyzing. You've dealt with it your whole life.
Overall, it's not an easy path. I think a lot of it depends on early support and the mental attitude/personality of the individual.
[1]https://www.divepod.to [2]https://en.wikipedia.org/wiki/Markedness
For the first ~ten years of my career I worked shit jobs for pretty mediocre pay at small companies that overworked and under appreciated me. I did Open Source to stay sane, to learn, for fun, and I leveled up every few years, learning CS, hardware, algorithms, FP, type systems, and more.
Eventually I worked at larger companies, smaller companies with big scale, and eventually FAANG.