I cold applied and was contacted by the head of engineering within a few days, which was a good sign to start with. I had a chat with him and then the team's hiring manager for roughly an hour each shortly after that. After that, there were three technical interviews, which were spread across a few days. First was a technical screen, which consisted of solving a fairly practical problem with a few parts that build on each other -- no "gotcha" LeetCode stuff.
The second was a system design interview, where the interviewer described a small hypothetical web application, and you are asked to think through major requirements, data models, components, etc., with questions to dig down from time to time. The third was a code review interview, where you are given a small repository of pre-written code, told the intent of the code, and then asked to go through the code and point out bugs, areas for improvement, etc. There was also an in-real-life meet-and-greet with an engineering manager, paid for by the company.
The following metrics were computed from 1 interview experience for the Secureframe Senior Software Engineer, Rails Web Applications role in United States.
Secureframe's interview process for their Senior Software Engineer, Rails Web Applications roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Secureframe's Senior Software Engineer, Rails Web Applications interview process in United States.