The training page is a catalogue of domains, not a single course with one fee and one length. Duration and fees are confirmed when you enrol. This note helps you pick a tab before you send a training enquiry. It does not invent a batch calendar, a salary, or a placement rate.
Training is a syllabus that ends in an artefact
Each track is meant to end with exercises and something you can show: a page, an API, a test suite, a query, a dashboard, or a small model lab. It is not attendance. After a programme you may apply for an internship or for job assistance. Those are not bundled automatically. If you need tickets and a completion letter, read the internship guide after you have the foundation. If you need mocks and a resume, that is a third step.
Web, when the goal is pages and interfaces
The Web tab lists frontend fundamentals (HTML5, CSS3, JavaScript, Bootstrap, TypeScript), React (hooks, routing, Redux or Context, API integration), Angular (modules, services, RxJS, Angular Material), and Node with Express (REST, JWT, middleware, uploads). Join fundamentals if you are comfortable with a computer and a browser and you have not built a page before. Move to React or Angular when you already want a component structure, not on day one if the fundamentals line is still unfamiliar. The training page’s own note for web says the exercises run from landing pages to a small UI that calls an API. Tools named there include an editor, browser devtools, and Git as you progress.
Full stack, when the goal is one application with data
The Full stack tab lists MEAN (MongoDB, Express, Angular, Node), MERN (MongoDB, Express, React, Node), and delivery basics (GitHub workflow, API design, Postman, deployments). Choose this when you want the front and the API in one project you can explain. Do not choose both MEAN and MERN at once to collect logos. Pick the front-end library you will actually demo. Delivery basics matter if your artefact never leaves your laptop: a repository and a request you can show in Postman are part of looking finished.
Mobile, languages, and data
Mobile lists Ionic (cross-platform UI, Angular with Ionic, native APIs), Android (Kotlin or Java basics, Android Studio, Firebase or SQLite), and iOS (iPhone and iPad apps, App Store delivery, shared product flows). Choose Ionic if you want one UI path across phones and you already lean Angular. Choose Android or iOS when the brief is that platform. Store delivery in a course is practice toward a listing. A client store account is still the client’s on paid product work.
Languages lists Python (OOP, a Pandas and NumPy introduction, scripts), Java (OOP, collections, JDBC), and C or C++ (memory, pointers, a DSA introduction). Pick a language track when a college subject or a job description names that language and you do not yet write it. It is a foundation, not a substitute for a full-stack artefact if the role you want is web.
Data lists Python for cleaning, exploratory analysis, and statistics basics, plus visualisation with Power BI, Tableau, and Matplotlib. Choose this when the artefact is a report or a chart a non-programmer can read. It is a different exit from a React portfolio.
AI labs, testing, databases, and cloud
The AI and ML tab lists machine learning with scikit-learn and model evaluation, plus deep learning and generative AI with a neural-net introduction and prompting for simple LLM apps. That is a course. It is not a production brief for a client reel. If you want Suon to make a promotional video, use the AI video guide, not this tab.
Testing lists manual testing (STLC, test cases, bug reports) and automation (Selenium, Cypress or Playwright, API tests in Postman). Choose it when you want to talk about quality in an interview, not when you want to avoid writing any code at all. Automation still asks you to read an application.
Databases lists MySQL (SQL, joins, indexing), MongoDB (CRUD, aggregation), and SQL Server (T-SQL, views, backups). Take a database tab with full stack, not instead of it, if your project stores users and records. Cloud lists Git and GitHub (branches, pull requests), Docker and CI (images, Compose, pipeline basics), and AWS fundamentals (EC2, S3, IAM, simple deploys). Choose cloud when deployment is the gap, after you have an app to deploy. A pipeline with nothing behind it does not demo.
How to write the enquiry
A second pass is worth doing after you pick the tab. Read the “who should join” and prerequisite lines in the open training section for that category, and notice what the project artefact is. Web ends in pages and a UI that calls an API. Data ends in a chart or a cleaned set. Testing ends in cases and bug reports. Cloud ends in a simple deploy of something that already exists. If the artefact does not match the conversation you want in a later interview, you have the wrong tab, even if the tool logos look attractive. Suon will not enrol you in five tabs to make the enquiry sound larger.
Name one primary tab and the artefact you want at the end. “React, and a small UI that calls an API” is enough to start. “Everything on the page” is not a track. Say whether you have already built the prerequisite the training page names for that category. Send it as a training enquiry. If you are a business wanting software rather than a seat, you are on the wrong page. Use the website or software guides instead.