Product Manager II

Zeta is a next-generation banking technology company providing cloud-native, fully stackable processing and core banking platforms for issuers. With a focus on scalability, compliance, and innovation, Zeta empowers financial institutions to modernize their technology infrastructure and deliver secure, seamless digital banking experiences.

Our impact runs at real-world scale. Today, over 25 million cards are live on Zeta-powered platforms across 7 countries, supported by a passionate team of 1,700+ Zetanauts across India, the US, EMEA, and Asia. Backed by SoftBank Vision Fund, Mastercard, and other reputed strategic investors, we reached a valuation of $2 billion in 2025.

Our focus is on establishing product lines that focus on key outcomes by addressing real customer pain points, modernizing legacy systems, and strengthening core fundamentals. As a result, our systems and platforms support a wide range of banking and payments capabilities, including:

If you would like to learn more about how we have grown and evolved over the years, watch our journey here. You can also explore our website and follow us on LinkedIn, Instagram,YouTube, and X.

 

Zeta is building a new consumer banking product for the US market. The focus is learning fast which features drive adoption, engagement and retention — and building them well.

 

You'll help grow the product through a steady cadence of experiments and feature launches. Each PM owns a business-outcome metric for one area of the product, and the roadmap that moves it. Example areas: onboarding and activation, engagement and retention, revenue, and trust and risk.

We need a hustler. The work will feel like a very early-stage startup: ambiguous problems, incomplete information, shifting priorities and no playbook. You'll bring structure to the chaos: find the answers, make the calls and get things shipped.

We expect PMs to use AI tools across the lifecycle — research, specs, prototyping, analysis — to keep iteration cycles short. PMs here go deep on how things are built, so hands-on software development experience is mandatory.

Own a business-outcome metric for your area, plus the guardrail metrics it must not trade away.

Keep a ranked backlog of experiments and features, prioritised by expected impact (RICE, ICE or similar).

Write each bet as a hypothesis with a primary metric, guardrails and a decision rule, all set before launch.

Match the method to the traffic: A/B tests and holdouts at scale; fake doors, usability tests and cohort analysis at low volume.

Size tests properly, report null and negative results as plainly as wins, and make the ship, iterate or kill call.

Keep a running log of what was tested, what was learned and what changed.

Take features from problem definition through spec, build, QA, launch and adoption.

Write specs engineers can build from: flows, edge cases, failure states, event instrumentation and acceptance criteria.

Work through technical design with engineering — APIs, data models, ledger and payment flows, third-party integrations — and make trade-off calls quickly.

Define output metrics (acquisition, activation, revenue, engagement) and the input metrics that drive them (funnel conversion, feature usage).

Own event instrumentation and data quality for your area.

Do your own analysis in SQL, product analytics tools (such as Mixpanel, Amplitude or MoEngage) and BI tools (such as Metabase or Superset).

Run continuous discovery with US customers through remote interviews, usability tests and surveys.

Turn what you hear and what the data shows into clear problem statements that feed the backlog.

Partner with designers on simple flows that earn users' trust.

Own product copy for your area.

Ship behind feature flags and in stages, with monitoring and a rollback plan.

Work with compliance, risk, banking partners, operations and support so every launch meets regulatory requirements and can be supported from day one.

Statistics and experiment design: hypothesis testing, significance, power and sample sizing, and common traps such as peeking and novelty effects.

Strong SQL, and fluency with product analytics and BI tools.

Ability to work through messy data sets and turn them into decisions.

Engineering fundamentals you still use: reading code, system design, APIs and data models.

A keen eye for design, and strong UX writing.

Clear written and verbal communication — specs and experiment readouts people can act on.

Meticulous program management across parallel workstreams.

Hands-on experience with user research.

6+ years of total experience, including: 3–4 years in product management, with features shipped and measured in production. At least 3 years of hands-on software development, writing and shipping production code as an engineer. This is mandatory.

A track record of experiments that changed a product decision.

Preferred: consumer fintech, payments or banking experience, ideally in the US.

Preferred: B2C products with a growth or experimentation focus.