Selected work.
Systems built and shipped: stack, decisions, and outcomes. Open code, open architecture.
Production Blockchain Infrastructure
DevOps Engineer · ChainZeeper
Nov 2022 — Present
Active Web3 application workloads needed reliable, repeatable deployments and resilient node infrastructure across development, staging, and production — with continuous uptime and secure access to production services.
Architecture
- Multi-environment topology (development, staging, production) with shell-based Infrastructure-as-Code for reproducible provisioning across AWS, DigitalOcean, and Vercel.
- Containerised services with Docker and Docker Compose behind an NGINX reverse proxy with TLS termination and access controls.
- Blockchain node infrastructure with continuous uptime monitoring and reliable RPC endpoint availability.
What I owned
- Built and own the end-to-end CI/CD pipelines (build, test, deploy) with rollback.
- Operate and maintain the blockchain node infrastructure and RPC endpoints.
- Hardened production security via NGINX config, IAM policy review, secrets management, and TLS.
- Lead incident response — root-cause analysis and permanent fixes.
Outcome
- Multiple production deploys per week with rollback capability, replacing manual release steps.
- Reduced manual deployment overhead through automated, reproducible pipelines.
Mobile App Release Automation
DevOps Engineer · ChainZeeper
2026
A cross-platform React Native (Expo) app was released to the stores by hand — manual builds, signing, version bumps, and uploads — which was slow, error-prone, and hard to audit.
Architecture
- GitHub Actions orchestrates EAS cloud builds and store submission; signing keys and build numbers are managed by EAS, never exposed on the runner.
- A published GitHub Release triggers a single signed build that auto-submits to the internal track; production is a one-click promotion with staged rollout. The same EAS submit profiles cover both Google Play and the App Store.
- Tag-driven semantic versioning via a dynamic Expo config, plus a workflow_dispatch build-id input to re-submit an existing build without rebuilding.
What I owned
- Designed and built the end-to-end pipeline and a one-command release script.
- Hardened it to supply-chain best practices: SHA-pinned actions, least-privilege GITHUB_TOKEN, scoped store service-account IAM, secret-based credential injection, concurrency guards, and job timeouts.
- Debugged real delivery failures — CI auth scoping, app-config plugin resolution, and store versionCode-reuse constraints — and corrected the design to upload-once-then-promote.
Outcome
- Replaced manual store releases with a single GitHub Release that builds, signs, and submits automatically.
- Safe production delivery via staged rollout and a human promotion gate.
Internal Full-Stack Tooling
DevOps Engineer · ChainZeeper
2023 — Present
Operations lacked visibility into infrastructure metrics, and routine engineering tasks were manual and repetitive.
Architecture
- Internal dashboards built in Next.js and the MERN stack to surface operational metrics.
- REST APIs backed by MongoDB and PostgreSQL schemas designed for internal team workflows.
What I owned
- Designed and built the dashboards, REST APIs, and database schemas end-to-end.
Outcome
- Streamlined routine engineering tasks and improved internal developer experience.
Cross-Platform Mobile Applications
Full-Stack / Mobile Developer
2021 — 2023
Product needed cross-platform mobile clients integrated with backend services, authentication, and notifications.
Architecture
- React Native clients integrated with backend REST APIs and authentication flows.
- Push notification services wired into the mobile clients.
What I owned
- Built and shipped the apps, including App Store and Play Store submissions.
- Integrated authentication flows and push notifications with backend APIs.
Outcome
- Published cross-platform mobile applications to both app stores.