Stripe Software Engineer Interview Experience — Three Parts of a KYC Validation Problem

Stripe·Software Engineer·Aug 2026
Technical Screenmedium

KYC, but verifying things like the company name, URL, abbreviation, and description. The first part was to check whether there was a business name. Skip entries without one. For entries with a name, check whether the remaining columns all have values. If they do, it's verified; otherwise, not verified. The output is verified/not verified and the name, one line at a time in input order. The second part checked two fields. One had a length limit of 5–32 characters, including spaces. The description field had to be checked for keywords, including words and phrases. I initially used str in str directly to get it implemented quickly. If a keyword was present, it was not verified. The third part checked whether at least half the words in the name appeared in another field, something like a nickname. If fewer than half appeared, it was not verified. Suffixes like LLC and Inc. were ignored. I ran out of time and didn't see the fourth part.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Stripe
Role
Software Engineer
Rounds
Technical Screen
Difficulty
medium
Interview date
Aug 2026
Questions from this interview
1 question

Real Stripe interview experiences

First-hand reports from Stripe candidates — the rounds, the questions they were asked, and how it went.

All 49 Stripe interview experiences