Ingest and land
Pull from files or a sample API into a structured landing zone with retries.
Internship
Build pipelines, checks, and runbooks with mentor support — production habits, not just notebooks.
What you get
Pull from files or a sample API into a structured landing zone with retries.
SQL (and light Python) that another engineer can read and rerun.
Freshness, uniqueness, and row-count tests so a silent failure is visible.
A scheduled job on Azure or an agreed runner — not a script you start by hand.
What to do when a source is late. You write the doc, not just the pipeline.
Code review standards you will meet in a first job: names, logs, and scope.
How we work
Share your background, a short note on the track, and when you can start. We confirm fit within a few business days.
Tools, working hours, communication norms, and your first dataset — so week one is not spent guessing.
Weekly goals on a real business problem. You ship work, not attendance screenshots.
A scheduled review every week. You get written notes on what to fix before the next sprint.
A portfolio piece you present: analysis pack, pipeline, or model — with assumptions written down.
Interview walkthrough of your project, résumé notes, and how to talk about the work honestly.
Client stories
I had never written a runbook. That exercise got more interview questions than the pipeline itself.
They made me add tests before adding features. Painful. Correct.
Azure exposure without a 40-hour certification slog. We built one thing well.
Help centre
SQL, Python, and Azure data services based on the cohort plan. You do not need prior Azure certification.
Yes. Internships are remote-first, with live mentor sessions on a published calendar.
Terms are confirmed per cohort. Some tracks include a stipend; others are project-based learning with a certificate and portfolio. We state this clearly before you accept.
Plan for 15–20 focused hours. Full-time blocks can be arranged for a shorter calendar.
No. We look for evidence you can finish work: a small project, coursework, or a clear note on why this track.
Tell us about your background, any SQL or Python you have, and your preferred start date.
Contact us