Want to know if this job is worth applying to?
Town of Goshen, New York, United States
Hybrid
About Zeta:
Zeta is a globally recognized next-gen banking technology company. Our modern platforms enable financial institutions and fintechs to launch extensible and compliant banking asset and liability products spanning cards, loans, and deposits. Our cloud-native and fully API-enabled stack supports processing, issuing, lending, core banking, fraud, loyalty, digital banking, and agentic AI solutions amongst many other capabilities.
Zeta has 1700+ employees with over 70% in technology roles across locations in the US, Middle East, and Asia - representing one of the largest and most capable teams ever assembled in banking tech. Globally, customers have issued 30M+ cards on Zeta's platform expected to grow to 60M+ in the coming years. Most recently valued at $2B, Zeta counts Softbank, Mastercard, and Optum amongst its investors.
About the Role
Zeta solves hard problems for financial institutions. We assemble solutions from our processing, issuing, payments, lending, core, and digital banking platforms to answer a problem an institution could not solve with what it already owns.
Every processor now says modern, API-first, and cloud-native, so the words no longer separate vendors. Buyers compare proof, and each alternative asks them to accept a compromise: a provider too old to move fast, one too new to trust with credit, or a program that is never really theirs.
This role joins two jobs that are usually split. The first is product: deciding which solutions go to banks, sponsor banks, and fintechs, how they are packaged and priced, and what gets built next. The second is solutions engineering: discovery, target architecture, proofs, and defending the design through architecture, security, and procurement review.
You hold both jobs with equal weight: product owner for a defined portfolio of solutions, and the person who proves them in the room. You own the strategy for your solutions and the case for what the platform builds next, and you keep every deal from becoming a custom build. This is a hands-on, 0 to 1 role with no team at the start but requires mentoring and working teams of engineers and product managers.
Know the Stack
Learn the full Zeta stack hands-on, from issuing across credit, debit, and prepaid to core banking, lending, payments, fraud, and agentic AI end to end
Reach the depth of the teams that build it: modules, APIs, low-code extension points, events, data model, and deployment, each used yourself the way a customer or engineer would
Own the Solution
Set the product strategy for your portfolio: which segments and recurring problems to serve, which solutions to build, and which to refuse or retire
Design the product, not only the architecture, for a named institution: customer, proposition, program structure, economics, compliance model, and operating model, before any integration is written
Settle who carries each obligation in a bank and fintech program (onboarding, underwriting, monitoring, disputes, reporting), in writing a bank's compliance officer will sign
Build the business case beside the technical one: unit economics, fees, reserves, and more
Turn the second and third engagement of the same shape into a packaged solution with a defined scope, price logic, positioning, and launch checklist, then run it with its own roadmap and adoption measures
Close the loop with the market: win and loss reviews, customer discovery, and usage, feeding product requirements and the case to the platform teams for what gets built next
Discovery, Architecture, and Coexistence
Run technical discovery inside large estates and find the problem worth solving
Produce the target architecture and integration design against the institution's existing core, ledger, data, and channel systems, as one proposition across several platforms, with clear scope now and later
Design coexistence and phasing: what moves first, what runs in parallel, what is decommissioned
Design side-by-side, product-by-product conversion paths for programs and banks with an existing book, scoped with delivery teams
Demos and Proofs
Build and maintain demo environments across credit, prepaid, and debit, for new programs and conversions, showing the workflows a customer actually runs
Run proofs of concept and bake-offs against criteria you helped the customer write
Enterprise Evaluation and Oversight
Own technical RFP and RFI responses, security questionnaires, and vendor due diligence
Carry the case through architecture review, security, and procurement
Own the technical answer to sponsor bank oversight: every program visible as it runs, ledger-level access on demand, every action recorded as an event, and complete files in hours.
Market Voice, and Handoff
Act as counterpart to a buyer’s technical leadership through evaluation, integration design, and launch
Build sponsor banks and fintech platforms into repeatable channels
Keep a working analysis of the field by cohort: legacy full-stack, modern words on older cores, newer platforms without a scaled revolving book, and program managers with capital
Work with Marketing on positioning and case studies, and speak at industry forums
What you build and own:
A strategy and roadmap for your solutions portfolio, agreed with the platform roadmap owners and built on win and loss evidence
At least three packaged solutions for recurring institutional problems, each with scope, compliance model, economics, pricing, and launch path written down, and each usable by a seller without you
A demo, reference architecture, and objection log library a new seller can run alone, covering diverse solutions spanning credit, prepaid, and debit
Product requirements traced to named deals, in a form the platform teams can plan against, with proposed roadmap items committed and shipped
At least one banking service provider or sponsor bank partner whose own team can position and demonstrate our capability unaided
What you contribute to:
Qualified institutions reaching technical evaluation, wins in proofs of concept, and new RFP and shortlist inclusion
At least one seven-figure ARR contract, with a technically qualified pipeline behind it
At least one program live on a solution you designed
One conversion of an existing book, from first technical conversation to signed decision
One institutional reference willing to talk to another bank's architects
15+ years across technology and commercial roles, combining more than one of engineering, product, solutions engineering, and customer success, in banking or fintech
Owned a product or solution line across strategy, roadmap, packaging, pricing, and launch
Defined or launched a financial product with a bank, sponsor bank, fintech, or payments company, from compliance review to live customers
Sold or built technology for US banks, credit unions, fintechs, program managers, or sponsor banks, carrying deals through architecture, security, and procurement review, with a working grasp of sponsor bank oversight and third-party risk
Hands-on card issuing and processing, with credit depth strongly preferred: revolving balances, interest and fee logic, delinquency, and the ledger beneath them
Breadth across at least 2 of core, deposits, payments, cards, lending, and digital
Preferred: running a product or solutions function at a sponsor bank, bank-fintech platform, or payments company; core migration in a live institution; a technical degree
Product judgment: decide what to build for one, what to package for many, and what to refuse, and say why to a customer who wants all three
Market sense: turn buyer, competitor, and win and loss evidence into a position, price, and roadmap
Program, compliance, and economics fluency: read a bank-fintech arrangement as a sponsor bank's risk officer does, and design interest, fees, interchange, and reserves into a product that holds up
Technical breadth with depth: command the architecture, APIs, and data model across enough of the stack to assemble one proposition from several platforms
Architectural judgment: design a target state, sequence the path, and defend both live against an institution's architects
Executive presence: brief a bank's board sponsors and a founder's investors in one week, then hold your own with engineers
Ownership: thrive in a 0 to 1 motion with no team at the start, and hold the line with the platform teams by making the case
