Yevhen Stuzhuk - Personal Portfolio
I am a Senior Software Engineer
Full-stack web apps and dashboards
End-to-end product interfaces, internal tools, dashboards, and data-heavy UIs with solid architecture, APIs, and persistence.
I design and ship web applications where the UI, business rules, and data layer work together reliably.
Typical engagements span admin tools, dashboards, APIs, and integrations. I favour explicit types, automated tests where they pay off, and pragmatic architecture your team can extend.
Delivery is iterative: clarify constraints early, implement vertical slices, and leave you with runnable builds and enough documentation to hand off or scale the team.
Representative work
Recent deliveries include nextevents and employment_cal—systems where full-stack web apps and dashboards skills (TypeScript, React, Astro, Node.js, PostgreSQL, SQLite, REST APIs, dashboards, forms, auth flows, testing) were applied end to end.
Those projects combined product UI, APIs, and operational concerns: roles, exports, integrations, and observability. The goal is always software your team can extend—not a one-off demo that collapses under real users.
Typical collaboration starts with a written brief: constraints, integrations, compliance, and what “done” means for the first release. We slice work into vertical milestones so you see progress every one to two weeks and can reprioritize without losing the thread.
After go-live we offer a short hypercare window: fix edge cases, tune performance, and transfer knowledge. Long-term support can stay with your in-house team or continue as a retainer—your choice.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
FAQ
Tap a question to expand the answer.
What stack do you typically use?
TypeScript across the stack: React or Astro for UI, Node.js for APIs, PostgreSQL or SQLite for persistence, plus REST integrations as needed.
How long does a typical project take?
Depends on scope. Focused tools often reach a usable MVP in 4–8 weeks with iterative vertical slices rather than a big-bang launch.
Do you write automated tests?
Yes where they pay off: critical user flows, API contracts, and data transforms—not blanket coverage for its own sake.
Can our team maintain the code after handoff?
That is the goal: explicit types, pragmatic architecture, short handoff notes, and optional pairing during transition.
What kinds of products do you build most often?
Admin panels, internal tools, dashboards, calculators, and content products where correctness and performance matter.
