AI Product Shipper - Payments

Nymbus, Inc.

6d • Remote

About The Position

Nymbus is seeking an AI Product Builder - Payments to define and build the next generation of payment capabilities. This role involves creating sophisticated, extensible payment solutions for financial institutions, translating complex payment domain problems into production-ready software. The individual will design system behavior, author specifications, shape APIs and data models, prototype solutions, and participate in implementation using AI-assisted development workflows. A deep understanding of how money moves through various stages of a transaction, including potential complexities like timeouts, duplicate messages, and exception handling, is crucial. This is a hands-on role focused on product creation and domain building within a squad, not a traditional product owner role. Hands-on software development experience is strongly preferred, or an exceptionally technical payments expert with demonstrated ability to design buildable software systems and work directly with engineers.

Requirements

• Seven or more years of experience building, designing, operating, or leading sophisticated payment systems within fintech, banking, financial services, payment networks, or payment technology.
• Demonstrated experience with payment switches, gateways, orchestration platforms, payment engines, processors, core-payment services, or similarly complex transaction-processing systems.
• Deep understanding of payment lifecycles, including initiation, authorization, clearing, settlement, posting, reconciliation, returns, reversals, rejects, and exception handling.
• Substantial experience with several of the following: ISO 8583, ISO 20022, ACH, wires, RTP, FedNow, payment APIs, card-network processing, settlement, and liquidity management.
• Ability to explain not only how a payment rail works, but how its rules and behavior should be represented in software.
• Experience shipping payment capabilities into production and supporting them through real operational conditions.
• Strong understanding of the correctness, control, security, auditability, and resilience expectations associated with regulated financial systems.
• Ability to reason deeply about software architecture, service interactions, data models, APIs, event flows, transaction boundaries, and distributed-system failure modes.
• Ability to read code, API definitions, database schemas, logs, traces, and payment messages and use them to diagnose system behavior.
• Strong understanding of REST APIs, asynchronous messaging, event-driven systems, data persistence, versioning, authentication, authorization, and integration patterns.
• Working knowledge of distributed-system concepts such as idempotency, ordering, retries, eventual consistency, concurrency, duplicate processing, timeouts, and compensating transactions.
• Proven ability to create system specifications that are technically implementable and operationally complete.
• Hands-on production software-development experience is strongly preferred.
• Candidates without recent hands-on coding experience must demonstrate exceptional technical depth and a history of directly shaping software at the architecture, data-model, API, workflow, and implementation levels.
• Active, hands-on experience using AI-assisted development tools for product design, specification, prototyping, coding, testing, analysis, or technical documentation.
• Demonstrated ability to use AI to accelerate delivery while maintaining strong independent judgment.
• Willingness to experiment continuously with AI-augmented workflows and improve how the squad designs and builds software.
• Comfort working in a spec-first, AI-first development model in which specifications, code, tests, and implementation evolve together.

Nice To Haves

• Direct experience designing or building systems that support multiple payment rails and payment-processing models.
• Experience integrating payment capabilities with core banking platforms, deposit-account systems, posting engines, general ledgers, fraud systems, sanctions screening, or reconciliation platforms.
• Experience with treasury, settlement, intraday liquidity, prefunding, payment limits, or position management.
• Experience completing payment-network certification or onboarding financial institutions to payment rails.
• Experience building high-volume, low-latency, highly available financial systems.
• Experience diagnosing complex payment-production incidents involving multiple systems, networks, or financial institutions.
• Experience designing operational consoles, transaction-repair capabilities, payment investigations, or reconciliation tooling.
• Experience with cloud-native, API-first, event-driven, or microservice-based platforms.

Responsibilities

• Help define and execute the product vision for modern, extensible payment capabilities supporting multiple payment rails.
• Translate payment strategies, client needs, network rules, operational realities, and regulatory constraints into buildable platform capabilities.
• Design payment flows spanning initiation, validation, enrichment, authorization, routing, clearing, settlement, posting, notification, reconciliation, returns, reversals, disputes, and investigations.
• Define common payment concepts and patterns while preserving the scheme-specific behavior required by individual payment networks.
• Design canonical payment models, transaction state machines, message transformations, lifecycle events, and exception taxonomies.
• Make informed product and technical tradeoffs involving speed, cost, finality, liquidity, risk, customer experience, operational complexity, and network availability.
• Develop a cohesive vision for how payment capabilities should work together rather than treating each rail as an isolated integration.
• Build with extensibility in mind so new rails, networks, message versions, clients, and payment use cases can be added without redesigning the underlying capabilities.
• Design and build capabilities for payment initiation, routing, orchestration, message validation, enrichment, transformation, and delivery.
• Define behavior for synchronous and asynchronous payment flows, including long-running and indeterminate transaction states.
• Design controls for idempotency, duplicate detection, sequencing, retries, timeouts, reversals, compensating actions, and replay.
• Define how the platform manages acknowledgments, network responses, status changes, rejects, returns, cancellations, and exception repair.
• Build APIs and event-driven interactions that expose clear, predictable payment behavior to internal and external consumers.
• Ensure payment status and transaction history remain explainable and traceable across services, integrations, and payment rails.
• Design operational tooling that enables support and payment-operations teams to inspect, understand, repair, and resolve transactions safely.
• Apply deep expertise across payment networks, standards, and integration patterns, including ISO 8583, ISO 20022, ACH, wires, RTP, FedNow, payment APIs, card and payment-network flows.
• Help establish repeatable patterns for payment-rail connectivity, message transformation, certification, configuration, and client onboarding.
• Design product behavior supporting settlement positions, funding requirements, prefunding, intraday balances, transaction limits, queues, cutoffs, and liquidity controls.
• Understand the relationship between payment processing, account balances, core posting, general ledger activity, settlement accounts, and reconciliation.
• Define how the platform should behave when funding is insufficient, limits are reached, settlement endpoints are unavailable, or liquidity conditions change.
• Partner with banking, treasury, finance, risk, and operations stakeholders to translate liquidity and settlement requirements into automated platform behavior.
• Provide transparency into current and projected payment positions, queued transactions, settlement obligations, and operational exposure.
• Own end-to-end product design from problem definition through system behavior, implementation, and production validation.
• Author clear, testable, implementation-ready specifications using AI-assisted, spec-driven workflows.
• Create API contracts, event definitions, message maps, state-transition models, sequence diagrams, data models, validation rules, error models, and operational scenarios.
• Define requirements with enough technical and domain precision that they can be implemented and tested without losing critical payment behavior.
• Model both the happy path and the difficult paths, including duplicate messages, late responses, out-of-order events, inconsistent statuses, network outages, timeouts, retries, and manual interventions.
• Prototype and validate solutions before committing to full implementation.
• Push through ambiguity by investigating, proposing, prototyping, and building to learn rather than waiting for complete requirements.
• Use AI-assisted development tools, including Kiro and Claude, as primary components of the product-development workflow.
• Use AI to explore designs, challenge assumptions, identify edge cases, generate specifications, develop prototypes, write and review code, create tests, and accelerate iteration.
• Build reusable domain context, prompts, examples, test fixtures, and specifications that improve the quality of AI-generated outputs.
• Critically evaluate AI-generated designs and code for correctness, security, maintainability, performance, and payment-domain accuracy.
• Participate directly in implementation. Depending on your background, this may include writing production code, modifying services, creating prototypes, reviewing pull requests, inspecting logs and traces, or working alongside engineers at the code level.
• Treat AI as a force multiplier—not as a substitute for payments expertise, technical judgment, or accountability.
• Partner daily with the Architect on system boundaries, API design, data models, event models, resilience patterns, security, and platform architecture.
• Coordinate with the Shipper on acceptance criteria, test strategy, certification requirements, release readiness, observability, rollback approaches, and operational support.
• Participate directly in technical design discussions and make informed tradeoff decisions with the full triad.
• Collaborate with clients, payment operations, compliance, finance, treasury, engineering, and other domain experts without becoming dependent on committee-driven decision-making.
• Surface risks, blockers, assumptions, and cross-squad dependencies early.
• Maintain shared context through specifications, decision records, working software, test scenarios, message examples, and product demonstrations.
• Design payment capabilities for correctness, availability, auditability, security, scalability, and operational resilience.
• Define test scenarios that reflect real payment behavior rather than only validating basic functional requirements.
• Build or help build automated tests for payment state transitions, message transformations, network responses, failure conditions, and exception scenarios.
• Ensure sufficient logging, tracing, metrics, alerting, and transaction-level observability are designed into every capability.
• Participate in diagnosing production issues through transaction traces, payment messages, events, data records, and code.
• Remain accountable after release. You do not hand off a feature and walk away; you stay engaged until the capability works reliably in production.

Benefits

• Annual cash bonus and equity options commensurate with role level and experience
• 100% remote work environment
• 401(k) plan
• Health, dental, and vision insurance
• Paid time off

What This Job Offers

• Job Type: Full-time
• Career Level: Senior
• Education Level: No Education Listed