TixelJobs
N
Nymbusincvia Greenhouse

Product Lead, AI (Builder)

REMOTEPosted 1d ago
OtherLeadFull-time#remote

Not sure if you're a good fit?

Upload your resume and TixelJobs AI will compare it against Product Lead, AI (Builder) at Nymbusinc. Get a match score, missing keywords, and improvement tips before you apply.

Free preview · Your resume stays private

About the Role

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 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.

WORK ENVIRONMENT:

We are a remote first company, with occasional travel required for team collaboration or client engagement.

POSITION SUMMARY:

At Nymbus, the Product Lead, AI (Builder) is the primary maker in our squad triad model.

You 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.

This is not a traditional product owner or product management role. You bring your own experience, research, and creativity to design products end-to-end, authoring specifications, shaping system behavior, and iterating rapidly using AI-assisted workflows. You own the "what" and the "how," translating domain problems into working, shippable software.

THE SQUAD TRIAD MODEL

You operate as one-third of a high-autonomy squad:

Builder (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. Deep domain knowledge is a plus; the ability to acquire it quickly is a must.

Architect (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.

Shipper (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.

Together, the triad owns outcomes end-to-end — from problem definition through production operation.

ESSENTIAL JOB FUNCTIONS / RESPONSIBILITIES

Product Design and Specification

  • Use AI tools (Kiro, Claude) to rapidly iterate on designs, edge cases, and alternative approaches
  • Own end-to-end product design from problem definition through system behavior and user experience
  • Author clear, testable, implementation-ready specifications using AI-assisted workflows
  • Define APIs, data models, and interaction patterns in partnership with the squad Architect
  • Translate business requirements and domain knowledge into buildable system specifications

AI-First Building and Implementation

  • Build working software using AI-assisted development workflows as the primary creation method
  • Generate, refine, and implement product and technical specifications using spec-driven development
  • Prototype and validate solutions rapidly before committing to full implementation
  • Push through ambiguity — when requirements are unclear, explore, propose, and build to learn
  • Leverage AI tools as co-developers, not just assistants, to multiply output and quality

Squad Collaboration

  • Partner daily with the Architect on API design, data modeling, and system architecture decisions
  • Coordinate with the Shipper on acceptance criteria, testability, and release readiness
  • Participate directly in technical design discussions and tradeoff decisions with the full triad
  • Surface blockers, risks, and dependencies to the squad early and proactively
  • Maintain shared context with squad partners through specifications, documentation, and working demos

Domain Ownership (Fintech Systems)

Apply expertise in one or more domains such as:

  • Core Banking including account structures, posting models, settlement processes, and data integrity
  • Digital Banking including online banking, mobile banking, user experience design, and self-service capabilities
  • Origination including account opening, onboarding workflows, KYC/CIP, and application decisioning
  • Lending including loan lifecycles, servicing logic, payments, and exception handling
  • Payments and Cards including transaction flows, authorization and settlement, and integration patterns
  • You don't need to be the deepest domain expert. You need enough context to ask the right questions, recognize bad answers, and translate domain problems into buildable specifications."

QUALIFICATIONS:

Product & Fintech

  • 5 plus years in product and/or engineering roles within fintech, banking, or financial services
  • Experience working with core banking or digital banking platforms
  • Strong understanding of complex, regulated environments and financial workflows
  • Proven ability to design and build systems and workflows, not just define requirements
  • Track record of shipping working software, not just producing documentation

Technical Fluency

  • Strong hands-on development capability across front-end and/or back-end technologies
  • Ability to own implementation end-to-end within a product domain
  • Comfort working across the stack as needed to deliver complete features
  • Plus - Understanding of REST APIs, data modeling, and system interactions
  • Plus - Familiarity with  Node.js, Prisma, Redis, Kafka/SQS, AWS deployment

AI-First Mindset

  • Active, hands-on experience with AI-assisted development workflows
  • Demonstrated use of AI tools for specification, code generation, and iteration
  • Willingness to experiment with tools and continuously improve AI-augmented building practices
  • Comfort operating in a spec-first, AI-first development methodology

CORE TRAITS

  • 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.
  • Problem Solver: Thrives in ambiguity. Frames problems clearly, explores solution spaces, and converges on practical approaches quickly.
  • Builder Mindset: Measures success by what ships. Prefers building and iterating over planning and discussing. Gets energy from creating working software.
  • Experimenter: Tests ideas quickly using AI tools and iterates based on results. Explores multiple approaches before committing.
  • Quality Driven: Focuses on correctness, clarity, and long-term maintainability. Treats specifications and code as durable assets.
  • Scale Oriented: Designs with performance, extensibility, and operational realities in mind from the start.
  • Ownership: Takes pride in end-to-end delivery. Does not hand off and walk away — stays accountable through production.

THIS ROLE ISN’T FOR:

  • Backlog administrators who manage tickets but do not build
  • Requirements writers who stay removed from how solutions get implemented
  • Developers who wait for fully specified work before starting
  • Individuals uncomfortable with ambiguity, cross-functional ownership, or AI-first workflows
  • Narrowly-scoped specialists who prefer staying in a single function

WHY THIS ROLE MATTERS AT NYMBUS

You won't spend months convincing leadership to let you use AI tools. Here, AI-first is the methodology, not an experiment. You won't wait for a committee to approve your direction. Three-person squads own thei

Share