Director - Solution Engineering

Zeta

Where
Remote (East Coast)

Posted 2 months ago· Checked live at Zeta 1 hour ago

Stale: open 70 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what Zeta asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Zeta's own hiring page 1 hour ago.
What is the job?
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.
What does it pay?
The posting doesn't say.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

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.

Responsibilities

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

Key Performance Metrics

Experience and Qualifications

  • 12+ 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 lin e 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

Skills

  • 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