Statement of Purpose- A complete guide (MS)

admissions-commiteeAdmission Committees go through a thousand of documents every day, and therefore it is important that the ‘Statement of Purpose’ starts with a very catchy anecdote. Instead of writing something abstract and generic, one should talk about a specific instance that showcases the candidates’ initial motivation for the subject.  It is always advisable to pick up a recent incident for your anecdote.

For an MS course, the student should write a lot about technical skills. The technical contribution to the final year projects/ mini projects/ publications should be focused on.  In each case one should specifically mention the objective as the utility of the project reaffirms its significance.

The next part is to focus on the professional experience.  The contributions to definite projects mark the dedication, technical expertise and accomplishments of the student. As for example, the candidate can mention if he automated a process and saved time/ resources/ money.

Why MS? Why Now? This paragraph is most important because it showcases the reason why you want to choose MS at this point in time.

A statement of Purpose has no meaning without its goal statement. Admission committee wants to know if the SOPstudent has a career roadmap. Having mentioned the short term as well as the long-term goal, the candidate indicates a definite purpose.

The University paragraph is another indispensable part of an SOP. This is to convince the admission committee that the candidate has conducted the required research about the university. As for example, the Professor’s name and publications justify your reason behind choosing the university.

The conclusion is written to summarize the entire SOP.

The MBA candidates need to submit an Statement of Purpose only if it has been mentioned prerequisite document by the University.

Sharing is caring:
Book your Free Counselling Session now!

Planning to study abroad?
Get free 1-on-1 counselling with our experts

Subscribe to this blog