An early-career story, and an honest way to tell it in an interview
I’ve spent 20 years learning to lead. A big part of that was learning to talk about the team. “We” hit the goal. I helped get us there. I trained myself to talk that way on purpose, because that’s what good leaders do.
Then I walk into an interview, and every “we” costs me a point. After two decades of giving credit away, I’m suddenly expected to speak a whole new vocabulary.
It’s harder than it sounds. I’m hard of hearing and have ADHD, and like a lot of neurodivergent people, I’m a facts person. If other people helped, “I did it” feels dishonest. So I say “we,” and I lose the point anyway.
Why I picked this story
It’s not the biggest program I’ve run. Years later I’d lead a CI/CD rollout across 22 Scrum teams and chair an architecture review board. But this is the project that took me from tech support into program management, and it’s the one I’ve always struggled to tell without either taking too much credit or hiding behind “we.”
How it started
Around 2011, I was a remote Technical Support Engineer at EMC. Customers kept telling us our case updates were hard to follow, and that it wasn’t clear where each case stood.
Part of the problem was the system itself. Every team managed its own update templates in our Oracle case management system, and they’d grown to well over 1,000. The interface couldn’t be changed. Engineers had to remember to set several fields and flags by hand on every update, which was clunky and easy to get wrong.
I had a habit of trying to fix our internal processes, and it got me invited to a Lean Six Sigma Kaizen event on customer communication. I was there to represent the support engineer’s view. I was one of only two support engineers in the room. Most people there had about 10 more years of experience than me, plus organizational leaders and program managers.
SET came out of that event, and our manager, MaryAlice, came up with it. I can’t take credit for SET itself. My part was making it real across a global organization that was known for resisting change. Some colleagues told me building a tool was a waste of time and I should just work my cases.
What SET is
SET stands for Summary, Evidence, Timetable. Every case update followed the same three parts:
- Summary: a short explanation of the issue
- Evidence: errors, logs, and what was found
- Timetable: the action plan and next steps
It worked because anyone reading a case could jump straight to the part they needed. An escalation manager could check the Timetable to see if the case was current. An engineer joining the case could read the Summary and Evidence.
What I built
My colleague Adam had built a small tool for our front-line intake team. I partnered with him, then took it over and made it my own.
I used AutoHotkey, a macro and automation program, to prototype an app that ran on every support engineer’s computer. It gave engineers SET as a simple 3-field form, so the design itself showed them how to use it. When they hit submit, it filled in the case and set all the right fields and flags automatically. The complexity stayed behind the scenes. It also had a timer for logging time on a case and an auto-update feature.
I had it track usage too, so we could see which templates were used most and when. That told us whether the program was working, and it meant we weren’t deleting templates blindly.
Then I worked with each product group on what SET could replace and what had to stay. Hardware dispatches needed their own variations so the case system could send the right parts to the field. Support limited to US citizens needed its own handling too.
I demoed it early and often, took feedback, and kept iterating. Adoption had to come from the bottom up (engineers) and the top down (leadership), not just town halls and an executive sponsor. I ran training in the US and Ireland and delivered about 50 presentations around the world: town halls, technical summits, roundtables, and executive briefings.
Who else made it happen
- MaryAlice, our manager, came up with SET.
- Adam built the original tool.
- Courtney handled logistics so I could stay on the critical path, and she crunched the numbers, including the adoption figure.
- Judy, our executive sponsor, fought hard for a global change that surely ruffled some feathers.
- Brendan laid the groundwork for the online support app I later moved off the old Oracle system.
The results
- 69% training adoption in the first 30 days after launch
- 85% of remote customer service engineers coached to compliance within 2 months
- Effective communication rating at a historic high of 80% in Q4 2011, up 5%, from customer survey data
- About 1,000 case templates audited and consolidated down to about 25
- A random inspection process as the quality check on case notes
- The EMC GTS SCP 2011 Audit Report named the SET practice a “Demonstrated Area of Excellence”
- The EMC Lean Six Sigma Cup in 2013
A gain like that usually took a year or more and several projects. This did it in one, and it made a bigger dent in global customer support than any project before it.
What it led to
The tool became the main driver for automating a lot of support tasks, and other parts of the company copied it. SET became the foundation for handing off cases, whether to the back line, the next shift or region, or another product group.
It also became the cornerstone of EMC’s new web-based support platform, support.emc.com, which replaced the old Oracle interface we couldn’t change. I became that platform’s Product Owner and Technical Program Manager. That’s where my career in program management started.
Two answers
So how do I tell all of that in an interview?
The “we” answer: “We built a case-notes tool and won the Six Sigma Cup.”
The honest answer: “Our manager came up with SET at a Kaizen event I was invited to as a support engineer. A colleague had built a small tool, and I took it over. I turned SET into a simple form that set every case field automatically, tracked which templates got used, worked with each product group, and ran the training in the US and Ireland. A teammate handled logistics and the numbers, and our executive sponsor fought for the change. We hit 69% adoption in 30 days and a record 80% communication rating, and it won the Lean Six Sigma Cup.”
The first is true but empty. The second is just as true, and the interviewer knows exactly what I did.
Why “I” feels dishonest
When your brain is wired for accuracy, “I” can feel like overclaiming. You remember who did what. Leaving them out feels like rewriting history.
Hearing loss adds a layer for me. For years, I wasn’t fully sure I’d caught everything said in a meeting. When you live with that doubt, you get careful about claiming things. “We” felt safer.
And after 20 years of leading teams, my vocabulary is built around “we” on purpose. None of this means my contribution was small. I put in the hours and was critical to the outcome. I just never learned to say so in a room built to hear “I.”
The simple version
Nobody builds a perfect answer on the spot. Interviews are already high pressure, and for neurodivergent candidates there’s more to juggle in real time. You need something simple enough to remember when your mind goes blank:
“It started with ___. My part was ___. I had help from ___.”
Filled in: “It started with a Kaizen event and our manager’s SET idea. My part was building it into a tool every engineer used, cutting about 1,000 templates to 25, and training engineers in two countries. I had help from a teammate on logistics and the numbers, and an executive sponsor who fought for the change.”
Where it came from, what you did, who helped. You stay honest, and the interviewer hears your part.
A practice drill
- Pick the story you tell most often.
- Write the three lines: where it started, your part, who helped.
- Say it out loud until it feels natural.
- Do the same for three or four more stories.
Writing it down first helps if you’re a facts person. Once it’s on paper, saying “I” is just reading the record.
Phrases to try
| Instead of | Try |
|---|---|
| “We came up with the idea.” | “My manager came up with the idea. I turned it into a working tool.” |
| “We cleaned up the templates.” | “I tracked which templates got used and worked with each product group on what to keep.” |
| “We trained everyone.” | “I ran the training sessions in the US and Ireland.” |
| “We hit 69% adoption.” | “We hit 69% adoption in 30 days. A teammate tracked the numbers, and I drove the training.” |
This isn’t only on the candidate
Candidates can practice, but interviewers carry part of this too. Many very capable people, especially good leaders, will struggle with “I” vs. “we” in real time, and that struggle says nothing about the work they did.
- Ask the follow-up. If someone keeps saying “we,” ask “What was your part?” Many will tell you exactly. They just won’t volunteer it.
- Judge the answer, not the pronouns. A precise “we” with clear ownership is a good answer.
- Share themes ahead of time. Telling candidates the topics you’ll cover lets them prepare real examples instead of building them under pressure.
Balance cuts both ways. Candidates can learn a simple way to own their part. Interviewers can make room for people who give credit by instinct.
I write about interviewing and working in tech with a hidden disability. If this helped, connect with me on LinkedIn.