
Perforce Software Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 21 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Perforce Software.
Software Engineer
It was a 3 technical round process, but I was only evaluated for one. The interviewer was a bit unprofessional, joining 5 minutes late and then bombarding me with questions without letting me finish. When I asked him to wait, he said we were short on time and had many questions. It felt like he just had to get through his checklist, and not a fair evaluation.
- Can you design a logging system that is scalable?
Software Developer
The whole thing was four parts: first a regular HR chat (30 mins), then a take-home task. After that, they spent 60-90 mins going over the take-home work. The last bit was a final chat with the boss and some team folks. This take-home thing was tough but let you show off good, solid code, way better than those Leetcode style ones. Then came code review and fixing bugs or making the take-home better. It was a good vibe check for the team dynamic, how code reviews work, and if it's a fit. The final interview was about 80% past work and 20% tech stuff, and they were really chill and easy to talk to. The offer and benefits were also really good compared to others. Overall, the process was pretty smooth, and the tasks were medium difficulty. I'd say go for it if you're looking, not much stress involved.
- What motivates your company change?
- What's your self-assessment on x?
- Tell me about difficulties faced in your previous role.
Principal Software Engineer
I applied through a referral. An HR person contacted me and set up the first round with the Hiring Manager. He asked me some questions about how I'd fit in for about 15 minutes and then moved on to technical questions. He gave me some code and asked about a design pattern, and also asked about Caching strategies. I later found out he wasn't in the team I was applying to. I passed that round and moved to Round 2. In the second round, I spoke with a really experienced and humble person. They gave me a backtracking problem, and I struggled and couldn't solve it. Overall, it was a good interview experience and a good learning opportunity.
- Could you solve the backtracking problem I'm about to give you?
Perforce Software Software Engineer Interview Questions
Quoted word for word from Perforce Software interview reports.
“Find the second smallest number.”
Read reports →“What is the distinction between passing by value and passing by reference?”
Read reports →“What is sanity smoke testing?”
Read reports →“What is regression retesting?”
Read reports →“Explain the differences between Linux OS and Windows.”
Read report →“Could you explain closures and promises in Javascript?”
Read report →“Can you design a logging system that is scalable?”
Read report →“Could you solve some JS problems involving arrays and objects without using built-in methods?”
Read report →“What do you know about pillars of OOP?”
Read report →Formats, difficulty and experience
Across all 21 Perforce Software interview reports.