Senior Site Reliability Engineer
Your frontdoor stays open. Reliably, at any scale.
Hi, I’m Kenji, the site reliability engineer behind frontdoorapp.co. While the team builds your website, inbox, and social presence, I keep the platform underneath it fast, secure, and online around the clock, so your front door never has an off day. Automate the toil, measure everything, stay calm under load: to me, SRE isn’t a job title, it’s how a platform earns trust.
The reason your site never goes down at 2am.
More than half a decade in Site Reliability Engineering.
Keeping high-throughput platforms fast, secure, and online, so the teams building on top of them can move fast.
What I do
Keep it reliable, observable, and fast.
Reliability & SRE
SLOs, error budgets, on-call, and blameless incident response that keeps systems calm under load.
Kubernetes & Containers
Cluster design and migrations, Docker, and Istio service mesh for workloads that scale cleanly.
CI/CD & Automation
Streamlined pipelines with Jenkins and GitHub Actions so teams ship fast and safely.
Observability
Metrics, logs, and traces with Prometheus, Grafana, and Elasticsearch. Dashboards and alerts that catch it early.
Infrastructure as Code
Reproducible infrastructure on AWS with Terraform and secrets managed in Vault.
Databases at Scale
Tuning and operating Cassandra and Aurora clusters for throughput and resilience.
Experience
Where I’ve run production
Years of keeping high-throughput platforms fast and dependable, and building the teams and systems that make that repeatable.
Senior Site Reliability Engineer
Keeping a high-throughput Web3 infrastructure platform fast and dependable, with a focus on automation, observability, and infrastructure that scales without drama.
Senior Site Reliability Engineer
Founded the SRE team and its practice. Led Kubernetes migrations, optimized database clusters, designed observability platforms, and streamlined CI/CD pipelines across the org.
About
How I keep your frontdoor dependable
I came up through electronics engineering into the space between code and infrastructure, and spent more than half a decade running production for a high-throughput platform. That taught me that reliability is a feature, not an afterthought, and that the best incident is the one that never pages anyone.
That’s what frontdoorapp.co runs on. When we tell a business their whole online presence will stay live on autopilot, someone has to make that true. I keep the platform behind it automated, observable, and calm under load, so every customer’s front door is open when theirs come knocking.
Automation over toil
I script the repetitive work away, so frontdoorapp.co can onboard every business on one reliable, automated backbone instead of hand-built setups.
Observable by default
Metrics, logs, and traces on everything we run, so a hiccup on any customer’s presence surfaces to me, not to them.
Calm under load
SLOs, error budgets, and blameless incident response. Traffic spikes and busy launch days are planned for, not fire-fought.
Reliability
What that means for your frontdoor
The reliability work is invisible when it’s done right. Here’s what it buys the businesses on frontdoorapp.co.
Always open
SLOs, fast recovery, and calm incident response keep your site, inbox, and pages live, so customers never find a closed door.
Fast, everywhere
Tuned infrastructure and clean pipelines mean pages load quickly and updates ship without downtime.
Secure and recoverable
Hardened systems, managed secrets, and backups keep your presence and its data safe, whatever happens.
Certifications
Verified credentials
Cloud, infrastructure, and networking credentials from AWS, HashiCorp, Cisco, and Microsoft, each verifiable on Credly.
Contact
Let’s build something reliable.
Working on hard infrastructure, scaling, or reliability problems? I’m always up for a good systems conversation.