Natalia Protasova

My background is in clinical psychology with a specialization in neuropsychology - and it's not a detour. It shaped how I think about interfaces: as systems that carry cognitive load, shape attention, and either support people or quietly frustrate them. That lens stays with me in every architecture decision.

I moved into frontend deliberately. I was drawn to the structural side of UI - the way a well-designed component system holds together under pressure, and the way semantic markup makes technology legible to everyone. I studied intensively, built real projects, and joined my first team.

At Prime Dev I worked on complex internal products for education and healthcare - operational dashboards, scheduling systems, and data-heavy interfaces used by people doing demanding work. In these environments, ambiguity in the UI has real consequences and accessibility is not optional.

I enjoy working with legacy systems - not just refactoring them, but understanding them first: the decisions that made sense then, the constraints that shaped them. There's something satisfying about improving a system while preserving what already works. Honestly, the interesting part is the problem, not the starting point.

Now I'm looking for a team where the problems are complex enough to be interesting - operational tools, design systems, or something entirely new. Learning a new stack has never been a problem for me; in fact, I enjoy it.