You do not universally need the GRE for a master’s in computer science. The requirement depends on the university, the exact programme, the entry cycle and sometimes the applicant’s circumstances. A programme may require scores, accept them optionally, waive them under conditions or refuse to consider them.
Check the current programme instructions before booking a test. “GRE accepted by the university” does not mean “GRE required for this master’s,” and “not required” does not always mean “not considered.” Those differences can change how you spend preparation time and money.
Start with the exact degree and entry term
Universities may offer several computing degrees: a research-oriented MS, a professional master’s, an online programme or a related data-science degree. Their admissions rules can differ even when they share a department or similar course titles. Use the exact programme name and campus in your search.
Record the intended entry term as well. A requirement described in an older application cycle may no longer apply. If the page does not clearly identify the relevant cycle, look for the current application instructions and ask the admissions office to resolve any remaining ambiguity.
Programme requirement
The department's current instructions identify whether the score is required, optional, waived or not considered for your application.
University-wide information
General graduate guidance may establish a default while allowing departments to set different rules. Read both where necessary.
I would build a shortlist before making the GRE decision. One required-score programme can change the plan for the whole application season, while a shortlist consisting entirely of programmes that ignore scores gives little reason to test solely for those applications.
Understand the four common policy categories
Required means the programme expects a qualifying submission under its stated rules. Optional means it allows you to decide whether to submit, though you should still read any explanation of how results are used. A waiver means a normal requirement may be removed when specified conditions are met.
Not considered is a stronger statement than not required. If a programme says it does not consider GRE results, sending a high score should not be treated as a hidden route to improving the application. Follow the instruction and focus on evidence the programme actually reviews.
| Policy | What it usually means | What to verify |
|---|---|---|
| Required | A score is part of the application requirements | Deadline, accepted test and reporting instructions |
| Optional | Submission is allowed but not mandatory | Whether the programme explains its evaluation role |
| Conditional waiver | Specified applicants may omit it | Eligibility and whether approval is automatic |
| Not considered | Scores are not used in review | Whether the instruction covers your exact degree |
| Unclear or conflicting | The requirement is unresolved | Written clarification from the programme |
Do not infer a waiver from someone else’s profile. Nationality, prior degree, work experience or another condition matters only if the programme’s current policy makes it relevant. A successful applicant’s anecdote does not replace the published rule.
A verified example shows why assumptions fail
Stanford’s computer science admissions policy states that GRE scores are neither required nor considered for its MS applicants. That is an example of a specific programme policy, not evidence that all computer science master’s programmes follow the same approach.
The lesson is methodological: read the programme’s own wording instead of applying a broad claim about US universities, highly ranked schools or computer science as a subject. A rule for one department cannot safely be extended to another without checking.
Keep a dated note of the policy while preparing your application, then recheck it before submission. Admissions instructions can change, and a page you saved during early research may not remain the final authority for a later cycle.
Decide whether an optional score adds useful evidence
If scores are optional, think about what the rest of the application already demonstrates. Relevant coursework, grades, projects, research and professional experience may provide substantial evidence of readiness. A test result is one possible additional signal, not a universal repair for every weakness.
Compare the likely benefit with the preparation cost and the time available. If testing would displace work on required materials, the trade-off may be poor. If several target programmes require the GRE anyway, taking it may make sense independently of its optional role elsewhere.
Avoid invented thresholds such as a score that guarantees admission or automatically cancels out a weak transcript. Unless the programme publishes a minimum, do not turn online averages into requirements. Even a published minimum describes eligibility or guidance, not a promise of acceptance.
Do not confuse the GRE with English-language testing
The GRE General Test and English-proficiency tests serve different purposes. A programme can omit the GRE while still requiring evidence of English proficiency from applicants who do not meet its exemption conditions. Conversely, meeting an English requirement does not automatically satisfy a GRE requirement.
Read the language-testing policy separately, including exemptions and accepted tests. A prior degree taught in English may matter at one institution and require different documentation at another. Do not assume that a rule from one application can be copied across the entire shortlist.
This separation is especially important when planning expenses and dates. A student may decide correctly that the GRE is unnecessary but still discover too late that another required test or document has a processing period. Maintain separate checklist items for each requirement.
Build a programme-level application tracker
For each programme, record the degree name, campus or delivery mode, entry term, deadline, GRE category and the source of the instruction. Add whether self-reported scores are accepted initially and when an official report is required. This converts vague research into a decision you can act on.
Include non-test requirements in the same tracker: transcripts, recommendations, statement, résumé and any programme-specific materials. Their exact form varies, so use the programme’s instructions rather than a generic list as the final checklist.
A hypothetical applicant considering four programmes might find one required-score option, two optional options and one that does not consider scores. The required-score programme then becomes the main reason to schedule the GRE. That is a planning example, not a description of particular universities.
Allow time for official reporting
An unofficial number shown at the end of the GRE is not the same as an official score report received by a university. ETS currently gives a normal official release window of 8–10 days after the test. The receiving institution may also need time to match the report to the application.
Check whether the deadline concerns taking the test, submitting self-reported results or receiving official scores. These conditions are not interchangeable. If you are close to a deadline, ask the programme what it accepts before relying on a last-minute appointment.
If you already have scores, check reportability and any programme-specific age rule. Then verify the recipient details and which administration you intend to send. A report sent to the wrong place or outside an accepted period does not become useful simply because the score itself is strong.
Resolve conflicting pages with a precise question
A university’s general admissions page may describe a default GRE requirement while the department publishes an exception. Look for explicit language establishing which rule applies. If the relationship is unclear, contact the programme rather than choosing the interpretation you prefer.
Write a concise question naming the degree, entry term and the two conflicting statements. Ask whether you must submit the GRE and whether a waiver or optional policy applies. You do not need to send a long biography or request an admission prediction to settle a procedural requirement.
Keep the response with your application records and follow any instructions it contains. If the reply still does not address your exact programme, clarify that point before paying for a test or submitting an incomplete application.
Strengthen the materials the programme actually evaluates
Where the GRE is not considered, invest effort in clear evidence of preparation. Explain relevant academic and technical work accurately, distinguish your own contribution in collaborative projects and choose recommenders who can discuss your abilities specifically. Do not replace missing evidence with inflated claims.
For a statement of purpose, connect your goals to the programme’s actual curriculum or research opportunities. Avoid generic praise that could describe any university. The objective is to show a coherent fit and a realistic understanding of the degree, not to compensate for an absent test with more adjectives.
Your next step is to classify every shortlisted programme using its current official instructions. Take the GRE when that verified shortlist or a well-reasoned optional submission justifies it. There is no universal computer science master’s rule, so the programme-level check is the decision that matters.