Things go wrong at companies all of the time. Whether it’s website outages, data breaches, or overwhelmed support teams, incidents are almost inevitable in a world increasingly run by technology. We're building the best way to help your entire organisation respond, review and learn when things go wrong, big or small.
Though we've only been around since March 2021, we’re backed by world-class investors at Index Ventures and Point Nine, and have more than 70 customers from all around the world. Our customers include high growth startups like Render and WorkOS to billion-dollar companies like GoCardless, dbt Labs and Loom.
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
We’re assembling a fantastic team of experienced, product-minded engineers - our early team is made up of people who have spent years writing reliable and scalable software at scale for companies like Monzo, GoCardless, Ravelin and MOO.
We’re building a product to help organisations respond confidently and quickly under intense pressure, which sets the bar incredibly high for both the quality of our product, and the systems that power it. The level of trust our customers have in us is huge, and we move mountains behind the scenes to make sure our systems are robust and reliable, whilst abstracting away complexity to provide a delightful user experience.
As an early engineer, this is a unique opportunity to help shape the product, and the way we build it. We’ve laid some good foundations, but we’re still very early in our journey, have a tonne of things we want to build, and a lot to learn along the way!
- 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.
- 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.
Research has shown that women are less likely than men to apply for a role if they don’t have experience in 100% of the requirements outlined in a job description. Please know that even if you don’t have experience in all the areas above, but think you could do a great job and are excited about shaping company culture, finding great people and building great teams, we’d love to hear from you!
How we build incident.io
We care far more about your mindset and your ability to solve problems than your familiarity with the tools and languages below, so please don’t let that put you off applying. However, we know enjoying the languages and tools you work with every day is important, and so wanted to share a little about what you can expect.
Our primary development stack is based on Go, Typescript with React, and Postgres, with a typed auto-generated client between the API to help us ship quickly. Most of us have a primary area of expertise, but we all work across the entire stack to some degree.
For infrastructure, we primarily use Heroku, but we leverage Google Cloud Platform heavily via BigQuery, PubSub, Cloud Storage, Stackdriver and more all, managed via Terraform.
We bias strongly to buying tools rather than building them, and invest heavily in a few vs having 20 ways to solve the same problems. We rely on Sentry for error reporting, Grafana + Prometheus for our metrics, dashboards and alerts, and Kibana for logging. We use CircleCI for automated testing and deployment.
How to apply
You can apply through this page in a few clicks, but if you'd prefer, you can also send an email to email@example.com or firstname.lastname@example.org. Whatever works best for you!
We embrace diversity at incident.io
. To build a product that’s loved by everyone, we need a team with all kinds of different perspectives, experiences, and backgrounds. That's why we're committed to hiring people regardless of race, religion, colour, national origin, sex, sexual orientation, gender identity, age or disability.
Note to recruitment agencies
We don't accept CV's from external parties or recruitment agencies. Any unsolicited CV's sent to us will be treated as property of incident.io, and any attached terms and conditions associated with these CV's will be null and void.