2020 State of the API Report
Who Works with APIs
Primary job function
We asked survey-takers about their primary roles, and it's approximately an even split: about half of respondents considered themselves developers (full stack, backend, frontend, or mobile), and about half have another role within the organization. The most popular role to work with APIs? Full stack developers, accounting for nearly 29% of survey responses.
While there is a wide diversity in the roles that work with APIs, there is one particularly clear concentration: over 77% of respondents listed their functional area as engineering/development. DevOps (26% in 2019)/API Ops (21% in 2019) were listed together in 2020 and combined for 34% in this survey. The developer relations/evangelism functional area nearly doubled in respondents from last year (7.5% in 2019), accounting for 13%. Education, product and project management, and customer relations are among a smaller group of other notable specific areas of work making use of APIs.
We asked individuals about their industry, and the order of the results mirrored the 2019 survey results. Technology led the way at 41.7% (versus 52.3% last year), followed by business/IT Services, banking/finance, healthcare, and retail. Gaming made its debut in this year's survey, at 1.2%.
Years of experience
It’s a young industry—74% of respondents reported between 0 and 5 years of experience with API development. However, a quarter of respondents have 6 or more years of experience. And those respondents with 6+ years of API development experience were significantly more likely to be API-first leaders than those with 0–5 years of experience.
Note: The previous four sections (primary job function, functional area, industry, and years of experience) will be frequently referenced throughout this report, as each one provides uniquely insightful ways to view survey responses.
We asked individuals about the number of people working on their team, and the majority have 10 or fewer on their team. The average team size registered at 13; however, the median was 7, due in part to the impact of some larger organizations.
Within primary job functions, CXO/VP had the highest average number of people on their teams, but technical architects had the highest median, suggesting CXO/VP had more extra-large teams. Within industries, gaming had the highest average number of people on their teams. Within functional areas, developer relations/evangelism had the highest average number of people on their teams. API-first leaders had more people on their team on average than others. Respondents with 6+ years of API development experience had more people on their team on average than those with 0–5 years of experience.
Number of developers in the organization
We found an interesting dichotomy in the number of developers at organizations. Respondents from organizations with 10 or fewer developers were most common, at 28.6%; however, the next largest category—those with 501+ developers—accounted for 19.6% of respondents.
Within primary job functions, DevOps engineer, technical architect, data engineer/scientist, and backend developer were most likely to be part of an organization with more than 500 developers. Within industries, the banking/finance organizations were most likely to employ 501+ developers. Within functional areas, those who identified themselves as engineering development were most likely to be part of an organization with more than 500 developers. API-first leaders were more likely to have 501+ developers in their organization than those rating it a 6 or less.