An interesting read. Do most engineers really prioritise money this much when accepting an offer? I understand that it feels good to be paid well, and you might as well negotiate, but when most tech jobs pay so much better than other work it seems insane to me to deal with amoral products, uninteresting work, and stressful interactions with shitty management practices just because they threw a big number at you.<p>The work environment at Snap doesn't even sound that bad, sadly.<p>* A weirdly culty first day? Plenty of tech companies do weird stuff like that, especially startup-adjacent recent IPOs.<p>* Incompetent bosses with confusing org charts and poor management skills? Not exactly uncommon in tech!<p>* Shitty vesting schedules (10/20/30/40 at Snap) -- see Amazon and quite a few other top tech employers.<p>* Tons of time wasted in sprint planning "marathons" and sprint reviews? Honestly, the 5 hours of planning time per sprint isn't even the worst I've personally experienced. Tends to show up when you have crappy managers with too many direct reports and a tendency towards micromanagement.<p>* Managers and HR "forgetting" spoken-word arrangements for remote work and vacations -- again, par for the course. A valuable lesson here that you ought to get this stuff in writing, insist on it in email form at the very least, perhaps CC'd to your manager's manager, before you can consider it real. Though I'm not sure how many companies, pre-covid, would honestly allow an software dev to work remotely for a "few weeks" both in the summer and around the holidays when they don't support remote work primarily.<p>I'm glad Marko got to spend some time with his father before he passed away, so at least there's a happy ending here. Just goes to show that even a crappy work situation can still teach you valuable lessons, and that you really really need to do your due diligence to identify these cultural issues <i>before</i> you sign an offer!