•
7+ years in a technical role, with at least 2 years in a technical lead or equivalent player-manager capacity — proven track record leading technical delivery, not just contributing to it, ideally in a client-facing or consulting delivery model.
•
Able to work across both software and data engineering; comfortable reviewing and unblocking React/TypeScript frontend work, Python (FastAPI/Django) or .NET backend work, and Azure data pipeline work — even if you don’t write every line yourself.
•
Hands-on experience delivering on Microsoft Azure — specifically Event Hubs, Azure Data Lake, Azure Databricks, Azure Digital Twins, AKS/containers, and Azure AI services.
•
Comfortable being the primary technical face of Sand to a client in a regulated, critical-infrastructure environment — able to translate technical trade-offs for non-technical stakeholders and hold your own with client architects.
•
A track record of setting engineering standards and mentoring engineers through delivery, not just managing tickets.
•
Able to work autonomously in a small, internationally distributed team while staying tightly coordinated with a Solution Architect and wider delivery organisation.
•
Relevant Bachelor’s degree in computer science, engineering, or a related field.
•
•
Azure: Event Hubs, Data Lake, Databricks, Azure Digital Twins, AKS, Azure AI services
•
Backend: Python (FastAPI / Django), .NET
•
Frontend: React, TypeScript
7+ years of engineering across multiple stacks and domains, shipping and operating production systems that mattered.
Genuine breadth. Not “full-stack” as in React-plus-an-API — full-stack as in the whole system:
•
Infrastructure (emphasis): Kubernetes, containers, networking, IaC — across AWS, Azure, and on-premises. You’ve run production infrastructure, not just deployed to it.
•
Backend: distributed services and stateful systems in Python and Node.js/TypeScript, on relational databases you know deeply.
•
Data engineering: pipelines, CDC/streaming, orchestration — moving heterogeneous data reliably at scale.
•
ML ops: serving and operating models and LLM systems in production, including offline environments.
•
Frontend: enough real experience to design, review, and build when needed.
You won’t be world-class at all of these — nobody is. Strong in most, dangerous in the rest, unafraid of any.
System design earned the hard way — you know what breaks at scale because you’ve been paged for it.
Range between IC and lead — you’ve led teams, you’ve been the strongest contributor on them, and you can tell which one a situation needs.
Agency. You don’t need all the requirements or someone telling you exactly what they want. Given a problem and a direction, you work your way around obstacles to an outcome.
Fast learning as a default state. New domain, new stack, new constraint — never intimidated by a problem you haven’t seen before.
Sleeves rolled up, always. You get stuff done — then you own that stuff.