Start Date
Immediate
Expiry Date
07 Jan, 27
Salary
60000.0
Posted On
09 Oct, 26
Experience
7 year(s) or above
Remote Job
Yes
Telecommute
Yes
Sponsor Visa
No
Skills
Industry
Information Services
tudytube makes professional development accessible, easy and actually enjoyable. Behind that platform sits a growing stream of learning data, and we want to put it to work for our customers, our product teams, and the AI-powered features we are building next.
We are looking for a Data Engineer who likes ownership. You will be the engineering backbone of a small data team: you turn messy source data into models people trust, and you leave the platform better than you found it.
You join the Product & Tech team as the data engineer in a team of three, working side by side with data analysts. The team will grow. Over time a dedicated data team with a Data Lead is likely. For now, you report to the Head of Engineering and you own our data platforms end to end.
That means real scope. You design, build and run the pipelines that take raw product and business data through to the marts that power analytics, reporting and product features. You talk to analysts, product managers and engineers, translate what the business needs into something that actually works, and keep quality non-negotiable: tests, monitoring and documentation are part of the job.
Part of our platform already runs on Databricks: a dedicated Azure environment for customers with strict security requirements. You will take ownership of it, working alongside the external specialists who built it until you run it independently. Next, you will help prepare our main warehouse move from Snowflake towards Databricks.
You have about 3–6 years of hands-on experience as a data engineer or analytics engineer in production. This is not a role with a large platform team behind you. You can take a new source or an analytical need and deliver a tested, monitored solution without someone looking over your shoulder.
You are comfortable in a scale-up: enough calm to handle a bit of chaos, and enough craft to put structure in place. You can explain trade-offs (batch vs streaming, incremental vs full refresh, build vs buy) to people who do not live in SQL all day. And you treat data as a product: if an analyst cannot find, understand or trust a table, the work is not done.