i made the PM to eng switch about 14 months ago. took a level drop, joined a startup to get reps in. that part was fine.
what i did not fully anticipate: how often "career switcher" becomes an implicit rejection reason. not stated directly in any email, but pretty clear from patterns in feedback i've managed to get and from where in the process things tend to break down.
the specific version i kept hitting: i'd get through screening and first round conversations. but when it got to the hiring manager or tech screen, i'd get the "we're looking for someone who has been doing this longer" response. which usually translates to: we don't know how to evaluate your non-linear path, and defaulting to YOE feels safer.
what actually helped me start getting past this:
leading with the specific skills, not the transition. instead of opening with "i switched from PM to eng," i started leading with the engineering work itself. what systems i'd built, what languages, what scale. the transition becomes context, not the headline.
naming the objection before they raise it. in behavioral rounds i started proactively addressing it: "i know my path looks non-linear on paper, so let me be specific about what the last year of hands-on work actually looks like." takes the air out of the unspoken concern.
targeting companies that explicitly value varied backgrounds. this sounds obvious but i wasn't doing it systematically. startups that need people who can think cross-functionally are a much better fit than companies optimizing for pure deep-stack specialists.
being honest about what i'm still building. trying to pretend i have 5 years of eng experience when i have 14 months was backfiring. owning the gap but being specific about the trajectory was more convincing.
if you're job searching as a career switcher and getting rejected, the instinct is to hide the switch. usually the opposite works better.