Turn the curriculum into a real next move. Build proof for the path you choose.

The most common path. After lesson 20 you have a GitHub portfolio with a containerized full-stack project, a working API, a database integration, and an AI-integrated feature. That is enough proof-of-work to apply to junior backend, junior full-stack, and junior AI engineer roles at startups and small companies.

What companies want at junior level: evidence you can ship something, communicate technically, and learn fast. The curriculum produces all three. What it does not produce is the formal computer-science theory (algorithms, complexity, OS internals) that some larger companies test for in interviews — those, you will need to study separately if you target Tier-1 product companies or FAANG.

Where to apply: AngelList, Wellfound, Y Combinator's job board, India-specific platforms (Cutshort, Hirect, Naukri tech roles), and direct outreach to startups whose tech you find interesting. Your GitHub link does more work than your resume in this segment.

Honest timeline: with the curriculum done and a polished portfolio, expect 3–9 months of applying before landing a role. Some land in weeks; some take longer. Variance is high; effort is the controllable variable.

The right path if you cannot wait three to nine months for a full-time role, or if you are still studying alongside the curriculum. Freelance work compounds: every project is a portfolio entry plus income plus reference for the next.

Where freelance work lives: Upwork, Fiverr (lower-end but easy to start), Toptal (higher-end, vetted), Contra, direct outreach via X / LinkedIn / GitHub. Indian freelance also exists on Truelancer, Freelancer.com, and through small agencies that subcontract.

What kinds of projects: after the curriculum you can credibly take on small full-stack builds, Dockerized deployment for someone's app, simple AI-integrated features (LLM API integration, basic chatbot), CMS-style sites, and database design / migration jobs. ABCsteps lessons 06-15 specifically prepare you for this kind of work.

Internship pipeline: ABCsteps does not currently have a formal internship program with placement partners. As the learner community grows and produces verifiable proof-of-work, introductions to small companies may become possible, but they must be earned by real shipped work rather than promised in advance.

Honest framing: freelance income takes time to build. The first few projects are usually low-paid; rates climb as you accumulate testimonials and case studies. Treat the first six months as deliberately cheap learning that pays you something.

The hardest path and the one with the highest ceiling. After the curriculum you have the engineering capacity to ship a real product end-to-end — frontend, backend, database, deployment, AI integration. The thing the curriculum cannot teach you is what to build and how to find users for it. That part is its own discipline (product, marketing, sales).

What you can credibly ship: a SaaS for a niche you understand (lots of small SaaS companies in India serve a specific industry), an AI-wrapper for a real workflow, a tool for a community you are part of, a paid newsletter or course (like ABCsteps itself), a small consultancy serving the same customer profile multiple times.

Honest framing: most first products fail to reach revenue. That is not a reason not to try; it is a reason to keep your runway honest. Build alongside a freelance income or a full-time role until your product covers basic costs. The curriculum's stack is genuinely production-grade; the bottleneck for entrepreneurship is rarely the engineering.

Where to learn the non-engineering parts: "Hooked" by Nir Eyal, "The Mom Test" by Rob Fitzpatrick, "Lost & Founder" by Rand Fishkin, "Indie Hackers" community, X / LinkedIn / YouTube content from operators (Pieter Levels, Daniel Vassallo, Justin Welsh in different niches). The engineering skills from ABCsteps + the product / marketing / sales skills from these sources is the whole stack of an indie founder.