A Complete Guide to Landing a Developer Job as a Non-Developer: What I Learned After Switching Jobs 3 Times
Last year, I successfully made the leap to a developer role as a non-CS major, and this year I moved to my second company. People around me ask about it often, so I thought I'd organize what I've learned so far. This isn't the absolute answer by any means, but I hope it helps anyone who, like me, started later in life.
1. Government-sponsored bootcamp vs. self-study: The bootcamp has a set curriculum, so it's good for building a study habit. I went the self-study route, though—I put together my portfolio using YouTube, official docs, and three mini projects. What matters most is finding the environment where you can stay consistent.
2. The core of a portfolio: Don't just list features you implemented. Structure it as 'Problem → Solution → Outcome.' My portfolio was a delivery app clone, and I wrote something like 'Improved delivery time prediction logic by 30% using caching.' That part came up most often in interviews.
3. Coding tests: As a non-CS background, you'll hit a ceiling anyway, so just solve Programmers Level 2 thoroughly. Instead of grinding Level 3, invest that time in CS fundamentals (networking, DB indexes). In practice, technical interviews ask more about CS.
4. Resume: Keep it to one page. When I submitted a three-page resume, my screening pass rate was below 10%. After cutting it down to one page, it jumped to over 40%.
Lastly, it's best to start preparing for your next move within six months of starting a job. Always name a slightly higher salary than what they offer, and weigh 'growth potential' just as heavily as benefits. Good luck, everyone.
10 answers
Agreed, there are also people for whom self-study is a better fit than government-funded training.
I'm a non-CS major too, and I really relate to #2... Portfolio structure matters a lot. They ask about it in every interview. Once I reworked the 'problem definition' part first, the questions I got totally changed.
Well, telling someone to only do level 2 coding tests seems like risky advice. These days, even new grads solve level 3 problems. Of course, CS fundamentals matter too, but those can be filled in later—the coding test is the first hurdle after passing resume screening.
Got a source? Something like statistics?
Wow, I was lost even during the government-funded program, so it's impressive that you did it self-taught. But I really think your environment matters. If I were on my own, I'd keep putting it off with no deadline, so I ended up choosing the government program.
It's true that CS fundamentals are more important, but wouldn't data structures come before network and DB indexing? That way, you can solve coding tests and it carries over to interviews as well.
I'm curious how they improved that caching by 30% lol
As someone currently in the industry, I really relate to #2. A portfolio without a defined problem is nothing more than a toy project. Interviewers also tend to focus their questions on that. As for #3, opinions are divided, but practically speaking, it's true.
The title says it's a perfect guide, but if it's 'not the definitive answer,' isn't it just a personal anecdote? Still helpful, though.
You can really feel the struggle in this post. Recommend. If you've changed jobs three times, there's got to be some insight, lol.