The company sells a relationship intelligence platform to enterprise revenue teams, built to show reps which people inside an account carry real influence. Customers include Webflow, Decagon, ElevenLabs, Brex, Cognition, and LangChain.
Revenue has grown 5x over the past year, and customer demand is moving faster than the product team can ship.
The company closed a Series A led by NEA, bringing total funding to $19M. Other backers include Salesforce Ventures and Y Combinator, plus operators such as Stewart Butterfield, Co-Founder and CEO of Slack, Cal Henderson, Co-Founder and CTO of Slack, and sales leaders from Figma, Box, Dropbox, Anthropic, and Notion.
The founders are Rachit Kataria, a founding engineer on Facebook Shops who helped grow it to 250M MAUs, and Will Wang, who launched Slack Huddles, which became the fastest-growing product Slack has built.
Responsibilities
Be the first ML engineer, leading ML and applied AI work, starting with the relationship graph that maps who knows whom, who trusts whom, and how those ties shift from deal to deal.
Report to Will Wang, co-founder and CTO, and build a research function from scratch.
Set the research direction and take full ownership of entire systems, not a single piece such as one ranking model.
Over time, lead the ML team as it forms around you.
Ship models that learn from every customer deal, with releases measured in weeks.
Publish findings, with the first white papers planned for Q1 2027.
This is not a traditional post-training research role. The focus is recommender systems, knowledge graphs, and learning from past deals in production. Backgrounds in classical ML, recsys, ranking, or graphs fit well, and you will move into applied AI when a problem calls for it.
Two openings. The senior role starts before the end of 2026: you set the agenda, own the first systems, and grow into leading the team. The mid-level role starts by the end of 2026 or in January 2027: you go deep on large parts of the system alongside the senior hire and grow quickly.
Define the research agenda for the trust graph.
Design and build the layered knowledge graph and the recommendation systems on top of it, covering embeddings, retrieval, ranking, and link prediction that improve with each deal, signal, and outcome.
Build next-best-action features that learn from past deals and outcomes to suggest who a rep should contact, why, and how.
Move research into production, from first experiment to shipped feature used by customers, and measure its effect on real deals.
Make system design and model choices, including when to use a third-party model or API and when to build in-house. Build the data, evaluation, and inference foundation that keeps everything fast and reliable at enterprise scale.
Publish what you learn in white papers and technical write-ups, speak at conferences, and bring findings back into the product.
Lead long-horizon projects across engineers: write the plan, align the team, and keep the work moving for months.
Build agents that surface the right relationship, person, or next step before a rep has to ask.
Help grow the ML team.
Requirements
You are an ML engineer first, with experience running ML systems in production at scale, ideally recommender systems, ranking, or graph-based models.
Hands-on experience with recommender systems, knowledge graphs, or people and social graphs, including retrieval, ranking, embeddings, and link prediction.
You can work on applied AI when a problem requires it.
You have taken research to a shipped product and measured whether it worked.
Solid grounding in modern ML, including embeddings, deep learning, and evaluation.
High agency and drive. You want to go deep, own large parts of a system, and grow fast. You get the goal, not the step-by-step.
Strong written and verbal communication. You explain how a model behaves to engineers, customers, and the wider company, and you write the doc that gets everyone aligned. This matters as much as technical depth.
A product-minded approach to research. You balance depth with product deadlines and tie your work to business outcomes.
Sound system design judgment, including build-versus-buy trade-offs between third-party models and in-house systems.
Preferred: published papers or white papers on knowledge graphs, recommendation, or applied ML, ideally from work that shipped.
Preferred: experience with people or social graphs at scale, such as friend or connection recommendations, identity resolution, or entity matching.
Preferred: an MS or PhD in a quantitative field, or equivalent research experience.
Conditions
Remote in the United States, or hybrid in New York or San Francisco.
Must be a US or Canadian citizen.
Benefits
Medical, dental, and vision insurance, fully covered.