Frontend engineer at Trezor. I work on the trezor.io shop. Before crypto, I built security software and systems for the Czech government.
Most of my work has been on products where a broken interface has consequences: security dashboards, government systems, a crypto storefront. That shapes how I build. State, data flow, types and tests get the same attention as the layout, because those are what keep a product changeable in year three.
At Trezor I build the e-commerce side of trezor.io: product pages, checkout, and the content that explains what a hardware wallet does. The device and its app belong to other teams. The shop still has to earn trust before it sells anything, because for a lot of customers this is their first real conversation about holding their own keys. I follow this industry closely and I believe self-custody matters.
I work from Figma, but the handoff is not the finish line. Type scale, motion timing, focus states and the reduced-motion path all get decided during implementation. Earlier in my career I drove a full product rebrand and built the component system behind it, so I know what happens when those details are left open.
I run agent-assisted loops for most of my work: spec, implement, review. Models handle the mechanical parts and the first draft. Architecture, product trade-offs and the final call stay with me. I keep testing new models as they ship, because the useful skill is knowing what each one is actually good at.
Frontend for the trezor.io storefront: product pages, checkout, campaign and content pages. Retail scale, with a catalog that has to explain a security product instead of just listing specs.
Red Team in Jamf Security Cloud, building the RADAR app for vulnerability management, threat defense and data policy.
Before that: eGovernment portals and electronic legislation for the Czech state, plus a full UI rebrand at TeamGuru.
I believe miracles happen outside the comfort zone.
I started out writing PL/SQL and Oracle Forms for a health insurance system. Angular, React, security, crypto, agent workflows: every move since has been into something I had not done before.
The loop is the same whether I am shipping a campaign page or a checkout flow: get the intent right, let agents carry the mechanical work, keep judgment on the architecture.
Tools in daily rotation
Tools change every few months. The habit of writing the spec before the code does not.
© 2026 Imrich Kascak — Brno · Prague