Technical Product Manager III

Bankjoy is a fintech startup providing modern digital banking products to community banks and credit unions. The Technical Product Manager III will own the vendor integration product area, managing fintech partnerships, technical requirements, roadmaps, documentation, and delivery from vendor evaluation through production. The role also leads cross-functional coordination, technical diligence, prototyping, and tooling automation across payments, cards, identity, data, and document integrations.

Responsibilities:

• Take vendors from first call to production. You'll dig into vendor API packages (Swagger specs, Postman collections, SSO and iFrame guides, certification checklists) before kickoff and find what the docs imply but don't say. You'll run the open-question list with each vendor, hold the line on scope and schedule, and own the pilot client relationship through UAT and go-live
• Write specs engineers love to build from. You'll write clear, readable PRDs and a companion context doc covering vendor requirements, gaps, tech debt, decisions, and open questions. You'll run a readiness check before engineering starts and break epics into small, testable stories that QA can accept with confidence
• Do your own technical diligence. You'll read our .NET backend and Angular frontend to understand how existing integrations work before anything is sized. You'll spot the surprises early, decide what can be reused, and occasionally ship a small change yourself on a branch when that's faster than writing a ticket
• Coordinate across teams. You'll partner with the authentication team on shared SSO code, with the banking core team on the data your vendors depend on, and with core product teams (account opening, lending, PFM) who rely on the vendors you manage
• Document what ships. You'll write product feature specs, vendor implementation guides, and client test guides so our Implementation team can roll out features without you. You'll also draft quarterly release notes for our clients and retire outdated documentation deliberately
• Design without waiting. You'll create first-draft screens in Figma using our design system and hand them to design for review. When a flow needs to be clicked to be understood, you'll build an HTML prototype
• Build your own tooling. We treat repeated PM work as a target for automation. You'll build and maintain AI agent skills that other PMs can use, keep a structured team knowledge base, and choose the simplest tool that gets the job done
• Lead the squad. You'll set priorities with the Tech Lead, sequence the roadmap against client contracts and vendor certification timelines, run sprint planning and backlog grooming, and own the Jira board. When someone asks "is this a bug or a setting?", you'll know the answer quickly
• Payments. Consumer and business bill pay, account-to-account transfers, and peer-to-peer payments, including the user-facing flows, the vendor SSO behind them, and the configuration that enables them for each client
• Cards. Card management and card SSO across the processors and card programs our clients use
• Data and identity. External account linking and aggregation, identity verification, credit score, and payroll and subscription connectivity
• Documents and imaging. eStatement SSO and check-image retrieval across multiple providers
• What comes next. New client contracts bring new vendors every quarter. You'll shape how each one joins the platform

Requirements:

• • 4+ years as a product manager on a B2B platform, with at least 2 years in integrations, payments, or fintech infrastructure
• • You've shipped at least one third-party integration end to end: vendor evaluation, requirements, certification, pilot, and production
• • You write clearly and concisely. Short sentences, active voice, no filler. (We'll ask for a writing sample.)
• • You've managed a vendor relationship where the vendor's process set the schedule
• • You can read C# and TypeScript well enough to trace a code path, spot a missing piece, and estimate a change
• • You're comfortable with git (branches, rebases, diffs, cherry-picks) and can open a PR
• • You understand SSO and API auth patterns in practice: OAuth client credentials, token exchange (RFC 8693), SAML, JWKS, signed URLs, and iframe postMessage
• • You can derive requirements from an OpenAPI spec or Postman collection
• • You know what puts a flow in PCI scope and what doesn't
• • You understand the credit union and community bank buyer. The institution is the client, the account holder is the user, and both need to be happy
• • You record decisions as they happen, with the reasons behind them
• • You ship first drafts fast and iterate in the open
• • You use AI tools daily and can show us a workflow you built, not just a prompt you typed
• • You understand how fintech products plug into a bank: which data comes from the core, which the vendor holds, and where the two disagree. Direct core experience is a plus but not required