
Trace
AI Workflow Orchestration Platform
Last verified August 17, 2026 · Updated daily
What Trace is building
Trace is a workflow orchestration platform that solves the most persistent and unglamorous blocker to enterprise AI adoption: agents do not know where they fit inside complex organisations. The platform builds a knowledge graph of a company's operational environment by reading the tools already in use - email, Slack, Airtable, project management software, any system that reflects how work actually flows. Once the graph is built, users issue high-level task prompts and Trace decomposes them into step-by-step workflows, delegates sub-tasks to AI agents with the specific context each agent needs to execute, and assigns remaining tasks to human team members. The result is an onboarding layer for AI agents that removes the months of internal integration work that most enterprise deployments currently require before a single agent can take reliable action.
Why this matters
Enterprise AI adoption has been measurably slower than the investment cycle suggests it should be. The reason is not model quality. The models are exceptional. The reason is that deploying an AI agent into a real organisation requires the agent to understand that organisation - its tools, its informal decision-making structure, where the handoffs between teams happen - in a way that currently takes months of custom integration to achieve. Every company that has tried and failed to deploy an AI agent at scale has hit the same wall. Trace is attacking that wall directly, and the knowledge graph approach is structurally more defensible than plugin-based deployment because it is built from what already exists inside a company rather than imposed from the outside by a new platform. Anthropic launched enterprise agent plugins the week before Trace's announcement. Atlassian is building Jira-native agents. But these are platform plays. Trace's bet is that context built from lived operational reality is more durable than context prescribed by a vendor, and that is an intellectually defensible position with a real moat if they can execute.
Open roles at Trace
2 positions we're tracking. Roles are re-checked daily and removed when filled.
Know when Trace is hiring before anyone else
A role stays uncontested for about four days. Here's the window — and where we put you in it.
From $9/month, cancel any time.
Watching Trace
0 applicantsRole spotted & verified
1You get the alert
1You've applied
~8Hits the job boards
250+Hiring outlook
Round closed February 26, 6 days ago. No job listings yet because the hiring conversation has not happened. Outreach this week means you are in the room before the room exists.
Working at Trace
Trace: AI Workflow Orchestration Platform. Founded , currently <50 employees. At this stage, expect broad remit, direct access to founders, and equity that still means something if the company works out.
Most Trace jobs are based in London.
How to actually get hired at Trace
Why applying the normal way doesn't work
With only <50 employees, Trace doesn't have dedicated recruiters. Founders review applications between running the company. The challenge isn't competition — it's visibility. Direct outreach wins.
Who to contact at Trace
Founding team
Tim Cherkasov was previously a product manager at Copper, a digital asset custodian, where he delivered an institutional product for State Street. Before that, a data scientist across hedge funds and scaleups, and a founder since the age of 17 across retail tech, travel, and web3. He is the public face of Trace, has been doing press since the TechCrunch announcement, and is reachable via LinkedIn. His framing of the core problem - the brilliant intern versus the manager who knows where to put them - is intellectually tight and repeatable. His background before Trace is not extensively documented in public sources, which means outreach from someone who has engaged carefully with the product thesis will stand out against generic enthusiasm. Contact: tim@trace.so or search LinkedIn.
Artur Romanov was a senior engineer at Deliveroo, where he built the grocery data-enrichment ML pipeline covering millions of items across thousands of retailers. That is a real-world, large-scale data problem with direct architectural relevance to what Trace is building: a knowledge graph that reads messy, inconsistent operational data and makes it useful for automated decision-making. He is a multi-time founder who has led backends in logistics and finance and deployed workflow automation across engineering and ops teams. His public thesis on the product is precise and quotable: "2024 and 2025 was still about prompt engineering. Now we've moved from prompt engineering to context engineering. Whoever provides the best context at the right time is going to be the infrastructure on top of which the AI-first companies will be built." That framing is the intellectual foundation of the entire company. Reference it in outreach to Artur and you signal immediately that you understand what they are actually building, not just what the headline says. Artur is currently based in San Francisco per LinkedIn, while Tim operates from London - the founding team is already distributed across two continents at five people.
What to show them
Trace's core deployment challenge is building the knowledge graph from a company's existing tools. This is a technical implementation process that requires integrating with Slack, email, Airtable, project management software, and custom internal systems that vary by customer. Someone needs to own this process with early accounts, build the default integration playbook from scratch, and feed quality signals back to the product team in real time. At this stage this person will likely be the first US-based customer-facing hire and will have direct access to the CEO on every implementation. Core skills: experience integrating with enterprise collaboration tools (Slack API, Google Workspace, Atlassian suite); familiarity with graph database concepts or workflow mapping; ability to translate technical implementation steps into language that non-technical operations leads understand; prior experience at an early-stage enterprise SaaS company where the integration playbook did not yet exist is directly relevant. For proof of work, sketch out what a Trace knowledge graph would look like for a 50-person startup using Slack, Notion, and Linear. Identify the ten most important nodes, the most important edges between them, and where the gaps that an AI agent would fall into appear. Post it as a one-page diagram or written description publicly. It does not need to be built. It needs to show you understand the mapping problem in a real operational context.
A cold email that works at Trace
What Trace screens for
The cap table tells you more than the press release does. Three signals stand out. First, WeFunder, a community crowdfunding vehicle, is unusual for enterprise B2B. It suggests the founder is building a distributed audience alongside a sales pipeline, which opens a GTM approach most agent orchestration companies are not taking and will require people who can operate across both community and enterprise motions simultaneously. Second, Goodwater Capital, whose portfolio includes Kakao and ByteDance-backed consumer platforms, almost never backs pure enterprise plays. Their presence implies a broader product surface area than the current positioning suggests - either a prosumer layer or a marketplace dynamic is likely in the roadmap. Third, Transpose Platform Management invests specifically in workflow platforms that become operationally embedded and eventually acquired. Their involvement is a structural bet on Trace becoming infrastructure, not just software. When an investor whose entire thesis is about acquisition outcomes writes a cheque at seed, they are already thinking about what Salesforce, ServiceNow, or Atlassian would pay for this in three years. That timeline creates a fast and specific hiring mandate: get the product embedded in enough enterprise workflows to be irreplaceable before the platform players replicate it.
Don't send a generic CV to Trace. Mirror the job posting's language to get past automated screening.
Don't make these mistakes
Don't send generic AI enthusiasm. The round closed six days ago - timing is everything. Reference Artur's "context engineering" framing if reaching out for technical roles. For commercial roles, Tim is the contact. The fact that they're distributed across London and SF at five people means remote-first is not a policy, it is the default.
Mistakes that kill Trace applications
At <50 people, a copy-paste CV is immediately obvious. It's an instant no.
Nobody cares what you want. Start with Enterprise AI adoption has been measurably slower than the investment cycle suggests it should be and how you'd help.
Don't apply and wait. The median AI application gets no response ever. One follow-up at day five roughly doubles reply rates.
Applying to Trace? Get the contact, not the form.
The Trace interview process
3 stages · 7 days typical · take-home: yes · modelled from similar companies
We don't yet have verified candidate reports for Trace. What follows is the typical process for a <50-person AI company — treat it as a model, not confirmed detail.
Interview stages
Intro Call
Video call · 30 min
Culture fit and role expectations
Founder or hiring manager
Technical Deep Dive
Video call or in-person · 60 min
Past projects and problem-solving approach
Technical founder or lead
Final Round
In-person or video · 45 min
Team fit and offer discussion
Founding team
Trace take-home assignment
Trace includes a take-home exercise in their interview process. For AI roles, this typically involves a practical problem that takes 2-4 hours. Focus on clean, working code over premature optimization. They're evaluating how you think and communicate, not just the solution.
Trace interview timeline
At days, Trace's process is faster than typical for AI (10 days at this size).
Interviewed at Trace?
Tell us how it went — stages, questions, timeline. Takes 90 seconds and it's how this page stays accurate for the next person.
Submit your Trace interview experience →Trace jobs, frequently asked questions
How many jobs does Trace have open?
Trace currently has 2 open roles, last verified March 2025.
Does Trace hire remotely?
All current Trace roles are based in London.
What roles is Trace hiring for?
Trace is hiring across Engineering, Product. The most recent opening is Enterprise Solutions / Implementation Engineer.
How do I apply for a job at Trace?
Apply directly through the links above, or read our guide on how to actually get hired at Trace.
Does Trace respond to cold emails?
We're still collecting cold email data for Trace.
Who is the hiring manager at Trace?
At this size, hiring is usually run by a founder or department head.
How competitive is it to get hired at Trace?
<50-person AI companies see ~50-100 applicants per role in two weeks. The 72-hour window is your advantage.
How many rounds is the Trace interview?
3 stages: Intro Call, Technical Deep Dive, Final Round.
Is the Trace interview hard?
It concentrates on technical depth and system design rather than abstract puzzles. The stage candidates find hardest is Technical Interview.
Does Trace give a take-home task?
Yes, Trace includes a take-home assignment.
How long does Trace take to get back to you?
Around 7 days across the full process.
What should I prepare for the Trace interview?
Prepare for technical depth and system design. A <50-person startup wants proof you can ship, not that you can whiteboard.
Where is Trace based?
Trace is headquartered in London, US.
Get Trace roles before they're posted
A role stays uncontested for about four days. Here's the window — and where we put you in it.
From $9/month, cancel any time.
Watching Trace
0 applicantsRole spotted & verified
1You get the alert
1You've applied
~8Hits the job boards
250+