Real, anonymous reports from people who interviewed for Software Engineer at Providence, newest first and distilled into what to expect across the loop.
My process with Providence felt a little unstructured. I ended up with three rounds total: two virtual interviews on Teams and then one in-person round at their office. The first two rounds moved along quickly, and I received feedback promptly after each of them, so I felt like I at least had a sense of where I stood.
Providence’s process felt hard partly because it didn’t come with enough information about what they expected from me. I went into the scenario interview without a clear picture of how their internal teams were structured, and that gap showed immediately.
The interview process typically consists of multiple rounds, often starting with an online assessment followed by two to three technical interviews and an HR round. Candidates noted that the structure was generally consistent, although some experienced variations in the number of rounds and the flow of interviews.
Technical interviews often emphasize core computer science concepts, including data structures, algorithms, SQL, and system design, with varying levels of difficulty across rounds. Candidates reported that the technical questions were grounded in their resumes and past projects, requiring them to demonstrate depth of knowledge and problem-solving skills.
Many candidates faced behavioral and managerial questions that assessed their fit within teams and their communication skills, often in a high-pressure context. This part of the interview was sometimes perceived as more challenging than the technical rounds, focusing on situational responses and teamwork dynamics.
Candidates experienced a range of communication styles from the recruitment team, with some reporting prompt feedback after each round, while others faced long periods of silence post-interview. Clear communication about expectations and the role was highlighted as crucial for candidate confidence.
Several candidates emphasized the importance of understanding the company's structure and the specific role requirements to effectively answer scenario-based questions. A lack of context prior to interviews was noted as a significant challenge that impacted performance.
While many candidates found the process structured and professional, there were mixed feelings about the overall experience, especially regarding the length of the process and the final outcomes. Some left feeling that the process was fair, while others felt it was drawn out or unprofessional, particularly in terms of communication and scheduling.