Domain Architect

Codetech•Grand Rapids, MI

About The Position

The Domain Architect owns the technical direction, architecture, and roadmap for the payments domain within Digital’s payment platform. The domain covers payment-related workflows that authorize, adjust, capture, and refund digital orders across credit/debit, EBT SNAP, and EBT WIC. The architect defines domain boundaries, models, shared vocabulary, and contracts, and aligns multiple teams around a consistent architecture. The role designs workflows using Temporal durable workflows, Kafka event streams, and Azure, with a focus on idempotency, recovery, reconciliation, and handling gateway timeouts or partial failures. It establishes standards for workflow versioning, observability, resilience, and PCI-compliant security. This is a hands-on architecture role involving prototyping designs, writing reference implementations, reviewing production code, mentoring senior engineers, and serving as the architecture point of contact for payment processors, benefit providers, and Finance. The architect works with Pricing, Orders Broker, and Order Finalization domains to ensure funds move accurately from checkout to the general ledger.

Requirements

10+ years of engineering experience.
5+ years building payment systems.
Expertise in domain-driven design, including bounded contexts, domain events, and context mapping.
Expert C# and .NET 8+ skills, with an expectation to continue coding.
Production experience with Temporal or a similar durable workflow engine.
Production experience with Kafka.
Experience with Azure PaaS, including App Service, Cosmos DB, APIM, and Key Vault, or similar technology on Google Cloud Platform.
Experience containerizing and running code in Kubernetes.
Production experience with idempotency, saga, and reconciliation patterns.
PCI DSS and tokenization experience.
Experience designing observability using OpenTelemetry or an APM solution.
A track record of aligning multiple teams on a shared architecture.

Nice To Haves

Temporal Nexus or Worker Versioning experience.
EBT SNAP or WIC processing experience.
Digital wallet experience with Apple Pay or Google Pay.
Experience with gateway APIs such as Aurus, Adyen, Fiserv, Worldpay, or Chase.
Experience with network tokens, DPAN, multi-capture, or marketplace split settlement.
Multi-cloud experience with Azure and Google Cloud Platform.
Experience with LaunchDarkly-driven migrations.
Experience with .NET Aspire, Testcontainers, or Mockoon/WireMock.
Experience with retail finance feeds, including TLOG, sales audit, or general ledger.
Grocery or omnichannel retail experience.
Google Cloud Platform experience.

Responsibilities

Own the payments domain architecture, technical roadmap, and key technical decisions.
Define domain boundaries, the domain model, shared vocabulary, and ownership of business operations across services and workflows.
Write architecture review board (ARB)-ready specifications and architecture decision records (ADRs).
Design idempotent and exactly-once operations using patterns such as sagas, compensation, outbox/inbox, and reconciliation.
Define API and event contracts with peer domains using OpenAPI, JSON Schema, and Protobuf.
Establish trust boundaries, including which systems compute or validate data and what consumers can rely on.
Build durable workflows on Temporal, including Nexus cross-domain calls, and set versioning standards for long-running workflows, patching, build IDs, and replay testing.
Design Kafka domain events, schema governance, retries, and dead-letter queues.
Architect payment workflows across the order lifecycle, including create, edit, cancel, finalize, and refund.
Design multi-tender orchestration for credit/debit, EBT SNAP, and EBT WIC, and integrations with payment processors and benefit providers for authorization, capture, void, refund, and reversal.
Handle gateway timeouts and unknown outcomes without double-charging or leaving unresolved charges.
Ensure EBT SNAP and WIC compliance with USDA FNS and state program rules.
Lead PCI DSS scope reduction and define tokenization, encryption, and key-rotation approaches.
Extend the domain to tenders such as Apple Pay, Google Pay, and split tender; support third-party marketplace payments, including multi-capture, over-capture rules, and split settlement.
Partner with Finance on reconciliation, TLOG reporting, and general-ledger accuracy.
Define payment service-level objectives for authorization, capture, refund, and compensation failures.
Build resilience using Polly and Temporal retry policies, and keep payment authorization within checkout timeout budgets across Azure and GCP.
Instrument tracing across HTTP, Kafka, and Temporal with OpenTelemetry.
Set testing strategy for unit, contract, replay, gateway simulation, and load testing.
Review production code, mentor senior engineers, and lead feature-flagged migrations off legacy paths.
Use AI coding agents and context engineering to speed up delivery.
Align multiple teams on a shared architecture and work with Pricing, Orders Broker, Order Finalization, payment processors, benefit providers, and Finance.