So there are two issues with this: 1. If I were looking to hire someone and read this, I would immediately be turned off. Why? Because part of being an engineer (or any employee really) is doing a bunch of stuff people don't enjoy doing. This includes: - Writing documentation - Writing tests - Fixing bugs - Talking to partners about a change/launch - Talking to lawyers - etc So I would be wondering: if you're signali…
1. I agree the author hasn't emphasised those things. If I was in need of those things, I might not automatically engage with the author. But, you've given a list of what you don't like doing - that isn't a universal list. Given that the author asks to be deeply involved in a human-centred project, it is not obvious to me that they don't like or are not prepared to do these things.
My point is that if you're signaling from the outset that you want to cherrypick those things then I, as your employer, don't actually know what you will or won't do. I don't know if you'll follow up on tricky-to-reproduce bugs (as an example) because that's "boring".
That's just creating work and uncertainty in dealing with those issues.