
How to Actually Get Hired
Who reads applications, which channel gets a reply, and what they screen for.
Don't make these mistakes
Pitching Zalos as a general-purpose AI automation play. William and Hung are very specific about the finance context and why it matters. Finance is different from every other department because accuracy is non-negotiable and every action needs an audit trail. If you cannot articulate why 90% accuracy is unacceptable in finance, or why screen-recording-based agent training is more practical than API integration in ERP environments, you will sound generic. Read the careers page copy carefully the team wrote it to filter for candidates who get it.
What gets their attention
The press release is specific: the $3.6M will go toward broadening the range of ERP systems Zalos can operate, building a context graph across the finance stack, and expanding the team. Two roles are live on the careers page right now. The careers page copy is notably good: "Fortune 500 companies run on software so painful that workers toggle between applications 1,200 times a day, losing 4 hours a week just navigating screens. These systems are so welded into a company it can cost $700M to replace a core ERP. So we're not replacing them. We're the layer across them." That sentence was written for candidates who want to work on a problem with genuine enterprise weight. The remote Software Engineer role means geographic distribution is acceptable. The London Senior AI Engineer role is the higher-signal hire London is where William Fairbairn is based and where the enterprise finance customer conversations are happening.
Why applying the normal way doesn't work
At this size (<50 people), ZALOS has no recruiting function. Founders handle hiring alongside everything else. Reach them directly or get lost in the inbox.
Who to contact at ZALOS
Founding team
William's career before Zalos follows a precise path into the exact problem the company is solving. He started at McKinsey, which gave him the analytical framework for how large organisations evaluate technology risk and transformation cost. He then joined Agicap as UK General Manager. Agicap is one of the largest Office of the CFO software platforms in Europe, used by thousands of mid-market companies to manage cash flow and financial operations, and in that role William spoke directly with hundreds of CFOs about their biggest operational frustrations. The answer he kept hearing was not "we need a new ERP." It was "our current ERP is impossible to get value from without a team of people manually stitching it together." That conversation is the founding insight for Zalos verbatim. He moved from observing the problem at Agicap to building the solution at Zalos after YC F25. He writes actively on LinkedIn about enterprise finance automation and the computer agent opportunity, and his posts are worth reading before any outreach because they tell you exactly how he frames the market. He is based in London, which is where the enterprise finance customer conversations are concentrated. LinkedIn: search "William Fairbairn Zalos."
Hung is one of the more technically credentialed CTOs in the London enterprise AI scene, with a background that maps almost perfectly onto the problem Zalos is solving. He spent five years at Apple building Apple Pay services, which at peak scale served hundreds of millions of daily active users across dozens of countries, each transaction requiring sub-second reliability, cryptographic security, and compliance with financial regulations across multiple jurisdictions. That experience gave him an unusually practical understanding of what it means to build financial infrastructure that cannot fail. He also contributed to other AI initiatives at Apple before leaving to co-found Zalos. His insight into why Zalos uses a computer-use agent approach rather than APIs is grounded in that background: enterprise finance systems frequently have no usable API, an incomplete one, or one that is too risky to use for live financial transactions. The visual interface is the only reliable path, and Apple Pay gave him the engineering discipline to build something operating at that interface reliably and securely. He is less publicly vocal than William and contributes technical commentary on LinkedIn rather than maintaining an active X presence. LinkedIn: search "Hung Hoang Zalos."
What to show them
Build a minimal computer agent that logs into a publicly accessible web application (a test ERP demo, or any form-heavy enterprise tool), executes a two-step workflow, and logs every action with a timestamp and screenshot. Share the code. It's directly analogous to what Zalos builds, and it shows you understand the core engineering challenge.
A cold email that works at ZALOS
What ZALOS screens for
What they look for: The press release is specific: the $3.6M will go toward broadening the range of ERP systems Zalos can operate, building a context graph across the finance stack, and expanding the team. Two roles are live on the careers page right now. The careers page copy is notably good: "Fortune 500 companies run on software so painful that workers toggle between applications 1,200 times a day, losing 4 hours a week just navigating screens. These systems are so welded into a company it can cost $700M to replace a core ERP. So we're not replacing them. We're the layer across them." That sentence was written for candidates who want to work on a problem with genuine enterprise weight. The remote Software Engineer role means geographic distribution is acceptable. The London Senior AI Engineer role is the higher-signal hire London is where William Fairbairn is based and where the enterprise finance customer conversations are happening.
Don't send a generic CV to ZALOS. Mirror the job posting's language to get past automated screening.
Mistakes that kill applications
At <50 people, a copy-paste CV is immediately obvious. It's an instant no.
Nobody cares what you want. Start with Enterprise finance is one of the last functional areas where "AI transformation" has mostly failed to deliver and how you'd help.
Don't apply and wait. The median B2B, Operations application gets no response ever. One follow-up at day five roughly doubles reply rates.
Frequently asked questions
How do I apply to ZALOS?
Through the roles on our ZALOS jobs page, or directly to a founder or department head if you can reach them. At <50 people, direct outreach outperforms the form.
Does ZALOS respond to cold emails?
We're still collecting cold email data for ZALOS.
Who is the hiring manager at ZALOS?
At this size, hiring is usually run by a founder or department head.
How competitive is it to get hired at ZALOS?
<50-person B2B, Operations companies see ~50-100 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 ZALOS, customize your CV, and apply while applicant counts are low.
Get early access →