$ whoami
SENIOR FRONTEND ENGINEER
OPEN TO NEW OPPORTUNITIES
Frontend Engineer with 8+ years of experience building web products across their full lifecycle. Worked on early-stage products, helping validate hypotheses and turn initial concepts into working solutions, as well as on large-scale, business-critical systems with complex architectures and business logic.
A career shaped by quality, product thinking and growing technical ownership.
Quality Product thinking Technical ownership Startup decisions
01 / QUALITY FOUNDATIONS
I started my career in QA with a foundation in HTML and CSS. After learning Python, I began using it to automate tests, building practical programming experience alongside my testing work and eventually automating 89% of test cases.
I was particularly interested in interfaces and user experience, so when an opportunity to move into frontend development came up, I took it.
Python Selenium
02 / UNDERSTANDING BUSINESS NEEDS
At Mel.fm, I built reader-facing experiences and tools for the editorial team. Working with editors and marketing taught me to understand the goals behind their requests and connect frontend work with business needs.
Alongside that, I gained experience improving a product used by millions of readers. I helped modernize the frontend through the transition from legacy Closure code toward React and implemented AMP pages that reduced mobile load time by 47%.
React GraphQL
03 / GROWING INTO OWNERSHIP
I joined an established tax-payment product for small and medium businesses, initially implementing analyst-defined tasks and learning to work within a Scrum team. As our team’s scope expanded to four products, I helped build three new services from scratch: employee payments, automatic tax savings, and a tax account for tracking tax deductions in a dedicated government system.
I handled frontend development largely independently for three products and collaborated on the fourth. Over time, I took ownership of features, contributed heavily to planning, and became someone teammates turned to for product context. I regularly reviewed code and worked through technical questions with colleagues, sharing knowledge and seeking advice.
My responsibilities also grew to include architectural decisions and long-term maintainability. I advocated for independent microfrontend modules so products could be released separately and their codebases kept manageable, while sharing a common technology stack and the bank’s design system. As part of the bank’s broader architectural transition, I migrated an application out of the legacy monorepository, reducing build time by 67% and eliminating cross-team release approvals.
My work extended beyond our own products. I developed a broad understanding of the bank’s frontend architecture and contributed changes to other teams’ products when integrating our functionality, aligning technical decisions with those teams when needed. For a unified entry point requested by product managers, I designed and delivered an integration that reused existing microfrontends and preserved separate repositories, reducing implementation effort while allowing both teams to develop and release independently.
React TypeScript Webpack Cypress
04 / STARTUP DECISIONS
Alongside my banking work, I joined an early-stage AI product using Vue and Nuxt. The startup environment gave me greater involvement in technology choices, weighing immediate delivery needs against future development.
I contributed to a KYB onboarding redesign that helped completion rise from 13% to 26%. I also co-developed an interactive reporting interface for exploring complex dependency graphs, helping evaluate visualization libraries against a demanding design, potentially large graphs, Vue compatibility, and active maintenance.
This experience broadened my technical range and gave me more practice choosing tools around the needs of a developing product.
Vue Nuxt
$ stack --inspect --only-with-production-experience
