Recharge Payments logo

Recharge Payments Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 7 interview experiences · FREE TO READ

3.7 Rounds average
Easy Typical difficulty
28.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Recharge Payments.

Showing 3 of 7
Recharge Payments logo
Recharge Payments

Senior Software Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical System Design

Had a recruiter call then interviewed with the hiring manager. They didn't ask me anything about my skills for the role, more like they asked questions they were comfortable with from their time as an engineer, which felt tangential to the job and not what I applied for. Then got an email saying they went with other candidates more aligned with the role, even though they told me they were hiring for my skillset. It's weird how they knew I wasn't aligned if they never asked me any role-related questions. Felt pretty biased.

Confirmed questions1 question
  • I was asked a system design question that had nothing to do with my role.
Recharge Payments logo
Recharge Payments

Software Engineer

Engineering · more than a year ago

Senior Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Technical screen
Interview formats
Behavioral Coding Technical Other

The interview process was great. It started with an intro call with the recruiter, then an interview with the Engineering Manager where we discussed general experience and some open-ended questions. After that, I had an onsite interview that included four parts: debugging, coding, product, and pragmatism & scale. Finally, there was an executive interview. Everyone I met was really nice and informative. The recruiters were very helpful in speeding up the process. No crazy or curveball questions were asked. If you're a good engineer and ask good questions, you should do well.

Confirmed questions2 questions
  • Tell me about a time type questions.
  • An easy/medium LeetCode problem was presented.
Recharge Payments logo
Recharge Payments

Software Engineer

Engineering

Mid Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

Had a quick 30 min phone call with an external recruiter that ReCharge uses for screening. It was basic, just going through my résumé and experiences. The call ended with a weird "What's your experience with API's?" after I'd already talked about integrating a SaaS product with dozens of APIs and maintaining one. The phone screen was enough to move on to the next step, a Google Hangout with the hiring manager (Adam). This interview was a disaster. He seemed annoyed from the start. He didn't ask about my experience, but instead asked "What do I like about Python" and "Why do I like Flask?". He then word vomited the tech stack (Flask, MySQL, Redis, Circle CI, GCP) and asked if I had questions. I asked about the SDLC, and all I got was "Agile Scrum". It was clear the hiring process lacked thought. Adam didn't want to converse and lacked enthusiasm. The interview was 20 mins of the 45 scheduled. I knew I wasted my time. The next day I got "Unfortunately, we have decided not to proceed with your candidacy...". Truly unprofessional, unpolished interview. Good Luck!

Confirmed questions3 questions
  • What do you like about Python?
  • What do you like about Flask?
  • What is your testing strategy?

Recharge Payments Software Engineer Interview Questions

Quoted word for word from Recharge Payments interview reports.

Can you tell me about your understanding of our product?

Read report

Can you share an instance where you had to resolve a conflict within your team?

Read report

Formats, difficulty and experience

Across all 7 Recharge Payments interview reports.

Interview formats

Technical 36.8%
Behavioral 21.1%
Coding 21.1%
System Design 15.8%
Other 5.3%

Interview difficulty

Easy 57.1%
Average 42.9%
Difficult 0%

Candidate experience

Negative 57.1%
Positive 28.6%
Neutral 14.3%