Jobbörse

Interfere turns a product's invisible failures into shared problems the whole team can see and fix. Every app has places where users get confused, blocked, or forced to abandon a flow, but most of those moments never make it into a support ticket. We detect those failures in real-time and provide every person responsible for the fix with the context they need. When Interfere flags a broken checkout flow, the PM uses our data to prioritize the issue, the designer sees where the experience broke down, and the engineer pulls the trace underneath. We're building the operating system for product quality, so teams can move from scattered symptoms to a shared understanding of what's actually going wrong. We're a seven-person team in New York, with $5.1M raised from Y Combinator, Vercel Ventures, Hummingbird, Designer Fund, and others. Interfere is already running in production with design partners, which means the work you ship will immediately help real teams find and fix the failures costing them users today. The category is still being defined, but the product to fill this gap is inevitable, and the company that gets there first will own how the next decade of teams ship software. We're looking for the people who will move at the speed that demands.

You'll be the first seller of Interfere's product, which means you're building a sales machine, not just joining one. You'll close revenue, but you'll also figure out who we should be selling to, how we should be selling to them, what lands, what kills deals, and what the repeatable playbook actually looks like. The founders are doing sales today. You're the person who makes that no longer necessary, and who turns the first few customer wins into a pattern the next ten AEs can run. Concretely, this looks like:

• Owning the full sales cycle end-to-end: prospecting, discovery, demo, technical evaluation, procurement, close
• Building the pipeline yourself through outbound, founder warm intros, community, content, or whatever works, rather than waiting for inbound to fill your calendar.
• Sitting across the table from engineers, platform leads, and CTOs and being credible about the technical problem Interfere actually solves
• Defining and refining ICP in real time: who closes, who doesn't, why, and what that means for the next 20 conversations
• Partnering with founders on pricing, packaging, and deal structure
• Bringing customer voice back into the product loop fast enough that what you learn this week shapes what we ship next month

• You've closed net-new business at a technical or developer-focused company meaning real revenue from real strangers, not just renewals or expansion on accounts someone else opened
• You're comfortable selling without a playbook, and you can build the pipeline from scratch. You know how to find the right person, write the message that actually gets a reply, and earn a meeting from a cold start
• You hold your own in a technical conversation. You don't pretend to be an engineer, but you understand the product deeply enough that engineers respect the conversation.
• You write clearly. Discovery notes, deal reviews, follow-ups, internal handoffs your default is sharp, structured, and short
• You're honest about what's working and what isn't. You don't sandbag the forecast, hide a dying deal, or oversell a feature that isn't ready

• Sold developer tools, observability, infrastructure, or technical SaaS
• Been an early or founding seller at a startup that actually scaled from those early days
• Comfort with usage-based pricing, bottoms-up adoption, or PLG-to-enterprise motions
• Background as an engineer, sales engineer, or technical PM before moving into sales
• A track record of breaking into accounts where you had no relationship and no introduction

• You've been the first or second seller somewhere and have the receipts: revenue closed, playbook written, motion built
• You closed a deal nobody thought was closeable, or unstuck one that should have died
• You can name the specific reasons your last three losses lost, and what you'd do differently
• You've sold something genuinely hard: a new category, a buyer who didn't know they had the problem yet, or an enterprise procurement gauntlet
• You write well enough that prospects actually respond, whether newsletters, threads, technical posts, or internal memos
• You can point to a customer who would take your call right now, even after you left the company

We're in person in New York City. The hardest parts of building Interfere, from system design to architecture tradeoffs to taste calls on the product, happen faster and better at a whiteboard with people physically in the same room. We measure work, not hours. Time at a desk is a poor proxy for whether work is getting done. But there's a lot to do and genuine urgency to being the category winners. Most people who do well here end up putting in serious hours because the problems are interesting and the upside is real. We ship daily, and we ship deliberately. Speed and taste are not in tension here. Every line of code is a choice: we don't let tech debt accumulate because velocity is easier. We write the code we would want to inherit, while still pushing meaningful changes every day. The roadmap is structure, not scaffolding. We plan out the week, so there's structure to what you take on. But the items on that roadmap are whole features and subsystems, each one a project in itself. If you see another problem along the way that needs solving, you own that too. It's your job to make your work into what it needs to be.

• Health, dental, and vision
• Visa sponsorship for exceptional international candidates
• We'll help you move to New York

1. Intro conversation with the founder
2. Onsite/work trial with the team in New York
3. References and offer

Send us your resume or LinkedIn, plus one piece of evidence we should look at. We want to see how you think and build. A short note on why Interfere helps, but the work matters more.