Orientation is complete.
Continue from here.

Use the orientation recording linked near the top of this page. It opens in Google Drive and can be revisited while you complete the remaining onboarding steps.

The syllabus is a blueprint of the ideas and topics our projects will revolve around. It gives you a 360° view of the concepts within each weekly theme; it is not a promise that we will teach or implement every single item listed. We may cover some concepts in depth, touch on others, and leave some unexplored. We do not claim to cover everything.

The weekly titles are our guide. For example, themes such as Classic ML Engine, Transformers, and LM Internals describe the broader ideas and abstractions we aim to cover through actual production-grade projects. We learn a topic by building a system around it, understanding the decisions involved, and exploring the concepts that the project requires, rather than treating the syllabus as a checklist of theory to finish.

If a project brings together every concept listed under that theme, great. If it does not need a particular concept, we may not cover that concept. We will not force every item into a project just to tick a box. The detailed list helps you see the wider landscape and discover directions you can explore independently, including reading papers or implementing individual concepts from scratch if those interests matter to you.

Our focus is generalization and discovery: helping you transfer what you learn in one project to an unfamiliar problem. The goal is to become someone who can investigate a new idea, ask useful questions, understand the trade-offs, and work out how to apply it. Implementing many isolated concepts from scratch can be valuable for deeper study, but completing a catalogue of those implementations is not the central goal of this cohort.

The weekly projects and their contents also evolve. We add, change, and rework substantial parts of what we build as the cohort progresses. You should not assume that every detailed project or subtopic will stay fixed, or that future cohorts will repeat the same implementation. The weekly titles provide the direction; the projects determine which concepts we bring into practice.

Ultimately, we are building your ability to cover unfamiliar material yourself. For example, before an interview, we want you to be better equipped to sit down with a topic, investigate it, discuss it, and reach a real understanding quickly. That ability to learn and reason independently is the outcome we work toward. Our commitment is to explore the weekly themes through production-grade projects, not to promise exhaustive theoretical coverage of every item in the syllabus.

The edited post-orientation Q&A document linked on this page consolidates repeated Slido submissions and answers the underlying concerns. Read that document before raising a repeated onboarding question.

Open Agreement v3.2 dated 2 August 2026, read it completely, download and retain a copy, then submit the separate acceptance form once. Electronic acceptance verifies identity and enrolment, records your understanding, enables Skool admission, and is required to request a conditional remedy. The deadline is 6 August 2026 at 11:59 PM IST.

No. The published Cohort 3 program fee is non-refundable whether or not the electronic acceptance form is submitted. Declining, omitting, or failing to complete acceptance does not itself cancel enrolment charges, create a refund entitlement, or reverse financing.

Your financing is a separate agreement with the lender. Not accepting this agreement, not joining Skool, or withdrawing does not automatically cancel or pause the loan or EMI. Review the lender’s Key Fact Statement and signed terms, and contact the lender immediately about any cooling-off period, cancellation, prepayment, foreclosure, charges, or closure. Antern cannot change or cancel the lender’s agreement.

Antern does not guarantee a job, interview, salary, income, client, contract, or any specific career outcome. The only conditional guarantee is the Positive Reply Guarantee defined in Section 5. It can be claimed only when every stated attendance, deliverable, outreach, content, response-time, and evidence requirement is met. Its remedies are the personal network activation and extended approved Antern/SBL outreach-system licence access described in the agreement.

You should be comfortable reading Python code; familiarity with object-oriented programming is helpful. The orientation will explain the focused pre-work to complete before the first core session.

Support is the most important part of this cohort, and we never take it lightly. Ayush personally addresses technical, strategy, career, and cohort questions inside Skool through proper, structured threads. This support continues throughout the cohort.

Anything requiring deeper technical, strategy, career, or cohort guidance will continue in structured Skool threads after admission. Private logistical or registration matters should be emailed to team@antern.co.

After your registration details, completed onboarding form, and agreement acceptance have been matched. Invitations are sent manually to the registered email address.

No. The program provides training, systems, portfolio guidance, outreach support, and community access, but jobs, offers, salaries, and hiring decisions are controlled by third parties.

Email team@antern.co only for private logistical or registration matters. Technical and curriculum questions will be handled through orientation and Skool.