Senior Database Engineer based in Vancouver, Canada. I specialize in keeping databases fast, reliable, and scalable — the kind that can't go down at 2am without someone losing sleep.
I've spent years working deep in MySQL, Aurora, PostgreSQL, and MongoDB at production scale, and I genuinely enjoy the performance tuning puzzle. Currently at Zendesk, working on cloud database infrastructure and automation.
Database Engineering & Administration High availability setups, primary-replica replication, multi-source replication, PITR recovery, zero-downtime schema changes with pt-online-schema-change, query optimization, index tuning, slow query analysis.
Cloud & Infrastructure Automated backup/restore pipelines to S3, monitoring and alerting scripts, ProxySQL for connection pooling and load balancing, container-based database deployments on Kubernetes.
Performance Tuning Execution plans, buffer pool utilization, locking contention, replication lag, I/O bottlenecks. If a query is slow or a replica is falling behind, I want to know exactly why.
🗄️ MySQL DBA Scripts & Toolkit — Production-ready Shell + Python scripts for automated backups (full, incremental, S3), replication health monitoring, user management, server resource tracking, slow query capture, PITR recovery, and data archival. Built from real production work.
⚙️ MySQL Development Work — Stored procedures, triggers, cursors, events, and table partitioning patterns for database-side application logic.
- Automation tooling for database provisioning and health checks using Python + AWS CLI
- Exploring ClickHouse for analytics workloads and time-series data at scale
- Writing up operational runbooks and architecture notes to publish here
Remote database engineering roles and freelance engagements — especially:
- Database migrations (on-prem → cloud, MySQL → Aurora, version upgrades)
- Performance audits and query optimization
- High availability architecture design
- Monitoring and automation setup
Best way to reach me for work inquiries is LinkedIn. I respond to real conversations, not cold form messages.
"A slow query in production is a problem. A query you don't know is slow is worse."