Senior engineer, hands-on approach
I build data systems that work reliably and can be maintained without me. No duct tape, no mystery code, no vendor lock-in.
Who I am
I'm a senior data engineer and automation specialist with [X] years of experience building production data systems. I've worked on everything from early-stage startup data stacks to enterprise migrations.
Before going independent, I led data engineering teams at [COMPANY PLACEHOLDER] and [COMPANY PLACEHOLDER]. I've seen what makes data projects succeed and what makes them fail.
Now I work directly with companies who need senior-level help without the overhead of a big consulting firm. You get me - not a junior associate who's learning on your dime.
What I believe
I have strong opinions about how data work should be done. These beliefs shape every project I take on:
Quick facts
- Location US-based
- Experience [X]+ years
- Timezone [YOUR TZ]
- Languages English
- Response time <24 hours
Principles I work by
Correctness first
Data that's wrong is worse than no data at all. Every pipeline includes validation. Every migration includes reconciliation. I don't ship until the numbers match.
Maintainability matters
Clever code is bad code. I write for the engineer who comes after me - clear naming, modular structure, and documentation that actually gets read.
Observability built in
If it runs in production, it needs monitoring. Logs, metrics, and alerts are part of the deliverable, not an afterthought.
Security by default
Credentials in environment variables. Least-privilege access. Encrypted connections. These aren't extras - they're table stakes.
Documentation or it didn't happen
Every project ends with runbooks, architecture diagrams, and recorded walkthroughs. Your team should be able to maintain it without me.
Simple beats clever
I don't use Kubernetes when a cron job works. I don't build microservices when a monolith is fine. Right-size the solution to the problem.
How I work
Communication
I adapt to your tools - Slack, Teams, email, or whatever you use. I provide weekly written updates with progress, blockers, and next steps. Calls are scheduled when needed, not wasted on status updates that could be an email.
Async-first
I work well with distributed teams. Most communication is async via documentation and recorded Loom videos. This works across timezones and creates a natural paper trail.
Transparency
You'll never wonder what I'm working on. I share my screen, give you access to repos, and explain what I'm doing in plain English. No black boxes.