Senior Field Engagement Manager
Firecrawl
Senior Field Engagement Manager
Firecrawl
Web-data platform for AI agents
You'll own Deployment's side of the rooms Firecrawl shows up in: the private dinners for the labs and companies we want to work with, the conferences where our buyers already are, and the hackathons and workshops where developers run the API for the first time. Operations runs the events. You run what they're for: you decide which accounts need to be in which room, get them there, hold your own technically once they arrive, and turn the conversations into qualified pipeline the pods can close. This is a pipeline seat that runs on events, not an events seat that reports on attendance. If you've done field marketing or developer relations, this is that job on the Deployment team, with a revenue scoreboard. You'll report to our VP of Deployment, and you're measured on the opportunities credited to you from the rooms you work, not on how many people showed up.
Salary Range: $181,000 to $215,000 USD/year OTE
Equity Range: Competitive equity. Details shared during the process.
Location: San Francisco, CA (SF HQ). On-site when you're not in the field. Travel up to 50 percent for events, with evenings when the room calls for it.
Job Type: Full-Time
Experience: 5+ years in roles that put you in rooms with developers (field or developer marketing, developer relations, community, solutions, or a technical seat with a pull toward the commercial side), or a body of work that makes the case. Either way, you can call an API and show someone what it did
Work Authorization: Open to candidates already authorized to work in the US. We also support H-1B transfers, F-1 OPT and STEM OPT, TN (Canada and Mexico), and E-3 (Australia). We’re not able to sponsor new H-1B visas for candidates outside the US.
Firecrawl is s a place for people who want to work at the frontier: an AI company building the infrastructure other AI companies run on, not one bolting AI onto an existing product. We move fast, go deep, and are building the tools superintelligence will rely on to gather data from the web. That library is called Alexandria, and it starts now.
In September 2026, we raised a $75M Series B led by Smash Capital, and we're spending it building the largest repository of knowledge in the world. We hit 8 figures in ARR in year one and more than doubled it in year two. We have 200k+ GitHub stars, putting us in the top 40 repositories of all time, and developers, agents, and category-defining AI companies build on us every day. Growth like this is rare, and we're just getting started.
We're a small team punching far above our weight, working out of SF HQ and our new Toronto Hub. Everyone here owns a real piece of the product and company, end to end, and runs it themselves. No hiding behind process or headcount.
Bias to action: We move fast, ship hard, and don’t wait to be told.
Realistic about AI: We’re clear-eyed about what AI can and can’t do, and we keep pushing to use it where it actually works.
All in: The next few years matter a lot, and we’re all in for them.
Human connection: As intelligence gets cheaper, relationships with customers, partners, and each other matter more.
Firecrawl already has a field motion. We host curated dinners for AI researchers at model labs, run a monthly community series at SF HQ, and show up at the conferences our buyers attend. Operations owns that program as a whole: the calendar, the production, and the orchestration across teams. The pods, each owned by a Forward Deployed Engineer with a Deployment Growth Engineer building pipeline into it, close what the field produces.
This role is Deployment's seat in that system. It decides which accounts need to be in which rooms, curates the guest lists for the revenue rooms, holds the table technically, and owns the follow-through until the pod's FDE takes the deal. It sits outside the pods so it can serve all of them, and every deal it sources goes to the pod whose ICP the account is in.
The Deployment team is small and technical. Every teammate can run the product, read the code, and talk to a customer, and this seat is no exception. This is the first dedicated field seat. Start by owning Deployment's ask for one region, build the revenue side of the program, then lead it as we add pods and cities.
Bring the Accounts to the Calendar. Each quarter, hand Operations the rooms Deployment needs: the ICPs and target accounts each one reaches, the format that fits them (a dinner, a workshop, a meeting block at a conference, a hackathon), and the credited-opportunity target behind it. Operations owns the calendar, the budget, and the production. You make the case for the rooms with pipeline math, and you work the ones they run.
Before an invitation goes out, every revenue room has a target list, a success metric, a teammate who owns the follow-up, and a conversion plan.
Curate the Room. Build the guest lists for the revenue rooms from the ICP map, the pods' target accounts, and the signup base, using the AI-assembled customer dossiers and the warehouse to find the right people, not just the right logos.
Run the invitation outreach in Firecrawl's voice through our outbound stack, and get replies to a yes. Hand Operations the list for registration and seating, and brief the teammates who'll be in the room on who's coming, what they're building, and why they matter.
Be Technical at the Table. Demo the API live: one request, one page, clean Markdown or structured data, in front of a researcher or a CTO. Run hands-on blocks at workshops and hackathons that take a developer from first Scrape to first Search.
Answer the first layer of technical questions yourself (JavaScript rendering, anti-bot, output formats, MCP) and know when to pull in an engineer.
Turn the Room into Pipeline. Run the pre, during, and post-event loop with the pods: account targeting before, introductions during, and follow-up within 48 hours after. Every conversation lands as a contact and an activity in the warehouse.
Hand each qualified deal to the FDE of the pod whose ICP the account is in, and stay on the thread until the FDE owns it. Operations owns the venue, the vendors, and the run of show. You own Deployment's side: who's in the room and what happens after.
Measure and Feed the Playbook. Report every revenue room on attendee quality, credited opportunities, pipeline created, and cost per credited opportunity. Run the pipeline half of the retro with Operations and change the next ask.
Write Deployment's half of the events playbook (guest curation, the pre and post loop, follow-through, measurement) into the playbook Operations keeps, and work with Product Marketing and Developer Experience on the talks and content that make a room worth attending.
How You're Measured. Credited opportunities from the rooms you work: a deal you sourced that the FDE of the account's pod took as owner. That handoff is the quality gate. Behind it: the pipeline and signings those deals produce, and what each credited opportunity cost to create. Not badge scans, not attendance.
Technically Fluent. You can read code, call the API, and show a developer what one request did to a page. You don't need to have been an engineer, but you need to be credible in a room full of them, and you need to want to learn the product to the level where you can demo it cold. Developer relations, developer marketing, a solutions seat, or a technical seat at an API-based company are all ways people get here.
You've Filled Rooms with Developers. Meetups, hackathons, dinners, workshops, a talk track at a conference: you've run them, not just attended them, and you can show what happened after.
Pipeline-Minded. You think of an event as a list of accounts with a plan, not a date on a calendar. You know what a qualified opportunity is and you're comfortable being measured on the ones the pods credit to you.
AI-Native. You use AI tools daily as core work infrastructure. Our GTM stack assembles customer dossiers, activity timelines, and usage data; you'll use them to research accounts, write invitations, and brief the room faster than anyone expects.
Taste, and Programs Others Can Run. You know the difference between a room that works and one that doesn't, and you notice which one you're in before the guests do. You've also turned a one-off that worked into a recurring program with a playbook someone else could run. That's the path from this seat to leading the function.
Urgency and Follow-Through. Same-day follow-up. The event ends when the last conversation is in the warehouse with a next step, not when the last guest leaves.
Clear Communicator. Invitations people answer, briefs teammates read, and a talk you'd sit through yourself.
Backgrounds That Often Do Well
Developer advocates who want a revenue scoreboard for the rooms they already fill.
Field or developer marketers from API-first or infrastructure companies who are done counting badge scans.
Community managers who built a recurring series developers kept coming back to.
Technical founders who ran their own dinner circuit and conference calendar to sell.
Solutions engineers and sales engineers who were always the one at the booth.
Someone who wants to run the events program. Operations owns events end to end: the calendar, the production, and the orchestration across teams. You own Deployment's side of every room: who, why, and what happens after.
Badge-scan marketers. If your success metric is leads collected rather than opportunities credited, this isn't the fit.
Non-technical hosts. Rapport gets people to dinner. Relevance and technical credibility get them to a second meeting.
People who need a finished playbook. We're building the field program as we go. If you need an account list, a runbook, and a quarter already planned before you can start, you'll stall here.
You've worked at an API-first or developer infrastructure company and marketed to engineers.
You've done developer relations or advocacy and have talks, workshops, or a hackathon you ran end to end to show for it.
You have a network in the SF AI and developer scene: labs, accelerators, meetup organizers, the people who decide who speaks where.
You've built or run web scraping, crawling, or RAG pipelines and can talk about JavaScript rendering, anti-bot, and Markdown for LLMs from experience.
You've used Firecrawl, or reached it through Claude Code, Cursor, or n8n.
You're comfortable with Luma, Missive, SmartLead, Slack, and reading a SQL query against a warehouse.
You've written a talk abstract that got accepted, or a workshop that sold out.
We operate at an absurd level of urgency because the window for what we're building won't stay open forever. If that excites you, keep reading. If it doesn't, no hard feelings, but this role probably isn't for you.
Salary that makes sense: $181,000 to $215,000 USD/year OTE, based on impact, not tenure
Own a piece: Gain competitive equity in what you're helping build
Generous PTO: 15 days mandatory, anything after 24 days, just ask (holidays excluded). Take the time you need to recharge
Parental leave: 12 weeks fully paid, for all parents
Wellness stipend: $100 USD/month for the gym, therapy, massages, or whatever keeps you human
Learning & Development: Expense up to $1,000 USD/year toward anything that helps you grow professionally
Team offsites: A change of scenery, minus the trust falls
Sabbatical: 3 paid months off after 4 years, do something fun and new
Full coverage, no red tape: Medical, dental, and vision (100% for employees, 50% for partner and kids). No weird loopholes, just care that works
Life & Disability insurance: Employer-paid basic life and AD&D, short-term disability, and long-term disability. Coverage for life's curveballs
Virtual care and a health guide: Teladoc for the couch doctor visit, plus Rightway to answer coverage questions and fight billing errors for you
Mental health: Talkspace, therapy and psychiatry on your schedule
Fertility and family building: Carrot, covering you and your partner
EAP: Free confidential counseling, legal and financial consults, and online will prep through Guardian
401(k) plan: Retirement might be a ways off, but future-you will thank you
Pre-tax benefits: HSA, FSA, and commuter benefits to help your wallet out a bit
Supplemental options: Extra life and AD&D, accident, critical illness, hospital indemnity, plus pet, legal, and identity protection through MetLife
SF HQ perks: Snacks, drinks, team lunches, intense ping pong, and peak startup energy
E-Bike transportation: A loaner electric bike to get you around the city, on us
Application Review: Send us your resume, two events you ran end to end (the goal, who was in the room, and what happened after), and a link to you speaking or demoing if you have one. We care about what you've done, not where you went to school.
Intro Chat (~25 min): A quick conversation to get to know each other before we go deep. We'll talk about what you've been running, what drew you to Firecrawl, and what you're looking for in your next role. Time for your questions too.
Field Program Interview (~55 min): We'll hand you a real quarter: the ICPs, a set of target accounts, the events calendar Operations is running, and a city. You'll make Deployment's ask into that calendar (which accounts need which rooms), curate one guest list, and walk us through the follow-through. Then you'll run one live Firecrawl request and tell us what it did. We're looking for account judgment, taste, technical credibility, and speed.
Founder Chat (~25 min): Culture, pace, ownership, and how you like to work. Time for your questions too.
Paid Work Trial (~40 Hours): Own Deployment's side of one real room with the team: curate the list, run the invitations, be at the table, and land the follow-through in the warehouse. Paid at a contractor rate. It's the truest signal for both sides. You see what the role actually feels like, and we see how you operate. We'll flex around your current commitments.
Decision: We move fast after the trial.
If you want to fill the rooms where Firecrawl's next customers meet us, and be the one they remember, this is your shot.
👉 Apply now.
Firecrawl provides a context API for AI agents to search, crawl, scrape, and retrieve clean content from the live web and structured indexes at scale. Its platform handles crawling, rendering, parsing, and cleanup so teams don’t need to build their own extraction pipelines. The Alexandria layer unifies official data providers, custom connectors, and Firecrawl indexes with the live web, enabling agents to discover sources and pull knowledge, including paid access like Wikimedia Enterprise. The service supports scale to millions of users and funds deeper indexes, search capabilities, and knowledge-contributor payouts.
Explore more opportunities at Firecrawl