Senior Payments Product Analyst

TEKsystems•Charlotte, NC

1d•$62 - $65•Hybrid

About The Position

The Payments organization is launching a new revenue‑generating product that monetizes how Wells Fargo shares data externally with trusted partners. This product is distinct from traditional payment rails—such as wires or Zelle—and is designed for a small but high‑impact client set, specifically fintechs and data aggregators. This role will operate at the intersection of product, technology, data architecture, and payments, translating conceptual ideas into structured requirements, user stories, and actionable design artifacts. The ideal candidate brings significant experience with modernized financial products, APIs, open banking standards (FDX), and data aggregator use cases.

Requirements

8+ years of experience in payments product analysis, product development, or technical business analysis.
Direct experience supporting or launching a modernized financial product within payments, digital banking, or open banking.
Strong, hands‑on experience writing Jira epics, stories, and technical requirements.
Familiarity with FDX APIs or similar open banking standards.
Strong verbal, written, and presentation communication skills.
Understanding of API architecture, system-of-record interactions, and data flow implications.
Knowledge of financial services, fintech integrations, and data aggregator models.
Ability to think critically and partner closely with technical teams.

Nice To Haves

Background supporting products with external data-sharing use cases (aggregators, fintech connectivity, open banking).
Experience with backend modernization or transaction execution redesign.
Project management skills—planning, status reporting, dependency coordination.
Ability to interpret architecture diagrams and influence future-state data design.

Responsibilities

Transform high-level concepts—currently communicated with limited documentation—into clear, structured user stories, epics, acceptance criteria, workflows, and tangible artifacts.
Define and document how the product will monetize data shared outside the bank, using existing infrastructure with newly introduced “toll gates.”
Break down backend transaction execution paths as systems evolve toward API-driven modernization.
Author technical requirements describing API interactions, system-of-record touchpoints, and expected behaviors for data inflow and outflow.
Collaborate with technology to understand and shape how APIs interact with internal systems.
Apply familiarity with FDX API standards and other open banking frameworks emerging as industry norms.
Evaluate upstream and downstream data flows that influence future-state architecture.
Think critically about how databases are designed and how data architecture choices support the product vision.
Work across a wide variety of enterprise groups—many outside Payments—to coordinate components of the product build.
Partner with technology, data architecture, risk, security, and business teams to ensure alignment.
Provide structured, clear communication to stakeholders at varying technical levels.
Support project tracking and progress updates (PM experience is beneficial).
Understand how data aggregators and fintechs (the product’s primary external users) consume banking data.
Bring experience with linking external financial apps (e.g., Venmo‑style use cases), data-sharing models, and modern API integrations.
Ensure product design aligns with expectations of aggregators and emerging industry interoperability standards.