An orientation to software and AI for anyone walking in — student, fresher, or someone with years of experience who never learned the process side. What AI is, how companies are structured, who does what, how software actually gets built and shipped, and the vocabulary everyone assumes you already know.
What is AI? What is machine learning? Start your journey here — no experience needed.
From 1943 to 2026. AI winters, breakthroughs, and what comes next.
See how Traditional AI, Generative AI, and Agentic AI solve real-world problems across healthcare, finance, education, and more.
Who builds software, who pays for it, and how money travels from a customer's problem to an engineer's salary — the business reality every process in this track exists to manage.
Services vs product companies, startups vs enterprises, tech domains, revenue models, and India's tech ecosystem — everything you need to know about the industry you are entering.
Meet the people who build software — from developers and designers to data scientists and DevOps engineers. Find out which role fits you.
SDLC, Agile, Scrum, Jira, Git, and CI/CD — understand how real software teams build and ship products.
BRD, FRD, HLD, LLD, ADR, RTM, RCA — the document map across the whole life cycle, plus how to write a bug report a developer can act on.
POC, prototype, MVP, GA and sunset — what each stage is for, the one question it answers, and what it costs to confuse them.
Jira, Git, GitHub, CI/CD, Confluence, Figma, Slack — the five categories every company has something for, and the ticket and code-review vocabulary you need on day one.
A realistic developer's day, how it differs for QA, BA and delivery roles, the rhythm of a two-week sprint, and the unwritten rules nobody explains on day one.
Code review, the testing pyramid, the environment ladder, CI/CD, and what happens when production breaks — the machinery that turns a ticket into running software.
Timesheets, contract types, the bench, utilisation, appraisals and RAG status reporting — the half of working life no course teaches.
The scope-time-cost triangle, estimation techniques, the critical path, the RAID log, and what actually happens when a project starts going wrong.
One architecture picture and the vocabulary hung off it — frontend, API, backend, databases, queues, monolith vs microservices, and the cloud service models.
Experience is pattern recognition. Six situations that will happen to you, the experienced move in each, what certifications signal, and the unwritten rules nobody writes down.
2 interactive labs — hands-on exercises for this track
150 questions across 6 modules — check how well you understood this track.