Weekend batches
For people already in a job. Same syllabus, same trainers, same projects — spread across a longer calendar so it fits around the week you already have.
Most of our weekend learners are two or three years into a job that is not going where they want it to. Accounts executives moving toward analytics. Support engineers moving toward development. Sales staff moving toward marketing analytics. The constraint is never motivation — it is that Tuesday evening belongs to someone else.
The calendar is longer. That is the only difference, and it is intentional.
It would be easy to compress a weekday course into the same number of weekends by cutting the labs, and plenty of places do. It produces learners who have seen everything and practised nothing. So the weekend format keeps every lab and every project and simply takes more weeks — a four-month weekday course generally runs six to seven months on weekends.
Six to ten hours a week outside class, consistently, for the length of the course. That is the number people underestimate, and it is the single strongest predictor of who finishes with a portfolio.
We would rather say this before you enrol than at the midpoint. If those hours are genuinely not available right now, a longer batch or a shorter course is a better decision than starting something you will not finish.
They solve different problems. Weekend batches solve "I cannot attend on weekdays". Online live batches solve "I cannot travel to the centre". Both run the same syllabus with the same trainers, and several courses run both, so you can pick the combination that fits. If your constraint is both time and travel, say so when you enquire and we will tell you which batches currently work.
A real beginner course for adults who have used a phone but never a computer for work — files, Windows, internet, email, typing and staying safe online, taught without assumption.
The certificate a great many government job applications ask for, taught as exam preparation with full-length mocks rather than as a general computer course that happens to mention CCC.
The standard entry diploma for office and computer work — fundamentals, Office, accounting basics and the internet, taught as practical work rather than as a syllabus to memorise.
The NIELIT foundation diploma, recognised for government posts and treated here as a programming course that happens to have an exam — because the practical and project marks are where candidates lose ground.
The four applications every Indian office runs on, taught around the tasks you will actually be judged on rather than as a tour of every menu.
The graduate-level computer diploma — programming logic, databases, office automation and a substantial final project, for people who already hold a degree and need computing on top of it.
The advanced diploma that follows the basics — programming, databases, accounting and design taught together, so you leave able to do skilled work rather than only office work.
The NIELIT advanced diploma, a genuine step up from O Level — data structures, databases, software engineering and networks, with a project that carries real weight in the result.
A structured path from spreadsheets to SQL, Power BI and Python, built around the four things a data analyst is actually paid to do — pull the data, clean it, analyse it and explain it.
Built around speaking rather than grammar exercises — because most learners in India already know more grammar than they can use, and the gap is confidence under pressure.
Python taught as a working tool rather than a syntax tour — you finish able to read unfamiliar code, automate real tasks, call APIs and write tests that catch your own mistakes.
Python, machine learning foundations and applied generative AI in one track — ending with a retrieval-augmented application you have built, evaluated and can explain end to end.
Excel automation taught as programming rather than as macro recording, so the tools you build keep working when the data changes and somebody else opens the file.
A short, applied track for people who already program — prompting with evaluation attached, retrieval systems, and the guardrails that separate a demo from something you can ship.
Database work for the office — designing tables that hold up, querying them properly, and building forms and reports colleagues can use without breaking anything.
Project scheduling taught as planning rather than as software training — dependencies, the critical path, resource conflicts and tracking a plan once reality starts disagreeing with it.
Office software and desktop publishing taught together, so you leave able to run the documents an office needs and the print work a small business needs, not one or the other.
Statistics, Python, SQL and machine learning taught as one connected discipline, with the emphasis on framing a problem correctly and knowing when a result is not real.
The reporting job taught properly — Excel, SQL, Power BI and automation, organised around producing the recurring reports a business runs on rather than around software features.
Preparation for the RKCL RS-CIT examination, taught to the published syllabus with timed mock papers, so you meet the exam format in class rather than on the day.
A short, practical course for people who need office-ready computer skills quickly — documents, spreadsheets, presentations, basic accounting and confident internet use.
Classical machine learning done properly — feature engineering, honest evaluation, and the discipline to notice when a good score is an artefact rather than a result.
Photoshop taught around non-destructive editing, so every file you build can be revised later — the habit that separates someone who can use the tool from someone who can work with it.
The vector tool most Indian print shops actually run, taught around the files they need — logos, cards, flyers and banners that reach the printer correct the first time.
The industry-standard vector tool, taught around building marks and illustrations properly — clean paths, real typography and files an agency or printer can open and edit.
Front end, back end, databases and deployment taught as one connected system, ending with applications you have shipped to a public URL and can walk an interviewer through.
The layout tool for anything longer than one page — master pages, styles and grids, so a hundred-page document stays consistent and a late change takes minutes.
The foundation everything else sits on — semantic HTML, CSS layout and JavaScript — taught until you can build and deploy a responsive, accessible site without reaching for a framework.
The job a print shop hires for, taught as the job — typing, layout, design and the preflight checks that decide whether a file prints correctly or comes back.
The stack large Indian enterprises and services firms actually run — Java and Spring Boot on the server, React on the client, with a relational database designed properly underneath.
One language across the whole stack, taught as a connected system — including the judgement about when a document database is the wrong choice, which most MERN courses never raise.
Editing taught as decision-making — what to cut and why, how to fix bad audio, and how to export once correctly — using the tool most professional edit suites actually run.
Django taught with the ORM's failure modes included — the N+1 query, the migration that will not apply — because those are what separate a tutorial project from a maintainable one.
The fast route to publishable video — cutting, captions, music and correct export for each platform, using a tool you can be productive in within a fortnight.
Power BI taught as a data modelling tool rather than a chart menu — star schemas, relationships and DAX first, because that is what separates a report that scales from one that breaks.
Motion graphics and visual effects built on compositing fundamentals, so a keyed subject sits inside the shot rather than on top of it, and an animation moves like it has weight.
The finance module of SAP, taught by configuring an org structure and closing a real period in it, so you can answer how the system works rather than only where the buttons are.
The procurement and inventory module, taught by running the procure-to-pay cycle end to end so you can trace what every document did to stock and to the ledger.
SQL taught against a database big enough that a bad query is noticeably slow, because toy datasets hide performance entirely and performance is half of what the job tests.
The sales module, taught by configuring pricing and running order-to-cash end to end, so you understand why an order priced the way it did rather than only where to click.
The full accounts-department skill set in one programme — Tally, GST, TDS, payroll, banking and reporting — practised across a complete financial year rather than as separate topics.
Tableau taught as analysis rather than chart production, with level of detail expressions and data structure given the weight they deserve — because that is where reports go wrong.
The Excel that offices actually run on — lookup logic, PivotTables, Power Query pipelines, dashboards and enough VBA to automate the work you repeat every month.
The shorter accounts programme — Tally, GST, TDS and Excel practised on a real half-year of books, for people who need to be hireable sooner rather than exhaustively trained.
The knowledge a bank or NBFC role actually requires — products, lending, KYC, compliance and customer handling — alongside the aptitude practice that recruitment tests are built on.
Markets taught with risk first — instruments, analysis, derivatives and position sizing — built around not losing capital, because that is the part that decides whether anyone lasts.
Running an online business end to end — marketplace and own-store selling, cataloguing, pricing, GST and ads — anchored on the unit economics most sellers work out too late.
The Microsoft stack taught as one connected system — C#, ASP.NET Core, Entity Framework and SQL Server — finishing with applications you have deployed and can defend.
PHP taught the way it is actually written now — modern syntax, Laravel, MySQL and real deployment — for the enormous share of the web that still runs on it.
Tally Prime taught through a full simulated financial year — vouchers, inventory, GST, TDS and payroll — so you finish having actually kept a set of books, not just clicked through menus.
The Angular-based JavaScript stack, taught with TypeScript and structure throughout — the version of full stack work that large teams and enterprise projects hire for.
What comes after core Java — Spring Boot, JPA, REST APIs, testing and deployment, taught by building a service you deploy and can defend in an interview.
GST taught as reconciliation work rather than as rules to memorise, because the job is finding why your books and the portal disagree — and that is where mistakes cost money.
Database administration taught by doing the frightening parts on purpose — you will lose a database and restore it, because that is the skill the job is actually paid for.
R taught for statistics rather than as a second Python — data wrangling, visualisation, testing and regression, with the discipline to interpret a result honestly.
Distributed data processing taught with judgement — Hadoop, Spark and pipeline design, plus the far more common case where a single machine would have been the right answer.
Networking and Linux foundations, then web application security, SOC monitoring and incident response — practised exclusively in isolated labs, with authorisation treated as a hard rule.
Connected hardware from sensor to dashboard — microcontrollers, wireless protocols, cloud ingestion and the power and reliability problems that decide whether a device survives deployment.
The offensive counterpart to our cyber security course — methodology, exploitation and reporting, practised exclusively in isolated labs with written authorisation treated as a hard rule.
Offensive security practised only on a lab you are authorised to attack, taught through a full engagement — scope, test, escalate, and write the report a client can act on.
The CRM platform taught configuration first — data model, security, automation and reporting — then Apex, so you can solve most problems without writing code at all.
Civil drafting in AutoCAD taught the way a site office judges a drawing — correct layers, real dimensioning, plotted to scale and readable by the person building from it.
Mechanical drafting judged the way a machine shop judges it — correct projection, tolerances that reflect function, and a drawing a machinist can work from without ringing you.
AWS taught by building and breaking infrastructure rather than by memorising service names, ending with an architecture you have deployed, secured, costed and can defend.
Electrical drafting for panels and installations — schematics, layouts, cable schedules and wire numbering — built so the person commissioning the panel can trace every circuit.
Parametric 3D modelling taught around design intent, so a model survives the change request — assemblies, sheet metal and drawings that update themselves.
The modelling standard in automotive and aerospace, taught through part design and surfacing — including the curvature continuity that decides whether a body panel is acceptable.
The toolchain taught around the goal it serves — shipping small changes safely and often — rather than as a list of products to name on a CV.
Creo taught around parent-child relationships and robust feature order, because in a strongly parametric package a careless reference is what breaks a model three weeks later.
Finite element analysis taught around validation, because a colourful stress plot is easy to produce and only useful once you can show it is not nonsense.
SEO, paid advertising, content, email and analytics taught around measurement, with real campaigns on real budgets and an emphasis on attributing results honestly.
Structural analysis taught with the checks that matter — realistic supports, correct load combinations, and verifying an answer before a design is issued from it.
Building-specific structural analysis — storeys, rigid diaphragms, shear walls and seismic response — with the drift and irregularity checks that decide whether a design is acceptable.
Design taught as decision-making you can justify, not decoration — ending with three case studies that show your reasoning, which is what design hiring actually assesses.
Model-based civil design — surfaces, alignments, corridors and earthwork volumes — where changing the road changes every section, profile and quantity automatically.
CAD taught to drawing office standard rather than as a tour of commands, because employers judge a drawing on layers, dimensioning and whether it plots correctly.
Building information modelling taught as one model producing everything — plans, sections, schedules and quantities — with the coordination habits that stop a project drifting apart.
Core Java properly, then Spring Boot — with real weight given to object-oriented design and the collections framework, because that is what enterprise Java interviews actually test.
The scheduling standard on EPC and infrastructure projects — WBS, critical path, resource loading, baselines and earned value reporting a client will hold you to.
HVAC design from first principles — psychrometrics, honest heat load calculation, duct and chilled water sizing — because an oversized system is the most common and most expensive mistake in the field.
Automation testing taught around the problem that actually kills automation projects — flaky tests — with waits, locator strategy and framework design given the weight they deserve.
Machine programming taught with the setup and simulation discipline that stops a crash — G-code by hand first, so you can read and correct what any post-processor writes.
Architectural visualisation taught around light and camera, because a correctly modelled room still looks wrong until the lighting and the lens are right.
Design principles first and software second, because employers hire for typography and layout judgement — the tools are learnable in weeks and the judgement is not.
The fastest way from a plan to a three-dimensional idea a client can react to, taught with the group and component discipline that keeps a model workable as it grows.
One codebase for Android and iOS, taught through to store release — because the parts that defeat people are release signing and store review, not widgets.
The renderer itself, taught properly — global illumination, physical materials, camera exposure and the optimisation that turns a nine-hour render into forty minutes.
Interior design taught as a delivered project — space planning, material selection, working drawings, 3D views and a costed BOQ — available as a certificate, diploma or advanced diploma.
The complete 3D pipeline taught in order — model, texture, rig, animate, light, render — ending in a showreel, because a showreel is what an animation studio actually hires from.
Native Android in Kotlin and Jetpack Compose, with the lifecycle and configuration-change problems taught head-on because they are what actually breaks Android apps.
The whole 3D pipeline in one free package — model, sculpt, shade, animate, render — so you can keep practising at home the day the course ends.
The studio standard for character work, taught with the rigging and animation depth those jobs test — plus the naming and file discipline a shared pipeline actually requires.
Digital sculpting taught form first — silhouette and anatomy before pores and wrinkles — and finished properly, with retopology and baked maps a pipeline can use.
Industrial automation taught on real hardware — ladder logic, analogue I/O, HMI and SCADA — with the interlock and safety discipline that separates a working panel from a dangerous one.
Firmware written close to the metal — registers, interrupts, timers and buses — debugged on real hardware, because embedded bugs live where a simulator cannot show them.
The fastest way to make electronics actually do something — sensors, motors, displays and code — taught by building prototypes you design rather than diagrams you copy.
A small Linux computer used properly — Python, GPIO, camera and networking — building headless devices that start on their own and keep running unattended.
MATLAB taught as an engineering tool — vectorised computation, signals, control and Simulink — with the habit of checking a simulation against something you already know.
Board design taken to manufacture — schematic, footprints, layout, planes and Gerbers — with the checks that decide whether a fab house builds it or sends it back.
Hardware description taught as hardware, not as programming — RTL that synthesises, testbenches that prove it, and designs that meet timing on a real FPGA.
Robots built and tuned on a bench — drives, sensing, closed-loop control and ROS — because a machine that moves fails in ways no simulation shows you.
Rooftop and small commercial solar taught end to end — honest load assessment, sizing, mounting, wiring, protection and net metering — with the site realities that shrink a paper design.
Jewellery design taken to manufacture — sketching, CAD modelling, stone setting and casting constraints — with the metal weight and costing a workshop will hold you to.
NURBS modelling for shapes parametric CAD handles badly — clean curves, continuous surfaces and watertight solids, with Grasshopper for anything repetitive.
The jewellery-specific CAD workflow — builders, gem tools, pavé and rendering — used properly, so the model that leaves your screen can actually be cast and set.
Relief modelling and CNC toolpath generation — vectors, layered reliefs, roughing and finishing strategies — with the tool and material judgement that decides cut quality.
Questions
Roughly one and a half to two times as long in calendar weeks, because you cover fewer hours per week. The syllabus, projects and trainers are identical. A four-month weekday course typically runs six to seven months on weekends.
No. The same trainers teach weekday and weekend batches, and the syllabus and project deliverables are the same. We would rather run fewer weekend batches than staff them differently, because the whole point is that the course is not a lesser version.
Between six and ten, depending on the course. This is the part working professionals underestimate. Class time teaches the concept; the practice between sessions is what makes it stick. If you cannot find those hours consistently, tell us and we will suggest a longer batch instead.
Tell your trainer in advance. Depending on the course you can attend that session with another batch or catch up on the lab work with support. Missing occasional sessions is manageable; missing the practice between them is what causes people to fall behind.
Next step
Tell us what you want to learn and we will help you pick the right course, batch and mode.
