Karthik started Railway preparation the way most aspirants do โ with strong content knowledge but no real sense of how they'd perform under exam conditions.
The Turning Point
The shift came after Karthik started taking a full Railway mock test every week, treating General Intelligence as a section to be timed and measured rather than just "revised." Weak spots in Analogy showed up within the first two attempts โ spots that months of reading notes had never surfaced.
"I stopped guessing what my weak areas were," Karthik says. "The mock test results told me exactly where I was losing marks in General Intelligence, and I fixed those specific gaps instead of re-reading the whole syllabus."
What Actually Changed
- A weekly full-length mock, treated as seriously as exam day itself
- A same-day review of every General Intelligence mistake, not a "later" pile
- A short, Analogy-only retest a few days after fixing a specific gap
- Tracking accuracy trend over weeks, not chasing a single good score
The Result
Rank 748 followed roughly 7 days of that routine โ not from learning new content, but from converting known concepts into exam-day accuracy through repeated, analyzed practice. Karthik's advice to other Railway aspirants: the mock score matters less than what you do in the 24 hours after seeing it.
Analogy at a Glance
| Aspect | Detail |
|---|---|
| Exam | Railway |
| Section | General Intelligence |
| Topic | Analogy |
| Where it fits | One of the recurring sub-areas within General Intelligence that Railway draws on regularly, rather than a one-off inclusion |
| Best practiced via | Short, timed topic tests rather than long, untimed reading sessions โ the format Railway actually uses |
| Revisit frequency | At least once every 10 days while this topic is active in your plan, and once more in final revision |
| Signal that it's exam-ready | Consistent accuracy across three separate timed attempts on Analogy, not one good score under no pressure |
| Common failure mode | Understood in isolation, but not yet tested mixed in with the rest of General Intelligence under real time pressure |
Related Reading
Common Mistakes to Avoid in Analogy
A few patterns show up often enough in Railway General Intelligence preparation that they're worth naming directly, so you can check your own routine against them before they cost real marks.
- Treating Analogy as optional because it "doesn't come every year" โ when it does appear, the marks lost are rarely made up elsewhere in General Intelligence
- Learning the concept once and never testing it under time pressure, so the gap between recognizing an idea and applying it in Railway's actual format never surfaces until exam day
- Solving Analogy questions strictly in book order, which hides how Railway actually mixes difficulty within a single General Intelligence section
- Not tracking accuracy on Analogy separately from the rest of General Intelligence โ a strong overall General Intelligence score can quietly hide one persistently weak spot
- Leaving Analogy for the final week, which leaves no time to retest after fixing whatever turns out to be wrong
None of these are about effort โ they're about sequencing and measurement. Fixing them costs nothing extra in study hours, just a different order and an honest, topic-wise accuracy check instead of a single General Intelligence percentage.
The fastest way to tell whether any of these apply to your own General Intelligence preparation is to look at your last two or three Analogy attempts side by side. If the same kind of mistake shows up more than once, it's not bad luck โ it's a pattern, and patterns are exactly what a focused round of practice on Analogy is built to fix before Railway does.
How to Practice Analogy the Right Way
Start with a small, focused set of Analogy questions at medium difficulty โ enough to confirm the concept holds up outside a textbook example, not so many that a bad first attempt feels discouraging. Time yourself even on this first pass; the habit of checking the clock matters more than the specific number of minutes.
Once accuracy on that first set is consistently good, move to a mixed General Intelligence set that folds Analogy in alongside everything else โ this is closer to what Railway actually asks, and it's the only way to find out whether Analogy holds up when it's not the only thing on your mind.
Log every miss with one line: what you thought, what was actually true, and which of the two changes next time. Reviewed weekly, that log becomes a more accurate map of your General Intelligence weaknesses than any generic weightage chart.
Give the log a second pass at the end of each week rather than only after each test โ patterns that look like one-off slips in a single Analogy attempt often turn out, across three or four attempts, to be the same conceptual gap wearing different disguises. That weekly review is usually where the real fix gets found, not in the test itself.
Finally, resist the urge to move on the moment a Analogy test goes well once. One clean attempt can be luck, a lighter difficulty mix, or simple familiarity with that specific question set. Treat Analogy as settled only after it holds up in a mixed General Intelligence paper under full Railway time pressure, reviewed honestly rather than skimmed.
Frequently Asked Questions
Is it worth re-reading notes on Analogy the night before Railway?
A light final pass is fine, but it shouldn't replace the last timed test โ recognition under no time pressure the night before rarely predicts recall under real Railway conditions.
What's the fastest way to know if General Intelligence preparation is actually working?
A timed, Analogy-focused mock test is the fastest honest signal. Untimed revision tends to overstate readiness, since it removes the time pressure the real Railway paper won't.
Does difficulty level matter when practicing Analogy early on?
Start at medium difficulty rather than the hardest variants โ Railway papers are rarely uniformly hard on Analogy, and building confidence on the common question types first makes the harder ones easier to diagnose later.
What should change in a Analogy routine in the final month before Railway?
Shift from building new understanding to full-length, timed practice that mixes Analogy into complete General Intelligence papers โ the final month is for confirming exam-day performance, not for learning material for the first time.
Is it better to time a whole General Intelligence section or just Analogy questions individually?
Both serve different purposes: per-question timing while learning Analogy builds a sense of pace, while full-section timing later in Railway preparation tests whether that pace survives alongside the rest of General Intelligence.
What does a "good" score on Analogy actually mean?
Consistency matters more than any single number โ accuracy that holds across three separate timed attempts on Analogy is a far better signal than one high score under low pressure.
How often should Analogy be revisited once it feels solid?
At least once more before the exam, via a short timed test rather than a re-read โ concepts that feel solid under no time pressure don't always hold up in a full Railway attempt.
Practice this topic
Take a Free Test