Statement Of Interest Example

Writing a Statement Of Interest That Actually Gets Read

A Statement of Interest is a formal document where you outline your qualifications, objectives, and the specific value you bring to an opportunity. It is not a resume, it is not a cover letter, and it is definitely not a generic essay about how passionate you are. I have reviewed hundreds of these for organizations that solicit them regularly, and the ones that survive the first round share one trait: they answer a question the reader actually has before the reader has to ask it. Below is a stripped-down example of a well-constructed Statement of Interest. I have simplified the specifics, but the structure and the way the details are handled is close to what successful submissions look like in real professional environments. Applicant: Jordan M. Ellis
Program/Position: Senior Research Analyst, Center for Urban Infrastructure
Date: March 12, 2025

I am submitting this statement of interest in response to the Center for Urban Infrastructure call for senior analysts focused on municipal water systems. Over the past seven years I have worked primarily on aging water infrastructure in mid-sized municipalities across the Pacific Northwest and the Midwest. My work has centered on hydraulic modeling, regulatory compliance assessments, and cost-benefit analysis for replacement versus rehabilitation decisions. The specific projects that align most closely with this role include my leadership of a four-year study for the City of Tacoma evaluating pressurized vs. gravity sewer alternatives, and my coordination of a multi-jurisdictional assessment for the Willamette Valley Watershed District that produced a $12 million federal grant application. Both projects required integrating field data with existing GIS layers and producing technical memos for non-engineering decision makers, which is the exact intersection this position emphasizes. My current focus is on predictive maintenance models for water main failures using machine learning applied to legacySCADA data. I am particularly interested in the Center's recent publication on corrosion rate forecasting in ductile iron systems, and I see a direct opportunity to expand that work into predictive replacement scheduling for partner municipalities.

I have attached my CV, three writing samples, and two letters of reference. I am available for an interview at your convenience. The difference between this and most submissions I see is that it does not waste space on declarations of enthusiasm. It does not repeat the job posting back to the reader. It names the work, the results, and the gap it intends to fill.

How to Build One Without Turning It Into Noise

Start with the constraint you are responding to. If there is a prompt, a range of topics, or a word limit, treat that as the boundary, not a suggestion. I once spent about forty minutes editing a Statement of Interest down from 950 words to 420 because the original author kept restating their degree in paragraphs that added zero new information. A paragraph should do one thing. If it does two, split it or cut it. The structure that works most of the time has three functional parts: context, evidence, and alignment. Context tells the reader what you are applying for and why it matters to you in a single sentence. Evidence is the bulk of the document and consists of specific projects, numbers, outcomes, and methods. Alignment connects your track record to the organization's current work or stated goals. Too many writers reverse that order or merge evidence and alignment until both become vague. Word choice matters more than people admit. Replace vague verbs with precise ones. Instead of "I worked on a project involving water infrastructure," write "I modeled hydraulic performance for a $4.2 million pipe replacement program." The second version communicates scope, technical level, and outcome in the same breath.

Common Pitfalls I See Repeatedly

The most frequent mistake is treating the document as a narrative arc. It is not a personal essay. Admissions committees and procurement officers do not want a story about your journey. They want to know whether you can do the work, what kind of work you have done, and whether your priorities match theirs. Sentiment dilutes credibility here. The second mistake is overclaiming. I have seen candidates describe themselves as "expert" in areas where they have only taken a course or attended a workshop. Readers notice. They also notice when someone cites a metric without context, like "increased efficiency by 30 percent" with no baseline, no timeframe, and no method. That reads as manipulation, not achievement. A single qualifying phrase like "within a pilot system over eighteen months" makes the claim verifiable. A third issue is length inflation caused by padding. A Statement of Interest above 750 words rarely gains anything unless the opportunity explicitly asks for more. Conciseness signals that you understand what the reader needs. Verbosity signals that you are hoping volume will compensate for weakness.

A Real Edge Case and the Workaround

About two years ago, I was reviewing submissions for a transportation planning grant where the prompt asked for a statement of interest but did not specify word count or formatting. One applicant submitted a seventeen-page narrative that included personal background, a full project history, and a detailed methodology section. Another submitted one page that named three specific municipal partnerships, cited two published datasets, and linked directly to the grant's evaluation criteria. The one-page submission moved to the next round. The seventeen-page one did not. The workaround in situations like that is to assume the reader will scan before they read, and to put the highest-signal content in the first three paragraphs. If your core qualification does not appear early, it will not appear at all regardless of how detailed your later sections are. I also encountered a case where the applicant had relevant experience but it was distributed across three different roles at different organizations, making it hard to present coherently. The solution was to organize by project type rather than by employer. That let me group analogous work under unified headings and avoid the disjointed chronology that was making the draft unreadable.

When This Document Type Is the Wrong Tool

A Statement of Interest is not appropriate when an opportunity explicitly requests a letter of motivation, a personal statement, or a research proposal. Those formats have different conventions. A letter of motivation expects personal narrative and future goals. A research proposal expects hypotheses, methods, and timelines. A Statement of Interest sits somewhere between a brief capability statement and a targeted cover letter. Using the wrong format usually means your submission gets routed to the wrong reviewer. It is also less effective when you are applying to a role where the selection process is heavily structured around standardized testing or portfolio review. In those cases, the Statement of Interest becomes decorative rather than decisive. I have seen applicants spend six hours refining these documents only to have the decision made entirely on test scores or portfolio quality. That is not a failure of the document. It is a mismatch between the document and the evaluation method.

Practical Checklist Before You Submit

Verify that every claim ties to a specific result or deliverable. Check that the name of the organization and the title of the opportunity appear exactly as written in the posting. Confirm the word count if a limit is stated. Remove any sentence that could be removed without losing meaning. Make sure the alignment paragraph references something the organization has published or announced recently, not something generic about their mission. Readers can tell when the alignment section was written for a different audience and then lightly edited. The process is not difficult. It is just easier to mess up than it is to get right on the first pass. Most solid statements take three or four drafts to reach a state where the evidence carries the argument without needing rhetorical support. If you want a reference document to compare your draft against, the example above follows the same structure and restraint that the strongest submissions I have seen use. The main adjustment you will need to make is replacing the project names, metrics, and organization references with your own verified details.