Ask HN: Should I be acqui-hired or not?
On one hand, I want to see our project 'succeed' and bring it to help more people, for our existing clients to be not be disrupted and have that experience (and line on my resume) of having spun out. It would be exciting to learn more about the industry, have a new role and continue to grow. I'm worried that the new startup doesn't appreciate the complexity involved in the migration or functionality we've designed and will fail our clients. A small side benefit is I wouldn't have to go through the interview prep and rigmarole.
On the other hand, I took a pay cut when I joined this project because I was starry eyed and believed in the vision (and still do). One could argue I already have that line on my resume now. I'm in my mid-30s now, have a family and more responsibilities and was expecting that compensation would go up. There are other startups/companies/opportunities out there that would provide more compensation and other career growth opportunities.
Any advice?
2 comments
[ 1.9 ms ] story [ 21.2 ms ] threadI would tread carefully: if it's a matter of the heart, that factors in, but: I would attempt to get guarantees from the acquirers before making the move in terms of work/life balance, length of engagement, etc.
It's more likely I'd take them on as a side client, charge per unit of work, but offer documentation and migration work for a (fairly large) fixed fee, and do that while you explore future gigs.
YMMV.