CAT 2016 – Game of Stools

I wasn’t planning to write an analysis this year, but several people have asked me for one and I figured it would be simpler to type it out once rather than again and again. As in the past, I’ll divide this into two posts, this one detailing the overall test-taking experience (which could be of use to next year’s candidates, I suppose) and another short one with my take on the test structure and level.  Some of you might directly wish to jump to the other one 🙂

Pre-test procedure:

I wrote CAT ’16 in the afternoon slot, at ARMIET Shahapur (ARMIET being Alamuri Ratnamala, um,  something something…this college has a name a South Indian could envy). Shahapur being a little beyond Asangaon – the local train frequency to which is abysmal – I had to leave by 10:30 and reach by 12:15. The whole train was full of CAT-takers as the next train was scheduled an hour and a half later. We were milling around outside till 1:15 (in extremely hot and dry weather), resulting in headaches and grumpy faces galore. In the meantime, some people got calls and messages from those in the first slot and got some inkling of the now-infamous pi-root confusion. Also, there were rumours that the DI section was easy, which seemed to make people happy.

Officially, we were allowed to carry only the admit card (to repeat what I said last year on the topic of admit cards, please make sure the print is decent; black and white is fine, but the photo should resemble you and the signature should be reasonably clear, and you need to stick one recent colour photo on the card) and an ID proof. The security check was surprisingly lax with no proper frisking and people with bags wandering all over the place trying to figure out where to go for the photo/thumb impression procedure (at least two people in my lab had carried their own pens and one his wallet). Also the labs were embarrassingly ordinary, with no AC and with three-legged backless stools instead of chairs. The first computer I was given did not start up. After half an hour of increasingly irritated hints and reminders to the invigilators I was finally allotted another (which turned out to have a mouse issue – more on that later). As in the past couple of years, everyone was handed a sheet of A4 paper and a pen . One could ask for more paper if one so desired, but I stuck to my policy of environment-friendliness and managed with just the 1 sheet.

During the Test:

I will talk about my own experience further down, but first a few general points worth noting:

  1. Scoring: the test instructions stated: for MCQs: +3 for a correct, -1 for a wrong and no penalty for unattempted questions. For TITA: +3 for correct, no marks deducted for wrong. However the individual questions mentioned +1 / -0.33 and +1 / 0 respectively. It should make no difference, either way the marks will be scaled to 300 I suppose.  However, this rattled quite a few people apparently.
  2. The sections were not further subdivided – last year VA had two sub-tabs for RC and VA and one could freely move between those during the available 1 hour. Similarly the DILR section had separate tabs for DI and for LR. This year each section was all in a single lot.
  3. The question palette was adjustable: it could be shrunk to the side on a click, and brought out again on another click. In theory, this was a nice idea, but in practice I think the implementation fell a bit short. As a result, every time one clicked an answer, the entire palette took a second to refresh. Consequently, the interface was not as smooth as in the past.
  4. The Calculator was a fairly basic one, unlike the (useless) scientific one of last year.
  5. As in the mock, there were more DI and fewer LR questions, much to the dismay of the majority who prefer LR. Also, once more there were 24 RC questions and reading skills were at a premium in the Verbal section. 
  6. The number of TITA questions reduced from last year.

For me, personally, the act of actually taking the test turned out to be easily the most irritating testing experience I have had over the past few years. It started off smoothly enough as the VARC section seemed easy. However, a few questions into the section I realised that something was seriously wrong as many questions I had answered were showing unmarked. After a few minutes of frantic experimentation I found the problem – the mouse was double clicking most of the time. So when I marked an option, it got marked and unmarked again in the same click. This led to a frustrating experience for the rest of the test, wherein I would click, check to see if it registered, try again…. In some cases it required as many as 5-6 attempts to get a question answered. And of course, it meant it was impossible to use the calculator, because typing a number like 1569 gave a result like 155669. Also, at the end the mouse seems to have unmarked one question in VA as the final tally showed me 33 and not 34 attempted.

On the whole, other than raising my blood pressure, this did not affect me much in the QA and VA sections since I usually have time left over in these (though I could not check my answers at the end as I normally do). In DILR, though, I rarely have spare time (less than 2 minutes, last year) and additionally had to calculate everything manually. As a result I ended up leaving 5 questions there, 1 set and 1 extra question. Still, the set I ended up leaving was arguably the nastiest of the lot (most people I have heard from seem to have left that even after trying it) so I suspect no great loss there. Overall I ended with 94 attempts, the first time since the CAT went online when I was unable to attempt everything. The questions I left were anyway the ones which seemed the nastiest, so it might not have much adverse effect on my score. However, that is kind of beside the point.

Had I been a serious aspirant, such an experience would certainly have severely hurt my performance. The frustration alone would have been traumatic. Add to it the lax security, the terrible seats, the announcements on the PA during the test – on the whole it left a lot to be desired, a disappointment given the much better experience of the past two years with TCS. In fact, my worst experience since the 2009 debacle. And my disenchantment was not over yet….

After the test:

Again, a long journey back (I got home at 8:30 pm eventually). Eventful, too, as the saga of the Facebook posts during the test was all over social media by then. I wish it could be brushed aside as a one-off aberration, but having seen the casual nature of security in my centre and heard what happened in other places….

I think the IIMs need to take a long hard look at these problems for next year, even if they choose not to publicly admit that anything went wrong. Anyone can say “concluded successfully” and “detected and dealt with” and brush it off. But it needs to be true as well. The trust of people in the sanctity of the test can be pushed only so far; and it is in the IIMs’ own long-term interests to maintain a certain standard. It is easier to maintain a reputation than to rebuild it.

I will shortly put up another post with my take on the paper. For a couple of other points of view, check out T’s post at CAT 2016  and V’s post) at CAT 2016


4 thoughts on “CAT 2016 – Game of Stools

  1. I agree with your point that this year’s exam experience was surely worse than last year’s. I had appeared just for the sake last year, as I was in my final year, but this year I had prepared for CAT 2016.
    The exam last year, though, difficult was great with user experience of software and strict security check. However, this year my center at Kalyan was filled with lousy people. T
    he test center had only 60 CAT aspirants to be seated but only48 PCs were working, of which 5-10 started working minutes before the test started. Also, luckily there were as many as 10-11 who didn’t show up at the center, probably due to its remote location or maybe lack of motivation, so the things went okay for center in that sense.
    Also, like last year, there were no cardboard compartments between aspirants sitting at my place. And the distance between the sittings chairs was less than what one has in crowded local train, I could get easily distracted with any movement of the person besides me and vice versa. To add to disappointment, when the exam started the lights in the center went off, thanks to a backup generator the PCs were working but lights and fans were switched off. So I literally solved verbal in darkness with no fans which added up the heat with my blood pressure rising due to frequent disturbances from the person besides me and no invigilator even looking around and asking him to stop talking loudly.
    To add to the frustration, person besides me had to switch his place mid-exam because the internet disconnected during his QA section. And my faulty screen was greeny due to which I was seeing question reviewed markers in brown and yellow instead of blue and green. Also, the mouse problem you describe was also there for me, which led to 1 min wastage while marking for a PJ TITA.

    I had made a promise to myself that I won’t blame external factors for my failure to not score but sometime when others report good experience and you couldn’t concentrate only because of such terrible arrangement, you at-least once think that maybe things would have been different..but let’s reserve that until the reserve day.

    Any way to let IIMCAT know about my worst experience with the center? Just to point out, this was a Symbiosis approved test center!

    • You could mail them (or call, but mail is better as there is physical evidence of your complaint) at whatever contact is provided on the website. But I doubt it will make a difference, honestly. As I replied to your earlier comment, it would be more fruitful to move on to the next exam you’re taking rather than dwelling on this and wasting your energy.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s