What to do about the MCQ round when all your prep is DSA
Half of that test was never going to be about code.
We keep hearing a version of this after off campus drives.
I solved both coding questions. I still got nothing back.
Then we ask what else was in the test, and it turns out there were thirty other questions.
Operating systems, databases, networks, a few that just show code and ask what it prints.
Those were scored too, and nobody had prepared for them at all.
Two questions to sit with before you plan any more study time.
It is two tests stapled together
An online assessment usually has a coding part and a question part, and your score is both of them added up.
A student who is strong at one and blank at the other lands in the middle, which is where the cutoff quietly removes people.
The two halves are not checking the same thing, so they cannot be prepared the same way.
The coding part asks whether you can work out a problem you have not seen.
The question part asks whether you remember what you have already studied.
Practice builds the first one. Recall builds the second.
How much time the question half actually needs
Far less than students fear, and in a different shape than DSA.
Short passes, repeated, close to the test window, with the notes closed while you answer.
What the questions keep coming back to:
- Operating systems, databases and networks, at the level your own course already taught them
- Basic object oriented ideas, asked as a definition rather than as a design
- Code that is printed on the screen with a question about what it outputs
- Simple aptitude and reasoning, where the only real enemy is the clock
The output questions are the ones students lose most, and they are the least mysterious of the lot.
They are asking you to read code line by line and track what changes, which is the same dry run you already do at the end of a DSA problem.
What we tell students honestly
Revision can be done in the week before a test. The coding half cannot.
An unfamiliar problem on test day either looks approachable or it does not, and that is decided long before the test opens.
So if you have a month and you are weak at both, the coding half gets the daily hour, and the subjects get two short sittings a week.
A DSA Framework Session is built for the coding half specifically. From the first session itself you can approach a new problem on your own, on any topic, and even without daily practice after, you still know how to start.
The outcome, plainly
Clearing an assessment is usually about not being blank anywhere, rather than being excellent in one section.
Two coding questions solved and thirty left untouched adds up to the same rejection as a weak coding section.
If you are not sure which half has actually been costing you, bring your last two attempts to the free mentorship call.
We will go through what happened in those tests and tell you which half your next month belongs to.
If an assessment link landed in your inbox this Saturday, which half of it would you be worried about?
Until you can solve it on your own.