Payment Integration Developers

Payment Integration Developers

Staff Engineer for Bank API and Partner Integrations — Hybrid, San Francisco, United States

Own bank API integrations, consent and token handling, service architecture and production reliability for open-banking payments.

Vacancy details

This is a private vacancy. Company details stay confidential until InVault confirms a serious candidate fit.

Status
Active
Date posted
2026-10-12
Open until
2027-01-10
Employment type
Full-time
Source-listed languages
Not specified
Language requirement
No mandatory language inferred
Work arrangement
Hybrid
Physical workplaces
San Francisco, United States
Applicant eligibility
Applicant geography not specified
Market focus
United States

Overview

Take technical ownership of the API connections that link a bank-payment network with banks, banking technology providers and data aggregators. This staff engineering role covers service architecture, partner integration contracts and production reliability, including the handling of customer consent and access tokens.

Requirements

  • The role typically requires ten or more years developing and operating production software, with staff-level ownership of important systems.
  • Relevant experience includes financial infrastructure, bank or aggregator APIs, distributed systems and Java or a comparable backend language.
  • Daily use of AI coding tools is expected alongside accountable human review.

Responsibilities

  • The initial work requires learning an established codebase and turning that understanding into clear design documents, interface definitions and operating runbooks.
  • Use those foundations to direct improvements, review implementation work and maintain integration testing as the platform evolves.
  • Partner certification and readiness for open-banking requirements form part of the domain.
  • Operational responsibility stays with the engineering team.
  • Own service health, on-call response, incident investigation and fixes that address recurring causes.
  • Strengthen observability and make tradeoffs around consistency, concurrency and idempotency explicit.
  • Work across existing engineering teams to transfer knowledge and help build the group that will maintain the domain over time.

Conditions

  • The position is hybrid in San Francisco, with office attendance Tuesday through Thursday.