AI Product Architect
Nymbus, Inc.
| Company | Nymbus, Inc. |
| Category | Data & Analytics |
| Location | Remote - United States |
| Remote | Remote |
| Employment | Not stated |
| Level | Lead |
| Salary | Not stated by the employer |
| Posted | 21 Jul 2026 |
| Last verified | 7 Aug 2026 |
| Source | Employer ATS (greenhouse) |
Description
Nymbus (https://nymbus.com/) isn’t just a leader in fintech; we’re a community of innovators passionate about reimagining banking. Our award-winning 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 architect. This role is the technical backbone across product squads who ensures what gets built can run safely, securely, and at scale. You will define and enforce design patterns, build foundational technical components, harden solutions for production, and own operational architecture using AI-first methodology, working together with Builders and Shippers to deliver outcomes end-to-end.
WORK ENVIRONMENT:
Nymbus is a remote-first company, with occasional travel required for team collaboration or client engagement. Working hours primarily align with the Eastern Time Zone; candidates located in the Eastern or Central time zones are preferred.
POSITION SUMMARY:
At Nymbus, the AI Product Architect is the system design and technical integrity owner in our squad triad model. You are a member of the Architecture team, report to the Chief AI Officer, and typically split your time product squads.
You are responsible for ensuring solutions meet the enterprise-grade bar. In each squad, you work alongside a dedicated Builder and a Shipper. You own the architecture from system design through production hardening, including the technical deployment and operating model. The Shipper owns release coordination and execution, while you provide required architectural signoff for the areas you own and may hold a release until those standards are met. You operate with an AI-first mindset, leveraging AI-powered tools to accelerate architecture analysis, technical design, implementation, reviews, and operational workflows.
This is not a traditional architect role centered on diagrams, review boards, or governance from a distance. You are a hands-on technical leader who regularly commits production code in the technical layers of the product, including event processing, data access, integration frameworks, observability, and shared services. You create the design and implement the foundational components that Builders use and extend to deliver product functionality. You own the “how it fits”, the “how it scales”, and the “how it runs safely”.
THE SQUAD TRIAD MODEL
You operate as one-third of a high-autonomy squad:
Architect (This Role) : Owns system design, technical integrity, production hardening, and cross-squad consistency. You design and implement foundational technical components, define the technical deployment and operating model, and sign off on release readiness for the areas you own. You may hold a release when architectural, security, performance, or operational requirements have not been met.
Builder (Your Partner) : 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.
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:
Platform Architecture and Foundational Engineering
Define system and reference architectures that align the solutions in each assigned squad with the broader Nymbus platform.
Own integration patterns, API contracts, data models, data flows, tenancy boundaries, and interoperability decisions.
Desi