I keep the software a business already runs on working — then make it better.
Maintenance, modernization, integrations, and automation for web applications, APIs, and internal tools. I read the system before I change it, and I leave it maintainable for whoever comes next.
Practical engineering for software the business already depends on.
Modernize an existing application
Add features, refactor the risky areas, and raise maintainability in apps that already carry daily operations.
Connect APIs and third-party systems
Design, repair, and extend REST APIs so data moves reliably between the tools your team already uses.
Build internal tools around real workflows
Dashboards, portals, and admin interfaces shaped around how the business actually operates today.
Automate validation, reporting, and repetitive work
Data-processing and automation that cuts manual handling and makes business information easier to trust.
Three examples from real business software.
A recurring SAP-data workflow needed heavy manual preparation before anyone could use the information.
Built automation that turned raw exports into usable interfaces. A ~40-hour process now takes about 30 minutes.
A desktop-based legal workflow had to become easier to access, maintain, and evolve.
Helped migrate it into a cloud web application with clearer structure — the team now runs on a maintainable Laravel and Vue.js system.
A large system needed better module boundaries and more maintainable communication between its parts.
Worked on decoupling modules and Kafka-based messaging, moving the architecture toward clear service boundaries.
A stack is a decision, not an identity.
Most systems don't need a new stack — they need someone who can work safely inside the one you already have. I've shipped in Python, JavaScript, PHP, and Java since 2011, and reading into an unfamiliar codebase is part of the job, not a blocker. What stays constant is the method: map it, change it carefully, document what changed.
Laravel · Node.js
Kafka · webhooks
crawling · validation
CI · deployment support
Useful improvements, visible progress, maintainable handoff.
Workflow, codebase, data flow, and constraints first — before proposing any change.
The parts that reduce risk, save time, or unblock the team come first.
Tradeoffs, risks, and progress stated plainly, so nobody is guessing.
Decisions documented, no clever solutions that become hard to support.
Have a system that needs maintenance, integration, or automation?
Send a short note about the system, workflow, or integration. I reply with next-step questions — usually the same day.
Contract, retainer, or fixed scope