> Markdown version of [/jobs/ext/4696243-data-engineer](https://www.wearedevelopers.com/jobs/ext/4696243-data-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Data Engineer - **Company:** Databricks - **Location:** Amsterdam, Netherlands - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Data Systems, Operational Data Store, Software Engineering, Data Processing, Databricks - **Published:** November 13, 2026 - **Apply:** https://www.werk.nl/nl/vacatures/72269922 ## About the Role When on-site with clients, you may encounter something very difficult to solve. At Xebia we work as a team and we've got your back. Everyone is just a message away and ready to help. We say People First, and we mean it. What you bring This role requires at least 3 years of relevant work experience. We care more about impact than years. ... ## Description You are a data engineer responsible for building, maintaining, and keeping operational data pipelines and integrations that power modern lakehouse platforms on Databricks. This role forms the technical backbone of our clients' data organizations. Without reliable data, no other part of the organization functions. You are familiar with software engineering and know your way around Databricks, building robust and scalable production systems. You enjoy not only bringing new products live, but also iterating and refining after go-live. What you do You implement foundational data systems on Databricks to store, transform, and process data at scale. Security, reliability, and future growth are always in mind. You explain your design choices, align team members, and help client teams make confident and informed decisions about their data landscape. You learn from experts from diverse fields and different environments and industries. You work long-term with clients in the healthcare or banking domain. You build deep domain knowledge while delivering meaningful impact. After go-live, you see what happens in practice and work on: - The edge cases and the slow leaks - Things that were "good enough" six months ago and that you now make excellent - Building a battle-tested system rather than an MVP