
Thirty Madison Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Thirty Madison.
Software Engineer
Applied online and got a quick response from the recruiter. The initial call covered compensation, the role, and the company. The first tech screen was scheduled, but the overall interview process felt very unorganized. Many interviewers seemed unprepared and disengaged. I advanced to the final virtual onsite rounds, which included four interviews: one for system design, one technical coding interview, one PM interview, and one leadership interview. However, my final tech screen was canceled on the day of the interview. It took about four business days and several follow-up emails with no reply to get it rescheduled. When I finally had the interview, I was forced to use a programming language I'm weakest in, despite my objections. The whole experience felt disrespectful and like a waste of my time.
- System design question about trapping rain water and interacting with a third-party API
- Questions concerning pagination strategies
Software Engineer
I interviewed with Thirty Madison and had a great experience. It started with an HR phone screen which was professional. Then there was a technical interview with the Engineering Manager which was really impressive because he was clearly passionate about the company's mission and vision, and you could tell he's a good leader. After that, I had panel interviews with different team members, which were friendly and professional, and the conversations felt natural. Overall, it was an excellent interview experience with Thirty Madison, showing their dedication and genuine interest in their mission.
- Tell me about your experience working at startups.
Software Engineer
It was a super standard interview process. First, there was a call with a recruiter. Then, a 1-hour technical interview. After that, I had a virtual on-site which consisted of a 1-hour technical interview, a 1-hour System Design interview, a 30-minute Leadership Interview, and finally a 30-minute Behavioral Interview.
- Did you solve any Leetcode easy/medium problems?
- Tell me about a regular system design you have worked on.
- Can you share some regular behavioral questions you have been asked?
Thirty Madison Software Engineer Interview Questions
Quoted word for word from Thirty Madison interview reports.
“Given a number, can you print out how you would "say" it? For example, 1 should be "one" and 101 should be "one hundred and one".”
Read reports →“Could you solve the problem of multiplying two numbers given as strings?”
Read reports →“Can you solve Leetcode Combination Sum #39?”
Read reports →“Can you solve Leetcode Combination Sum #40?”
Read reports →“Solve a LeetCode easy or medium problem.”
Read report →“Why are you interested in Thirty Madison?”
Read report →“How do you approach the relationship and collaboration between development and product management teams?”
Read report →“What makes you want to join Thirty Madison?”
Read report →“Did you solve any Leetcode easy/medium problems?”
Read report →Formats, difficulty and experience
Across all 13 Thirty Madison interview reports.