Strategy & Ops

What we're looking for

• You've owned commercial or operational work at an early-stage company, run a hard problem in consulting or banking with operator-level rigor, or built something of your own and have evidence of doing it well.

• You can take an ambiguous business problem, define the next useful step, and ship without waiting for someone to tell you the right answer.

• You think in systems and numbers. You can build the model, read the cohort data, and explain what it means in plain English to a room that includes both an engineer and a board member.

• You write clearly. Investor updates, customer narratives, internal docs. Your default is sharp, structured, and short.

• You can hold enough technical depth to talk to engineers without bluffing, understand what Interfere actually does, and help sell something complex, even if you don't write production code yourself.

Nice to have

• Experience at a developer tools, infrastructure, observability, or technical SaaS company

• Have run or materially contributed to a fundraise (seed, Series A, or later)

• Built a go-to-market motion from zero: first customers, first playbook, first hires

• Background in consulting, banking, or investing paired with real operating experience

• Comfort with SQL, light scripting, or whatever it takes to answer your own questions without waiting on someone else

• Exposure to usage-based pricing, bottoms-up adoption, or developer-led growth motions

Strong signals

• You started something (a company, a side project, a meaningful initiative) and have something tangible to show for it

• You took on scope at a previous company well beyond your title and ran with it

• A piece of writing, a financial model, a launch, or a system you built where the quality is obvious in the first few minutes

• You've operated in a role with no playbook and built one as you went

• You've sold something hard, hired someone great, or shipped a launch that materially moved a company forward

• You can point to a moment where you spotted a real problem before anyone else did and saved the company from it

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.