After raising a seed round from some fantastic investors, we’re looking for someone passionate about building robust systems, delightful product experiences and a fantastic team. 

Engineering at incident.io

About Us

• We ship fast. We know laying solid foundations is important, and we spend time on doing this well where decisions will have a lasting impact. However, we also believe that the primary risk for us is building the wrong thing, rather than building the thing wrong. We prefer to ship things at “70% done” so we can learn fast.
• We keep things simple. We believe strongly in using a few proven technologies we understand deeply, and we adopt new technologies sparingly, when we think there’s a tangible benefit for customers, or our team. We also buy existing software when we can, rather than building it ourselves.
• We invest heavily in developer experience. Whether it’s metrics, logging, tracing and error tracking, or development workflow. Build times are blazing fast: our CI to deploy time is ~5m. Everyone uses a M1 Pro Macbook, and you have budget for other equipment should you need it.
• We believe code isn’t everything. We value well written proposals, clear documentation, tests and commit messages and try to be kind to “future us”. We’re also pragmatic - sometimes we need to make tradeoffs here, and we trust each other to use our experience to make them wisely.
• We’re highly collaborative. One of the benefits of a high trust team is we often work autonomously, but as a team we’re very collaborative by nature. Two heads are often better than one, and we frequently lean on each other to solve problems together.
• We value serendipity. As a default, we aim to focus the majority of our effort on one objective at a time, but we’ve repeatedly seen great ideas strike at unlikely moments. Some of our best features exist because someone took a quick detour after an inspiring chat with a customer or colleague.
• We put engineers in front of customers. Everyone is in our community slack, and is encouraged to speak to customers and join in the conversations. Customers love it, and we think it makes us better at what we do!
• We’re open and transparent by default. We’re all on the same team, and we share the highs and the lows together. The vast majority of our internal documents, meeting notes and documentation is open by default, and it’s a similar story in Slack, where we prefer public discussions wherever possible.

About You

• You have more than 3 years of experience working as a product engineer. We'll be accepting applications from folks with less experience in future, but right now we need people who can hit the ground running.
• You have production experience working with either Go or React.
• You enjoy speaking directly with customers and understanding their problems.
• You care more about outcomes and impact than the exact implementation, or the tools used to solve the problem.
• You want to help build a team, not just be part of it. You’re happy to take the extra time to explain things, provide actionable feedback, and level up those around you.
• You prefer working collaboratively and are happy to regularly pair up with colleagues on problems and solve them together.
• You are comfortable when faced with a lot of ambiguity, both technically and organisationally. You’re happy to tackle problems without a clear definition or solution.
• You enjoy owning problems end to end, from the early exploration of the problem through to releasing things to customers, and understand that often doesn’t involve writing code.
• You share your work early, whether it’s a draft of a proposal, or the MVP of a customer facing feature. You’re happy putting something out there when it’s “70% done”.
• You use technical debt as a tool. You care about resilience, tests and documentation, but understand there are times we need to ship quickly and make pragmatic tradeoffs.

How we build incident.io

How to apply

Note to recruitment agencies