
Payability Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 9 interview experiences · FREE TO READ
Which role are you interviewing for?
7 roles · 9 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Payability.
Python Developer
The interview process was very smooth and pleasant. The people I talked to were nice, and the developers were helpful. They were happy to answer my questions about their own experiences, contributing to a generally good vibe.
- Can you explain what lambda functions are in Python, including their limitations and any instances where you've used them?
Product Manager
The interview process began with a phone interview with a recruiter, followed by a phone interview with the hiring manager. Then, I interviewed with a designer and another PM. The process was paced well, but the team sometimes took two weeks to get back to me about the previous round, and it could take another two weeks to schedule the next interview. After my last interview, there was about a four-week period of no response. I had to reach out, and they mentioned they were finishing up other interviews. Two weeks later, the recruiter emailed to say they had moved on with other candidates. The communication could definitely be better.
- What wireframe tools have you used?
- Can you describe how you would improve onboarding, drawing from your previous role?
BI Analyst
The interview process was quite disappointing. It kicked off with a recruiter call, which was pleasant. After that, I had a technical assessment with the hiring manager, and I passed that without too much trouble. The final round was meant to be four separate meetings with five interviewers in total, but two ended up canceling last minute. One of these calls, with the CTO, ended 13 minutes early because they had another meeting to get to, and I didn't even get to ask any questions. I finished the final round feeling like I wasn't a good fit because I lacked the technical background and experience they were looking for; I get that a startup needs someone who can hit the ground running. However, if their candidate treatment is any clue to how they treat employees, I'm sure there would have been a culture clash too.
- Can you tell me about your experience using Google BigQuery and SQL in a real-world, production setting?
Business Intelligence Product Manager
Had a phone screen first, then met with 4 different people in person, including the co-founder. They asked for some of my work, then there was a super easy SQL/tech skills review over Google Hangouts. Then, a final 'surprise' tech screen with random SQL questions. The whole thing was pretty disorganized, kinda unplanned, and the SQL questions were a joke. No BI visualization questions came up. They didn't give a reason for not hiring me after all that time, just sent a generic email from a no-reply account.
- What should I have asked you that I didn't?
Payability Interview Questions
Quoted word for word from Payability interview reports.
“Can you explain what lambda functions are in Python, including their limitations and any instances where you've used them?”
Read reports →“What wireframe tools have you used?”
Read reports →“What does a successful partnership look like to you?”
Read reports →“What should I have asked you that I didn't?”
Read reports →“Can you tell me about your experience using Google BigQuery and SQL in a real-world, production setting?”
Read report →“Could you outline your process or offer sample recommendations for how you've generated leads for a sales team?”
Read report →“What makes you the best candidate for this role?”
Read report →“Can you describe how you would improve onboarding, drawing from your previous role?”
Read report →“Can you discuss your past work experience?”
Read report →Formats, difficulty and experience
Across all 9 Payability interview reports.