School 01 / Pilot
Software Engineering
Six months of programming, web, backend, testing and deployment. You finish with a portfolio and a capstone you present in public.
The month-by-month plan, on film.
A walkthrough of the six months is planned, one short film per month, from the same month plan written out below.
Reading the six-month plan
Walkthroughs are not published yet. The month table below is the same content in words.
What you can do at the end.
Four abilities, each one demonstrated in a project rather than described in an essay.
Read and write code
You can take a written problem and turn it into a working program, then explain each line.
Build for the web
You can ship a responsive multi-page site and a backend with a database behind it.
Test and deploy
You can write tests, find a security mistake before someone else does, and put the app online.
Work in a team
You can split work, review someone else's code, and present the result without hiding behind slides.
Month by month, with the output.
Proposed, not finalSix months, six outputs
| Month | Focus | What you finish with |
|---|---|---|
| Month 01 | Programming foundations Command line, version control with Git, and problem solving in a first language. | Small programs and a Git repository |
| Month 02 | Web fundamentals HTML, CSS and JavaScript, built as pages a real person can open on a phone. | A responsive multi-page website |
| Month 03 | Backend and data APIs, databases and the server code behind a form. | A working CRUD application |
| Month 04 | Engineering practice Testing, security basics and deployment. | A tested application with documentation |
| Month 05 | Team project A small team builds one thing, with mentor reviews at each milestone. | Project milestones and a review log |
| Month 06 | Capstone Finish, document, and present the work in public. | A portfolio-ready project and a presentation |
A proposed structure. It can change before the cohort starts, and any change is published here rather than announced in a live session.
What you need before day one
- Computer A laptop or desktop. A phone is not enough for the labs.
- Internet Enough for a live session and a package install.
- Time The proposed load is 10 to 15 hours a week.
- Language Comfort reading technical English. Tamil is supported in sessions.
No prior programming is assumed. No entrance exam.
What is not required
- No degree, diploma or mark sheet is checked at application.
- No age bracket is published yet. The minimum age is a founder decision.
- No fee is collected before the fee page is published.
- No laptop is provided.
Honest note
If you cannot commit ten hours a week for six months, this programme will not work for you. That is the main prerequisite, and it is not a formality.
How the work is marked.
Final rubric before admissions| Dimension | Weight | What the marker looks at |
|---|---|---|
| Conceptual understanding | 20% | Quizzes, oral explanations and short written responses. |
| Practical assignments | 30% | Individual work, marked against a written rubric. |
| Projects | 30% | Functionality, quality, originality, documentation and iteration. |
| Communication and collaboration | 10% | Peer work, presentations and technical writing. |
| Final demonstration | 10% | A live walkthrough, questions and a short reflection. |
Attendance is not a grading component. Work that is not submitted is not graded. The final demonstration is individual: the project may be built by a team, but you present and answer for your own part.
Before you apply.
If a question is not answered here, write to admissions@sethu.skills.
Is this a degree?
Will this get me a job?
Is the fee published?
Can I work while studying?
What language are the sessions in?
What happens if I fall behind?
Admissions are interest only.
Register interest and you will be told when the window opens, with the dates published here first.