Artem Zhabinsky / Senior Software Engineer | Frontend - BFF - API Integrations
I design, build and modernize serious web and mobile products across frontend architecture, BFF layers, API integrations, delivery pipelines and product-facing technical leadership.
Product UI
BFF
API contracts
Delivery
The work sits between product surface, backend contracts and delivery reliability. That is where complex teams usually lose time.
Design systems, application shells, state boundaries, rendering strategy and migration paths for React and Next.js products.
Useful when the frontend has outgrown feature-by-feature delivery and needs a stable technical shape.
End-to-end implementation across frontend, Node.js services, data contracts, integrations and release workflows.
Strong fit for teams that need senior execution without separating product thinking from engineering quality.
Clean backend-for-frontend layers, REST API design, third-party integrations and typed contracts between systems.
Keeps frontend teams productive while protecting product surfaces from backend and vendor complexity.
Manifest V3 extensions, workflow utilities, private dashboards and automation surfaces for teams that need better development or operational tooling.
Useful when a small, sharp browser extension or tool can remove repeated manual work from a product team.
Incremental rebuilds, framework upgrades, test recovery, bundle cleanup and safer paths from old code to current architecture.
Built for business-critical products that cannot pause delivery for a rewrite.
Measurement-led performance work, automated test strategy and delivery pipelines that keep releases predictable.
The target is not prettier tooling. It is lower risk, faster feedback and better product reliability.
The stack is intentionally weighted. The center of gravity is TypeScript, React, Next.js, Node.js, BFF/API work, testing, CI/CD and performance.
Core stack
A concise view of where the judgment comes from: high-load, regulated, operational and delivery-sensitive product environments.
Fintech
Built and modernized product surfaces for high-load trading and risk workflows, with emphasis on performance, data contracts and internal operator trust.
Mobility
Worked on fleet and driver-facing product systems where operational clarity, wallet flows and mobile reliability mattered more than visual novelty.
Betting and casino
Contributed to large-scale frontend modernization in a high-traffic environment with demanding reliability and delivery requirements.
Product studio
Shipped web and mobile products for startup and scale-up clients, balancing architecture decisions with changing product constraints.
Earlier engineering
Built a practical fullstack foundation across UI implementation, integrations and maintainable application delivery.
A concise view of the systems Artem is typically brought in to design, modernize or ship. Client details are anonymized where needed.
Public case studies will be added selectively. Until then, these summaries describe credible engagement patterns without exposing confidential implementation details.
Trading workflows
A permission-aware web application for investor operations, workflow review and execution visibility across internal and vendor data sources.
Stabilized a complex product surface by moving integration complexity into typed BFF contracts and clearer frontend boundaries.
Mobility operations
A dense operational dashboard for fleet status, driver activity, incidents, documents and financial workflows across regional teams.
Improved operator speed with stable filtering, role-aware views and product instrumentation for workflow decisions.
Mobility fintech
A React Native mobile surface for balances, payouts, document flows and support touchpoints in a driver-facing product.
Raised confidence around money-adjacent flows through clearer API contracts, end-to-end coverage and resilient mobile states.
Humanitarian technology
A support coordination platform for intake, eligibility checks, case status and partner-facing operational reporting.
Kept the system maintainable and legible for non-technical staff working with sensitive, high-context operational data.
High-traffic gaming
A staged modernization of betting and casino frontend surfaces constrained by legacy architecture, heavy traffic and delivery pressure.
Improved release confidence through incremental migration, stronger regression coverage and bundle-level performance work.
Browser extension
A Manifest V3 extension that helps developers recreate authenticated sessions on localhost from dev, stage, UAT and production-like tabs.
Turns repeated login and environment switching into a controlled local workflow while keeping cookie handling inside the browser.
The value is not just code output. It is turning ambiguous product and integration work into decisions, contracts, feedback loops and shipped software.
Principle 01
Start by finding the product boundaries, data ownership and delivery constraints. Then choose the smallest architecture that can survive real growth.
Principle 02
Technical decisions are framed around release risk, maintenance cost, operator trust and product velocity, not tool preference.
Principle 03
Frontend, BFF and API layers should have explicit responsibilities. That makes product work faster and integration work less fragile.
Principle 04
Measure the expensive paths, reduce unnecessary client work, keep bundles lean and make quality visible in CI before users feel the damage.
Contact
Available for selected projects, modernization work and product teams that need a strong frontend/fullstack partner across architecture, delivery and integrations.