• Requirements come from the platform's investor as a business need with no technical design. I turn them into an architecture, then implement, deploy and run it in production myself - the technical decisions, the infrastructure and the on-call are mine.
• The competition platform runs live: load comes in bursts and people follow the results as they happen. When a start-order reservation opened, 184 applications arrived in the first second and the longest wait for an answer was 600 ms.
• Designed the GraphQL layer in Hot Chocolate: persisted operations, operation cache and subscriptions that let people follow results and other events in the system live.
• Migrating the messaging from MassTransit to Wolverine on RabbitMQ over licensing terms, in production and with no downtime.
• Production runs on Docker Swarm on Oracle Cloud. Fixed a corrupted overlay network during a live outage, and moved observability from Aspire Dashboard through SigNoz to OpenObserve, which fits the hardware budget.

C#, ASP.NET Core, Hot Chocolate GraphQL, EF Core, MassTransit → Wolverine, RabbitMQ, PostgreSQL, Redis, Lucene, Quartz · Nuxt 4, TypeScript, UnoCSS · Docker Swarm, Oracle Cloud, Traefik, OpenTelemetry, GitHub Actions

• Every job had to match in CrewCost and in Procore, wherever it was changed. I owned the sync: changes in CrewCost went out to Procore, and changes in Procore came back through webhooks. Idempotent writes and conflict resolution made sure no job was ever created twice. I also designed and built a sync module for third-party integrations, and comments.
• Job-cost reports are where a contractor reads the numbers, and every one has to reconcile with the ledger under it. Built new reports and reworked the existing ones against the ledger.
• Fully remote across a 6-9 hour time-zone gap, in English: a weekly sync, written tickets, the technical design on me.

C#, ASP.NET Core, EF Core, PostgreSQL, Quartz · NUnit, xUnit · Docker, AWS

• Built the integration module that runs user-supplied Python scripts inside a sandbox - untrusted code on shared infrastructure, so isolation and resource limits were the design.
• Audited a Node.js sandbox for user JavaScript: host objects passed into it (console, for one) let a script reach the host environment and compromise the machine it ran on. The findings led to fixes.
• Manual or scheduled configuration sync from another Integray instance.

C#, ASP.NET Core, Node.js, Python, PostgreSQL, Quartz · Angular, TypeScript, CSS · Docker

Go, cobra, gqlparser · GraphQL, OpenAPI v3

Django, PostgreSQL, GraphQL · Nuxt, UnoCSS · Docker