Get hired atRecord OS×The Anti Job Board

How to Actually Get Hired

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

<50 peopleLondonAI

Don't make these mistakes

Suggesting that AI will replace accountants. That is explicitly not the product thesis, and Dhruv has said so publicly. Any outreach that implies the automation story is about headcount reduction in accounting firms will immediately disqualify the sender.

What gets their attention

Episode 1 Ventures is the most significant signal. Episode 1 is one of the leading UK pre-seed and seed investors, writing £1M to £2M first cheques in fintech, AI, developer tools, and marketplaces. Their portfolio includes six unicorns. They focus specifically on the pre-seed to seed phase where velocity matters most. Their portfolio companies at this stage are typically pushed hard on product shipping and commercial traction, not product theorising. Six people, a working beta, and a regulatory mandate means the next six months are about scaling the engineering team and the accounting firm pipeline simultaneously. The angel roster amplifies the commercial signal. Former CFOs and senior leaders from Wise, Revolut, Deliveroo, and Alphabet are not writing cheques into tax software because they find the category interesting. They are writing cheques because they have run finance functions at fast-scaling companies and they know exactly how painful self-assessment is for the people their companies employed: founders, early employees, contractors, and landlords whose income structure does not fit a PAYE form. These are also the first 100 customers. The capital is the hiring signal: a six-person team just raised $2M with an explicit mandate to scale before 1.7 million new filers hit the MTD threshold in 2027. That timeline is the forcing function. Contact: founders@recordos.com

Why applying the normal way doesn't work

Record OS is <50 people. No recruiter, no HR. Your application goes to a founder juggling everything. Cold outreach is how you actually get seen.

Who to contact at Record OS

Who decides:a founder or department head
Best channel:LinkedIn or direct email

Founding team

DC
Dhruv Chadha
Co-founder & CEO

Dhruv Chadha studied at the University of Oxford before building a career as a finance executive at some of the most analytically demanding institutions in technology. He worked in finance roles at Google before joining Wise, where he operated inside one of the most data-driven financial technology organisations in the world and witnessed firsthand how payment complexity creates cascading complexity in personal tax situations for employees with equity, multi-currency income, and international earnings. He then became CFO at Nansen, the blockchain analytics platform, which placed him at the intersection of crypto finance and the specific tax treatment problems that arise when income is denominated in volatile digital assets. That is three consecutive roles where the people around him had income structures that made self-assessment genuinely difficult. While testing the Record OS platform, Dhruv found a £38,968 error on his own 2023-2024 Self Assessment, even with professional help. He posted about this publicly on LinkedIn. The willingness to make that admission public is a specific kind of intellectual honesty: he is not selling a product that claims to be perfect. He is selling a product that caught an error that a human professional missed, in his own return, and whose output is better because the AI and the accountant check each other. That is a more credible product thesis than any benchmark. His ZoomInfo profile carries a reference quote from a colleague: "Dhruv is very detail-oriented and while working together, he watched the balance sheet like a hawk without ever losing sight of our primary objective." That is the CFO character. The balance sheet precision of a professional accountant combined with the systems thinking of a technology operator is exactly the combination needed to design a product that is both technically sound and financially credible with accounting professionals. He met José in mid-2024 and the two spent time experimenting with AI applications before deciding that self-assessment was the category worth building into. They began building Record OS at the start of 2025. His public LinkedIn output since founding concentrates on the MTD IT policy timeline, the self-assessment error rate problem, and product updates from the beta. He has also posted about Broc, which appears to be a prior product experiment from his Wise period. He operates in the UK fintech community and attended the Accountex conference to represent Record OS, which is the correct venue for reaching accounting firm decision-makers.

JLDLP
José Luis De La Peña
Co-founder & CTO

José Luis De La Peña holds a Master of Science in Telecommunications Engineering from Danmarks Tekniske Universitet (DTU) in Denmark (2010-2012), one of the leading technical universities in Scandinavia, which gave him his foundation in distributed systems, signal processing, and network architecture before he moved into software engineering professionally. His career moved from early freelance and agency engineering work through SubscribEz and Reto-Moto before he joined Generation Home (GNH), a London-based mortgage lender that was building digital mortgage infrastructure for UK homebuyers, as an engineer. GNH is the mortgage lender that Record OS's brief refers to: the experience of building financial services software for a compliance-heavy, document-intensive industry gave him exactly the engineering context that self-assessment automation requires. He then joined Wise (then TransferWise) as a software engineer, where he worked on systems at a company that had already redefined how international payments worked and was preparing for its Nasdaq listing. His LinkedIn post on the day of the Wise Nasdaq listing reflects genuine pride in what the team had built. The experience of building engineering infrastructure at a regulated fintech that operates under multiple national regulatory frameworks is the preparation for building an HMRC-integrated AI platform. His early research work, visible in his LinkedIn profile, involved integrating social network APIs into a unified graph using NoSQL technologies like CouchDB and Redis, which is an early signal of his interest in data integration and unification problems — exactly the engineering challenge at the core of Record OS, where financial data from multiple sources (bank feeds, accountant records, HMRC data) must be normalised into a single coherent filing. He moved from computer science and legal tech into engineering roles at Wise and mortgage lender GNH. The legal tech reference in his background, not confirmed in publicly available sources but noted in AccountingWEB, suggests he has exposure to document-heavy, compliance-sensitive software environments beyond just fintech. His DTU telecom background, his GNH fintech engineering, and his Wise payments experience together make him the right technical co-founder for a product that needs to integrate cleanly with HMRC APIs, handle complex financial document parsing, and operate under the audit and data security expectations of UK accounting professionals.

DC
Dhruv Chadha
Co-founder & CEO

Dhruv Chadha studied at the University of Oxford before building a career as a finance executive at some of the most analytically demanding institutions in technology. He worked in finance roles at Google before joining Wise, where he operated inside one of the most data-driven financial technology organisations in the world and witnessed firsthand how payment complexity creates cascading complexity in personal tax situations for employees with equity, multi-currency income, and international earnings. He then became CFO at Nansen, the blockchain analytics platform, which placed him at the intersection of crypto finance and the specific tax treatment problems that arise when income is denominated in volatile digital assets. That is three consecutive roles where the people around him had income structures that made self-assessment genuinely difficult. While testing the Record OS platform, Dhruv found a £38,968 error on his own 2023-2024 Self Assessment, even with professional help. He posted about this publicly on LinkedIn. The willingness to make that admission public is a specific kind of intellectual honesty: he is not selling a product that claims to be perfect. He is selling a product that caught an error that a human professional missed, in his own return, and whose output is better because the AI and the accountant check each other. That is a more credible product thesis than any benchmark. His ZoomInfo profile carries a reference quote from a colleague: "Dhruv is very detail-oriented and while working together, he watched the balance sheet like a hawk without ever losing sight of our primary objective." That is the CFO character. The balance sheet precision of a professional accountant combined with the systems thinking of a technology operator is exactly the combination needed to design a product that is both technically sound and financially credible with accounting professionals. He met José in mid-2024 and the two spent time experimenting with AI applications before deciding that self-assessment was the category worth building into. They began building Record OS at the start of 2025. His public LinkedIn output since founding concentrates on the MTD IT policy timeline, the self-assessment error rate problem, and product updates from the beta. He has also posted about Broc, which appears to be a prior product experiment from his Wise period. He operates in the UK fintech community and attended the Accountex conference to represent Record OS, which is the correct venue for reaching accounting firm decision-makers.

JLDLP
José Luis De La Peña
Co-founder & CTO

José Luis De La Peña holds a Master of Science in Telecommunications Engineering from Danmarks Tekniske Universitet (DTU) in Denmark (2010-2012), one of the leading technical universities in Scandinavia, which gave him his foundation in distributed systems, signal processing, and network architecture before he moved into software engineering professionally. His career moved from early freelance and agency engineering work through SubscribEz and Reto-Moto before he joined Generation Home (GNH), a London-based mortgage lender that was building digital mortgage infrastructure for UK homebuyers, as an engineer. GNH is the mortgage lender that Record OS's brief refers to: the experience of building financial services software for a compliance-heavy, document-intensive industry gave him exactly the engineering context that self-assessment automation requires. He then joined Wise (then TransferWise) as a software engineer, where he worked on systems at a company that had already redefined how international payments worked and was preparing for its Nasdaq listing. His LinkedIn post on the day of the Wise Nasdaq listing reflects genuine pride in what the team had built. The experience of building engineering infrastructure at a regulated fintech that operates under multiple national regulatory frameworks is the preparation for building an HMRC-integrated AI platform. His early research work, visible in his LinkedIn profile, involved integrating social network APIs into a unified graph using NoSQL technologies like CouchDB and Redis, which is an early signal of his interest in data integration and unification problems — exactly the engineering challenge at the core of Record OS, where financial data from multiple sources (bank feeds, accountant records, HMRC data) must be normalised into a single coherent filing. He moved from computer science and legal tech into engineering roles at Wise and mortgage lender GNH. The legal tech reference in his background, not confirmed in publicly available sources but noted in AccountingWEB, suggests he has exposure to document-heavy, compliance-sensitive software environments beyond just fintech. His DTU telecom background, his GNH fintech engineering, and his Wise payments experience together make him the right technical co-founder for a product that needs to integrate cleanly with HMRC APIs, handle complex financial document parsing, and operate under the audit and data security expectations of UK accounting professionals.

What to show them

Record OS is a production product in beta: HMRC API integration, AI document parsing, accountant-facing review interface, and quarterly submission workflows. As the beta expands to more accounting firms and the MTD IT deadline drives adoption, the engineering team that built it at six people needs to grow. The stack is likely TypeScript/Python on cloud infrastructure with the HMRC MTD API at the centre. Core skills: TypeScript or Python, REST API integration (HMRC MTD API or comparable government financial APIs), document parsing and AI pipeline integration, production-grade web application development, UX sensibility for professional/accountant-facing interfaces, fintech compliance awareness. Proof of work: Build a minimal HMRC MTD IT-compatible digital record submission: connect to the HMRC sandbox API, generate a quarterly update payload from mock income and expense data, and submit it. Document the OAuth flow, the data schema, and the error handling for HMRC API rejections. This is literally what Record OS does for every client. Publish the code.

A cold email that works at Record OS

Subject: Full-Stack / Product Engineer, [your one-line proof]
Hi Dhruv, I built a minimal HMRC MTD IT submission using the sandbox API: [link]. The interesting problem was the income category mapping — HMRC's schema doesn't map cleanly onto how most accounting software structures revenue lines. I have a specific view on how to handle that in the Record OS data model. I want to work on the system that finds £38,968 errors. Worth 15 minutes?

What Record OS screens for

Episode 1 Ventures is the most significant signal. Episode 1 is one of the leading UK pre-seed and seed investors, writing £1M to £2M first cheques in fintech, AI, developer tools, and marketplaces. Their portfolio includes six unicorns. They focus specifically on the pre-seed to seed phase where velocity matters most. Their portfolio companies at this stage are typically pushed hard on product shipping and commercial traction, not product theorising. Six people, a working beta, and a regulatory mandate means the next six months are about scaling the engineering team and the accounting firm pipeline simultaneously. The angel roster amplifies the commercial signal. Former CFOs and senior leaders from Wise, Revolut, Deliveroo, and Alphabet are not writing cheques into tax software because they find the category interesting. They are writing cheques because they have run finance functions at fast-scaling companies and they know exactly how painful self-assessment is for the people their companies employed: founders, early employees, contractors, and landlords whose income structure does not fit a PAYE form. These are also the first 100 customers. The capital is the hiring signal: a six-person team just raised $2M with an explicit mandate to scale before 1.7 million new filers hit the MTD threshold in 2027. That timeline is the forcing function. Contact: founders@recordos.com

A tailored CV beats a generic one. Use Record OS's job description language to clear filters.

Mistakes that kill applications

A recycled CV gets rejected fast at Record OS (<50 people). They notice.

Don't open with what you want. Open with what Record OS is dealing with right now — Another 1, and what you'd do about it.

Applying and waiting = silence. Follow up at day five — it roughly doubles your odds of a reply.

Frequently asked questions

How do I apply to Record OS?

Through the roles on our Record OS jobs page, or directly to a founder or department head if you can reach them. At <50 people, direct outreach outperforms the form.

Does Record OS respond to cold emails?

Not enough data yet on Record OS's cold email response rates.

Who is the hiring manager at Record OS?

At this size, hiring is usually run by a founder or department head.

How competitive is it to get hired at Record OS?

Typical applicant count for AI roles (<50 people): 50-100 in two weeks. Apply fast.

Have your application sent for you

We find roles at companies like Record OS within 48 hours of them appearing, build a CV tailored to the posting, and send it while you're still applicant number ten.

Get early access →

Related