Get customers live, then keep them running.
Enterprise customers connect Banklink to their own finance and operations systems through our API and SDKs, hosted link requests for their customers, scheduled fetches and signed webhooks. Each of those integrations has to go live correctly and keep working when a bank changes something.
You’ll be the customer’s technical contact from the first integration call onwards: scoping the integration with their engineers, running onboarding through to go-live, and staying with the account as its dedicated support contact.
You’ll also be the person who brings what customers run into back to the product, so the next integration is easier than the last.
What you’ll own
- Enterprise integration. Work with each customer’s engineers to map their accounts, banks and data flows onto Banklink. Choose between stored-login link requests and one-off access requests, and design schedules and webhook delivery that fit their systems.
- Post-sales onboarding. Take a new customer from sandbox keys to live traffic: organisation verification, API keys and IP allowlists, webhook signature checks, test runs, and a go-live checklist both sides sign off.
- Ongoing dedicated support. Be the named contact for your accounts. Answer technical questions, investigate failed fetches and missed webhooks using logs and audit trails, and keep the customer informed until the issue is resolved.
- Working examples. Build sample integrations, scripts and walkthroughs in TypeScript or Python that customers can adapt, and keep integration guides and runbooks current.
- Feedback to the product. Write up recurring problems, missing features and documentation gaps with enough detail for engineering to reproduce and act on.
- Careful handling of bank data. Never ask for credentials or keys over email or chat, use the least access you need to help, and treat customer data in logs and tickets with the same care as the platform does.
What you bring
- Experience taking enterprise customers live on an API product. You’ve run technical onboarding or integration projects for B2B software, and can describe one that went wrong and how you recovered it.
- Hands-on with APIs. You can read and write TypeScript or Python, use curl, read HTTP logs, and work through authentication, webhook and retry problems before escalating them.
- Clear writing. Integration guides, incident updates and handover notes that a customer’s engineer or finance lead can act on.
- Composure when something breaks. When a customer’s bank feed stops, you find out what happened, say what you know and what you don’t, and follow through.
- Care with sensitive data. You understand why bank credentials and personal information need careful handling, and know the basics of POPIA.
Experience with South African banks, accounting systems such as Xero or Sage, or financial data integrations would help.
How we’ll work together
You’ll work with the founder and the engineering team. Customers get one accountable person who knows their setup. Reproduce an issue before you escalate it, and confirm the fix with the customer once it ships. Use AI tools where they help; review and verify what you send customers.