What Reviewers Look For in the MS SOP — Engineering
This rubric looks for a clear engineering-focused statement that leads with what you can do now, shows specific technical preparation and work, and explains a realistic direction for graduate study or professional practice. It also checks whether you connect your preparation to the program and make claims about your abilities that your examples support.
What We Check
What the statement's opening establishes about the applicant before it establishes anything else.
The account the statement gives of what the applicant has been trained on and at what level.
What the statement shows the applicant producing with the preparation it claims.
Whether the direction the statement states sits at a level the preparation it shows can support.
Whether the statement connects the receiving program's own demands to the preparation the applicant has.
Whether every claim the statement makes about the applicant's readiness is either bounded or named.
Mistakes We Flag
- Starting with childhood interest or broad passion
- An extended early-life story, lifelong-passion statement, or general description of engineering can delay the evidence readers need about your current skills and goals. Lead with a course, project, measurement, analysis, or build instead.
- Listing courses or tools without showing their use
- A list of classes, grades, or software does not show what you learned to do. Explain the topic, level, or output of a course, and name a problem you used a tool to address.
- Describing team work without your role
- If every sentence says what the team or company did, readers cannot tell what you handled. Identify a calculation, decision, component, test, repair, or analysis you personally completed.
- Naming a project or program feature without a connection
- A build is more useful when you say what it had to achieve, and a program course, lab, track, or faculty interest needs a link to preparation you already describe. Prestige or a list of names alone does not make that connection.
- Making broad claims with no evidence
- Claims such as expertise, mastery, or being fully prepared need support from a course, standard, tool, or piece of work. State the extent of your experience and use concrete examples.
How this rubric reads your essay
- Built from published reader guidance — the sources are listed below.
- Scored per section against defined criteria, not general impressions.
- Calibrated for consistent scoring, so a better draft shows up in the score.
References
Supports reading a coursework or professional engineering statement on the same terms as a research one, and the 500-to-1,000-word length these programs publish: the graduate college posts a research-focused prompt set and a separate professional-focused set side by side, both at a 500-1000 word maximum, and the professional set asks no faculty question and no scholarly-question item.
Supports naming the branch of engineering you want to work in rather than the discipline alone - "You will be required to describe exactly what you wish to study." and "'Mechanical Engineering,' for example is not specific enough." - and leaving life history to another document, since "It should not be a personal life history."
Supports writing about something you designed or built and what it had to do: several engineering master's programs here ask "What was the most complicated thing you've ever designed/built, either physical or virtual? Please describe it here."
Supports putting numbers on your experience ("Quantify your experiences to show concrete impact. How many people were on your team? How many protocols did you develop?") and keeping a childhood story short, since "If you talk about it at length (more than ~2 sentences), you are taking up space that should probably be used to talk about who you are today."
Supports treating a very short statement as complete: master's applicants here get a "Statement of Purpose (1,000 -character limit)", and the department adds that "The research concentration areas play a key role in who will review your application."
Supports the word band ("Approximately 500 to 1,000 well-selected words is better than more words with less clarity"), the technical-register rule ("Write technically, or in the style of your discipline. Faculty are the people who read these statements."), industry work as evidence, conditional faculty naming, and the separate-document rule ("The Personal History Statement should not duplicate the Statement of Purpose.").
Supports opening with what you can do now rather than a childhood story: "Avoid common clichés in your SoP. In particular, try to avoid childhood anecdotes or goals." and "The admissions committee is interested in your current goals, skills, and strengths."
Supports not needing to name a professor or a group: "However, not naming a specific group of interest is not an automatic 'reject'." It also counts competition work as real evidence - "Who is the one that took their project team to the national competition?"
Supports attaching real work to any professor you do name ("Do not just name-drop professors; make sure to mention their recent work and why it excited you.") and not spending space on your resume, since "You do not want to waste precious real estate by reciting what can already be found in your resume."
Supports writing a professional statement without a research question: the academic statement of purpose "should have a forward-looking focus. Tell us about your professional goals and how your academic background prepared you for the M.Eng. program.", and the separate personal statement is where personal motivation goes.
Supports using your discipline's ordinary technical words while avoiding sub-field jargon: "Use technical language where appropriate; however, avoid jargon and acronyms specific to your sub-field. Faculty from research areas across the department may read your application."
Supports a one-to-two-page statement and treating a career goal as a full answer: the department asks for a "one-to-two-page statement" addressing "some of the following" questions, the first being "What are your career goals after the completion of your degree?"
Frequently Asked Questions
Do I need research experience, a publication, or a faculty contact?
No. The rubric does not require a job, internship, publication, thesis, faculty member, or secured supervisor. Course projects, competition work, and personal builds can all show relevant work.
Do I need to name a professor or research question?
No. Naming faculty is optional, and a direction stated as a track or technical area plus a use for it can be complete without a research question. If you name a faculty member, connect that person’s work to your own preparation and direction.
How specific should my goals be?
Naming only the engineering discipline is too broad. Name a branch, track, concentration, technical area, class of problem, system, application, or technical use for the degree, and connect it to work or preparation you discuss.
How long should the statement be?
Follow the receiving program’s stated limit. Published limits vary, including 500 to 1,000 words, 1,000 characters, and one to two pages; a shorter statement can still work when it fully makes its case.
Get your essay scored across all 6 dimension with specific, actionable feedback. Two free reviews per day — no credit card required.
See how statement of purpose review works