Roman Miakotin
Solution Architect & Engineer · Kyiv, Ukraine (remote)
I build systems meant to hold where they're not allowed to fail. Fifteen-plus years in high-load distributed systems — written mostly in Go, across healthcare, telecom, and crypto, where an outage isn't a bad day but a real cost to real people. That constraint shapes how I think about architecture, trade-offs, and what "done" actually means.
How I think
This blog is the long version: field notes one layer up from any single product — on resilience, on the way software itself gets built, on the decisions that don't show up in a stack but decide whether a system survives contact with reality. If you want to know how I reason before we ever talk, read a few posts. That's the point of them.
- Resilience by design, not by heroics. Systems that degrade predictably and recover on their own beat ones that need a human awake at 3am.
- Architecture is about what you can change later. I optimise for the decisions a team will need to reverse, not for elegance on day one.
- Ship, observe, correct. Judgment under ambiguity beats a perfect plan that arrives too late.
What I'm looking for
I'm looking for a founding CTO role with an early-stage team — founders who need someone to own the technical bet end to end: architecture, the first builds, the first hires, and the standards the product is held to. If you're building something that isn't allowed to fail and you think this way too, I'd like to hear from you.