EN

KeksOwl's personal website

Open to a lot of things!

Frontend Engineer focused on interactive UI, product thinking and engineering quality.

I work on complex product interfaces where frontend is not just presentation, but part of the product itself — interaction design, responsiveness, accessibility, usability and the long tail of details that shape how software feels in everyday use.

Most of my work lives somewhere between engineering, UX and product thinking: building interactive tooling, refining workflows, improving interface clarity and creating interfaces that feel reliable, responsive and intuitive over time.

Currently working with TypeScript, React and modern frontend tooling on complex interactive surfaces at Songsterr.

About

Hi! I'm Semyon, or just Keks — a frontend engineer who treats UI as a system, not a set of screens. I think about how components scale, how state flows, how an interface holds up when the network drops or a screen reader takes over. The kind of work where engineering decisions shape what the user feels — even if they never notice.

I work well in teams that blur the line between design and engineering — where both sides care about the result, not just the handoff. Whether it's two people or twenty, what matters to me is honest code review, async-first communication, and enough documentation that decisions don't get lost between sprints.

Outside of work I run tabletop RPG campaigns, build FoundryVTT modules, and translate video games and rulebooks from English to Russian. Turns out localization is just frontend with higher stakes: one wrong word and your bard starts a diplomatic incident.

  • Composition

    Components that work together, not just in isolation. How state flows between modules matters more than how any single one looks inside.

  • Product thinking

    The best frontend work starts before the ticket. Understanding why something exists shapes how it should feel.

  • Craftsmanship

    Details compound. Tooltip timing, focus order, empty states, loading sequences — the sum of small decisions is what users call 'polish'.

  • Ownership

    If I shipped it, I see it through. From first deploy to steady state — that's when the interesting edge cases surface.