Learn · Software developer

💻 Software developer

Write, test and ship code professionally.

Employers hire on demonstrated ability, not certificates. Every stage below ends in something you can show: a repository, a deployed page, a passing test suite.

The path, in order

1. Foundations (4–6 weeks)

One language properly, rather than three badly. Variables, control flow, functions, collections, and enough of the standard library to stop reaching for tutorials. Python or JavaScript are the pragmatic starting points because the job market and the learning material are both deep.

Beginner coding challenges on Syllab

2. Data structures & algorithms (6–8 weeks)

Arrays, hash maps, strings, linked lists, trees, then sorting and searching. Aim for fluency on the first four — the overwhelming majority of screening questions live there. Do fewer problems more thoroughly rather than racing a count.

3. Build two real things (4–8 weeks)

One project with a database, authentication and a deployed URL; one smaller tool that solves a problem you personally have. Two finished projects outperform ten abandoned ones, because finishing is the part employers are actually screening for.

4. Version control and collaboration (ongoing)

Git branches, pull requests, code review, and writing a commit message someone else can read. This is the daily texture of the job and it is the thing bootcamp graduates most often lack.

5. Interview shape (2–4 weeks)

Narrate your reasoning out loud while coding, because silent correctness scores worse than audible thinking. Rehearse in the format you will actually face.

Where people lose months

⚠Collecting languages instead of depth. Three half-known languages interview far worse than one you can reason in fluently, because every follow-up question exposes the gap.
⚠Tutorial loops. Following along with a video feels like progress but builds recognition, not recall. Close the tutorial and rebuild the same thing from a blank file — that gap is the actual learning.
⚠Never deploying. A project that only runs on your laptop cannot be checked by a recruiter in thirty seconds, which is all the time it will get.

Common questions

Do I need a computer science degree?

No, and a large share of working developers do not have one. What a degree substitutes for is proof, so without one you need a portfolio that removes the doubt: two finished, deployed projects and a public commit history do that job well.

Which language should I start with?

Python if you lean towards data or backend, JavaScript if you want to see visual results early and target web roles. Both have deep job markets. The choice matters far less than sticking with one long enough to get fluent.

How long until I can apply?

Most career changers reach an interviewable level in four to eight months of consistent part-time study. Start applying around the two-thirds mark — interviews reveal your remaining gaps faster than more study will.

Put it to work

School-level foundations for this subject live on our sister site Syllab.

Other paths: Accounting & CA · Data analyst · Commerce & economics · English & communication · All paths