About

I'm the person who builds the thing, not the one who sells it. Given an unfamiliar stack (a laptop NPU, a Wayland compositor, someone's accounting platform), my instinct is to go all the way down until I actually understand it, then build something correct on top.

How I work

I go deep into systems I didn't start in: a laptop NPU, a Wayland compositor, someone's ERP. The results have to hold up under the domain's own experts. AMD's engineers merged 20+ of my toolchain fixes, one into LLVM itself; a client's accountants confirmed the compliance catches. AI does a lot of the typing. That's the headline; the reality is the discipline that keeps it correct: benchmarks, labeled gold-sets, WER gates, byte-exact diffs. That discipline, not the AI use, is how I stay right in a stack I didn't start in. The verify signature is that discipline made visible. Most claims open to their receipt. Where there's no public proof, I say so plainly instead of dressing it up.

Availability

Remote-first · open to relocation · Moscow (UTC+3)

taimuraz@kaitmazov.com · github.com/atassis↗ · linkedin.com/in/atassis↗

Colophon

Built with Astro and self-hosted type (Source Serif 4, Inter, IBM Plex). No analytics, no CDN fonts. Every claim that can open to its receipt does. See why this site.