2024 · Selected work
Lobasoft Enterprise Platform
A 35-app enterprise platform for ERP, financials, payroll, HR and audit workflows.
Commercial source code is confidential. I can provide an architecture walkthrough and discuss selected implementation decisions where client agreements allow.
- Role
- Front-end Engineer
- Location
- Vilnius, Lithuania · Hybrid
- Engagement
- Commercial product development
- Period
- March 2024 – Present
About the project
Lobasoft is a large enterprise software ecosystem composed of 35 React applications and 12 shared packages. Its products support data-heavy operational workflows across finance, accounting, payroll, HR, audit, document management and employee self-service.
The front-end is organised as a Turborepo monorepo with reusable UI, form, data, document and domain packages. A config-driven architecture turns resource definitions into consistent forms, lists, filters, actions and detail views while still supporting specialised product workflows.
My contribution
- Scope — As the sole front-end engineer, I own delivery from established OData/REST contracts to production workflows across accounting, payroll, HR and audit.
- Platform foundation — Built and maintain 12 shared packages and a config-driven resource layer that produces consistent forms, tables, filters, actions and detail views across 35 applications.
- Specialised workflows — Delivered purchase/sales orders and invoice approval, employee document submission with qualified and non-qualified e-signing, and time-tracking, with React PDF output for invoices, orders and HR processes and React Email notifications tied to workflow state.
Engineering proof
What was hard, what I chose, and how I checked it.
Challenge
As the sole front-end engineer, I had to modernise data-heavy workflows across 35 applications without fragmenting interaction patterns or breaking established OData and REST contracts.
Product & engineering decisions
- Recurring resource behaviour moved into shared packages, so applications describe their domain instead of reimplementing forms and tables.
- Document, signing and financial workflows each got a screen built for their own needs, rather than being squeezed into one generic model.
Quality & outcome
- Strict typing, package boundaries and targeted Turborepo builds surface the blast radius of a shared-package change before it ships.
- Playwright smoke coverage runs across all 35 applications, with targeted specs for two-factor authentication, master-data flows, deep links and form field requests.
A new resource adopts established forms, tables and actions through configuration alone. Specialised financial and document workflows extend the same shared foundation rather than reimplementing it.