Software Engineer
Mintive
San Francisco, CAFresher1h agovia LinkedIn
This job at a glance
- Who can apply
- New grads, no experience needed
- Must know
- PythonTypeScript
- Work
- On-site in San Francisco
- Pay
- Not stated by the employer.
- Skill demand
- Python69%TypeScript21%of 120 similar entry-level jobs posted in the US this week
- Listed
- Oct 27, 2026 · still open
Sign in free to see which of these skills your resume already shows.
About the Role
The Software Engineer role at Mintive involves owning features end-to-end, from conception to production, across gateway infrastructure, enterprise deployments, and agentic systems. The work primarily leans backend and infra, but responsibilities can extend to UI development and fixing connectors during security reviews.
Key Responsibilities
- Own features end-to-end, from conception to production.
- Work across gateway infrastructure, enterprise deployments, and agentic systems.
- Develop UI when needed.
- Fix connectors during security reviews.
- Shape problems, make architecture, product, and UX calls.
- Harden enterprise paths.
- Design connectors.
- Protect security-sensitive surfaces.
- Catch generated code that is quietly wrong.
- Ship within hours.
- Learn directly from founders and customers.
Requirements & Tech Stack
- TypeScript, Python, CockroachDB.
- AI-native environment.
- Primary working environment: Claude and Codex.
- Use of a fleet of agents to enhance productivity.
Qualifications
- A builder with a track record of shipping to real users (product, internal tool, open-source project, or serious side project).
- Ability to ship and iterate without waiting for specs or approvals.
- Strong fundamentals and fast learning ability.
- Care about product value and customer needs over technical purity.
- Serious consideration for infrastructure, including blast radius, trust boundaries, and impact on customer agents.
- Ability to read unfamiliar code, reason from first principles, and explain tradeoffs.
- Comfortable across the stack or able to pick up new languages, protocols, and domains quickly.
- Excitement to build with agents and learn their capabilities and limitations.
- Existing daily use of AI and desire for a low-process environment.
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.