Don't waste your time; go apply at another company.

They ask for an intense take-home assignment (roughly 10 hours) before chatting with any developers.

During my final interview, I thought I knocked things out of the park on the technical side. I was devastated to get a vague, canned email stating the company did not want to move forward with any positions.

The company will dump you and give zero feedback on how to improve, which is unacceptable since they ask for 20 hours of your time when all is said and done. The company did follow up with a specific rejection reason after I asked for clarification. However, the details were vague and gave no actionable way to improve.

The most disturbing part of the final interview process was the behavioral portion. Maybe the person giving it was having a bad day (I'm not sure). But after making myself vulnerable and sharing a story from my career, I was asked to provide a better example. The person conducting the interview seemed rather keen on getting a specific answer I could not provide.

The interviewer was reluctant to provide more details when I asked for clarification on what they wanted to know concerning their questions. It felt more like I was on trial for being a witch than an engaging behavioral interview. I've done many behavioral interviews over the past decade and never run into a situation like this.

Constructive Criticism:

• If the company is looking for specific niche candidates, then conduct a behavioral interview before asking someone to complete a take-home challenge.
• Not providing detailed feedback post an intense interview process is not appropriate and generally an industry standard. Not doing this will prevent talent from applying, as negative reviews build up and prevent people from re-applying in the future.
• In interviews, don't ask people to define random, obscure programming terms. Focus on questions that prove a higher understanding of coding fundamentals and working in teams.

• Modify the take-home with a code pair.
• Architect out a CRUD app.
• Cliche behavioral interview questions, probably taken off the first Google search result.
• Asked to define some common JavaScript terms like variables, closures, hoisting, etc. (fairly easy).
• Asked to define a bunch of rarely used React-specific terminology questions. Felt more like a pop quiz than an engaging conversation around expertise.