Difficulty
Average
Candidate-reported interview insights
Explore commonly reported questions, interview rounds, difficulty, duration, and candidate experiences at 33Across.
Difficulty
Average
Average rounds
2.5
I had a phone call with the head of HR/talent acquisition, which went really well and I felt I made a good impression. The second interview was a video meeting with the hiring manager based in Chicago. Unfortunately, we had terrible connection issues, and the interviewer seemed inexperienced and uninterested, not even looking at the screen, even after the tech problems were fixed. The job description didn't emphasize JavaScript as a major requirement. When I mentioned I didn't have JavaScript experience but was willing to learn, they seemed to lose interest. I never heard back from them and received no feedback, which was quite disappointing.
The first step was an online coding round. After about a week, I found out I passed and they wanted me to come to their New York office. There, I met with two engineers who each gave me a problem to solve, which I managed to do. This part lasted an hour. Following that, I had an hour-long remote interview with another engineer. The final stage was supposed to be with a VP, but due to their absence, it was postponed indefinitely. Despite the unusual ending, the engineers were all very pleasant, making it a positive overall experience for a front-end role where I primarily used Javascript.
I went through 2 interview rounds and chatted with 4 people total. It was a shame because I really liked the company and the job, but they ended up not hiring for the role anymore.
A focused selection of the most detailed candidate-submitted questions.
Practice technical, system design, and behavioral questions with Zitlee.
Interview information is based on candidate reports and may not represent the current official hiring process of 33Across.