Data Engineer
About the role
- Security work: fixing code security issues, updating identities/secrets, ensuring secure endpoints.
- Governance: data partitioning, physical access restrictions, compliance related updates.
- Feature innovation and continuous platform enhancements.
- Maintaining and improving pipelines across Cosmos (MapReducer) and Azure data platforms (HDI, ADLS Gen2, Spark). Typical Task Breakdown & Operating Rhythm
- 15–20% security-related fixes (code vulnerabilities, endpoint issues, secret rotation).
- Governance and compliance work (data partitioning, access control).
- Writing, modifying, and debugging code and services.
- CICD, monitoring, and standard engineering lifecycle practices.
- Mostly heads down execution work, following a task list and completing high priority deliverables quickly.
- Collaborating with FTEs who will help onboard and accelerate ramp up.
- Using SAW device access for AME domain work (pre prod/prod as allowed).
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
