Events & Promotions
|
|
GMAT Club Daily Prep
Thank you for using the timer - this advanced tool can estimate your performance and suggest more practice questions. We have subscribed you to Daily Prep Questions via email.
Customized
for You
Track
Your Progress
Practice
Pays
Not interested in getting valuable practice questions and articles delivered to your email? No problem, unsubscribe here.
Apr 2610:00 AM EDT
-11:00 AM EDT
The Target Test Prep course represents a quantum leap forward in GMAT preparation, a radical reinterpretation of the way that students should study. Try before you buy with a 5-day, full-access trial of the course for FREE!
Apr 2711:00 AM EDT
-12:00 PM EDT
Prefer video-based learning? The Target Test Prep OnDemand course is a one-of-a-kind video masterclass featuring 400 hours of lecture-style teaching by Scott Woodbury-Stewart, founder of Target Test Prep and one of the most accomplished GMAT instructors
Apr 2808:00 AM PDT
-11:00 AM PDT
Whether you are just beginning your MBA journey or fine-tuning your path to a 700+ score, GMAT Day is designed to give you a competitive edge.
14 Sep 2025, 03:45
Kudos
Bookmarks
Hi everyone!
I recently scored a 695 on my GMAT Focus Edition (Q88, V81, DI84) after what feels like the longest journey of my life. This was my third attempt, and honestly, I'm just relieved that I can finally move forward with MBA applications with a score I'm proud of.
I come from an engineering background and work in finance, so you'd think Quant would be easy for me. Well, GMAT has a way of humbling everyone, and I learned that the hard way over the past year and a half.
The Breakthrough MomentWhat led me to e-GMAT was actually a YouTube video about table analysis. I was watching Payal's video on how to spot correlation trends, and she explained this simple technique: just look at whether the first half and second half of data are talking to each other, and most of the time you'll get the answer.
I had solved so many data table analysis questions before, but nobody had ever taught me this simple technique. Coming from a math background, I used to calculate standard deviations and all that complex stuff, but GMAT is all about time management. That video made me realize I needed sharp, focused strategies rather than lengthy mathematical approaches.
Quant Journey: From Q80 to Q88Here's the thing about being an engineer taking the GMAT - you walk in with overconfidence thinking "I can definitely solve everything." But it's not about solving; it's about solving correctly under time pressure while avoiding what people call "silly errors" (which aren't silly at all - they're process errors).
My biggest revelation was understanding that my knowledge wasn't the issue. The issue was accuracy and process. I was making small comprehension errors - reading something but understanding something else. The process skill files in e-GMAT taught me to write down exactly what the question was asking before even starting to solve.
Initially, I skipped these process files because I thought I knew better. Big mistake. Only when I went through them systematically did I realize my accuracy improved dramatically, despite my knowledge staying the same. These files taught me to identify problem types first, then visually approach the problem, and only then start the solving process.
The PACE algorithm was incredible for someone like me who already had decent Quant foundation. It helped me skip concepts I knew well and focus on application gaps, saving me over 35 hours while maintaining effectiveness.
Data Insights: The 97th Percentile JourneyDI was initially my biggest fear. After that YouTube video discovery, I knew I had to focus here, but I was hitting everything randomly without structure.
Two major issues with DI preparation: limited practice problems (everyone treats the OG like a Bible you shouldn't touch) and no good interface to practice in GMAT-like environment. e-GMAT solved both - tons of additional problems and an interface that mimicked the actual test.
Going through the full DI course, I learned there are only five types of problems in DI. No problem will be completely new outside these five. What impressed me was how e-GMAT connected everything - they'd say "if you haven't done verbal comprehension, go there first." This showed real user insight about what skills are prerequisite for DI success.
My biggest realization was that my highest error rate was in non-math-related DI questions. This pushed me to strengthen my verbal foundation, which then improved my DI performance.
The Time Management Game-ChangerMy mentor Dhruv told me something that changed my entire DI approach: "You will always make two, three errors, and that's fine." I was aiming for 100% accuracy, which was impossible.
After analyzing the stats, I realized DI is the most forgiving section. At 82% accuracy, you're still in the 95-96th percentile. The penalty for not attempting a question is much higher than attempting it incorrectly.
My strategy became: attempt everything, make educated guesses on 4-5 questions I couldn't solve completely, and focus on getting the easier ones right. On test day, I even skipped a complex TPA question, made broad assumptions, marked two answers, and moved on. Turns out I got it right anyway!
Verbal: The Overconfidence TrapI had scored V85 on my previous attempt, so I got overconfident and didn't focus much on verbal prep. Big mistake. Test day brought really long humanities passages (my previous attempt had business passages, which aligned with my work), and I struggled.
The e-GMAT verbal course taught me fundamentals I didn't even know I was missing. I couldn't distinguish between main idea and primary purpose questions - I thought they were the same! The course taught me that primary purpose is more abstract than main point, and this clarity helped me approach these questions systematically.
Mock Test Reality CheckMy mock scores were consistently around 675-685, never hitting that 695-mark. But Dhruv always said 10-20 points variation on test day is normal, and he was right.
What made e-GMAT mocks valuable wasn't just taking them but analyzing them afterward. The questions were very close to actual GMAT difficulty, and I found them slightly harder than the real test, which prepared me well.
The sectional analysis helped me understand that when you perform well in early sections, later sections become harder due to the adaptive algorithm. This explained why my test day experience felt different across sections.
Breaking the Quant NarrativeThere's a narrative online that e-GMAT is great for Verbal but not for Quant. Having improved from Q80 to Q88, I can confidently say this narrative is outdated.
e-GMAT's Quant 2.0 offers: extensive problem bank, structured course progression, cementing quizzes for targeted practice, and the new Neuron OG integration. For someone at my level, I could focus on cementing quizzes rather than starting from basics, which was incredibly efficient.
The platform's analytics showed me exactly where I was spending too much time (4 minutes instead of 2 minutes on certain problem types), helping me identify process inefficiencies even when I was getting answers correct.
Test Day ExperienceQuant felt surprisingly easy, which initially worried me (I thought I wasn't getting adaptive difficulty). Verbal was challenging throughout, especially the RC passages. DI started difficult but became manageable once I applied my time management strategy.
The mental comfort of knowing I could make 4-5 errors in DI and still score well was crucial. I finished with 5 minutes left and reviewed every question, changing one answer.
Key Takeaways1. Process over knowledge: Especially for engineers, GMAT isn't about knowing more math; it's about executing correctly under time pressure.
2. Structured preparation wins: Random practice won't get you those final 50 points. You need systematic identification and fixing of specific weaknesses.
3. Listen to your mentor: Dhruv's guidance on time management, section strategy, and realistic expectations made all the difference.
4. DI is forgiving: Don't aim for perfection. Strategic question selection and smart time management can get you 98th percentile.
5. Platform quality matters: Having the right interface, question bank, and analytics can significantly accelerate improvement.
Final ThoughtsThis 50-point improvement took patience, structured preparation, and letting go of overconfidence. The journey from 645 to 695 taught me that the final percentiles are the hardest to achieve - you don't need help going from 60th to 90th percentile, but going from 90th to 98th percentile requires expert guidance.
To anyone struggling with similar challenges: trust the process, focus on accuracy over speed initially, and remember that those "silly errors" aren't silly - they're systematic issues that can be fixed with the right approach.
Thanks for reading, and feel free to ask any questions about my journey!
Attachments
GMAT Snap.PNG [ 25.19 KiB | Viewed 429 times ]
14 Sep 2025, 23:08
Kudos
Bookmarks
Hi, congratulations on an amazing score!
Can you kindly help with the resources for your prep?
Did you exclusively focus on the content provided by E-GMAT or referred to other resources as well? Would love to get some help on the DI resources
Can you kindly help with the resources for your prep?
Did you exclusively focus on the content provided by E-GMAT or referred to other resources as well? Would love to get some help on the DI resources
15 Sep 2025, 20:40
Kudos
Bookmarks
The way you discovered that your engineering background was simultaneously your greatest asset and your biggest obstacle is fascinating! That moment when you realized you were calculating standard deviations for table analysis while a simple "first half vs second half" comparison would suffice - that's the exact type of breakthrough that separates 645 from 695 scorers.
I'm particularly intrigued by something you mentioned that I see frequently but rarely articulated so clearly: the distinction between "silly errors" and what you correctly identified as "process errors." You wrote about comprehension errors - reading something but understanding something else. Can you elaborate on how exactly you caught yourself making these errors? Was there a specific moment when you realized these weren't random mistakes but systematic patterns?
The Engineering Paradox in GMAT Success
Your experience highlights a pattern I've observed across hundreds of engineers: the more mathematically sophisticated you are, the harder it becomes to embrace GMAT's preference for elegant shortcuts over rigorous calculations. What's interesting is how you transformed this liability into an asset by channeling that same analytical rigor into process optimization instead of problem-solving complexity.
For others from similar backgrounds reading this - notice how the breakthrough came not from learning more math, but from unlearning the instinct to over-engineer solutions. The DI strategy you described (accepting 4-5 educated guesses to ensure full attempt) demonstrates mature test-taking.
What was the hardest "unlearning" moment for you beyond the table analysis example?
I'm particularly intrigued by something you mentioned that I see frequently but rarely articulated so clearly: the distinction between "silly errors" and what you correctly identified as "process errors." You wrote about comprehension errors - reading something but understanding something else. Can you elaborate on how exactly you caught yourself making these errors? Was there a specific moment when you realized these weren't random mistakes but systematic patterns?
The Engineering Paradox in GMAT Success
Your experience highlights a pattern I've observed across hundreds of engineers: the more mathematically sophisticated you are, the harder it becomes to embrace GMAT's preference for elegant shortcuts over rigorous calculations. What's interesting is how you transformed this liability into an asset by channeling that same analytical rigor into process optimization instead of problem-solving complexity.
For others from similar backgrounds reading this - notice how the breakthrough came not from learning more math, but from unlearning the instinct to over-engineer solutions. The DI strategy you described (accepting 4-5 educated guesses to ensure full attempt) demonstrates mature test-taking.
What was the hardest "unlearning" moment for you beyond the table analysis example?
