Thank you for your feedback. We recognize there is always room for growth in how we engage with candidates and your input will help inform the interview training that we provide to our team. We’d also like to take this opportunity to provide some further context on our hiring philosophy and practices. Every role at Instrumental has a defined interview template – which is typically 8-12 pages long – detailing the competencies we’re looking for and the specific interview modules and questions we will ask each candidate. Many templates also include guidance on what kinds of signals we’re looking for in each question – and there is rigorous debate and iteration from team members during the process of the template construction. With that said, our team has made a deliberate decision to deliver early-stage interviews in a conversational style. We find this puts candidates at ease, enabling the interview to feel more like a “get-to-know-you” conversation in both directions. In regard to Instrumental’s technology stack, companies make technology decisions for a variety of reasons. We believe for engineering roles, it’s incredibly important for candidates to be able to ask questions and understand the technology stack we use to ensure it’s aligned with the candidate’s interests or developmental goals. In addition, all candidates have an opportunity at the end of each interview to ask clarification questions— including directly to our CTO & VP of Engineering in onsite stages for engineering positions.

Thank you for your feedback. Instrumental takes all reports of prejudice and unprofessionalism very seriously and we have conducted an internal investigation. While the results of our investigation did not produce any information to substantiate these claims, we welcome any further feedback to be shared directly with people-team@instrumental.com. Regarding the coding assignment, Instrumental strongly believes in building an inclusive interview process. We believe that a work sample is one of the best indicators of performance and we also understand that not all candidates do their best work in a live coding environment. As such, all of our interviews include a module which can be completed asynchronously. Async modules are reviewed by our most senior engineers, all of whom have gone through the same rigorous interview process. Our product is mission-critical for our customers. Subsequently, Instrumental's engineering team has a high bar for deploying code into our production systems. We know that candidates are busy, so we've tried to design fundamentals-focused assignments that can be finished within 1-2 hours in place of a live coding interview, which many candidates have expressed a preference for. Since these assignments are focused on fundamentals, they are not useful for implementation in Instrumental’s product. Instrumental has never and will never use candidates' coding submissions in our product. If candidates have questions or concerns about this in their interview, there is dedicated time to ask questions or seek clarification.