RepostedKlaviyo logo

Klaviyo · Phone screen → Onsite

In process

Klaviyo SWE Intern Interview Questions: 15 Experiences

Software engineer · InternshipSep 2023
Shared by

Klaviyo SWE intern reports, 2021–2026: collaborative Python web-app and debugging rounds, a three to 3.5-hour final, plus one AI Engineer Intern update.

At a glance

  • Process: a recruiter screen or OA, a collaborative coding round, then a final of about three to 3.5 hours: two technical sessions (web app, API or debugging in Python with SQL) and a behavioral or manager session (01, 02, 03).
  • Asked recently: web apps, APIs or webhooks in 4 of 5 current SWE reports (Stripe webhooks in 01, a weather API app in 02, API design in 04); debugging with a SQL-injection check (05).
  • Difficulty: interviewers were interactive and did not expect every answer to be right (01); the OA felt LeetCode-like (04).
  • Practise first: Stripe Webhook Debugging, Weather API Application and Flatten JSON to Key-Value Pairs.

Coverage: Klaviyo software engineering, SDE and full-stack internships, Boston where stated: five current reports (Oct 2024 – Mar 2026) and nine older ones in History (2021 – Oct 2023). Plus one AI Engineer Intern update from November 2025, kept separate from the SWE counts.

What came up

Klaviyo's intern loop is practical: extend or fix a small Python web app, often with SQL, while talking it through with an engineer. Counts cover the five current SWE reports.

Topic Reports Last seen
Web apps, APIs or webhooks 4 of 5 Mar 2026 (report date)
Python with SQL or databases 2 of 5 Nov 2024 (report date)
Debugging and code improvement 2 of 5 Feb 2026 (report date)
Behavioral 3 of 5 Feb 2026 (report date)

A candidate can appear in more than one row.

Questions we found

Project Coding

Question Reports Last seen
Create and fix Stripe webhooks 1 Feb 2026 (report date)
Build a weather app using an API, plus frontend code 1 Mar 2026 (report date)
Design APIs in Python 1 Oct 2024 (report date)
Debug a Python program: SQL injection, then further improvements 1 Oct 2024 (report date)

Behavioral (BQ)

Question Reports Last seen
What are you looking for in an internship? 1 Nov 2024 (report date)
Tell me about a time you collaborated 1 Oct 2024 (report date)

6 detailed candidate timelines, loops, and screens

01: Stripe webhooks in a 3.5-hour final

Report date: Feb 12, 2026 · Role: Software Engineer Intern · Result: No offer

  1. Three consecutive interviews, two technical and one behavioral, about 3.5 hours in total.
  2. The coding task: create and fix Stripe webhooks.
  3. Challenging, but the interviewers were interactive and did not expect every answer to be right.

AI 01: AI Engineer Intern: worried about the web-app round

Report date: Nov 17, 2025 · Role: AI Engineer Intern · Status: Final round ahead

  1. Their final was coming up and they were most concerned about its Web App portion; they asked others what to expect. No questions or result were shared.

02: A weather API app and frontend work

Interview date: Sep 2025 · Report date: Mar 17–18, 2026 · Role: Full-stack Software Engineering Intern

  1. A three-hour superday that included building a weather app using an API and writing frontend code. No language or API provider was named.

03: An OA, then a three-hour virtual final

Report date: Nov 21, 2024 · Role: Software Engineer Intern · Result: No offer

  1. An online OA, then a three-hour virtual final: two hours of Python and SQL web development, and a behavioral session that asked what they were looking for in an internship.

04: Python API design after an algorithm-style OA

Report date: Oct 22, 2024 · Role: Software Engineer Intern · Location: Boston · Result: Accepted offer

  1. A LeetCode-like OA, then a final focused on designing APIs in Python, which felt like system design.
  2. A behavioral question about a time they collaborated.

05: Python bugs, SQL injection, then improvements

Report date: Oct 7, 2024 · Role: Software Engineer Intern · Result: No offer

  1. HR reached out; the first interview was debugging a Python program, including whether SQL injection was possible.
  2. After the fixes, the interviewer asked what else they would improve.

History (before November 2023)

These nine reports are more than three years old, so they stay out of the counts and tables above.

06: A collaborative first interview from a career fair

Report date: Oct 30, 2023 · Role: Software Engineer Intern

  1. Found a real-world code sample's bugs and improvements with the interviewer: API calls, HTTP client/server calls and basic SQL. Very collaborative.

07: Pair programming before a three-stage final

Report date: Oct 24, 2023 · Role: Software Engineer Intern

  1. A phone screen, then pair programming with system-design talk and debugging, and a question on optimizing the code. A three-hour, three-stage final was still ahead.

08: A train task, a weather app and JSON recursion, then an offer

Report date: Oct 19–25, 2023 · Role: SWE Intern · Result: Verbal offer

  1. Applied Sep 7; recruiter screen Sep 19; first collaborative coding round Sep 28 on the train problem.
  2. Final (Oct 18): a four-part weather app where finishing every part was not required and communication mattered; recursively flatten JSON into key-value pairs, improved with help, then the reverse conversion; a manager talk on projects, why Klaviyo, and learning something fast.
  3. A verbal offer on Oct 24; under two months in all.

09: Three 30-minute final interviews and an offer

Report date: Nov 15, 2022 · Role: Software Engineering Intern · Result: Offer

  1. Recruiter Oct 17; first interview Oct 21 with Flask and Requests.
  2. Final Nov 9–10, three sessions of about 30 minutes: Flask and Requests again, a medium recursion problem, and a manager talk on projects. Offer Nov 15.

10: Two of four app tasks, then a rejection

Report date: Nov 4, 2022 · Role: SDE Intern · Result: Rejected

  1. Campus recruiting; a straightforward behavioral interview Oct 8; a small Flask, Requests, REST and SQLite program Oct 15.
  2. Final (Oct 21): an app task adding Pony ORM, two of four parts done (the interviewer said most people do not finish); a fairly standard medium recursion problem with test cases and Python questions; and drawing their local architecture, then moving it to AWS with Redis, S3 and an API gateway, likely prompted by cloud certifications on their résumé. Two behavioral questions followed. Rejected about a week later.

11: Three technical sessions in four hours

Report date: Nov 2022 · Role: SWE Intern · Result: Rejected

  1. A campus fair Sep 28, invite Sep 29, interviews Oct 1 and 12, and an automated rejection Oct 14.
  2. About four hours of technical sessions: learning JSON and React-like work on the spot, then breaking down nested JSON with recursion.

12: A small ticket and an offer

Report date: Jan 19, 2022 · Role: Software Engineering Intern · Result: Accepted offer

  1. An intro call, then a technical interview working a small ticket with an engineer.
  2. A final of two technical interviews and a talk with the head engineer, including how they debug broken code.

13: Two API calls and a scaling follow-up

Report date: Nov 2, 2021 · Role: Software Engineer Intern · Result: No offer

  1. Write two API calls and update a database; simple-looking, but the expectations were unclear at first. Follow-up: handling millions of requests.

14: A fast career-fair process

Report date: Oct 21, 2021 · Role: SDE Intern · Result: Offer

  1. Career fair and application Sep 13; invite Sep 16.
  2. Sep 20: a collaborative work simulation, debugging a project and adding features while two engineers watched.
  3. Final Sep 27: an easy-to-medium algorithm question, collaborative coding and behavioral. Offer call Sep 28.

Patterns across the reports

  1. Three-hour finals. 01, 02 and 03 each described a final of three to 3.5 hours.
  2. Web tasks, not puzzles. Stripe webhooks (01), a weather API app (02), API design (04) and debugging a Python program (05).

Common questions

How long is the Klaviyo intern final round?

Three to 3.5 hours in the recent reports (01, 02, 03).

What coding does Klaviyo ask interns?

Practical Python web work: webhooks, an API-backed app, API design and debugging, sometimes with SQL (01–05).

Does Klaviyo expect you to finish every task?

One candidate was told perfect answers were not expected (01).

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.