Eight Months Into Self-Studying Backend as a Non-CS Major: My Roadmap So Far

I came from a humanities background with zero relevant experience, and now I'm working as a backend developer at a small company. I'm writing this down in case a summary of how I got here might help someone.

1. Choosing a language — At first I had no idea what to do, so I watched YouTube and dabbled in a bit of everything. In the end, I picked just one (Python) and stuck with it for three months. Doing several at once was poison for me.

2. Building the basics — Just continuing to watch syntax lectures wasn't great. Buying one data structures book, typing out the examples by hand, and solving problems stuck with me much more.

3. Understanding web architecture — HTTP, routing, and DB design were the real backbone. If you design and build one REST API yourself, you'll get a much clearer feel for it.

4. Projects — I did two toy projects and one team project. Being able to explain "why I built it this way" was far more important than the number of projects.

5. Applying — I started applying in my sixth month. I kept getting rejected at the resume stage, but after getting humbled in interviews, I kept revising things.

To be honest, I'm still not what you'd call good. I think just sticking with it was the big thing. If you're just starting out, don't be too impatient.

by 월급루팡26

7 answers

This is so true lol. For me too, sticking to just one language ended up being faster. I wasted a year trying a bit of this and that.

by 지나가던행인129 · ▲0

Congratulations on landing a job in 8 months, but... isn't it hard to say the market situation now is the same as it was then? I've heard it's become much tougher for non-majors entering as new grads these days. I think this should probably be seen as a case where you got lucky.

by 카페인중독345 · ▲0

Well, I think it was a bit risky to start applying from the sixth month. Someone with a solid foundation naturally gets better timing for applications too—if you rush it, you’ll just rack up resume rejections and end up getting burned out mentally, won’t you?

by 알고리즘고수155 · ▲0

Which data structures book did you use? I keep just taking grammar lectures and I’m losing momentum—could you recommend one?

by 뉴비탈출134 · ▲0

Agreed, point 3 is really the key. If you don’t understand HTTP and database design and only dive into frameworks, everything will collapse later.

by 주말개발자514 · ▲0

The part about fixing things after failing interviews resonates with me the most. I kept getting rejected at the resume screening stage, and I felt really self-critical at that point. I think it’s important to somehow make it to the interview stage. Do you happen to have any tips for increasing your resume pass rate? I’m always wondering how much to elaborate on project descriptions in the README.

by 데이터덕후748 · ▲0

I really agree that being able to explain “why you built it this way” matters more than the number of toy projects. I just kept increasing the number, and when an interviewer asked why I used a certain technology, I couldn’t answer a single one lol. That was a big realization for me. In the end, it’s better to go deep into one project.

by 코딩하는곰23 · ▲0