Payroc logo

Payroc Interview Questions
& Process

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

Based on 53 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
56.6% Positive experience

Which role are you interviewing for?

20 roles · 53 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Payroc.

Showing 4 of 53
Payroc logo
Payroc

Employee Relations Specialist

HR · nearly a year ago

Mid Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Group
Interview formats
Behavioral Technical

So the interview process began with Kerry from the HR team, and we talked for about an hour. She mostly asked me scenario-based questions and questions about my past experience. Talking to her got me really excited about the job and the company. After that, I interviewed with the manager, which was pretty similar. The last step was with Angela, who's the Head of HR. That interview was tougher, but I still left feeling interested in the role and the idea of working with the HR team.

Confirmed questions1 question
  • What's motivating your job search?
Payroc logo
Payroc

Software Engineer

Engineering · nearly a year ago

Mid Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Background check Offer
Interview formats
Technical Coding Presentation

It was a very one-sided interview process. The first interview involved a lot of OOP questions, but there wasn't any time left for me to ask questions. They didn't put much effort into getting to know me, and they never explained anything about the company or the role. The whole interview process felt impersonal, with communication only through generic email addresses and no actual person involved. After the first interview, I was given a take-home test to build a Layer 4 Load Balancer. The instructions were only about three sentences long, extremely vague, and I only had 72 hours to complete it. There were no acceptance criteria or specifications provided. After spending a significant amount of time developing my very first Layer 4 Load Balancer, the second interview required me to spend 70 minutes explaining my solution; it didn't seem like they even bothered to read my code. The interviewers didn't even appear knowledgeable about the language the role required (C#), and I had to explain certain language features I used in my solution, which shouldn't have been necessary. And after the audacity of not even reading my code and solely relying on my 70-minute explanation (unlike every other take-home test I've done where they actually read my code beforehand): I still had very little time for my own questions, no explanation of the company or the role, and they had the nerve to reject me afterward without any feedback. When I followed up for feedback, I was told my solution lacked unit tests, even though I was never asked to include any and only had 72 hours to complete the task, so why would I add unit tests??? Absolutely ridiculous. They showed no concern for my time at all. And yet, I still see them hiring for many roles. Please don't waste your time with this company; they're looking for unicorns.

Confirmed questions4 questions
  • Can you tell me about your understanding of OOP concepts?
  • Could you implement a layer 4 load balancer?
  • Can you explain your solution for the Layer 4 Load Balancer?
Payroc logo
Payroc

Test Engineer

Engineering · more than a year ago

Mid Easy Neutral experience No offer 5 rounds
Interview process
Recruiter call Technical screen Take home Presentation Panel
Interview formats
Technical Presentation Behavioral

I applied for the role via a recruitment agency, and the whole interview process took about three weeks. Everyone I spoke with was really nice. It started with a call from the recruiter, followed by interviews with the PayRock team, specifically the QA Manager and an Automation Engineer. After that, I was given an assignment focused on API payment scenarios, which I had to present. The final round involved presenting this assignment to a larger group, including VPS. I felt I did well in all the interviews, but unfortunately, I didn't get the job. I actually enjoyed the overall process, though there was one thing I didn't appreciate. I asked for feedback on why I was rejected, but I never heard back, which was disappointing considering they claim transparency as a core value. I hope they improve on providing feedback in the future.

Confirmed questions3 questions
  • Can you describe test scenarios for payment APIs?
  • Tell me about your past work experiences.
  • How can we improve our processes?
Payroc logo
Payroc

Architect

Engineering · more than a year ago

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

The interview process has two parts. The first part is an hour long and covers your CV and some technical questions about APIs. The second interview is called a Technical Audition and lasts 1.5 hours. You get a short URL problem and have 15 minutes to create architecture diagrams. You have to present them and answer questions. The first interview was well organized, friendly, and open. The second interview was disorganized, the questions were weird and not related to the designs, and they were eating on the call, which wasn't professional. I didn't get a good feeling about it.

Confirmed questions2 questions
  • How would you design a Restful api?
  • Can you explain how you would implement the Tiny url algorithm?

Payroc Interview Questions

Quoted word for word from Payroc interview reports.

Could you explain the difference between HTTP status codes 400 and 500?

Read reports

Can you explain how you would implement the Tiny url algorithm?

Read reports

Could you describe SQL Joins, left joins, inner joins, primary keys, foreign keys, and composite keys?

Read reports

Can you explain abstract methods, abstract classes, polymorphism, and encapsulation?

Read report

How do you stay current with technology news and advancements?

Read report

Formats, difficulty and experience

Across all 53 Payroc interview reports.

Interview formats

Behavioral 44.8%
Technical 29.5%
Presentation 12.4%
Coding 6.7%
Other 2.9%

Interview difficulty

Easy 22.6%
Average 67.9%
Difficult 9.4%

Candidate experience

Positive 56.6%
Negative 28.3%
Neutral 15.1%

Reports by job function

Engineering 17
Sales 17
Marketing 7
Operations 6
HR 3
Other 1