People who take pride in work that lasts, no matter where they started.
Small team. everyone shapes delivery and client outcomes. We want clear thinking, quiet competence, and code you would still maintain years from now.
Most work is direct with client teams (founders, CTOs, ops) on real business problems.
We hire across software, security, and product -- and the grey areas between them. We do not post open roles; if the mission resonates, start the conversation by email.
We value cross-disciplinary expertise. Hard problems rarely fit one background. If our mission lands and you care about systems clients and their customers rely on daily, reach out.
What matters is that you care about the craft, think clearly under pressure, and want work that outlasts the project. Instincts matter more than which industry taught them.
Own what you ship from architecture through deploy and ongoing reliability.
Direct communication; docs other engineers can run with.
Comfortable across infra, backend, frontend; go where the work is.
Know when to build and when not. Simplicity over cleverness; reliability over novelty.
Fully distributed; async by default. Clear writing moves work without constant meetings.
Small team, high ownership. Meaningful problems, minimal process. Time goes to building.
Engineers work directly with clients. You gather context, ask good questions, and shape solutions instead of chasing tickets.
Systems we stand behind. You maintain and evolve what you ship; decisions that age well.
Small team, high bar. This is probably not a fit if any of the following are true.
Email careers@opusmoor.com. Use the role title or “General application” in the subject line. In the body, include something you built you are proud of (link, repo, write-up; show thinking); where your interests pull you; short intro (who you are, why Opusmoor).
Client, not candidate?
Contact Us