Account Executive

What we're looking for

• 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

Nice to have

• 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

Strong signals

• 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

How We Work

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.

Compensation and logistics

• Health, dental, and vision

• Visa sponsorship for exceptional international candidates

• We'll help you move to New York

Interview process

1. Intro conversation with the founder

2. Onsite/work trial with the team in New York

3. References and offer

How to apply

Send us your resume or LinkedIn, plus one piece of work 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.

A meeting lands on your calendar

If they’re a yes, I book the chat. You show up — that’s the whole job-hunt.