Let me be straight with you: I am not someone who was going to crush the GMAT naturally. I come from Portugal, I studied engineering, and when I first sat down to take an official practice test on my own — zero prep, no plan — I got a 555. That number sat with me for a while.
I told myself it would be a one or two month thing. Intensive prep, done. Easy. I was very, very wrong about that.
But here I am, six months later, with a 675 (V88,Q83,DI79) and a 95th percentile — and honestly, a lot of the credit goes to understanding one simple thing: the GMAT is not a knowledge test. It's a pattern test. Once I accepted that, everything else started to make sense.
Why I Didn't Try to Figure This Out AloneI was doing what a lot of people do — preparing by myself using official materials, trying to categorize question types from scratch, building my own system. And I was failing at it. Not because I wasn't working hard, but because I was wasting effort reinventing something that already existed.
Later I actually came across an e-GMAT debrief interview online — someone sharing their story, just like this one — and thought, if they've already mapped all of this out, why am I spending weeks building a system from nothing? That was the moment I signed up.
What I didn't expect was how structured the foundation stage would be. The course doesn't just throw questions at you. It walks you through concepts in bite-sized chunks, then makes you apply each one before moving forward. There's a real logic to the sequence — concept files, then learning activities, then practice. And the learning level grades that come after each module kept me honest about whether I'd actually internalized something or just read it.
The CR Problem — My Worst Nightmare, Eventually My Best Section (100%ile)I want to talk about CR first because it was genuinely the hardest part of my prep, and also where I changed the most.
Around November and December, I was stuck. I couldn't pass the medium cementing quizzes on Scholaranium. Stuck at 50% accuracy — on medium questions. Not hard, medium. That is a really demoralizing place to be when you've been studying for weeks. I remember thinking, maybe this is just not for me.
What I did was give myself a break from it. I switched over to quant for a while, let the CR material settle, and when I came back I went through the application files again — slowly. Not to get through them faster, but to actually pay attention to the structure of every argument. What's the conclusion? What's the assumption holding it together? What kind of weakness would break it?
And then something clicked. I genuinely can't explain it better than that. One week I was stuck at 50%, and then I was hitting 70-80% on the hard cementing quizzes. It wasn't that I did anything dramatically different. I think I just spent long enough living inside the material that the patterns became obvious. The words change, the scenarios change — but underneath, it's the same structures repeating themselves.

The pre-thinking framework that e-GMAT teaches for CR was the key tool here. Before looking at the answer choices, I'd force myself to predict what a correct answer would need to do. That single discipline — pausing to think before jumping to the options — probably accounted for most of my improvement on that section.
Quant: Just practice won’t helpI thought quant was going to be my safe section. I was strong in math back in school. But the GMAT has a way of humbling you.
Here's what I did wrong at first: I just did questions. All day. As many as I could. I actually ran out of questions in certain topics — which is saying something given how many e-GMAT has in Scholaranium. And I wasn't improving. I was just doing the same type of wrong thing, faster.
The
error log provided on the platform changed that. Not just keeping one, but actually using it. After each wrong answer, I'd sit with it and ask — what type of mistake was this? Was I rushing? Did I miss a constraint? Did I not write out the given information before starting? The pattern I kept seeing was that I was trying to solve problems before I'd fully understood them. I was trying to be fast, and that was making me slow.
The process skill that really stuck with me was simple: read the question, write out the constraints, only then start solving. It sounds obvious. But in test conditions when you're watching the clock, your brain wants to skip that step. Training myself not to skip it was probably the most valuable thing I did for quant.
In my second attempt, I handled quant the same way — calm, methodical, even when I was low on time. Read. Write. Solve. And it held up.
Data Insights — Decent Progress, a Tough Test DayDI was never my biggest issue. I went through the course content, worked through the Owning the Dataset approach, and got comfortable with the different question types. My average on mocks was consistently around 81-83 for DI, so going into the exam I felt fairly confident there.
On test day, I hit one question that was genuinely hard and it threw me a bit. I think that disrupted my rhythm more than it should have. The score came in lower than my mock average and landed up with DI79, which was frustrating — but it also taught me something. Confidence in a section doesn't mean you're immune to a hard question derailing you mid-section. Managing that moment is its own skill.
The Mock RollercoasterMy first full mock after completing most of the course: 575-600. I sat there for a moment after seeing that thinking, all that work and I'm basically back where I started.
But the scores moved. Slowly and then all at once. The sectional mocks on e-GMAT were where a lot of the foundational work finally showed up — separately testing verbal and quant helped me see where my real weaknesses still were, rather than having them masked by a strong section. The analytics at the end of each test gave me great insights on the type of questions I was getting wrong, if I was overspending time on certain questions, rushing through which helped me improve.

One thing I got wrong early with sectionals was volume. I thought I'd improve faster by doing five or six a day. Instead I was exhausted and sloppy by the third one. Cutting down to one or two per day, with proper rest in between, gave me much better data and kept my stamina intact. More sessions wasn't the answer — better sessions were.
About a week before my second attempt, I took a mock and scored around 80th percentile. That sent me into a spiral. Then I took an official mock and hit 95th percentile. That's the GMAT experience — variance is real, and at some point you just have to make peace with it.
The First Attempt, and What Actually Mattered After ItMy first attempt didn't go as planned. One section went sideways, and when that happens on the GMAT it has a way of carrying into the next. I came out knowing I hadn't shown what I'd built.
Here's the thing though — my mentor Abha helped me see that the work was already done. In the two weeks between attempts, we didn't go back to fundamentals or learn anything new. We just did sectionals and full-length mocks, working on test-taking discipline specifically: pacing, mental stamina, switching modes between question types. The foundation was solid. It was the execution that needed calibrating.
That reframe — the work is already there, you just need to show it — made a real difference going into attempt two.
Test Day: Madrid, Coffee, and No NotesI'm from Portugal, and my nearest test center didn't have open slots, so I traveled to Madrid to take the exam. One hour before it started, I had a coffee — I'd deliberately avoided caffeine in the days leading up so it would hit harder. That's my version of test day prep.
I did verbal first, then quant, then DI. For verbal, I didn't take a single note during the exam. For CR, I ran the pre-thinking process entirely in my head. For RC, I spent real time on the passage upfront and trusted that the detail questions would come faster as a result. That approach worked.
Quant felt uncertain. The first question didn't seem hard, which made me think my verbal had gone terribly. I bookmarked a few questions I wasn't sure about and kept moving. I grabbed food during the break, reset for a few minutes, and went into DI trying not to carry any of the anxiety from earlier sections.
When I saw the results — 675, V88 — I couldn't process it immediately. Six months is a long time to wait for a number.
One suggestion— don't quit after one bad attempt. My first test didn't reflect what I'd built. If I had stopped there, all those months of work would have counted for nothing. The score that ends up on your application is the one you keep going for.
Attachment:
GMAT-Club-Forum-i2ayn9rv.png [ 94.54 KiB | Viewed 538 times ]
Attachment:
GMAT-Club-Forum-j8klp646.png [ 68.46 KiB | Viewed 517 times ]
Attachment:
GMAT-Club-Forum-dmjog8x2.png [ 70.21 KiB | Viewed 468 times ]