Backend & Architecture
Designing and building resilient, event-driven microservices and the contracts between them.
- Java
- Spring Boot
- REST APIs
- Apache Kafka
- Event-driven design
- PostgreSQL
- JUnit
- MapStruct
- SOLID
Software Engineer · Architecture · Platform Engineering
I build microservices at scale — and the tooling that makes teams faster.
Backend engineer in the telecom B2B / BSS domain, designing event-driven Java / Spring Boot systems for product ordering, offerings, billing and shipping. I pair that with deep platform engineering and a habit of turning engineering friction into shipped developer tools, IDE plugins, and AI / MCP automations.
15+tools & services shipped
5languages in production use
3IDE / editor platforms targeted
Capabilities
What I bring to a team
Platform & DevOps
Getting services to production reliably and keeping quality gates honest along the way.
- Docker
- OpenShift / Kubernetes
- Helm
- Jenkins
- GitHub Actions
- SonarQube
- JaCoCo
- Nginx
- Linux
Developer Tooling & AI
Turning recurring friction into shipped tools — extensions, plugins, MCP servers, agents.
- VS Code extensions
- IntelliJ plugins
- TypeScript
- MCP servers
- AI agent workflows
- Static analysis
- Python automation
Frontend & Product
Shipping clean, accessible UIs when the tool needs a face — and full apps end to end.
- React
- Svelte
- Next.js
- Astro
- Material UI
- Flutter
- HTML / CSS
Selected work
Projects
Code Insights
ActiveVS Code · TypeScript · Java · 2025
JUnit/JaCoCo coverage and fully offline SonarQube analysis, inside your editor.
- Embedded a real SonarLint + sonar-java engine, shaded into a runnable jar — full rule parity with the server, no per-scan calls
- Auto-detects Maven/Gradle and resolves per-module classpaths and generated sources
- Secrets stored via VS Code SecretStorage — never in settings
Auto Flow View
ActiveVS Code + IntelliJ · 2025
A visual dependency graph of TestNG flows — shipped on two IDE platforms.
- Heuristic Java analysis in VS Code; native PSI in the IntelliJ port
- Layers tests by depth to expose parallel groups and inherited steps
- One concept, ported cleanly to a second editor platform
webblock
In progressGo · Linux · nftables · 2026
A per-user, system-wide website/IP blocker that enforces at the Linux kernel packet layer — no setuid anywhere.
- Blocks egress at the kernel packet layer (nftables / iptables+ipset) so even raw-IP curl is caught
- Root daemon + unprivileged CLI over a Unix socket — no setuid bit anywhere; caller identity via SO_PEERCRED
- Per-user private blocklists with an O(1) data plane (hash sets + per-uid verdict map) and atomic, fail-safe applies
swagger-view
ActiveOpen source · TypeScript · GPL-3.0 · 2026
Local-first Swagger/OpenAPI preview with zero callbacks to any server.
- Refactored to SOLID services (parser, analyzer, navigation, cache)
- Hash-based caching + debounced updates for snappy previews
- Transaction-safe deletion (bottom-to-top to avoid line shifts)
Writing
From the blog
Turning a folder of projects into a developer story
What I learned writing my own READMEs, org profile, and portfolio — how to choose a static-site stack, structure a repo's front page, and quantify your impact honestly without overclaiming.
How I built this site: local-first, tracker-free, with Astro
The build journey of this very site — choosing Astro, picking paths over subdomains, pivoting from a blog to a full portfolio, auditing for telemetry, and a sneaky SVG encoding bug.
How I choose an architecture
My repeatable process for architecture decisions — start from the constraints, write an 'alternatives considered' table, and make the trade-off explicit. With examples from real projects.
Let's build something solid.
Open to conversations about backend architecture, platform engineering, and developer-experience work.