[Hiring] Senior API Data Analyst @impact.com

Role Description

The API Analyst keeps a company-wide picture of how our APIs are used, what they cost, and where integrations go wrong, and turns that picture into a weekly operating loop. You work where the public API meets the systems behind it. The teams that own each API own its behaviour, its caching, and how large a customer's limit should be. Gateway and platform engineers own how those limits are enforced. This role supplies the evidence, the automation, and the weekly pressure those decisions need.

Day to day you live in request logs, latency and row-volume signals, rate-limit behaviour, and partner usage patterns. You automate the checks that turn a one-off investigation into a continuous view of API health. Each week you work that view: catch misuse and bad integration patterns, name APIs that should be retired or capped, triage alerts, and hand the owning team a record they can act on.

When a problem sits in one integration, you help shape a proportionate response so the platform stays stable and everyone else's access stays usable. You also help say what good looks like for customers.

What You'll Do

• Run API usage as an operating loop
  • Build a continuous picture of how our APIs are actually used: who is calling what, at what volume, with which date ranges, paging patterns, concurrency, and how widely a single integrator's traffic is spread.
  • Detect and explain fan-out risk: traffic that looks fine for one account but becomes a platform incident when a partner spreads load across many accounts at once.
  • Each week, work the API usage record. Identify misuse, bad integrations, spikes, and APIs that should be retired or capped. Triage the alerts. Keep a living history so the next incident starts from evidence.
  • Separate expensive work from cheap work: understand when a long-running call was waiting in a queue versus actually heavy, and when a wide date range costs more or less than many narrow ones.
  • Hand the owning teams the metrics they use to choose caching, rate-limit sizes, date-range caps, and concurrency. Stay with them until the evidence is understood.
• Turn observability into evidence for guardrails
  • Automate analysis across log search, data warehouses, and reporting tools: recurring checks, red flags, and briefings that surface bad patterns early, including with AI-assisted triage where it earns its keep.
  • Propose concrete limits grounded in real usage plus room to grow: short bursts, sustained rates, and a ceiling across an integrator's full footprint.
  • Partner with gateway and platform engineers on how rate limits, access tokens, and HTTP 429 responses enforce the limits those teams have set.
  • Recommend patterns such as date-range caps, concurrency limits, synchronous versus asynchronous versus streaming delivery, and limited-scope credentials.
• Raise the bar on integration patterns and the customer story
  • Study how large partners and peers integrate, including synchronous, asynchronous, streaming, and bulk export, and how they cap concurrency.
  • Work with partnership and product colleagues on strategic and enterprise partners so proposals for rates, spare capacity, and migration reflect platform cost and risk as well as the commercial goal.
  • Help define what good looks like for third-party integrators, so we can set expectations in the contract.
  • Turn what we learn from early partners into playbooks for the next integrator: clearer categories, clearer ceilings, better documentation, cleaner onboarding.
• Hold one company-level view
  • Connect what the teams that build APIs, analyse usage, and run the gateway each see into one company-level view of API health.
  • Hold the tension between protecting the platform and letting customers run their businesses on our APIs.
  • Champion changes that improve both platform health and the client experience.
  • Apply the same observability to newer API surfaces, including APIs built for automated clients.

Qualifications

• Senior analytical profile.
• Several years in a role that mixes data analysis, platform or API observability, and operational triage.
• Observability and log analysis.
• Statistics and quantitative judgement.
• Automation and engineering depth.
• A weekly operating habit.
• API and integration literacy.
• Judgement.
• Clear communication.

Requirements

• Hands-on experience with API gateways, rate-limit buckets, and token scoping.
• Familiarity with warehouses and analytical tools used for traffic analytics.
• Experience supporting large business-to-business or partner API programmes.
• Exposure to query-cost or resource-based measures of API work.
• Interest in APIs built for automated clients.

Benefits

• Flexible Working: Responsible PTO policy for time off.
• Health and Wellness: Up to 12 fully covered therapy/coaching sessions per year and monthly gym reimbursement.
• A Stake in Our Growth: Restricted Stock Units (RSUs) with a 3-year vesting schedule.
• Investing in Your Growth: Free Coursera subscription and PXA courses.
• Parental Support: 26 weeks of fully paid leave for the primary caregiver and 13 weeks for the secondary caregiver.
• Technology Financial Support: Technology stipend and monthly internet allowance.