
Procore Technologies Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 107 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Procore Technologies.
Software Engineer
Applied in early March, the interview process was lengthy and a bit disorganized. Had an HR screening in mid-May, followed by a coding interview the same week. This coding interview was unexpectedly an OOP pairing session, not just problem-solving as advertised, which was a bit confusing. Then, there was a long silence until mid-July, when I was told the remaining three interviews (backend, values, and hiring manager) would be scheduled. However, only two interviews actually happened, and my follow-up about the missing hiring manager interview was ignored. The backend interview also lacked clear format guidance. After that, another two-month wait, and then in early September, I was informed the position was no longer available. Communication was slow, expectations weren't clear, and some interview stages seemed to be skipped.
- Your task is to implement 5 functions, each with its own unit tests, to find the cheapest available worker who possesses a required skill, given a set of workers each having one or more skills. The Worker class and Skill enumeration are already defined.
- For the backend interview, you'll need to design a database schema for a task management service and then define its API endpoints.
- You'll also be asked about system design concepts, like scalability, reliability, or architecture trade-offs.
Software Engineer
The hiring process began with submitting an online application, which led to a recruiter call. Next, there was an online technical screen conducted by a software engineer. Most of the communication was with the recruiter. The engineer during the tech screen was quite condescending and dominated the conversation. They used unprofessional language like 'sweetie' and spent about 20 minutes of the 40-minute slot explaining the problem, which felt like mansplaining. It was bizarre and obvious that the interviewer might have biases related to gender. After the screen, I reported the interaction to the recruiter. Subsequently, an individual from Procore Technologies in Austin, TX, left a religiously abusive message on a message board I manage, saying, 'Not only do you suck at coding, [negative statement about the spiritual nature of the website].' I strongly suggest the company re-evaluate their staff, as both gender and religious discrimination are illegal. Overall, it strongly suggests a toxic work environment.
- Create the most cost-efficient employee schedule by processing an array of employee data with hourly rates and an array of weekly job openings.
Software Engineer
The interview process was pretty standard, with the recruiters keeping me in the loop and helping me prepare at each stage. It started with a quick chat with the recruiter. Then, there was a coding challenge with another developer. After that, the main interview had four parts: coding in a language I picked, a quick system design discussion, and some behavioral questions. I hit a few snags with the coding challenges; the first one was meant to be collaborative, but the second one wasn't really. The interviewer kept themselves muted the entire time and didn't offer any guidance or even simple acknowledgments. It went so poorly that they kindly offered me another shot. On the next coding challenge, the data input was incorrect, which I didn't notice until I was almost done. I brought it up but probably should have pushed back more. They offered me a role one level lower than what I applied for, likely due to my coding performance. I had another hiring manager chat lined up, but I'd already accepted a competing offer. The recruiters really made the overall experience much better by giving prompt feedback and being supportive when I let them know I was going with another opportunity. John and Matt are amazing! My only suggestion is to really perfect the coding challenge, ensuring the inputs are accurate and the questions are easy to understand. If the core coding challenge isn't collaborative, be upfront about it to set the right expectations.
- What are some basic behavioral questions?
- Tell me about the coding challenge, which was quite different from other companies.
- Can you describe the system design questions?
Procore Technologies Software Engineer Interview Questions
Quoted word for word from Procore Technologies interview reports.
“How can you make combinations of 5 cent and 3 cent stamps to reach a certain value?”
Read reports →“What is the time complexity of your function for iterating over every possible integer?”
Read reports →“Can you write a function to convert a number to its Roman Numeral representation?”
Read reports →“Implement the class functions in a given class skeleton with unit tests, aiming to pass the tests.”
Read reports →“Can you determine if a string has duplicate letters and present three solutions (double for loop, single for loop, hashmap) along with their efficiency differences?”
Read report →“Can you write a function to optimally assign 3 and 5 cent postage to a postage amount above 8 cents?”
Read report →“Can you implement a simple blog using Sinatra that saves user input to a file?”
Read report →“How would you approach creating a Roman numeral converter, for example, converting 19 to XIX?”
Read report →“Create the most cost-efficient employee schedule by processing an array of employee data with hourly rates and an array of weekly job openings.”
Read report →Formats, difficulty and experience
Across all 107 Procore Technologies interview reports.