Description
Summary We're an AI-native B2B outbound company. We build the systems that source leads, run campaigns, and handle replies at scale for around 20 clients. You'd own our internal engineering: the sourcing modules, the internal SaaS, and the systems that keep the whole machine running. Most companies make you work for free to get hired. We pay you to audition. Here's the deal. We give you one paid project. You build it. Every working build gets paid $100, whether you win the seat or not. The best build also wins the seat, and that job pays $3,500+/month all in, with no ceiling. So there's no downside to trying, and a real upside to winning. Why this role is worth your time You own systems end to end. Nobody hands you tickets and watches you close them. You build the thing, you ship it, you run it. You get paid on what you produce, not the hours you sit online. Ship fast and ship clean and you earn the most. That's the whole logic of the pay structure. And you get sharp at building with AI. You'll use Claude Code and Codex every day to build lead lists and ship faster than you thought possible. That skill is worth more than this job alone, and you'll own it for the rest of your career. This is not a quiet 9-to-5 where nobody notices what you do. If that's what you want, close this now. If you want to build real systems, own them, and get paid on output, keep reading. What you'll actually do Build and maintain sourcing modules. Develop internal SaaS features. Research new ways to use Claude Code to build lead lists and ship faster. You'll work across the stack with Clay, HeyReach, Smartlead, Supabase, and n8n. The paid project We don't read CVs first. We watch you build. You build one working sourcing module. That's a small program that pulls a list of companies or contacts from a source of your choosing (a directory, a job board, an API, a scrape, whatever), cleans and standardises the data into a consistent format, and sends it to an endpoint we give you. It turns a raw source of leads into clean, structured, ready-to-use data. Self-contained. No more than three hours. You're expected to use Claude Code or Codex to build it fast, because that's how we work. We run it on a group call. Everyone gets the SOP and the specs, and you work out what needs doing yourself. We're hiring for initiative. Nobody here gets handheld, and half the test is whether you can take a spec and run with it. The brief covers the inputs, the outputs, and what we mean by useful internally, so you have everything you need to build without asking. We judge every submission on three things: Reliability. Does it work every time. Error handling. What happens when the source is messy, incomplete, or breaks. Usefulness. Is this something we'd actually run internally. We don't care how clean the code is. Only that it hits those three. Every working build gets the $100. One engineer wins the seat, with the uncapped variable on top. To apply Record a short custom Loom telling us why you're a fit and what you'd bring. Say the word "pipeline" out loud in it so we know you read this the whole way through. No word, straight to the bin. Under 5 minutes. We care about how you think, not production value. Send it with anything else you think earns you the seat.