Clay is an immature engineering organization that is grappling with its identity. Unfortunately, this shows in the interview process.
My perspective is that Clay is trying its best to maintain a very flat organizational structure that allows the CEO to maintain directional control of the company, but this limits opportunities for development. The lack of a strong technical founder also means that engineering is poorly organized. The department skews very junior, and best practices are not adopted. The ethos of the company tries to encourage engineers to be product owners/managers while simultaneously stifling input.
My advice would be to stay away until a major reorganization occurs and several new Heads are instituted.
Pretty standard interview process. Emphasis on coding proficiency, a technical design session, and a behavioral screen.
Following stages:
If I asked your manager, what feedback would they have for you?
The following metrics were computed from 6 interview experiences for the Clay Software Engineer role in United States.
Clay's interview process for their Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for Clay's Software Engineer interview process in United States.