Product Analyst Internship

Phyllo is a data gateway that allows social data to be accessed from source platforms (e.g. YouTube, Twitch, Upwork, Shopify, etc.). We build the underlying infrastructure that connects with every creator platform, maintain a live data feed to the systems used by these platforms to manage creators' data, and provide a normalized data set so that businesses can use creators' data in a simple yet impactful way.

Website: https://www.getphyllo.com/

As a Product Analyst Intern, you'll sit close to the product team and spend a lot of your time inside our APIs — calling endpoints, inspecting payloads, comparing what we return against what the source platform actually shows, and flagging anything that doesn't add up. You'll turn those findings into clear, actionable inputs for PMs and engineers. This is a hands-on role. You won't be writing strategy decks in week one. You'll be testing, digging, documenting, and building the kind of product instinct that only comes from touching the actual product every day.

• →API understanding and testing (core of the role)
• →Build a solid working knowledge of Phyllo's API suite — what each endpoint does, what data it returns, and which use cases it powers
• →Test endpoints hands-on using Postman — create and maintain collections and environments, chain requests, set up variables, and write basic test scripts
• →Validate request and response behavior: status codes, error messages, required and optional fields, pagination, rate limits, webhooks, and auth flows
• →Write lightweight scripts (Python or JavaScript) to run repeatable checks across platforms, compare responses over time, and catch regressions or missing data at scale
• →Run data quality investigations — when a follower count, engagement metric, or content record doesn't match the source platform, figure out where the gap comes from
• →Support pre-release sanity checks and QA before features go live Product analysis and support
• →Read our API documentation critically and flag mismatches between what's documented and how the API actually behaves
• →Write clear bug reports and tickets in Jira with reproduction steps, sample requests, and expected vs. actual responses
• →Reproduce and triage issues reported by customer-facing teams, and help narrow down root causes
• →Pull and analyze usage data to answer questions like which endpoints are used most, where errors cluster, and which platforms are least reliable
• →Run competitive and benchmarking analysis on other creator-data and API providers
• →Help maintain internal documentation, release notes, and changelogs

• We're hiring for aptitude, not experience. If you're early in your career and these describe you,
  apply.
• Final-year student or recent graduate in any discipline — Computer Science, IT, Engineering, Statistics, or Economics backgrounds tend to ramp fastest, but a strong generalist works too
• A real understanding of how APIs and the web work: HTTP methods, status codes, JSON, headers, query parameters, authentication tokens, and webhooks. You should be able to explain what a 401 means and why it's different from a 403
• Comfortable with Postman (or able to get comfortable fast) — you've hit an API, read a response, and figured out what went wrong
• Basic scripting ability in Python or JavaScript — enough to loop through a list of IDs, hit an endpoint, and dump the results somewhere useful
• Working knowledge of spreadsheets; familiarity with SQL is a strong plus
• Attention to detail. A lot of this job is noticing that one field is null when it shouldn't be
• Clear written communication — you can describe a bug precisely enough that an engineer can fix it without a follow-up call
• Structured thinking and genuine curiosity: you ask "why is this happening" before you ask "what should I do"
• Ownership and follow-through. You'll be given loosely defined problems and trusted to come back with answers
• Comfort with ambiguity and a habit of asking questions early rather than guessing quietly
• Available to work full-time for the internship duration

• You've built or shipped something that consumed a third-party API — a side project, hackathon build, or college project all count
• Familiarity with Jira, Swagger/OpenAPI, or API monitoring tools
• Exposure to SQL, Metabase, Looker, or similar analytics tools
• Genuine interest in the creator economy, social platforms, or influencer marketing
• You've written technical documentation before, even informally