ETL code review

Who this is for

Teams that maintain batch or micro-batch pipelines — warehouse loads, regulatory reporting chains, or operational replicas — and want an external reviewer who has shipped similar jobs. Common triggers: a new tech lead, POPIA-related retention changes, or a failed go-live that pointed at “the SQL layer.”

What you receive

• A findings document grouped by severity (blocker, major, minor, note)
• Inline references to files, line ranges, or job names — no vague “consider improving quality” bullets
• A 45-minute readout call with your maintainers to argue about trade-offs
• Optional retest pass within 14 days if you land fixes and want a delta check

What we examine

Transformation logic (SQL, dbt models, Spark notebooks, Python operators), incremental load predicates, deduplication keys, null handling on late facts, retry and alerting hooks, and test coverage that actually guards grain — not only “row count > 0.”

What we do not do

We do not run your production jobs, alter live data, or take over implementation unless you book a separate build engagement. Reviews are read-only on the artefacts you provide.

Timeline & delivery

Standard turnaround is five to ten business days from repository access and agreed scope. Rush slots exist at a surcharge when our calendar allows.

Location

Remote by default; readout calls suit SAST business hours. On-site kickoff in East London or Buffalo City is available for enterprise clients with facility access requirements.

Preparation

Share read access or an export, a one-page data-flow sketch, and the names of jobs in scope. Redact PII columns if policy requires — we can review structure without sample values.

Pricing basis

Quoted per engagement from job count and codebase size. See rates for starting figures. A 30% deposit confirms the slot; balance on delivery of the report.

Next step

Submit a review brief or email info@terra-pipeline.digital with repository size and target date.