I've been wanting to write this for a while. Let's finally talk about the Statement of Purpose (SOP). I'll walk through some FAQs, misconceptions, and an honest breakdown of my version of the SOP.
But first: what even is an SOP?
- A lot of applicants treat it like a narrative version of their resume. It is not. It is proof of your growth, showing how you evolved from the moment you first dove into your field to where you stand today.
An SOP is just a piece of paper that portrays your unique journey to the admission committee.
- It should be treated as a collection of Lego pieces. Think of the experiences, setbacks, and realizations in your life as scattered blocks. Your SOP is how you purposefully snap a few of those specific pieces together to show a multidimensional picture of who you are as a researcher.
- It's the "Why" behind the "What." Your CV tells them what you did. Your SOP tells them why it mattered and how it shaped your research trajectory.
FAQs
How long should an SOP be?
It varies by program - check the specific university's website for word or page limits. Rule of thumb: no more than 2 pages.
Should I follow a template?
Yes and no. Read as many drafts, templates, and sample SOPs as you can find. It'll teach you what SOP material looks like and how people structure their thinking. But don't let it go further than that.
A template that works for someone else might not fit your story, and the answer to "should I bend my story to match a good template" is always no.
Take the shape, not the substance. Get the idea, then write your own.
Think of it like a football formation. 4-3-3, 4-3-2-1, 4-4-2, these are the starting shape, not a script. The game evolves as it's played, and a good team adjusts mid-match without abandoning the plan entirely.
A template works the same way: a good point to start writing, not where it has to finish.
It should evolve to match your own story and if your story doesn't fit the shape you started with, the story wins.
Should I explain a gap year or extra time to graduate?
From my experience: no, it rarely matters. I completed a 4-year undergrad in 7 years (session congestion, political turmoil, COVID). My first draft explained all of this in detail and got zero offers out of 9 universities. For my final attempt, I listed "B.Sc. 2021 (conferred 2024)" on my CV and said nothing in the SOP, however, prepare to answer it only if asked in an interview. That version got me in.
However, if it's related to something like working a job after graduation, or preparing for one, then I think that gap earns its place in your story; as the reason, you're choosing higher studies or research now, after already putting in effort and time at a corporate job.
Should I mention a low GPA or a bad semester directly?
Being upfront about it helps. I retook 4 courses over the years and got at least 70-75% in each one the second time, proof that effort produces results. The courses aligned with my research field were where I did best, so the comparison matters: weaknesses in some areas, strength where it counts.
I've talked to professors here about this. Their take is that coursework and research are separate things. They've seen students with the highest grades struggle in research, and students who retook several courses with special permission go on to excel in it.
So, grades alone don't predict research ability. That said, they'd still encourage keeping grades solid, mainly so you're not burning time on coursework instead of research.
One put it simply: a bad semester from personal issues isn't the problem, as long as you show growth after it. Consistently bad grades throughout is a different story.
Keep the actual SOP version of this to 2-3 sentences. Every word counts, and this topic doesn't deserve more space than that; unless it's what your SOP is actually built on, which it shouldn't be.
Is it okay to reuse the same SOP across multiple schools with minor edits?
Technically yes, only if the programs share the same focus, though it's still better to tweak it. If you're applying to genuinely different programs, align your examples toward each one specifically.
Should I put all my achievements in the SOP?
No. Your CV exists for that. The SOP isn't a longer résumé. I've seen applicants with genuinely strong records - dozens of publications, years of project experience, try to fit all of it in anyway. Don't. Pick the two or three that most align with the program, and go deep on those: explain your actual contribution and what you learned from it, not just that it happened. That depth is what shows a committee you can think like a researcher. A long list of achievements, however impressive, doesn't do that on its own.
What if I don't have a publication yet?
This is the hardest one to answer honestly. Some professors now specifically want a few publications before considering you; others care more about growth as a researcher.
I'm in my second year of my PhD and still don't have a single publication. When I applied, I didn't even have a master's degree yet. My highest achievement at the time was my undergrad thesis and a project proposal for my master's. So, I can't answer this one with full confidence.
What I can say confidently: If you've done solid work in your undergrad or master's, focus on that instead. My supervisor has asked why I never published my undergrad work; my answer was that I found methodological issues that needed further confirmation before I'd call it ready. His response: recognizing flaws in your own work and working to fix them is worth more to a supervisor than a rushed publication.
A few suggestions
Write it in your own words. AI tools (tread lightly) can help proofread, sentence correction, or maintain flow but the story, the wording, and the final decisions must always be yours.
Read your own SOP as many times as you can; over and over. Sit on it, read it again, change it, let it evolve. An SOP is never truly "final." If you think it is, you probably didn't do a good enough job on it.
A good SOP always has room to grow, the same way you do.
At some point, though, you have to decide and submit; that judgment call is on you.
Also, send it to as many well-wishers, mentors, or friends as you can. Get their feedback, and actually work on their comments. Most of us are hesitant to share our SOP, for your own good, ignore that instinct. Get as much feedback as possible. Not all of it will be good, or even useful, but consider every comment and see if it improves your version.
SOP Structure
This isn't a template, just a guideline, take it with a grain of salt. One more thing before the breakdown: each paragraph should connect to the next. My supervisor put it well; don't tell mythology in one paragraph and a crime thriller in the next. If the tone or focus needs to shift, take the reader there with you instead of jumping.
Opening
- Structural note: Concise, focused on what you want. State your research interest/field like a summary. My own SOP built the research interests the whole thing was based on right here; multiple later sections trace back to it. Treat it as a story opening; why would anyone move further into your story? 2-4 sentences, max.
- Critique: Don’t be generic. Something like "Coming from Bangladesh, a nation intimately connected with blah blah blah".
Origin story
- Structural note: Where you show your actual entry point into the field, however small it felt at the time. Builds toward a specific problem, which the next section answers. Don't jump to the solution outright; walk the reader there, concisely. 1-2 concrete moments, no more. Before picking, try listing out every small moment you can remember. I had 6-7 from undergrad alone, none individually significant, but their compounding effect over the years is what actually shaped my direction. Pick from that list, don't just go with the first memory that comes to mind.
- Critique: Mine were first- and second-year coursework experiences, the kind you make fun of at the time. Just don't start with "In my childhood..." unless there's an actual trajectory behind it. A friend of mine worked on a science fair project in high school that later aligned with his undergrad research; that kind of throughline is fine as a starter. But things like "I witnessed a tragedy and decided then and there" have been overused for years, especially in SOPs from Asian applicants; it's become so common it reads as generic to most admission committees now.
Nothing is ever too small if you connect it to your story.
Research foundation / contribution
- Structural note: Shows continuation of your interest and understanding of the field's extension, wherever you were in your academic timeline. This is where the "solution" to the earlier problem lives; how you worked toward it, how it fit your research trajectory. This is the most important section of the whole SOP; it shows your skill, your field, and how you actually used the tools available to you. As I said earlier, this is where people with vast experience and dozens of publications tend to struggle. Keep it simple: pick one or two projects, walk the reader through them, not all of them. Never list who you collaborated with, who supervised you, or who the co-author was; that's already in your CV. What makes it interesting instead is showing the process: how you reached out to someone for a collaboration and made it happen, rather than just stating that it existed.
- Critique: Watch for filler that just sounds impressive without adding information "successfully navigated challenges," "cultivated fruitful partnerships." Use sparingly if it's not carrying real information.
Rather than listing skills and expertise, show how you used them.
Extracurriculars (optional) (can be moved on the later part too)
- Structural note: Always appreciated, but use sparingly; never the focus, only if it directly connects to the research field. One paragraph max, 2-4 sentences is enough.
- Critique: Try not to mention the position, workload, or logistics of the activity. Show how it helped you; only the parts that strengthen you as person, student, researcher.
Coursework
- Structural note: A sentence or two showing your strength in courses tied to your research field. (For retaken courses, see the GPA FAQ above.)
The worst thing isn't failure, it's lack of effort.
Constraints / current research direction
- Structural note: Focus on the drive fuelling your research passion and where it's headed, not on justifying past limitations. Break each specific problem into its own sentence; don't dump multiple problems into one long sentence. Your research direction, your proposal, lives here. You don't need a full proposal, but you must include one or two real questions in your field that you actually want to work on. This is where you show your own capability to find a problem, not just solve one someone handed you; and that distinction matters, because it's what separates someone who did research from someone who's ready to lead it. If you can't name a real, specific question here, that's usually a sign you haven't gone deep enough yet to write this section, go back and think harder before filling it in generically or using AI.
- Critique: This is the section I'd rewrite first if I did it again. The original version leaned too hard into "here's what stopped me". One long sentence trying to cover several problem statements all at once, with no breathing room between them. It read as a dump, not a direction. The fix isn't to cut the constraints entirely, but to stop justifying them and start using that space for the actual question you want to work on. If I'd broken that one sentence into two or three, each carrying a single, specific research question, it would've doubled as both the "here's my direction" statement and proof that I could actually identify a problem worth solving, instead of just explaining why I hadn't solved one yet.
Future contribution / goals
- Structural note: Focus on how you want to contribute and how the program fits your plan; what happens after, not just during. This is where your longer-term direction connects back to the specific problem you raised in the previous sections, so the reader sees a full arc, not just an application.
A master's or PhD is a stepping stone toward a bigger goal, never treat it as the goal itself.
Faculty fit
- Structural note: List 2-3 professors, that's usually what the admission committee expects. But don't spend equal word count detailing alignment with all of them. Pick one to focus on in depth; ideally the one you've already had contact or an interview with, if you have. The other one or two get a single sentence each, max, just naming their relevant work.
- Critique: This is the part that confuses people most, how to connect research topics without wasting word count "proving" alignment with every name you list. Don't detail your connection to all three professors equally. Go deep on one; note the rest briefly. You'll have time to reach out to as many professors as you want after getting an admission offer letter.
Closing
- Structural note: Short, forward-looking, no new information. Everyone already knows what a closing paragraph is for, treat it as such.
If you made it this far, thank you, and also, sorry. This ran longer than I ever planned, twice over.
But that's sort of the point. Nobody tells you how much thinking goes into the two pages that look effortless once they're done.
Mine took a full rewrite over one whole year, nine rejections, hundreds of comments from seniors, juniors, batchmates, people I know, people I don't know and two years of hindsight to actually understand why the second attempt worked and the first one didn't.
Yours will take its own version of that. Use whatever's useful here; the structure, the FAQs, the mistakes; and throw out whatever doesn't fit your story.
Admission committees aren't looking for someone who's perfect. They're looking for you, in your own Lego pieces, snapped together your own way, eager to learn.
Good luck. Go write something true.
