Company / Careers

Build calmer on-call experiences.

MonoDuty works on the infrastructure between a failing system and the person who can fix it. That calls for careful engineering, clear product thinking and strong ownership.

01 / Opportunities

A current home for future roles

Open positions are published on this page when they become available; this page is the company’s current vacancy source.

If your experience is especially relevant to alert routing, on-call systems or developer infrastructure, you can introduce yourself through our contact page in the meantime.

02 / The work

Problems worth owning

The work sits at the intersection of failure-aware systems and a product people must be able to inspect under pressure.
Product

Design for stressful moments

Make incident workflows legible when attention is limited and every extra step carries a cost.

  • Clarity
  • Accessibility
  • Operations
Engineering

Make alert paths observable

Build and inspect the ingestion, routing and delivery paths behind time-sensitive notifications.

  • APIs
  • Reliability
  • Observability
Team

Own a complete problem

Work close to users, make decisions directly and follow changes through from idea to production.

  • Ownership
  • Feedback
  • Execution

03 / What matters

Signals we value

01

Evidence over theatre

Show the decisions you made, the constraints you handled and what changed because of your work.

02

Clear communication

Good operational software depends on precise writing, thoughtful handoffs and honest trade-offs.

03

Care for the edge cases

The difficult paths — failure, recovery and uncertainty — deserve as much attention as the happy path.

04 / Next step

Your work fits this problem space?

Introduce yourself and tell us which part of incident response you would want to improve.