When I first saw 455 on that diagnostic screen, I googled what it meant. Bad idea. The percentile rank made it worse. I'm an engineer — numbers don't scare me. But that one did.
The DI section was the real culprit. I'd assumed accuracy was what mattered, so I was careful, methodical, and completely ran out of time. Lesson one: You cannot leave questions unanswered. I switched to e-GMAT shortly after. My mentor's response to my first email: This is aggressive, but doable if you put in the effort. That was enough.
Quant: From Q77 to Q87Logic Over FormulasEngineering instinct said: load up on formulas, grind through calculations. That framing was wrong. While going through the
e-GMAT course, I discovered Quant is about pattern recognition and logical application within a tight window — each topic has a handful of core concepts, and the exam tests which approach you find fastest.
Word ProblemsThe main thorn. Problem statements are deliberately wordy, designed to blur which variables matter. My approach: deconstruct, write out the core variables, solve, then check against the original constraints before marking. The e-GMAT
error log revealed a recurring blind spot — implied constraints. The distinction between integer and positive integer kept catching me. Once I started tracking every instance, it became a pattern I could fix. Before the exam, those logs were my best revision tool. On test day, whenever I saw "integer," something clicked automatically.
CementingThe e-GMAT Scholaranium cementing quizzes were where real improvement happened. The urge to skip ahead is irresistible — you finish a concept and think, I get this, let me move on. The platform pulls you back. My mentor was clear: you're at 50%, but don't move yet. Push to 70%. The difference between those two numbers is the difference between thinking you understand something and actually executing it under pressure.
Verbal: From VA81 to VA84Critical ReasoningIt isn't intuitive reasoning — there's a structure to it. The
e-GMAT course introduced me to the negation test for assumption questions and pre-thinking — forming an expectation of what the correct answer looks like before reading the options. That shift changes how you evaluate choices entirely.
My mentor walked me through a progression I resisted: slow down, understand the failure mode, then accelerate. Ten minutes on a question, then five, then two and a half. I kept trying to shortcut with volume. He told me volume wasn't the issue — I hadn't internalized why I was getting things wrong. He was right.
Reading ComprehensionI developed a paragraph-by-paragraph note approach — four to five words per paragraph, capturing what the author is doing and where they're going. For shorter passages, this works beautifully. For longer ones, I adjusted to noting structure rather than detail. Main idea and inference questions practically answered themselves.
Data Insights – Making Peace with IncompleteDI was always going to have the least prep time. My mentor's guidance: don't chase everything equally. Data Sufficiency is learnable and the highest-volume question type — the e-GMAT DI course made this prioritization clear. TPA builds on Quant concepts you already know. MSR I didn't touch. DI79 with genuinely limited prep time. I'll take it.
The Mock RollercoasterThis part is hard to write because it was genuinely messy. Great quant in one test, verbal falls apart. Strong verbal next time, quant slips. A 635 gave real hope. A 595 shook it. The day before the exam, my last mock was a 595.
What I held onto: across those mocks, I had done each section well — just never in the same test. My mentor reframed it: you've demonstrated the ability. Now the job is to put it together in one day.
Those mocks also taught me de-calibration the hard way. I'm decent at Number Properties, but I'd stay on a stuck question because I was supposed to be good at it. Five, six minutes gone. Last four questions unattempted. The e-GMAT sectional mocks made this pattern impossible to ignore. My mentor had said early on: at 1:50, you know whether you have a path forward. If you don't, leave it. That only became real after a couple of quiz scores I couldn't explain in my update email.
Key Takeaways- Complete the section — an unanswered question costs more than a wrong one
- Don't move on at 50% cementing accuracy — get to 70%. That gap is where execution lives
- Error logs are revision tools, not just records — write them well and read them before the exam
- De-calibration takes practice; a few badly timed disasters will teach it faster than theory
- For DI with limited time, go deep on Data Sufficiency first
Final ThoughtsThe e-GMAT platform is completely self-sufficient. Following the structure without shortcuts — and having someone actually track your progress, push back when you rationalize "close enough," and reframe the hard moments — changes how seriously you take the process.
220 points. It took longer and felt harder than I expected at almost every stage. Worth it.
Attachments

GMAT SC.png [ 40.95 KiB | Viewed 152 times ]