Complex browser applications
Interactive workflows, dashboards and internal tools built around usable states, predictable behaviour and maintainable modules.
JavaScript engineering for products that need to move
Turn difficult JavaScript work into dependable releases.
I help product teams untangle demanding frontend and Node.js work: incomplete features, slow interfaces, unstable integrations and code that has become hard to change. The goal is working software your team can continue owning.
Browser and server-side JavaScript
Direct technical collaboration
New features or existing systems
10+years shipping web software
75+projects delivered
1senior engineer you work with
JavaScript work I handle
From interactive interfaces to the services behind them.
I can own a focused delivery stream or work through the technical debt blocking your existing roadmap.
Node.js services
APIs, workers and integration services designed with explicit validation, error handling, observability and operational boundaries.
TypeScript adoption
Practical migrations that improve confidence around important domain code without stopping delivery for an unnecessary rewrite.
Platform integrations
Payment, CRM, analytics and vendor APIs connected with resilient flows rather than optimistic happy-path code.
Frontend performance
Rendering bottlenecks, oversized bundles and slow interactions measured and improved where users actually feel the delay.
JavaScript modernisation
Fragile older code stabilised in useful increments while preserving the business behaviour the product depends on.
Choose the right starting point
Bring a release, a bottleneck or a system that needs ownership.
The engagement is shaped around the actual delivery risk rather than a generic developer placement.
Feature Delivery
A substantial JavaScript feature taken from technical discovery through implementation and release.
- Requirements and edge cases clarified
- UI and service work coordinated
- Testing around critical behaviour
- Release notes and handoff
Reserved JS Capacity
Reliable weekly capacity for a team with more JavaScript work than its current developers can absorb.
- Prioritised delivery queue
- Fits your review workflow
- Frequent visible progress
- Flexible renewal points
System Improvement
A deliberate programme of fixes for a JavaScript application that is slow, brittle or difficult to extend.
- Codebase and runtime assessment
- Risk-ranked improvement plan
- Incremental refactoring
- Performance and reliability work
Need a defined block of senior development time?
View current capacity and hour packages
A productive collaboration
Good JavaScript work needs product context, not isolated tickets.
I work best where technical decisions can be connected to users, release priorities and the real constraints of the application.
You want someone to solve the whole engineering problem.
- A product or technical owner can answer domain questions
- The outcome matters more than preserving a predetermined implementation
- Code review and testing are part of delivery
- You value early warnings about hidden complexity
The role is limited to blindly clearing disconnected tasks.
- There is no access to the application or relevant decision makers
- Every technical choice is fixed before discovery
- The schedule assumes quality checks can be skipped
- The only comparison is the lowest available hourly rate
International client experience
Remote collaboration shaped by real client work.
I have worked directly with clients in the United States, Canada, the United Kingdom, Germany and other international markets. For roughly the past six years, most of my client work has been with US-based businesses—across time zones, established team workflows and direct stakeholder communication.
United StatesCanadaUnited KingdomGermanyInternational
Selected JavaScript work
JavaScript used across real interfaces and systems.
Recent projects where JavaScript supports product behaviour, integrations and dependable user journeys.
Web Application
ESG Rating
The ESG Rating application helps users efficiently fill out questionnaires, and the Croatian Chamber of Economy (CCE) to collect, process, evaluate and rank ESG-related…
View project
Web platform
JamSesh
Live music shows platform that enables artists and venues to create profiles, manage shows, and engage with fans.
View project
Working JavaScript stack
Modern tools without framework theatre.
JavaScriptTypeScriptNode.jsViteREST APIsGraphQLPostgreSQLRedisVitestPlaywrightDockerCI/CD
Before we open the repository
Questions teams ask about JavaScript support.
A short technical conversation is usually enough to establish the system boundaries, working model and sensible first step.
Yes. I work on browser applications and Node.js services, especially when a feature crosses the boundary between interface, application logic and an external API.
Usually. I identify the areas creating the greatest delivery or runtime risk and change them incrementally behind tests and observable behaviour.
Yes. I favour gradual adoption around important interfaces and frequently changed modules rather than converting every file before value can ship.
Yes, provided they are not actively harmful. I first understand why the current choices exist, then propose changes only where the benefit justifies disruption.
Yes. I use measurements from the actual application to trace rendering, network, bundle and main-thread costs instead of applying generic optimisation checklists.
Work is visible through your normal repository and planning tools, with direct communication and agreed overlap from my Central European time zone.
Start with the blocked release
Make the JavaScript roadmap easier to ship.
Describe the product, the codebase and the work your team cannot currently move forward. I will tell you whether I can own it and what I would examine first.