Global technology companies use incident.io to empower teams to run incidents from start to finish, by getting the right people involved in real-time on Slack.
Our platform integrates with tools you already use, with intuitive workflows and guiding actions to support your team through tough situations. Auto-generated timelines and post-mortems eliminate busy work and focuses effort on high impact work.
Rapidly fix and learn from incidents, so you can build more resilient products.
The Engineering team is formed of experienced, product-minded engineers. It is made up of people who have spent years writing reliable and scalable software at scale for companies like Monzo, GoCardless, Ravelin and Freetrade.
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. 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 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.
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.
What you’ll be doing:
- Shipping fast: laying solid foundations with lasting impact is important, but the primary risk for us is building the wrong thing, rather than building the thing wrong.
- Keeping things simple: we believe strongly in using a few proven technologies we understand deeply, and we adopt new technologies sparingly.
- Investing heavily in the 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.
- Believing code isn’t everything: we value well written proposals, clear documentation, tests and commit messages and try to be kind to “future us”, while making tradeoffs wisely.
- Collaborating: one of the benefits of a high trust team is we often work autonomously, but as a team we’re very collaborative by nature
- Valuing serendipity: as a default, we aim to focus the majority of our effort on one objective at a time, but some of our best features exist because someone took a quick detour after an inspiring chat with a customer or colleague.
- Getting in front of customers: everyone is in our community slack, and is encouraged to speak to customers and join in the conversations, our Customers love it!
- Being 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.
This role could be ideal for you if you:
- Have production experience working any programme language, such as: Go, Python, Ruby on Rails or React.
- Want to help build a team, by working collaboratively to problem solve and taking extra time to explain things, provide actionable feedback, levelling up those around you.
- Enjoy speaking directly with customers to understand their problems and caring more about outcomes and impact than the exact implementation or tools.
- Are happy share your work early, whether it’s a draft of a proposal, or the MVP of a customer facing feature; putting something out there when it’s “70% done”.
- Feel comfortable when faced with a lot of ambiguity, both technically and organisationally; happy to tackle problems without a clear definition or solution.
- Use technical debt as a tool; caring about resilience, tests and documentation, but understand there are times we need to ship quickly and make pragmatic tradeoffs.