I design and build complete web applications — from user-facing interfaces and internal tools to APIs, databases, integrations, and background workflows. The result is software that works as a whole and remains maintainable after launch.
Explore the systems I can build and the technologies behind them. Switch between solution and technology views, then select any capability to see how it contributes to a complete product.
Problem — multiple clients needed to use one API product without exposing data, access, or processing workflows across organizations.
Solution — built a shared API platform with client-specific environments, JWT-based authentication, role-aware access control, configurable input normalization, tenant-specific processing, and isolated service and database layers.
Problem — critical answers were buried across years of documents, wikis, and tickets.
Solution — a retrieval-augmented assistant that answers in context and cites its sources every time.
Problem — business teams needed one place to manage users, projects, statuses, assignments, reports, and operational data instead of relying on disconnected tools and manual processes.
Solution — built and supported role-aware admin interfaces, operational dashboards, filtered data views, reporting workflows, status tracking, assignment management, and the backend APIs that powered them.
Problem — a data API needed a faster and more resilient read path without sending every request directly to the database.
Solution — built a production-style .NET API with cache-aside reads through in-memory cache, Redis, and PostgreSQL. Successful writes refresh both cache layers, while Docker Compose provides a reproducible local environment.
Problem — users needed to upload business documents, convert them into multiple formats, track progress, and retrieve the result without blocking the main application.
Solution — built an API-driven .NET service with upload and status APIs, background processing, Microsoft Office-based conversion, SignalR notifications, retry and failure handling, workspace cleanup, and isolated conversion workers that could be scaled independently.
I work best on serious, long-lived software where understanding the product matters as much as completing the next task. I think through the architecture, communicate clearly, and take ownership of the result rather than simply closing tickets.
I work across the full stack, with particular depth in backend architecture, APIs, databases, integrations, and data-intensive workflows. I care about how the entire system fits together — not only how individual features are implemented.
Tell me what you want to launch, improve, or repair. Share the current state, the main problem, and the outcome you need — I’ll respond with concrete technical thoughts.