What the GRE Actually Tests, and Who Needs It

The most useful thing to understand about the GRE is what it is not. It is not a test of advanced subject knowledge, and preparing for it as though it were is the most common way graduates waste months.

It tests familiar content under unfamiliar pressure

The quantitative content stops at roughly secondary level — arithmetic, algebra, geometry, basic data interpretation. Nothing a numerate graduate has not met.

What is tested is whether you can handle that content quickly, accurately, and without falling for distractors written by people who know how careful thinkers behave.

This is why mathematicians and engineers sometimes score moderately. Their instinct is to solve properly when estimating would do, to derive rather than substitute the answer options, and to treat every question with equal rigour. All three cost time, and time is the binding constraint.

The verbal section is similar: the vocabulary matters, but the structural reading — spotting whether a sentence's logic is contrast or continuation — decides more questions than word knowledge does.

Who actually needs it

Fewer people than assume so, and it is worth checking before committing.

Requirements vary widely by country, institution and department, and several programmes have dropped it or made it optional. Some keep it for funding decisions even where admission does not require it.

Check the specific department's page, not the university's general admissions page, and not a summary written by anyone else. Departments within one institution frequently differ.

If your target programmes do not require it, the preparation time is almost certainly better spent on your research proposal, your writing sample, or your references — all of which weigh more heavily in most postgraduate decisions.

Preparing efficiently

Diagnose before studying. Take a full timed practice test cold. Most people discover their problem is pacing rather than knowledge, which points the preparation somewhere completely different.

Work on speed on easy questions, not difficulty. The score improvement for most candidates comes from doing routine questions faster and more reliably, not from mastering hard ones.

Learn the trap patterns. On quantitative comparison especially, the same oversights recur: forgetting negative numbers, zero, and fractions between 0 and

1. Keep a log of what caught you — the list is short and repetitive, and that is the point.

For verbal, read dense non-fiction regularly. Serious journalism and academic prose build the contextual sense that flashcards do not. Word lists have a place, but learn words in sentences and grouped by connotation rather than alphabetically.

The analytical writing

Often neglected because it is reported separately, and for some programmes that is a reasonable call — but check, because a few weight it meaningfully, particularly for international applicants where it doubles as evidence of written English.

If it matters for your list, the preparation is quick: understand what the two task types ask for, write three or four timed responses, and get them read by someone who will be honest about structure. Most candidates lose marks on organisation rather than argument quality.

A realistic timeline

Eight to twelve weeks of consistent work is enough for most graduates to move their score meaningfully. Beyond about four months, returns diminish sharply.

Sit it early enough to retake. Scores improve on a second attempt for most people, largely through familiarity, and leaving no room for one is an avoidable risk.

And treat it as a hurdle rather than a showcase. For nearly every programme, a score above the threshold stops being a differentiator — the application is won on the research proposal and the references. Spending six months to move from comfortably sufficient to slightly better is time taken from the parts that actually decide it.