Product Engineer
incident.io, London
The role
At incident.io http://incident.io, what you build is yours: the whole loop, from hearing directly from customers what's worth building, to building it, with the trust to run with it and make something you're actually proud of.
What you need
- "If not me, then who" is basically how you operate. You don't wait around for something to be officially yours before you deal with it.
- You own your work, but you build as a team. You unblock people, back your teammates up, and care as much about the team shipping great things as about your own bit of it.
- You spot things before anyone asks you to. If a customer's about to notice a problem, you've usually already fixed it.
- You communicate clearly, whether that's a Slack message to a customer, a design doc, or explaining a tricky trade off to your team.
- You're comfortable in ambiguity, not just tolerant of it. Early ideation, half formed problems, and shifting priorities don't throw you off.