Ho sostenuto un colloquio presso Stepful (New York, NY) nel mese di ago 2025
Colloquio
30min HR interview
30min Interview with Tech Leadership
Take home test. Build a Rails app with a Javascript front end that let's users take quizzes
System Design for Ticketmaster
30min interview with Product Designer
Build a terminal based version of Tetris
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 2 mesi. Ho sostenuto un colloquio presso Stepful
Colloquio
1. Recruiter Call
2. Take home assignment. Full CRUD app where you have to build a calendar where you book / schedule meetings for coaches. Takes days to complete even though they say it takes 3 hours. Horrible assignment.
3. Review the CRUD app with a team member. You have to do everything in the assignment because the whole purpose of the call is to go over your completeness on it. Even though on the assignment they say to not go over the expected time limits. Then they will ask you about how you can prevent a ridiculous edge case of many users at the same time
4. System design interview. Design ticketmaster. Not easy.
5. Onsite. Code a CLI application (tetris game). You are forced to provide a starter for the cli app, essentially a take home project. The task to provide a CLI starter was given to me the night before so i had to rush to put one together.
6. Meet with a growth officer, half hour. Waste of time meeting where he asks you about which of the 4 company "values" represents you the most
7. Meet with a product team member where she grills you on how to convert users and gauge success. Team member was condescending and pompous.
8. Meet with CTO to just talk tech.
I was rejected even though I thought I did extremely well overall, especially on the technical side. I was rejected with the citation of "cultural mismatch" which was incredibly disrespectful and deflating. They wasted a month and a half of my time. Do not waste your time interviewing for this company.
Domande di colloquio [2]
Domanda 1
System Design Interview
Build a ticketing app like Ticketmaster
Pretend for a second that you’re my tech lead. We’re working together on a project to design a ticketing application like Ticketmaster from scratch, and you’re leading its design. How would you design this application and communicate its design to me?
To start, let’s skip search, user signup, etc. We have a logged in user, who is on a page for an event. The user should be shown ticket options, be able to select one or more tickets, and make a purchase. For example, an event page could look like this:
Dua Lipa Concert (2020-08-17 10:00 AM PST)
---
General Admission Ticket — 83 available
Premium Booth Ticket — 11 available
Or this:
Phantom of the Opera (2020-07-28 7:00 PM PST)
---
Section 1A - Standard Ticket — 25 available
Section 2A - Standard Ticket — Sold out
Talk through or write down how you think the application flow, data models, and APIs should look like.
What does the happy path look like?
What are some possible failure cases?
Can your design support both general admission (ie. a pool of identical tickets) and assigned seats (specific set of tickets where each is different)?
