Get hired atSageOx×The Anti Job Board

How to Actually Get Hired

Who reads applications, which channel gets a reply, and what they screen for.

50+ peopleSeattleAI

Don't make these mistakes

Positioning yourself as someone interested in AI coordination in general. SageOx has a specific and defensible architectural thesis, connectivity is not comprehension, and they will only respond to outreach that engages with that thesis or demonstrates comparable technical depth. Do not say "I'm passionate about AI agents." Say what you have built and where you think the memory retrieval layer breaks.

What gets their attention

Canaan is the most important signal. They are one of the oldest venture firms in the US (founded 1987) and have backed PayPal, ZoomInfo, LivePerson, LendingClub, and Lending Tree. GP Maha Ibrahim is tagged directly in Ajit's LinkedIn announcement post, which is not a coincidence. Canaan typically backs companies they have been tracking for months before the check is written. Their presence signals the thesis has been rigorously stress-tested. At Canaan's check size, the expectation is that SageOx will build the canonical infrastructure layer for the agentic coordination market, not just a useful tool for AI-native teams. That scale ambition shapes what they hire for: people who can build infrastructure that other developers build on, not just end-user products. Pioneer Square Labs is Seattle-native and backed Read.AI, which also operates in the AI team coordination space. That portfolio overlap is not a conflict. It is a signal that PSL has conviction in the coordination infrastructure thesis and is backing both the meeting intelligence layer (Read.AI) and the team memory layer (SageOx) simultaneously. Founders' Co-op, led by Chris DeVore, was the very first investor in Remitly, the company that both Milkana Brace and Galex Yen came from. That relationship is explicit: Matt Oppenheimer publicly congratulated Galex when SageOx was announced, naming the Remitly connection directly. Founders' Co-op's check is a community bet as much as a financial one. Ajit has been explicit about the team philosophy: intentionally small, agent-heavy. "A small number of key hires" means every role is a high-leverage, high-bar addition. The people hired in the next 90 days will define the architecture of the product. Contact: founders@sageox.ai · hello@sageox.ai · @TheSageOx on

Why applying the normal way doesn't work

SageOx has an ATS but the real pipeline is referrals → sourced → recruiter picks → cold apps. You can still get through, but know where you stand.

Who to contact at SageOx

Who decides:the hiring manager
Best channel:LinkedIn or direct email

What to show them

The core technical challenge at SageOx is building a memory layer that is structured, fast, and comprehension-aware rather than just a vector store. Someone who has worked on knowledge graphs, structured memory for agents, context retrieval systems, or the hard engineering of making AI memory queryable and reliable at production scale is the precise fit. Ryan Snodgrass's distributed systems background and Ajit's XetHub data infrastructure work (building git-scale storage with chunking and deduplication) both point to infrastructure-first thinking. They will hire someone at the same level. Core skills: Distributed systems, structured knowledge representation, LLM context management, vector and graph databases, Python, production ML infrastructure, agent framework internals (LangGraph, LlamaIndex, custom), evaluation design for memory retrieval. Proof of work: Build a minimal shared context layer for a two-agent system where Agent A records a decision with its reasoning, and Agent B consults it before acting on a conflicting input. The interesting engineering problem is the retrieval design: how does Agent B know to check and what it actually gets back. Publish the code and write a README explaining the retrieval mechanism and its failure modes at scale.

A cold email that works at SageOx

Subject: Staff AI/Infrastructure Engineer (Agent Memory Systems), [your one-line proof]
Hi Ajit, I built a minimal two-agent shared context system where Agent B consults Agent A's decision history before acting: [link]. The retrieval design is the hard part and I documented where it breaks at conversation scale. Your thesis that connectivity without comprehension creates an enterprise crisis is exactly right and I have been thinking about the retrieval layer that makes comprehension work. Worth 15 minutes?

What SageOx screens for

Their focus: Canaan is the most important signal. They are one of the oldest venture firms in the US (founded 1987) and have backed PayPal, ZoomInfo, LivePerson, LendingClub, and Lending Tree. GP Maha Ibrahim is tagged directly in Ajit's LinkedIn announcement post, which is not a coincidence. Canaan typically backs companies they have been tracking for months before the check is written. Their presence signals the thesis has been rigorously stress-tested. At Canaan's check size, the expectation is that SageOx will build the canonical infrastructure layer for the agentic coordination market, not just a useful tool for AI-native teams. That scale ambition shapes what they hire for: people who can build infrastructure that other developers build on, not just end-user products. Pioneer Square Labs is Seattle-native and backed Read.AI, which also operates in the AI team coordination space. That portfolio overlap is not a conflict. It is a signal that PSL has conviction in the coordination infrastructure thesis and is backing both the meeting intelligence layer (Read.AI) and the team memory layer (SageOx) simultaneously. Founders' Co-op, led by Chris DeVore, was the very first investor in Remitly, the company that both Milkana Brace and Galex Yen came from. That relationship is explicit: Matt Oppenheimer publicly congratulated Galex when SageOx was announced, naming the Remitly connection directly. Founders' Co-op's check is a community bet as much as a financial one. Ajit has been explicit about the team philosophy: intentionally small, agent-heavy. "A small number of key hires" means every role is a high-leverage, high-bar addition. The people hired in the next 90 days will define the architecture of the product. Contact: founders@sageox.ai · hello@sageox.ai · @TheSageOx on

Don't send a generic CV to SageOx. Mirror the job posting's language to get past automated screening.

Mistakes that kill applications

At people, a copy-paste CV is immediately obvious. It's an instant no.

Lead with their problem, not your ambition. SageOx is focused on The AI agent coordination problem is the defining infrastructure challenge of 2026 — show you understand that.

Don't apply and wait. The median AI application gets no response ever. One follow-up at day five roughly doubles reply rates.

Frequently asked questions

How do I apply to SageOx?

Through the roles on our SageOx jobs page, or directly to the hiring manager if you can reach them. At null people, direct outreach outperforms the form.

Does SageOx respond to cold emails?

We're still collecting cold email data for SageOx.

Who is the hiring manager at SageOx?

At this size, hiring is usually run by the hiring manager.

How competitive is it to get hired at SageOx?

-person AI companies see ~100-250 applicants per role in two weeks. The 72-hour window is your advantage.

Have your application sent for you

Early applications win. We track companies like SageOx, customize your CV, and apply while applicant counts are low.

Get early access →

Related