Product Operations (Shipper)
Nymbus, Inc.
| Company | Nymbus, Inc. |
| Category | Operations & Admin |
| Location | Remote - United States |
| Remote | Remote |
| Employment | Not stated |
| Level | Not stated |
| Salary | Not stated by the employer |
| Posted | 10 Jul 2026 |
| Last verified | 3 Aug 2026 |
| Source | Employer ATS (greenhouse) |
Description
ABOUT NYMBUS
Nymbus (https://nymbus.com/) is not just a leader in fintech; we are a community of innovators passionate about reimagining banking. Our modern core platform and cloud based technology serve as the backbone for financial institutions eager to modernize and excel.
Nymbus is building the next generation of fintech platforms and that requires a new kind of delivery leader. This role is the quality and release backbone of the squad — the person who ensures what gets built actually reaches production reliably, correctly, and on cadence. You will own delivery, validation, and operational readiness using AI-first methodology, working hand-in-hand with your Builder and Architect to ship outcomes end-to-end.
WORK ENVIRONMENT:
We are a remote first company, with occasional travel required for team collaboration or client engagement.
POSITION SUMMARY:
At Nymbus, the Product Operations (Shipper) role is the delivery and quality owner in our squad triad model.
You are responsible for ensuring working software reaches production reliably and meets the quality bar. Working within a dedicated squad alongside a Builder (who owns product intent, specification, and implementation) and an Architect (who owns system design and technical integrity), you own the ship — from validation through release. You operate with an AI-first mindset, leveraging tools like Kiro and Claude to accelerate testing, quality assurance, and deployment workflows.
This is not a traditional QA or release manager role. You are a full-stack delivery professional who defines acceptance criteria, automates validation, manages releases, monitors production health, and drives operational excellence using AI-assisted workflows. You own the "how it gets to production" and the "how we know it works."
THE SQUAD TRIAD MODEL
You operate as one-third of a high-autonomy squad:
Shipper (This Role): Owns delivery, quality assurance, release management, and operational readiness. You are the person who ensures what gets built meets quality standards, passes validation, and reaches production reliably.
Builder (Your Partner): Owns product intent, specification, and implementation. The Builder is the primary creator — designing system behavior, authoring specs, and iterating with AI tools to produce working software. You collaborate daily on acceptance criteria, testability, and definition of done.
Architect (Your Partner): Owns system design, technical integrity, and cross-squad consistency. The Architect ensures solutions are scalable, maintainable, and aligned with platform architecture. You collaborate on deployment strategy, observability, and operational requirements.
Together, the triad owns outcomes end-to-end — from problem definition through production operation.
ESSENTIAL JOB FUNCTIONS / RESPONSIBILITIES
Quality Assurance and Validation
Use AI tools (Kiro, Claude) to rapidly generate test cases, edge case scenarios, and validation suites
Define and own acceptance criteria in partnership with the Builder and Architect
Design and implement test strategies — automated, property-based, integration, and end-to-end
Own the quality gate — nothing ships that does not meet the published standard
Drive test automation as the default — manual testing is the exception, not the norm
Release Management and Deployment
Own the release process from build artifact through production deployment
Manage deployment cadence, release coordination, and rollback procedures
Define and enforce release readiness criteria across the squad
Monitor deployment health and drive rapid resolution when releases do not perform as expected
Leverage AI tools to accelerate deployment automation, incident analysis, and release coordination
Squad Collaboration
Partner daily with the Builder on acceptance criteria, testability, and definition of done
Coordinate with the Architect on deployment architecture,