Talent Community Lead

About Us

At

Rox

, we believe in empowering people to do their best work.

Our platform supercharges sellers with autonomous revenue agents to do the manual work so they can focus on what they do best: selling. Just as coding agents 10x’d engineering, revenue agents 10x customer work.

We are reimagining the revenue stack by building the world’s first revenue operating system, from the application layer to the system of context. With Rox, humans are evolving to orchestrators while agents manage the end-to-end customer lifecycle.

Rox powers Global 2000 leaders in banking, hardware, construction, and sovereign AI, while serving dominant AI winners like Ramp and Cognition.

Underlying all of this success is an unwavering, shared belief in the mission, with an unreasonable commitment of doing whatever it takes to make it a reality.

The Team

Nothing is possible without the world-class team, assembled to redefine how businesses operate.

Members on our team have:

• Founded and exited successful companies
• Held the highest positions at Google, AWS, Confluent, and New Relic
• Won IMO and IOI gold medals
• Published field-defining papers

We’re backed by the best, including Sequoia, General Catalyst, Google Ventures, Elad Gil, and Chris Ré.

Core Principles

Taste: Craft beautiful experiences.

No matter how small, we strive to make sure every detail is right. We care deeply about every interaction, both in terms of whether it helps the seller get the job done, but also how the product makes them feel. We get a visceral feeling when something is off and stop at nothing to make sure we make it right. We never settle, continuously exploring ways to delight sellers.

Obsession: Commit unreasonably.

In all aspects of our craft, we commit. We not only are immediately reactive to customers’ requests but are proactive about driving value even before they ask. We are also obsessive about always learning and honing our craft, improving ourselves and product every single day.

Action: Get it done.

Talking is easy but the difference comes from the execution. We lean heavily towards making thoughtful yet fast decisions and delivering immediately. We play in a field where trust is paramount. We earn the trust and right to empower the best sellers by forging a history of over-delivering on the promise at record speed.

Your Role

As Talent Community Lead at Rox, you’ll build the engineering scene around Rox: the hackathons, open source, technical content and builder rooms where cracked AI engineers, research engineers and hackers want to be. The best engineers don’t find their next company on a job board. They find it at a hackathon at 2 AM, in a repo, or at a dinner where someone they respect is building something hard. You make Rox the company in that room.

You’ll work directly with our founders and engineering leads (the IMO, IOI and ICPC medalists and researchers who built the product) as your speakers, co-hosts and co-authors. You’ll run our hackathon presence, launch signature Rox builder events, ship technical content with our engineers, and keep a live map of who is building what across the AI-native scene.

This is one of the most visible seats at Rox, and your impact is counted: every engineer who meets Rox through you is credited to you, on a public scoreboard every month. It’s an early seat, right before the breakout, so you write the playbook instead of inheriting one. You’ll report to Erin Wilson, our Head of Talent.

If you’re online, cracked, shameless about the grind and already part of the scene, we’d love to talk.

Responsibilities

• Own Rox’s hackathon presence end to end (Hack the North, HackMIT and others): our tracks, our engineers on site, judging, and follow up with the best builders
• Launch and run signature Rox builder events in SF: engineering tech talks, hackathon nights, and a recurring builder breakfast or dinner that top engineers make time for Build an open source community around Rox and community projects, with a public contributor leaderboard
• Plan our engineering leads’ IRL calendar: which rooms we’re in, who speaks, what they talk about, and how every good conversation gets followed up
• Ship technical content with our engineers: pick topics, get drafts written, edit, and publish on rox.com and X
• Keep a live map of the AI-native builder scene (the teams, hosts, rooms and engineers worth knowing) and share it with our engineers
• Build relationships with the strongest student builders at MIT, Waterloo and Caltech
• Keep strong builders close to Rox long after the event ends, through alumni and builder networks
• Be a recognized face of Rox on stage, at events and online
• Post the community scoreboard every month where the whole company sees it
• Use the Rox product every week, so you can talk about it with real conviction
• How We Credit Your Impact
• Aura should be countable. The goal is a sentence the whole company can say out loud: this person brought 25 game-changing engineers into Rox.
• Every touchpoint has a name on it. Every event, hackathon, technical post, open source contribution and community referral is logged to a named engineer in the Rox Talent Graph the day it happens.
• Four milestones per engineer: first touch, engaged repeat, in conversation with Rox, and joined (or brought in an engineer who joined).
• A clear elite bar. An engineer counts when they clear at least two of these: shipped something builders use (widely used open source, a production AI system, a notable launch); a top competitive record (IMO, IOI, ICPC or hackathon finals at that level); research or systems work others cite or build on; an early or core engineer at a breakout AI company; our engineering leads would want them on their own team.
• Credit rules. First touch credit goes to the first logged touchpoint. Assist credit goes to every later touchpoint that moved an engineer to the next milestone. The two are shown separately so nothing double counts, and nothing counts unless it was logged when it happened.
• One public scoreboard, every month: elite engineers brought in, next to the full count at every milestone, plus event attendance and repeat rate, open source contributors, and content reach.

Qualifications

• You’ve built a community that cracked engineers, hackers and researchers want to be part of: you’ve organized hackathons, run builder events where top engineers show up, or you’re a known figure in an engineering scene
• Proof of work in public: event pages, recaps, repos, posts, and the numbers behind them (attendance, repeat rate, what got built)
• Engineering fluency: you can hold a real conversation about what an engineer is building and why it’s hard, and engineers trust you to represent how they work
• Online and plugged in: you post on X (or wherever builders are), and you know the hosts, rooms, group chats and engineers that matter in SF
• Shameless grind and operator first: you’ll host the 7 AM breakfast, judge the 2 AM hackathon demos and ship the recap by noon, without being managed through any of it
• Clear, specific writing: you’ve written or edited technical content engineers were proud to put their names on Market mapping: you’ve mapped a builder scene or a set of companies into a list people acted on Cool but cracked: the builders you host think you’re one of them
• Strong plus: you were the scrappy early community, DevRel or events person somewhere right before it broke out
• Be located in or willing to relocate to San Francisco, in the office at least three days a week