Ironclad runs a slightly involved interview loop, even by Silicon Valley standards. A recruiter reaches out to you for a call. If that screen goes well, you get introduced to the Hiring Manager. If that’s promising, then there’s a technical screen. The technical screen is a standard coding question but note that Ironclad tries to do everything in Typescript, which is an interesting choice. This means that your interviewer may be rusty at other languages. I don’t recommend programming in Typescript if you’re not familiar with it, but be prepared to explain what you’re doing. The next set of interviews is a panel, where your first meeting is actually an Ironclad demo. That is, they demo Ironclad to you. I actually thought this was a great way to provide context, since Ironclad is a pretty niche product and it’s unlikely that you’ve used a Contract Lifecycle Management (CLM) system before. I thought it was insightful to see what the user experience is like, and also to experience the app’s performance. The panel will involve a behavioral interview, which was very standard. It also has a Systems Design interview, which was also pretty standard. The twist on the panel will be the Technical Project, where you get 1.5 hours to implement a simple product. I don’t think it’s possible to finish it, so you should probably sketch out the major components and then fill in the important details until you run out of time. You’ll then spend some time with an interviewer describing your solution and answering questions about it.

On site had two technical interview and a couple non-technical sessions. There was one system design and one coding challenge. This was a while ago so it may be different now