Senior Software Engineer

Job Overview

You're a senior software engineer shipping production code into Minoa's core platform to solve the hardest technical problems our enterprise customers pay us to solve. You'll spend ~70% engineering, ~20% customer partnership, ~10% product thinking. Five‑plus years of experience, founder‑level ownership, and fluency in both hardened production systems and frontier AI‑assisted prototyping.

We are building the intelligence layer for the outcome economy: value agents that uncover what each customer uniquely gains from a product, generate defensible business cases in minutes, and measure ROI across the full customer lifecycle. Our customers include Snowflake, Ironclad, Vanta, Benchling, Cognite, and Pendo. Zero churn, six‑person team, creating a new category.

Value intelligence is harder than it looks. A business case for a $3M Snowflake deal requires stitching together data from Salesforce, the customer's data warehouse, their product telemetry, their financial model, and public‑market comps – then reasoning about counterfactuals in a way a CFO will actually sign off on. Every enterprise has a unique value framework, unique data shape, and unique buying committee.

The system must be flexible, rigorous, and auditable.

• Agent orchestration over messy enterprise data: Getting a value agent to reliably navigate a customer's Salesforce schema, product analytics, custom objects, and financial model – and produce a number a finance team will trust.
• Generalizing customer‑specific logic into platform primitives: Building abstractions that make the tenth deployment fast without custom code that rots.
• Production AI systems that public companies run deals on: Latency, reliability, auditability, and cost all matter for sales leaders running live pipelines.
• Turning prototypes into product at speed: The right prototype in front of a customer on Friday often becomes a platform feature next month. You'll make that transition work.

This is a software engineering role close to customers. You'll own 2–3 concurrent customer engagements, write production code, and own the technical gaps that block revenue. This is not an implementation or professional services role; you won't be configuring templates or running deployment scripts.

Two modes you switch between:

• Hacker mode: Build a custom UI on top of our API to prove a use case by Friday.
• Architect mode: Turn a prototype into a platform primitive with care for performance, reliability, and API design.

• 2–3 concurrent customer engagements tied to specific revenue outcomes. Each maps to winning a customer, unblocking an upsell, or securing a renewal.
• Production code in our core platform. Real commits, PRs, and reviews that other engineers build on.
• The translation layer between field and product. Convert deployment signal into clear tickets and architectural proposals.
• Pushing through organizational inertia. Adopt and use features within a 1,000‑person sales org, engaging stakeholders and enabling adoption.

• 5+ years of engineering experience shipping production systems at scale.
• Founding engineer, early core engineer at a startup, or senior engineer at a company of fewer than 20 people.
• Equally fluent at shipping production code and hacking fast prototypes.
• Strong customer engagement. Comfortable speaking with C‑level stakeholders and proposing solutions.
• Product and commercial instincts. Focus on revenue, adoption, and generalization.
• Enthusiastic about ambiguity. No playbook or manager‑driven projects; own outcomes.

Compensation: $150–240K base plus up to 1 % equity.

Benefits: Health, dental, and vision coverage.

Work setup: In‑person in San Francisco, regular travel to customers across the US and Europe.

• Intro call with one co‑founder (~20 min)
• Background interview + technical deep‑dive (~90 min)
• Founder interview (~30 min)
• On‑site working session in San Francisco (1 day) – pair with us on a real customer problem
• Reference calls and offer

Apply here on Linked In or send a note to richard. No cover letter needed – a link to something you built and a paragraph on the hardest technical problem you've shipped is perfect.