Full-stack engineer · System analyst

Sviataslau Bely

About four years with vendors and end clients: building TypeScript/React and Java/Spring products, and working as a system analyst—requirements and process modeling, data and API clarity, backlog and acceptance criteria, and shipping features without losing the thread between business intent and code.

LinkedIn sbelywork@gmail.com GitHub

Based in Poland · Open to remote · English B2+ · Speak (BY, RU) · Delivery & analysis

What I bring

Full-stack implementation together with system analyst work: clarifying what to build, how data and APIs should behave, and how to verify it in production. The cards below split that into themes for a quick scan.

UI engineering & alignment

React and TypeScript components and flows built for reuse, with tests in CI. Often the same person who refines UI behavior, acceptance criteria, and alignment with backend contracts.

Services, schemas & integrations

Java and Spring services, REST and SOAP, mapping from complex enterprise schemas. Code and structure stay readable for the next developer—or analyst continuing the story.

From elicitation to release

Workshops and requirements, BPMN/UML when they help, backlog quality, then implementation, review, and production support—so “what we agreed” stays connected to what ships.

Technical stack

Tools and practices I have used in both engineering and system analyst roles: implementation stacks alongside analysis, data, integrations, and analytics

FRONTEND

BACKEND

DEVOPS

SYSTEM ANALYTICS

BUSINESS ANALYSIS

DATA & SYSTEMS

INTEGRATION & APIS

ANALYTICS & TRACKING

Own projects

Outside client work I like to turn my own product ideas into something real—small apps and experiences where I own the concept, UX, and implementation end to end. It keeps experimentation honest and reminds me what shipping from a blank page feels like.

Oni AI Assistant

macOS companion for technical interview prep powered by Claude Code—undetectable on screen share, focused on algorithms and live coding. Public landing, download flow, and product narrative.

  • Swift
  • macOS
  • Claude

CYBER PARTY

Fullscreen browser club experience: сustomizable dancers, visual effects, and retro DJ-style playback—built as a playful second-screen party experiment.

  • JavaScript

Arcteryx Pro iPad Figma layout

iPad-oriented product UI explored in Figma; click the card to download the exported result frame as a PNG.

  • Figma

ClearUI — Neomorphism Storybook lib

Component library with a soft neomorphism look, shipped as @clear/ui and documented in Storybook—live controls, variants, and a deploy you can browse without cloning.

  • TypeScript
  • React

Dimension

Product-style landing built around the browser graphics stack: HTML Canvas for layered drawing and Three.js for depth, lighting, and motion in the scene.

  • JavaScript
  • HTML
  • Three.js

ATM Console

Terminal-style ATM flow in Java: Maven build, Hibernate on PostgreSQL, Dockerized database, and JUnit 5 tests. Run with make run or from the IDE once Postgres is up.

  • Java
  • PostgreSQL
  • Docker

Capability summary

How engineering and system analysis show up against the stack bands above

Product UI

React and TypeScript, Next.js and microfrontends where required, Tailwind, MUI, PrimeReact, Redux, TanStack Query, Zod, Yup. Testing with Jest, React Testing Library, Cypress, Playwright—paired with UI-side specs and acceptance thinking when the role spans analysis.

Services and data

Java (including 21), Spring Boot, Spring Security, Hibernate, JPA, REST and SOAP, GraphQL where applicable, XML and JSON mapping, PostgreSQL on RDS, Flyway, Liquibase, JUnit, Mockito. Microservices and distributed systems when the architecture calls for them, including tracing how data moves through services.

Platform and delivery

AWS: S3, ECS, ECR, RDS, CloudFormation, CDK, CloudWatch. Docker, Kafka, CI/CD, Git. Datadog, OpenSearch/Elasticsearch, and related observability when the environment uses them.

System & business analysis

Core system analyst practice: requirements elicitation, business and system analysis, process modeling, BPMN, UML, gap analysis, acceptance criteria, backlog management, Agile (Scrum/Kanban), stakeholder management.

Data, APIs & analytics

Analyst-style data work: SQL, analysis, mapping, validation, KPI and metrics definition, data flow and lineage, JSON/XML. REST, GraphQL, API analysis, Swagger/OpenAPI, Postman, event-driven architecture. Product and ops insight: Google Analytics (GA4), Grafana, Amplitude, AWS OpenSearch/Elasticsearch, CloudWatch, Datadog.

Modeling, design & collaboration

Sparx Enterprise Architect, Draw.io, Lucidchart, Obsidian, Figma, Miro. MS Teams, Skype, Zoom, Google Docs. Jira, Confluence, Excel, Azure DevOps alongside the usual IDE and quality tooling.

Also used

Node.js, Express, Knex, MongoDB when the stack calls for it. Vue 2/3, Vuex, Vuetify. WebStorm, VS Code, IntelliJ, LaunchDarkly, SonarCloud—plus anything already listed when a project tilts more toward pure delivery or a narrower analysis scope.

If you are looking for someone who both ships full-stack software and keeps requirements, models, and APIs coherent, email a short description of the role or project

Email me