Build something that matters .
Momor is a small team building a judgment-aware orchestration system. Search shows that system working in public, and enterprise deployments apply it inside complex workflows. If the principles on this page resonate with how you work, let's talk.
What it's like here.
We hire people with something to prove.
We're going to hire people who got the same treatment our founder did. Experienced engineers who were laid off and told, in so many polite ways, that they were done. That the industry had moved past them. And we'll bring in the new blood too — the folks getting displaced because some CEO got convinced a language model can replace them. If you're in either of those camps and you know your craft, we don't think you're expendable. We think you're exactly who we need.
The work spans public Search and deployed workflows.
Momor is a small team building one system. Momor Search runs in public, and enterprise deployments apply that same system inside workflows where confidentiality isn't optional. You might spend the morning debugging a streaming issue in public Search and the afternoon designing how DocReader should parse a 47-page inspection report for a luxury real estate deployment. The range is the point.
Ship it. Prove it. Iterate.
We put public Search into production in seven months for under $30K. That velocity isn't temporary — it's how we operate. If you need three months of planning before writing code, this isn't the right fit. If you can hold a design in your head, ship a working version, and refine based on what you learn, you'll feel at home.
AI is a multiplier, not a replacement.
We say this as a company that built its entire product with AI assistance. Momor wouldn't be Momor without Claude Code. But from where we're sitting, AI is a tool that makes good engineers more productive — not a thing that makes engineers unnecessary. We use AI tools heavily. We expect you to. But we also expect you to know when the tool is wrong, to catch the thing it missed, and to bring the judgment that comes from years of actually shipping production systems.
The people who thrive here.
Engineers who build, not just code.
Writing code is table stakes. We need people who understand the problem, design the solution, build it, ship it, and own the outcome. The full loop, not just the implementation step.
People who care about craft.
The difference between a good product and a great one is in the details that most people skip. Retry logic. Edge cases. The error message the user sees when something fails. We care about all of it.
People comfortable with ambiguity.
We're building one system that has to work across public Search and enterprise deployments in a market that changes weekly. If you need a fully specced Jira board to feel productive, this isn't the place. If you can navigate uncertainty and ship anyway, it is.
People who say what they think.
We don't have time for politics. If you disagree with a decision, say so directly. If you have a better idea, propose it. The best argument wins, regardless of who makes it. We'd rather have an uncomfortable conversation today than a failure we could have prevented.
No open roles posted? Write anyway.
If what you've read on this page describes how you work, reach out. Tell us what you're good at and why Momor interests you. We'd rather hire the right person than the right resume.
careers@momor.ai →