It was pretty slow and had to follow up once. You get a call asking for your previous experience. Then you get a phone call for the technical interview. The only problem with me was that I emailed the recruiter if I would be tested in Ruby a week before since I never learned Ruby and then the day of the interview she tells me the interview will only be in Ruby.
Usually SWE roles are common alg and DS questions in any language. Had she gotten back to me I would have brushed up on the language and probably have done better in the interview and not seemed like a fool that didn't know the language completely. The language was easy to pick up during the interview, but I think someone with Ruby experience was chosen over me because I felt like I did well.
Write a super simple blog post in Ruby and HTML that should know about routes and submit button stuff. I had to be walked through it though because I didn't know they would make me program only in Ruby until the day of.
I did well on web development questions or anything that did not have to be coded in Ruby.
The following metrics were computed from 35 interview experiences for the Procore Software Engineer role in United States.
Procore's interview process for their Software Engineer roles in the United States is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Procore's Software Engineer interview process in United States.