In response to b, I think that’s true for the 80k job. I decided not to apply for the 80k job because it was WordPress, which is horrible to work with and bad for career capital as a developer. Other developers I spoke to about it felt similarly.
But this isn’t true of all of the jobs.
For example, the GiveDirectly advert says “GiveDirectly is looking for a full-stack developer who is ready to own, develop, and refine a broad portfolio of products, ranging from mobile and web applications to backend data integrations. As GiveDirectly’s only full-time technologist they will be responsible for developing solutions to the organization’s most challenging technical problems, and owning the resolution from end to end.”
When I unsuccessfully applied to Wave it similarly sounded like a standard backend web development job, not WordPress or tying together google sheets.
Just to clarify to future 80k engineers who are reading this—the current site is in WordPress so the job would involve some WordPress work, but we expect much work in the future won’t be in Wordpress e.g. our career quiz has an angular JS front-end; if we build our own career tool then it would likely be in ruby on rails on a sub-domain.
In response to b, I think that’s true for the 80k job. I decided not to apply for the 80k job because it was WordPress, which is horrible to work with and bad for career capital as a developer. Other developers I spoke to about it felt similarly.
But this isn’t true of all of the jobs.
For example, the GiveDirectly advert says “GiveDirectly is looking for a full-stack developer who is ready to own, develop, and refine a broad portfolio of products, ranging from mobile and web applications to backend data integrations. As GiveDirectly’s only full-time technologist they will be responsible for developing solutions to the organization’s most challenging technical problems, and owning the resolution from end to end.”
When I unsuccessfully applied to Wave it similarly sounded like a standard backend web development job, not WordPress or tying together google sheets.
Just to clarify to future 80k engineers who are reading this—the current site is in WordPress so the job would involve some WordPress work, but we expect much work in the future won’t be in Wordpress e.g. our career quiz has an angular JS front-end; if we build our own career tool then it would likely be in ruby on rails on a sub-domain.
I suppose (c) is a more valid concern than (b) then.