We need a senior, payments-literate Business Analyst who can take raw business ideas for our client's payments platform and turn them into analyzed, sized, development-ready work — so the bank's senior engineers can go back to engineering.
Role snapshotTitle: Senior Business Analyst, Payments / API Platform
Product: an API-driven B2B payments platform with a few UIs.
Engagement: Unosquare consultant embedded with the client's agile delivery teams.
Location: Nearshore remote (assumed: Mexico / LatAm), working US Eastern hours.
Seniority: Senior, with 5+ years as a BA. Banking or payments experience is required.
Language: Fluent business English. The role is stakeholder-facing all day.
Headcount: 1 to start. The client mentioned possibly needing "a good analyst or two."
Why the role existsClient has never had a BA function; a handful of senior engineers do the analysis, design, pre-sales, support and coding themselves, and that has become the bottleneck.
- Vague work reaches the teams.
The platform was built by a few highly experienced consultant engineers who could take a one-sentence ask and run with it. Newer engineers can't, so they've been limited to UI work and bug fixes.
- No intake or prioritization process. There's no PMO, so "anybody can ask for anything at any given time." Leadership is building a list of every ask and everything in flight, but items are a mix of features, epics and stories with no consistent definition.
- Current behavior isn't documented. Feature calls get derailed "for the 100th time" rediscovering how things work today, such as roughly 25 permission levers across primary admins, admins and users with entitlements by payment rail. A QA tester is the de facto expert because she had to reverse-engineer it.
- The client model has outgrown the product. Client platform now serves bank clients, vendors, third-party platforms and internal departments (internal teams are onboarded as if they were external clients). Requirements need someon