Product Operations (Shipper)

Job Description

Job Description:\n\nABOUT NYMBUS\nNymbus ( 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.\nNymbus 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.\nWORK ENVIRONMENT:\nWe are a remote first company, with occasional travel required for team collaboration or client engagement.\nPOSITION SUMMARY:\nAt Nymbus, the Product Operations (Shipper) role is the delivery and quality owner in our squad triad model.\nYou 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.\nThis 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."\nTHE SQUAD TRIAD MODEL\nYou operate as one-third of a high-autonomy squad:\nShipper (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.\nBuilder (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.\nArchitect (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.\nTogether, the triad owns outcomes end-to-end — from problem definition through production operation.\nESSENTIAL JOB FUNCTIONS / RESPONSIBILITIES\nQuality Assurance and Validation\n\n Use AI tools (Kiro, Claude) to rapidly generate test cases, edge case scenarios, and validation suites\n Define and own acceptance criteria in partnership with the Builder and Architect\n Design and implement test strategies — automated, property-based, integration, and end-to-end\n Own the quality gate — nothing ships that does not meet the published standard\n Drive test automation as the default — manual testing is the exception, not the norm\n\nRelease Management and Deployment\n\n Own the release process from build artifact through production deployment\n Manage deployment cadence, release coordination, and rollback procedures\n Define and enforce release readiness criteria across the squad\n Monitor deployment health and drive rapid resolution when releases do not perform as expected\n Leverage AI tools to accelerate deployment automation, incident analysis, and release coordination\n\nSquad Collaboration\n\n Partner daily with the Builder on acceptance criteria, testability, and definition of done\n Coordinate with the Architect on deployment architecture, observability, and operational concerns\n Participate directly in technical design discussions with focus on testability and operability\n Surface blockers, risks, and dependencies to the squad early and proactively\n Maintain shared context with squad partners through dashboards, release notes, and quality metrics\n\nDomain Ownership (Fintech Systems)\nApply expertise in one or more domains such as:\n\n Core Banking including account structures, posting models, settlement processes, and data integrity\n Digital Banking including account opening, onboarding workflows, KYC and CIP, and user experience design\n Lending including loan lifecycles, servicing logic, payments, and exception handling\n Payments and Cards including transaction flows, authorization and settlement, and integration patterns\n\nQUALIFICATIONS:\nTechnical Fluency\n\n Strong hands-on capability in test automation, CI/CD pipelines, and deployment tooling\n Ability to own the delivery pipeline end-to-end within a product domain\n Comfort working across the stack to validate behavior at every layer\n Bonus - Understanding of REST APIs, data modeling, and system interactions\n\nAI-First Mindset\n\n Active, hands-on experience with AI-assisted testing and delivery workflows\n Demonstrated use of AI tools for test generation, deployment automation, and incident analysis\n Willingness to experiment with tools and continuously improve AI-augmented delivery practices\n Comfort operating in a spec-first, AI-first development methodology\n\nProduct & Fintech\n\n 5 plus years in delivery, quality engineering, and/or DevOps roles within fintech, banking, or financial services\n Experience working with core banking or digital banking platforms\n Strong understanding of complex, regulated environments and financial workflows\n Proven ability to ship software reliably in high-stakes, correctness-critical systems\n Track record of owning delivery end-to-end, not just executing test scripts\n\nCORE TRAITS\n\n High Agency: Takes ownership of delivery outcomes and drives work forward without waiting for permission or heavy process. Identifies what must ship and makes it happen.\n Problem Solver: Thrives in ambiguity. When something is broken, failing, or unclear, digs in and drives to resolution quickly.\n Shipper Mindset: Measures success by what reaches production and stays healthy. Gets energy from reliable, high-quality releases — not from process for its own sake.\n Experimenter: Tests delivery approaches quickly using AI tools and iterates based on results. Explores automation opportunities before committing to manual processes.\n Quality Driven: Focuses on correctness, reliability, and operational excellence. Treats test suites, deployment pipelines, and monitoring as durable assets.\n Scale Oriented: Designs delivery processes with growing volume, increasing complexity, and operational realities in mind from the start.\n Ownership: Takes pride in production health. Does not hand off after deployment — stays accountable through operational stability.\n\nWHAT WE ARE EXPLICITLY NOT LOOKING FOR\n\n Manual testers who do not automate\n Release coordinators who schedule but do not own quality\n QA professionals who wait for code to be thrown over the wall\n People uncomfortable with ambiguity or cross-functional ownership\n Those unwilling to adopt AI-first delivery practices\n Individuals who view their role as narrowly scoped to testing alone\n\nWHY THIS ROLE MATTERS AT NYMBUS\nNymbus is building the next generation of fintech platforms — and that requires delivery professionals who own the full arc from validation through production health. The AI Product Shipper is the quality backbone of our squad model: the person who ensures everything that ships is correct, reliable, and production-ready, amplified by AI tools and partnered with world-class Builders and Architects.\nThis role sits at the center of our transformation, where AI, delivery excellence, and operational rigor converge to redefine how financial software reaches production.\nBENEFITS:\nABOUT NYMBUS\nNymbus ( 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.\nNymbus is building the next generation of fintech platforms and that requires a new kind of product builder. This role is the engine of the squad — the person who takes product intent and turns it into working software. You will design, specify, and build products using AI-first methodology, working hand-in-hand with your Architect and Shipper to deliver outcomes end-to-end.\nWORK ENVIRONMENT:\nWe are a remote first company, with occasional travel required for team collaboration or client engagement.\nPOSITION SUMMARY:\nAt Nymbus, the AI Product Builder is the primary maker in our squad triad model.\nYou are responsible for transforming product vision into reality. Working within a dedicated squad alongside an Architect (who owns system design and technical integrity) and a Shipper (who owns delivery, quality, and release), you own the build — from specification through implementation. You operate with an AI-first, spec-first mindset, leveraging tools like Kiro and Claude to accelerate every phase of product creation.\nThis is not a traditional developer or product owner role. You are a full-stack product builder who authors specifications, writes code, designs interactions, and iterates rapidly using AI-assisted workflows. You own the "what" and the "how" — translating domain problems into working, shippable software.\nTHE SQUAD TRIAD MODEL\nYou operate as one-third of a high-autonomy squad:\nBuilder (This Role): Owns product intent, specification, and implementation. You are the primary creator — designing system behavior, authoring specs, and iterating with AI tools to produce working software.\nArchitect (Your Partner): Owns system design, technical integrity, and cross-squad consistency. The Architect ensures your solutions are scalable, maintainable, and aligned with platform architecture. You collaborate daily on data models, API contracts, and integration patterns.\nShipper (Your Partner): Owns delivery, quality assurance, release management, and operational readiness. The Shipper ensures what you build meets quality standards, passes validation, and reaches production reliably. You collaborate on acceptance criteria, test coverage, and deployment strategy.\nTogether, the triad owns outcomes end-to-end — from problem definition through production operation.\nESSENTIAL JOB FUNCTIONS / RESPONSIBILITIES\nProduct Design and Specification\n\n Use AI tools (Kiro, Claude) to rapidly iterate on designs, edge cases, and alternative approaches\n Own end-to-end product design from problem definition through system behavior and user experience\n Author clear, testable, implementation-ready specifications using AI-assisted workflows\n Define APIs, data models, and interaction patterns in partnership with the squad Architect\n Translate business requirements and domain knowledge into buildable system specifications\n\nAI-First Building and Implementation\n\n Build working software using AI-assisted development workflows as the primary creation method\n Generate, refine, and implement product and technical specifications using spec-driven development\n Prototype and validate solutions rapidly before committing to full implementation\n Push through ambiguity — when requirements are unclear, explore, propose, and build to learn\n Leverage AI tools as co-developers, not just assistants, to multiply output and quality\n\nSquad Collaboration\n\n Partner daily with the Architect on API design, data modeling, and system architecture decisions\n Coordinate with the Shipper on acceptance criteria, testability, and release readiness\n Participate directly in technical design discussions and tradeoff decisions with the full triad\n Surface blockers, risks, and dependencies to the squad early and proactively\n Maintain shared context with squad partners through specifications, documentation, and working demos\n\nDomain Ownership (Fintech Systems)\nApply expertise in one or more domains such as:\n\n Core Banking including account structures, posting models, settlement processes, and data integrity\n Digital Banking including account opening, onboarding workflows, KYC and CIP, and user experience design\n Lending including loan lifecycles, servicing logic, payments, and exception handling\n Payments and Cards including transaction flows, authorization and settlement, and integration patterns\n\nQUALIFICATIONS:\nProduct & Fintech\n\n 5 plus years in product and/or engineering roles within fintech, banking, or financial services\n Experience working with core banking or digital banking platforms\n Strong understanding of complex, regulated environments and financial workflows\n Proven ability to design and build systems and workflows, not just define requirements\n Track record of shipping working software, not just producing documentation\n\nTechnical Fluency\n\n Strong hands-on development capability across front-end and/or back-end technologies\n Ability to own implementation end-to-end within a product domain\n Comfort working across the stack as needed to deliver complete features\n Bonus - Understanding of REST APIs, data modeling, and system interactions\n\nAI-First Mindset\n\n Active, hands-on experience with AI-assisted development workflows\n Demonstrated use of AI tools for specification, code generation, and iteration\n Willingness to experiment with tools and continuously improve AI-augmented building practices\n Comfort operating in a spec-first, AI-first development methodology\n\nCORE TRAITS\n\n High Agency: Takes ownership of outcomes and drives work forward without waiting for permission or heavy process. Identifies what should be built and builds it.\n Problem Solver: Thrives in ambiguity. Frames problems clearly, explores solution spaces, and converges on practical approaches quickly.\n Builder Mindset: Measures success by what ships. Prefers building and iterating over planning and discussing. Gets energy from creating working software.\n Experimenter: Tests ideas quickly using AI tools and iterates based on results. Explores multiple approaches before committing.\n Quality Driven: Focuses on correctness, clarity, and long-term maintainability. Treats specifications and code as durable assets.\n Scale Oriented: Designs with performance, extensibility, and operational realities in mind from the start.\n Ownership: Takes pride in end-to-end delivery. Does not hand off and walk away — stays accountable through production.\n\nWHAT WE ARE EXPLICITLY NOT LOOKING FOR\n\n Backlog administrators who manage tickets but do not build\n Requirement translators removed from implementation\n Developers who wait for fully specified work before starting\n People uncomfortable with ambiguity or cross-functional ownership\n Those unwilling to adopt AI-first development practices\n Individuals who view their role as narrowly scoped to a single functio