Don't teach generic aptitude puzzles disconnected from the syllabus. Map what you already study each semester to what companies actually test in interviews, and train for real conceptual clarity there — not memorized definitions.
| Subject | What gets tested | Where it shows up | The common gap | Concept-clarity training |
|---|---|---|---|---|
| Programming Fundamentals (C) | Pointers, arrays, recursion, memory allocation, "predict the output" tracing | Online test + first technical round | Memorizes syntax but can't trace how code executes in memory | Trace-the-code drills; a mental model of stack vs. heap |
| Data Structures & Algorithms | Arrays, linked lists, stacks/queues, trees, sorting/searching, Big-O | Coding rounds, online judge tests, live coding | Can define a structure but can't choose the right one for a problem | "Which structure, and why" reasoning practice under time pressure |
| OOP (Java/C++) | Encapsulation, inheritance, polymorphism, abstraction; overloading vs. overriding | Technical interview, viva-style questioning | Recites the four pillars but can't give a working example | "Explain it with your own example" drills instead of textbook definitions |
| DBMS & SQL | Normalization, joins, keys, ACID properties, live SQL queries | Often a dedicated SQL round — near-universal | Knows normalization theory but can't write a correct JOIN under pressure | Hands-on query writing against a real mock database |
| Operating Systems | Process vs. thread, deadlocks, paging/segmentation, scheduling, semaphores | Technical rounds, viva | Memorized deadlock conditions but can't recognize one in a scenario | Scenario-based questions: "is this a deadlock, and why?" |
| Computer Networks | OSI/TCP-IP layers, HTTP vs. HTTPS, DNS, IP addressing | Technical rounds (lighter weight, still common) | Lists OSI layers but can't explain what happens at each one | Trace a real request end to end — "what happens when you hit enter" |
| Web Technologies | HTML/CSS/JS fundamentals, DOM, client-server model | Role-specific rounds, practical coding tasks | Knows the syntax but has never built anything end-to-end | Small real projects, not syntax study |
| Software Engineering | SDLC models, Git/version control, testing types | Technical/HR crossover, especially product companies | Can name Agile vs. Waterfall but never used Git or a sprint | Hands-on Git practice, a mock sprint simulation |
| Aptitude & Logical Reasoning | Quantitative aptitude, logical reasoning, verbal ability | First-round online test — the pass/fail gate for most recruiters | School-level math gone rusty from disuse | Timed practice sets — speed and accuracy, not re-teaching math |
| Communication / HR Round | Explaining technical answers clearly, project walkthroughs, behavioral questions | Final round, after technical clearance | Strong technical knowledge, loses the offer under pressure | Mock interviews with working alumni |
DSA and DBMS are near-universal across recruiters — they get the most training time. Web Tech only matters for students targeting dev roles. Effort isn't spread evenly across all ten subjects.
A low score on DBMS routes a student to the DBMS concept-clarity module specifically — not a generic "practice more aptitude" message.
Every placement season, alumni mentors report back the actual questions they were asked — feeding straight into the map, season after season.
"We make sure your students deeply understand what they're already being examined on, in the form interviews actually test it" — a claim a generic aptitude platform can't make.
The same method applies to MCA, BBA, B.Com and MBA — each has its own core-subject list and its own interview pattern. MCA leans even more DSA/DBMS-heavy at a deeper level; BBA, B.Com and MBA map to case studies, financial and marketing concepts, and group discussions instead of coding rounds.
Ask us about the map for your specific program.