We are looking for a Staff Software Engineer to set the technical direction for our Payments team — a critical engineering domain responsible for building, scaling, and evolving the payments infrastructure that powers every transaction across the Collectors ecosystem.

This team owns the full lifecycle of payment capabilities: integrating with and abstracting across multiple payment gateway providers (including Stripe and PayPal), supporting payment methods spanning credit card, ACH, and digital wallets, and building both the APIs that downstream services depend on and the web application experiences that customers and internal tools rely on.

As a Staff Software Engineer, your influence extends beyond your team to the technology organization. You have expertise in the entirety of the Payments portfolio — how our services interact and how money and data flow between them — and you are building the same understanding of adjacent systems across grading, marketplace, vault, and identity. 

This is a high-impact, high-visibility role. Payments is the financial backbone of our marketplace — touching grading order checkout, vault and consignment transactions, partner payouts, and customer wallet top-ups. You will own architecture decisions, gateway strategy, and the quality bar for everything that ships.

We believe there is significant value in onsite partnership and team collaboration, and candidates within 1-hour commuting distance of the office may be expected to work onsite most of the time. Additional details will be discussed during the recruiting process.

• Own the architecture of the Payments domain end to end: Hold expertise across the entirety of the team's products and services — C#/.NET payment services, the distributed event-driven systems they run on in AWS and Kubernetes, their relational and NoSQL data stores, gateway integrations, and the frontends they serve — including how they interact, how data flows between them, and how they fail. Architect for iterative, autonomous development and future scaling through clean service boundaries, contract design, clear data ownership, and well-sequenced migration paths.
• Set multi-gateway strategy and lead high-stakes migrations: Define the abstractions across payment gateway providers — Stripe, PayPal, and others — so that adding, swapping, or failing over between providers is a low-risk, well-understood operation; own payment flows from initiation through settlement, refund, and reconciliation; and drive gateway migrations, payment-method expansion, and re-platforming efforts with low-risk cutovers under live transaction volume, where correctness of money movement is non-negotiable.
• Set the bar for security, compliance, and resilience: Establish the standards for PCI-DSS practice, tokenization, idempotency, retry and webhook reliability, audit controls, testing strategy, and observability — then use operational data to drive stability and performance improvements, partnering with Security and Compliance to maintain and advance our certifications.
• Lead complex, multi-quarter delivery: Lead projects of moderate-to-significant scope spanning 1–2 quarters, coordinating engineers, stakeholders, and dependencies to a predictable landing; plan using an explicit value-vs-cost framework so urgency and prioritization are easily understood by team and stakeholders alike; and surface blockers and delays to the right people before they become surprises.
• Drive cross-functional execution: Translate business requirements into technical solutions and partner across Payments, Marketplace, Grading, Vault, Finance, Security, and platform teams to deliver seamless payment experiences that connect the Collectors ecosystem — building a working model of adjacent systems, including CRM, identity, and data/ETL, that lets you catch cross-system risks early.
• Multiply the engineers around you: Mentor senior and mid-level engineers through design reviews, pairing, and feedback; foster a culture of knowledge sharing and documentation within your team and with business stakeholders by initiating and facilitating meaningful discussions around complex issues; and build strong relationships with teammates, your manager, Payments' business and Finance stakeholders, and senior engineers across the organization.
• Lead an AI-first approach to building: Establish standards and guardrails for AI coding tools — code review expectations, testing requirements, security and IP hygiene — identify where AI agents accelerate payments work, and raise the org's collective AI fluency by sharing proven workflows and coaching engineers on when the tooling helps and when it misleads.

• 8+ years engineering experience, including demonstrated technical leadership of multi-engineer, multi-quarter projects. You have a track record of designing, shipping, and scaling products with measurable business impact at a high-growth company or a scaled consumer platform.
• Expert-level backend engineering in C# (.NET). You own complex API surfaces, async patterns, and data consistency in distributed systems, and you are recognized by peers and leaders as an authority in your domain.
• Full-stack range. Hands-on production experience across the entire stack — React, Svelte, and TypeScript frontends, API and service layers, data stores, and the infrastructure they run on — with the judgment to design and review at every layer, even where others do the bulk of the implementation.
• Deep payments or fintech expertise. You have owned gateway integrations, idempotency, webhook reliability, tokenization, reconciliation, and PCI compliance in production, and can reason about failure modes where money is at stake.
• Deep database and data-modeling expertise, both relational (e.g. PostgreSQL) and NoSQL (e.g. DynamoDB). Schema design, migrations, query performance, and the realities of shared-database coupling between services.
• Strong distributed-systems fundamentals. Service boundaries, API and contract design, Kafka-based event-driven architectures, messaging, idempotency, and failure handling — designed and operated in production.
• Production AWS and Kubernetes depth, with infrastructure-as-code fluency (CDK and/or Terraform).
• A track record of raising engineering standards across testing strategy, observability, documentation, and incident response.
• Observability-first mindset. You instrument what you ship using Datadog or similar tools, build dashboards and alerting, and use distributed tracing to debug production issues.
• Security-minded. You treat payment security as a first-class engineering concern, not an afterthought, and partner with Security and Compliance to maintain and advance our certifications.
• AI-first engineer. Daily fluency with AI coding assistants and agentic tools (Claude Code, Copilot, Cursor, or similar), experience integrating them into team workflows (CI, code review, documentation), and mature judgment about verification, security, and the limits of AI-generated code.
• Familiar with Agile/Scrum methodologies. You're comfortable working in iterative delivery cycles, participating in sprint planning, and adapting quickly to changing priorities.
• Influential communicator. Excellent written and verbal communication with technical and business audiences alike, with sharp analytical and troubleshooting instincts — you align engineers, product partners, and stakeholders without direct authority, make crisp calls, and bring people with you.
• Bias for ownership. You have an extreme ownership mindset and will wear any hat required to get the job done. You thrive in a fast-moving, self-directed environment — you set the bar, hold it, and take full accountability for outcomes.
• Passion for collecting is a plus.