this is the thing that tripped me up the most when i was going from nonprofit program management into tech ops. every interviewer wants to know 'why the switch' and if you're not careful you end up giving an answer that sounds like you're escaping something rather than moving toward something.
my first version of the answer was genuinely bad. 'i want more impact, i want better compensation, nonprofit work can be really thankless.' all true. all terrible to say out loud in a job interview.
what actually worked, after about 8 failed first rounds:
anchor it in a skill you've been growing toward, not a thing you're leaving. for me: 'i've been running vendor operations and cross-functional project coordination for four years. tech ops is where that skill set scales.' that's it. forward-looking, specific, not a complaint.
have a specific moment that made the direction click. i talked about implementing a Salesforce workflow at my nonprofit and realizing i was the person everyone came to when systems broke. that moment is both true and demonstrates aptitude. hiring managers can smell a made-up origin story.
do not trash your previous field. doesn't matter how underpaid or mission-burned you are. the interviewer hears 'this person will eventually say the same thing about us.'
the question i got at every single interview was some version of: 'why now?' meaning why not sooner, or why didn't you just go into tech originally. i had to practice that answer a lot. settled on something like 'i needed the depth in program management before i could do the ops role well. i didn't know that until i had it.' felt honest and not defensive.
one thing nobody told me: the 'why switch' answer is different at different levels. at more junior roles they mostly want to know you're committed and won't bounce. at senior roles they want to know your transferable expertise is real, not a resume reframing exercise.
three months into the new role now. the translation did work. but the interview framing was the actual hard part.