Company
systemzero
Annual salary
Not disclosed
Location
London, UK
Listed
61d ago
- Experience:
- 6 to 10 years
- Workplace:
- Remote - Based only in Amsterdam or London, working UK/CET hours. The engineering team often co-works from WeWork offices, and the whole company meets on-site about every 2 months in New York, London or Amsterdam.
- Equity:
- Competitive equity
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
Remote (listed in London, UK).
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We are looking for a Senior Data Engineer with 6, 10 years of experience to own the Python data pipelines and data ontology behind systemzero's AI-native operating system for CFOs. You'll be a hands-on IC who owns problems end to end, solves them without waiting to be told how, and wants to grow into a tech lead. Over the next 6 months you'll guide a core data team of four, made up of a mid-level engineer and two new hires. You'll report directly to the CTO in a flat, low-ego team that works through problems together. Your work decides whether our agents can reason correctly over GAAP-grade financial data, where hallucinations aren't tolerated.
What will you be doing?
- Building and owning production Python pipelines that load customer data into our graph and vector store (SurrealDB)
- Adding new data providers and connectors to the platform, such as Snowflake, ERP, accounting and billing systems
- Designing the data ontology so that AI retrieval and agent reasoning across multi-entity financial data stays accurate
- Owning your work end to end across data, DevOps and infrastructure in a remote-first team that solves problems together on frequent calls
- Moving from about 80% IC work toward a 60/40 split, with the 40% spent mentoring the core data team and shaping long-term data architecture
Common questions
How do I apply for the Senior Data Engineer (AI & Data Products) (UK) role at systemzero? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
Is this role remote? +
Yes, the listing is remote. Remote - Based only in Amsterdam or London, working UK/CET hours. The engineering team often co-works from WeWork offices, and the whole company meets on-site about every 2 months in New York, London or Amsterdam.
Data Engineer interview prep
Questions Data Engineer interviewers often ask. They aren't taken from this listing.
How do you design an ETL pipeline to be idempotent so reruns don't duplicate data?
I design loads around upserts keyed on a natural or surrogate key rather than plain inserts, and I make each pipeline stage stateless with respect to its inputs so rerunning it with the same input produces the same output. Partitioning by a processing date and overwriting the whole partition on rerun is another reliable pattern, especially for batch pipelines.
When would you choose a star schema over a snowflake schema for a data warehouse?
A star schema keeps dimension tables denormalized, which trades storage and some data redundancy for simpler, faster queries. That's the right call when query performance and ease of use for analysts matter more than storage efficiency. A snowflake schema is worth the extra join complexity when dimension tables are large, change frequently, and normalization meaningfully reduces storage and update anomalies.
How do you handle schema evolution in a pipeline that ingests data from a source you don't control?
I treat the ingestion layer as schema-tolerant by landing raw data first, before any strict schema is enforced, and applying schema validation at a later transformation stage. This way a new or renamed field upstream doesn't break ingestion outright. I also version the schema explicitly so downstream consumers can detect and handle changes rather than silently breaking.
What's your approach to choosing between a batch and a streaming architecture for a new data pipeline?
The deciding factor is how fresh the data needs to be for the downstream use case, not how technically interesting streaming is. If consumers only need daily or hourly updates, batch is simpler to build, debug, and operate. Streaming is worth the added complexity only when there's a real requirement for near-real-time data, like fraud detection or live dashboards.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →