Data Engineer

• You’ve designed, built and operated production data platforms or major parts of them, and can explain the architectural decisions you made and their consequences.
• Strong engineering fundamentals. You bring strong SQL, data modelling and production programming skills, with practical experience in orchestration, testing, deployment and operating reliable pipelines.
• Judgment about the data itself. You can evaluate whether a source is fit for a particular use, reconcile inconsistent information and make uncertainty or gaps visible to downstream consumers.
• You’ve handled inconsistent formats, changing schemas, incomplete records, rate limits and integration failures. You’re comfortable working beyond clean, well-documented APIs.
• A product mindset. You care about the decisions your data supports. You can work with domain experts and product engineers to translate an ambiguous need into a useful data product.
• Architectural ownership. You can review an existing system, establish a direction and deliver improvements incrementally. You understand access controls, privacy and the responsibilities that come with combining customer and external data.
• Clear communication and initiative. You surface problems early, write down decisions and challenge assumptions constructively. You’re comfortable making progress without a fully specified ticket.

Bonus

• Experience building data foundations for AI products, including retrieval, document processing or evaluating the quality of information supplied to agents.
• Experience modelling policy or regulatory information, including versioning and effective dates.
• Experience with property, financial services, geospatial data or international datasets.
• Familiarity with GCP, where we run our infrastructure, and experience working alongside backend engineering teams.
• Experience establishing data standards or helping build a data team.

This role isn’t for you if

• You just want to keep the pipelines running. You’ll need to care about which data we use, whether it can be trusted and how it improves the decisions our products support.
• You want a fully specified architecture to implement. We need someone who can assess what exists, challenge assumptions and take ownership of the technical direction.
• You only want to work with clean, structured data. Important information arrives through documents, policy announcements and inconsistent external sources. Making it usable is part of the job.
• You want to stay removed from the product or domain. You’ll work closely with product engineers and property experts. Understanding what the data means and how it is used is essential.
• You don’t connect with how we work. Our values—No BS, pursuit of excellence, feedback obsessed and healthy ego—mean communicating directly, holding a high bar, seeking feedback and being willing to change your mind.