Distributed back-end systems
Service boundaries, state transitions, message-driven workflows, retries, duplicate detection and clear failure modes.
Senior Software Engineer Senior .NET Developer
Senior software engineer building reliable back-end systems and document-processing workflows.
I work across .NET, TypeScript, SQL, messaging, Kubernetes and CI/CD. Most of my work has been in enterprise environments where systems need clear state, reliable processing, useful diagnostics and careful integration with other platforms.
.NET TypeScript Messaging Kubernetes
What I work on
Systems that need clear behavior under real operational pressure.
Document and file-processing workflows
Backend coordination for file ingestion, metadata persistence, OOXML/PPTX processing and browser-backed document workflows.
Engineering quality and delivery
CI/CD, automated tests, code analysis, versioning, Docker, Kubernetes and practical delivery habits for long-lived systems.
Observability and operations
Health checks, logs, traces, correlation IDs and diagnostics that help teams understand what a system is doing.
Selected work
Representative work, without exposing sensitive context.
These notes describe the technical shape of the work rather than dates, client timelines or internal details.
01
Adobe product engineering
Backend and platform engineering for document-processing and presentation-import workflows at Adobe, involving TypeScript, Node.js, Bazel, Kubernetes-based infrastructure, browser automation and server-side OOXML/PPTX processing.
- Large TypeScript monorepo
- Headless Chrome, Puppeteer, Playwright and Chrome DevTools Protocol
- Architecture, implementation and team delivery
02
Restricted enterprise ingestion platform
Distributed .NET microservices for asynchronous file and report ingestion in a restricted enterprise environment.
- .NET, C#, SQL Server and background worker services
- Artemis, AMQP and enterprise messaging
- Kubernetes, Helm, CI/CD, idempotent processing, retries and operational diagnostics
03
Memory-leak investigation tooling
Tooling around Playwright, Chrome DevTools Protocol and memory analysis workflows to make frontend memory-leak investigation more repeatable and easier to inspect.
- Browser automation workflows
- Repeatable capture and inspection steps
- Developer-facing diagnostics
04
Delivery and engineering quality
CI/CD pipelines, code analysis, versioning, Docker, Kubernetes and automated testing to make delivery workflows more predictable and easier to diagnose.
- Azure DevOps and build pipelines
- Testcontainers, Playwright, SpecFlow and Selenium experience
- Practical release and verification workflows
Experience summary
Product engineering, enterprise integrations and platform work.
I have 13+ years of experience across product engineering and independent consulting. My work has ranged from ASP.NET systems and enterprise integrations to distributed microservices, document-processing workflows, platform tooling and CI/CD.
I usually work close to the boundary between application code, databases, message brokers, deployment pipelines and operations.
Earlier public experience includes work with:
- Kafka, Kubernetes/EKS, Testcontainers and Azure DevOps pipelines
- ASP.NET Core, Vue 3, TypeScript, PostgreSQL and document-management systems
- ASP.NET MVC/Core, WCF, SQL Server, NServiceBus and automated acceptance tests
- IdentityServer, RabbitMQ, Redis, TFS build workflows, WiX installers and technical design documentation