Software Engineer, Geek, and Dad of twins in Aichi, Japan.
Backend engineer with 10+ years of experience designing and building scalable systems on the cloud.
Building cloud platforms, not just using them.
- Languages: Go (primary), Python, Ruby, JavaScript/TypeScript
- Swift (cross-platform), Rust, Kotlin, Java
- Protocols / Ecosystem: Protocol Buffers, gRPC, REST
- Domains: Cloud infrastructure, distributed systems, backend architecture, cloud security & compliance (detective controls for government cloud)
- Interests: Observability, reliability, concurrency, and control planes
- Engineering Style: Turn ambiguity into structure. Build systems that scale — both technically and organizationally
- Terminal Life: Minimalism, vim bindings, and a deliberate rejection of syntax highlighting
- Personal site: thara.dev
- Blog: blog.thara.jp
- GitHub: github.com/thara
- Bluesky: @thara.jp
- LinkedIn: Tomochika Hara
I design systems that make complex problems understandable and operable.
I've led server architecture for a metaverse platform, scaled mobile game backends past 10M downloads, and now build services that meet government cloud requirements.
- Lead architecture and development of scalable backend systems and cloud services
- Define system boundaries, data models, and protocols for distributed environments
- Drive projects from unclear requirements to production through cross-team collaboration
- Design development processes (CI/CD, release flows, documentation) for scalability and reproducibility
Most of my work focuses on making systems — and teams — operate predictably at scale.
- Taming ambiguity: turning vague requirements into shippable systems
- Sustainable teams: documentation, design docs, and processes that outlive any single engineer
- Boring reliability: observability, daily releases, and zero-downtime migrations over heroics
Systems engineer, terminal enthusiast, and firm believer that tools should stay out of your way.
Ideal weekend: silence, a clean terminal, and two sleeping kids.
Turned off syntax highlighting. On purpose.
I don’t recommend it — but it’s mine.