Finding API Engineers for a Leading FinTech Company

Financial Services

May 13

Request

A San Fransisco-based financial services company focusing on data transfer networks came to Zintro for help getting niche participants for a mission-critical internal project. The company creates APIs that their clients use to connect their own platforms to different financial services platforms, and they couldn’t figure out why some APIs were used heavily while others seemed to be useless to their customer base. They knew customers were getting started but not finishing integrations, and they couldn’t get anyone to tell them why abandonment rates were so high. The company decided to use Zintro to connect with engineers from banks and financial service companies that manage Open Banking API work and integrations at their respective companies. The goal? Find out A) why people were dropping off at such a high rate and B) walk through their API documentation together to uncover potential blockers.

Solution

The Zintro project team was tasked with finding a niche role - engineers that worked on integrations and Open Banking APIs. More specifically, the company wanted to speak with individuals who spent half of their time or more on API and OB work. Zintro would need to identify, screen, and schedule experts on this topic, and fast. Since financial services and technology are two of Zintro’s most served industries, it would be easy for Zintro to pull relevant experts from their extensive network. The hard part would be finding those individuals with the exact focus required by the client.

Results

Following an in depth screening process, Zintro was able to present the company with 39 profiles that fit their particular request. These were engineers and tech leads from banks, investment management companies, stock trading apps, and personal wealth apps. The client decided to interview 18 out of the 39 experts presented and finished the project in seven business days. So, what was the problem? Firstly, they found that people were confused by the API documentation. Secondly, it turned out there was a commonly used 3rd party security system for financial services that was blocking multiple steps from being implemented. However, no error message was shown because of a bug, so engineers were abandoning the process and using alternative options.

By the Numbers