Engineering & Technology
Web API / REST Services
Enterprise API Delivery and Integration
I have delivered full-stack production applications and developed API services that connect applications and support product functionality. My current employment work includes integrating Zendesk help-center documentation and training with internal services that provide custom role-based access, alongside the REST, SOAP, SaaS, and automation experience documented below.
The shared application foundations I built use .NET 10 ASP.NET Core APIs with layered services, repositories, shared libraries, configuration validation, resilient HTTP clients, and trace-correlated errors. Authentication integration, feature management, caching, and configurable telemetry support the broader starter's engineering baseline.
I wired OAuth and OpenID Connect (OIDC) into my starter application using Okta. The QA framework I primarily developed includes isolated OAuth/OIDC validation flows, API mocks, schema validation, reusable test clients, and controlled resource lifecycles.
Defensive API Boundaries
In the marketing-site starter, I implemented a same-origin API proxy between the Next.js client and ASP.NET Core backend. It validates write payloads with Zod, restricts upstream destinations, filters headers, limits request and response sizes, applies timeouts, and returns safe errors with trace correlation.
This foundation makes integration contracts and failure behavior explicit. Unit, client, and browser tests accompany the starter, while the reusable QA framework supports API, browser, data, and container-backed validation across application boundaries.
Read about the marketing API boundary and quality engineering.
RESTful Service Design
API and integration work has been a consistent part of my career across enterprise systems, SaaS solutions, automation, and personal projects. My experience includes RESTful service development, service-to-service integration, and practical API usage in business workflows where reliability and clarity matter more than novelty.
Serverless and Integration Direction
Recent public starter work includes a dedicated C# API starter and a C# Azure Function starter, reflecting my current interest in creating reusable service foundations for teams. In prior work I also delivered integrations using SOAP and REST, including enterprise platform integrations and API-driven automation.
Operational Thinking
My API work is shaped by QA and support experience, so I naturally think about diagnostics, failure modes, testing, and clear operational behavior. The seq-mcp project extends that thinking into AI tooling by exposing a controlled service surface with structured error handling, validation, Docker packaging, and observability-minded usage.