Software Engineer

About the Role

Mintive is building the infrastructure for companies to run their work with agents. Our first product is an MCP gateway providing agents with governed access to company data and tools. We are expanding the agent stack to include connectors, monitoring, sandboxing, long-running agents, and memory, aiming to become the system on which a company's work runs. This is an in-person role in the San Francisco Bay Area.

Key Responsibilities

• Own features end-to-end, from conception to production, across gateway infrastructure, enterprise deployments, and agentic systems.
• Work across backend and infra, with flexibility to contribute to UI or fix connectors during security reviews.
• Utilize Claude and Codex as primary working environments, leveraging agents to increase speed.
• Focus on judgment calls: shaping problems, architectural decisions, product and UX, hardening enterprise paths, designing connectors, protecting security-sensitive surfaces, and identifying issues in generated code.
• Ship within hours, with blurred roles and direct learning from founders and customers.

Requirements & Tech Stack

• Primary tools: Claude, Codex, and a fleet of agents.
• Comfortable across the stack, or able to learn new languages, protocols, and domains quickly.
• Experience with TypeScript, Python, and CockroachDB is a plus.
• AI-native: Excited to build with agents and learn their capabilities and limitations.
• You already build with AI every day and want room to move without heavy process.

Qualifications

• A builder with a track record of shipping to real users (product, internal tool, open-source, or side project).
• Ship and iterate without waiting for specs or approvals.
• Strong fundamentals and ability to learn quickly.
• Prioritize product value and customer needs over technical purity.
• Take infra seriously, considering blast radius, trust boundaries, and code impact.
• Ability to read unfamiliar code, reason from first principles, and explain tradeoffs.

Nice to Have

• Developer-facing products, protocol or gateway work, or infrastructure at scale.
• Background in security, identity, or permission systems.
• Contributions to open source, MCP servers, or agentic frameworks.
• Design sensibility.