Interesting, thanks for posting. So what could also be going on is "synergies" as they call them. It is quite possible that Songtradr has staff/functions that they think they can share across the acquisition. This happens a lot when a portco (what Songtradr is to whoever owns them) buys an adjacent company.

Of course it's also possible that that it's specific places (i.e. the content) that are being gutted as they aren't seen to be worthwhile.

The things is that once a company sells, it keeps the name, but can instantly become a different company as far as culture goes. If we want to complain about bandcamp being crappy to its people, the finger should be pointing at the owners (whatever round it was) who a) made the hires and b) made the decision to sell. You are throwing your employees to the wolves when you do that. Once you've sold, the decisions are now ultimately made by a new entity with new priorities (for better or for worse).

This is one of the reasons I advise any younger devs I talk to to understand their employer's ultimate game plan. If the employer is hoping for an exit in the period during which you plan to work for them, you should be under no illusions that your job is safe or will stay the same, and you should be getting compensated accordingly. This is the cost of working in the gravy train - we get the high salaries, but we also get the uncertainty that comes with working in a business where exits are so frequent. The two are connected. (And I have been on the employee side during an acquisition twice now, so I've been there.)

> You are throwing your employees to the wolves when you do that. Once you've sold, the decisions are now ultimately made by a new entity with new priorities (for better or for worse).

At its heart, tech is adapting to change and uncertainty through the fusion of creativity and process. Job changes are just another input.