Software Engineer
Mintive
San Francisco, CAFresher2d agovia LinkedIn
About the Role
You will own features end to end, from conception to production, across our gateway infrastructure, enterprise deployments, and agentic systems. The work leans backend and infra, but nothing is off limits: when the product needs a better UI you build it, and when a connector breaks during a security review you fix it.
Key Responsibilities
- Own features end to end, from conception to production.
- Work across gateway infrastructure, enterprise deployments, and agentic systems.
- Build UIs when the product needs them.
- Fix connectors during security reviews.
- Shape the problem, make architecture, product, and UX calls.
- Harden enterprise paths.
- Design connectors.
- Protect security-sensitive surfaces.
- Catch generated code that is quietly wrong.
Requirements & Tech Stack
- Claude and Codex are your primary working environment.
- You use a fleet of agents to move faster.
- Agents write much of the code and review PRs.
- Roles are blurred and we ship within hours.
- You will learn directly from the founders and from customers.
- Work in person in the San Francisco Bay Area.
Qualifications
- You are a builder with a track record of shipping to real users (product, internal tool, open-source project, or serious side project).
- You ship, then iterate, without waiting for specs or approvals.
- You have strong fundamentals and learn fast.
- You care about product value and customer needs over technical purity.
- You take infra seriously; you think about blast radius, trust boundaries, and what happens when your code is in the path of every customer's agents.
- You can read unfamiliar code, reason from first principles, and explain your tradeoffs.
- You are comfortable across the stack (TypeScript, Python, CockroachDB), or you pick up new languages, protocols, and domains fast.
- You are excited to build with agents, and to learn when they help and when they hide a problem.
- You already build with AI every day and want room to move without heavy process.
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: engineers who care about design, designers who think about infrastructure.