how products are built from scratch.

The thinking behind them.

How you approach something that doesn't exist yet.
How you think beyond just features.
How you figure things out when there's no one holding your hand.

Not just coding but actually how to think beyond code,

the attention to detail, to decide what matters and what not.

For students and early stage engineers who want to learn about how product is built in the industry that can be used by customers — not just features but the actual product, the thinking behind it, the journey from blank sheet of paper to full fledge working product.

Specially if you want to build a product from scratch, from 0, or if you want to join a good startup as their founding engineer, or later on to the CTO path. I will help you learn how you can grow, how to think like a CTO / founding engineer while building a product so that things can scale.

> Coding can be done easily but the thinking behind that takes time to build.

The architectural decisions — what to use, what not to use — it's a specific part that gets better as you start working, practicing more and more.

I can't promise ki you will learn all these things in just few months, but at least you can start — you will get the initial guidance.

> I strongly believe ki best learning theory padhne se jada implementation se hoti hai.

Just start implementing and you will learn while making. I have learnt maximum in that way only, and this is the exact structure we follow here. We will just start implementing things and you will learn along the way.

Developer Sarthi batches are not just a course or cohort — it's way beyond that.

A simulation programme that tries to mimic closely how things work in industry, and specially early stage startups.

What happens in live (online) batches

day 1 · ideaevery day · small micro decisions and tradeoffs2–3 months · MVP

We decide an idea on day 1, given people attending the batch. Based on that idea, in next 2–3 months we will build an MVP out of that — and we will approach that as I have approached that idea in real life scenario, as if a founder came to me with actual startup idea and I have to create an MVP for them.

Every day will consist of small micro decisions and tradeoffs that will shape the product. And that decisions — why we have taken it, what if we have gone other way — everything will be discussed.

I can promise

Your end goal should be learning, and for that I can promise that you will know plenty of things at the end.

Uske outcomes mein you might get a job or an internship, but that's not anything I am promising or we are targeting for. Only focus will be on learning and how you will improve.

I can't promise

If you are coming here ki yahan se karne ke baad aapko job ya internship mil jayegi — frankly it's a possibility, an outcome, but I can't promise that.

>The thinking takes time to build.

It's not like ki just ek MVP bana liya and you don't need any handholding after that, or aap ek dum se sab kuch karne lag padoge —

but at least your journey will start.

— Sood

Message me to know when the next batch will start.

Message me on LinkedIn ↗

linkedin.com/in/sood2105