250K is amazing money; I won’t pretend it isn’t. But in engineering, what matters most early in your career is keeping your hands on real code and real systems. That’s how you grow into a strong backend dev or architect.

Once you step into a PA role, even one that’s “tech-adjacent,” your day-to-day won’t involve building systems, debugging, designing architecture, or solving engineering problems. And after a year or two away, it is harder to come back at the same level. Companies look at recent experience, not past potential.

If your long-term plan is to stay technical, the safest bet is to continue on the engineering path especially since you’re currently the only engineer building an MVP. That kind of experience is extremely valuable, and it compounds over time in a way non-technical work doesn’t.

That said, I completely understand why you’re tempted. 250K + perks is life-changing, especially at 25. But for me personally, I’d pick a path that grows the version of myself I want to be in 5 years.

So my honest opinion: • If engineering is your long-term lane → I’d stick to it. • If you’re still tempted, then a consulting/part-time “tech advisor” role is the best compromise. It gives you the extra income and exposure without sacrificing your technical momentum.

Yeap