Come teach the thing you wish someone had taught you properly.

You will own roughly a third of the DSA course — graphs, dynamic programming and the interview patterns that sit on top of them. That means writing the lecture, writing the practice set, writing the editorial, recording it, and then fixing it when support mail says it did not land.

You are probably right for this if you have four or more years writing production software, you have interviewed at least fifty candidates, and you have a strong opinion about the order in which recursion, memoisation and tabulation should be introduced.

What the week looks like: two days authoring, one day recording, one day on mock interviews and mentorship, half a day on support, and a half-day of your own study time.

Band: published in the first call, along with the formula behind it.

System Design is our newest course and the one that most needs someone who has actually operated a system at scale rather than read about one. You will rebuild the second half of the syllabus around case studies you have lived through — the outage, the migration, the capacity decision that turned out to be wrong.

You are probably right for this if you have run a service with real users and real pages, you can explain a consistency trade-off without a whiteboard, and you are comfortable saying "it depends" and then removing the ambiguity.

What the week looks like: heavy authoring for the first two quarters, then a steady rhythm of live sessions and mock design interviews.

The classroom, the progress engine, the certificate pipeline and the settings that repaint the whole product. Our platform is deliberately plain — semantic HTML, CSS custom properties and ES modules, no framework — because it has to stay fast on a five-year-old phone on a college network.

You are probably right for this if you can name three things that make a page feel slow that have nothing to do with bundle size, you take keyboard navigation and screen readers as requirements rather than tickets, and you enjoy deleting code.

First project: the accessibility pass on the classroom — focus order, live regions and a reduced-motion path through every animation on the site.

You are the person on the other end of support@bruteinfo.in between 10:00 and 19:00. Most of the queue is access, invoices, certificates and "I am stuck on this lecture and I do not know what to ask" — which is the interesting half.

You are probably right for this if you write clear English and Hindi or Marathi, you can read a stack trace well enough to know who to hand it to, and you have the patience to answer the same question kindly for the fortieth time.

The part that matters: every month you present the five things learners got most stuck on to the curriculum team, and they are expected to fix them.

Engineering departments across Maharashtra, Karnataka and Telangana buy our six courses for whole batches. You will run those relationships end to end: the first conversation with a training and placement officer, the pilot cohort, the reporting the department needs, and the renewal.

You are probably right for this if you have sold into education or enterprise before, you are comfortable spending a week a month on a train, and you would rather lose a deal than promise a placement percentage we cannot control.

What you will not be asked to do: quote a job guarantee, run a scarcity campaign, or discount below the published per-seat price.