the job posting said "5+ years program management, ideally with policy experience." i have 3 years and no policy background.
i applied anyway because the mission matched something i care about and i thought the worst case was a form rejection. it was a form rejection. but what happened between application and rejection is the thing worth sharing.
because they did bring me in for an initial call. and that call turned into a real conversation about the organization's direction that i found more interesting than most interviews i'd had for roles i was technically qualified for. the director of programs was just a genuinely engaged person who seemed to enjoy talking about the work.
when the rejection came she wrote a personal note attached, not a form, that said they were going with someone with more policy background but that my portfolio on community partnerships was strong and she was keeping my details.
three months later she emailed me about a coordinator role at a partner organization. different organization, better fit for my current experience level. i start in august.
the specific lesson i took from this: in the nonprofit sector in particular, the interview process is often as much about whether you're a plausible person in their ecosystem as whether you tick every box on the JD. the JD is frequently aspirational.
also, applying for roles you're slightly underqualified for is part of how you find out where your actual ceiling is. rejection that reveals the ceiling is more useful than never applying.
still felt terrible to get the initial no. that part doesn't change. but the sequence after it mattered.
4 replies
returner_ren (Primly starter)
the nonprofit ecosystem point is real. i've noticed that in smaller mission-driven orgs, who referred you or what adjacent work you've done carries more weight than specific years-of-experience boxes. the informal network is doing a lot of work.
ops_omar (Primly starter)
congrats on the august start. also good reminder that a rejection from one org in a sector isn't the same as a rejection from the sector. the director keeping your details and passing your name along is how a lot of nonprofit hiring actually works.
pivot_pat (Primly starter)
"the JD is frequently aspirational" is true across sectors but especially true in nonprofits and early-stage startups. they're writing the job they'd love to hire for, not the job they'll actually close. 70-80% of requirements is often enough.
Primly Team
One underappreciated part of “rejection recovery” is what you do immediately after a thoughtful no. If the rejection includes any signal (like “missing policy background” but “strong partnerships”), it can be worth sending one tight reply that does two things:
1) Confirms you heard the gap and names your plan to close it (even if it is just: reading list, volunteering on a policy adjacent project, shadowing, or a small writing sample). 2) Makes the referral ask easy: “If you hear of a coordinator or associate level role where partnerships are the main lever, I would be grateful if you kept me in mind.”
In most nonprofit processes at this level, hiring managers remember candidates who reduce the cognitive load and stay professional without pushing.
What is the best “post rejection” message you have sent (or received) that actually led to a referral or a second conversation?