Three roles,
one program
Worked on a career development program from every angle: as the team lead who ran it and built its documentation, as a participant who went through it herself, and as a host manager who designed the onboarding framework on the receiving end. Each role informed the next.
Most people touch a program like this from one side. I touched it from three. Running it gave me the operational picture. Participating gave me the human one. Hosting gave me the chance to build what I wished had existed at every earlier stage. The infrastructure I created at each step was shaped entirely by what I had seen and felt at the one before it.
What I brought to this
What I learned
I spent years helping people find opportunities through this program: writing proposals, coordinating timelines, building the documentation. When I went through it myself, I saw it completely differently. The gaps I hadn't noticed from the outside became obvious from the inside. That shift directly shaped the onboarding infrastructure I built afterward.
The most consistent finding from participant feedback was that people didn't apply because they didn't feel ready. That wasn't a motivation problem. It was a tools problem. I responded by building things that made readiness feel attainable: a self-assessment, a skills framework broken out by hard skills, soft skills, and business acumen, and clearer proposal language that named what someone would actually gain. Treating feedback as a design input rather than a complaint is a habit this program built in me.
When the Residency opportunity came up for me personally, I was the one who hesitated. I had spent years encouraging others to push past that feeling. Having to take my own advice, and seeing it pay off, gave me a much more grounded way to talk to participants about the discomfort of growth.
The full arc
Three distinct phases across three years. Three different vantage points on the same program.
My starting goal was straightforward: grow awareness and bring in new opportunities. That meant going on what my manager called a "PR tour" — setting up meetings across teams to explain what Help Wanted and Residency were and what a good opportunity looked like. The growth from that outreach was clear. But alongside it, I was listening carefully to what wasn't working.
A Residency opened up for a role that felt like a stretch: more technical than my background, an unfamiliar team, a new set of expectations. I had spent years encouraging agents to apply for things that scared them. I applied.
"I didn't feel ready. It had been intimidating. But discomfort and the unknown is a sign that you're growing, not failing. You don't have to know everything to start. You just have to be willing to learn."
Now on the receiving end, hosting residents onto my own team, I built the onboarding infrastructure from scratch. Informed by every friction point I had noticed as a participant and every gap I had seen from the program side.
What changed
Every tool built at each phase made the next one easier: the proposals brought in better opportunities, the self-assessment brought in more confident applicants, the onboarding checklist made hosting repeatable for anyone. The program grew because the documentation grew with it. Three full-time transitions came from people who, at some point, had been told the opportunity existed and were given the tools to believe they were ready for it.