Social Tables Interview Questions
& Process

This was a long interview process. It started with 2 phone interviews, each lasting 30-40 minutes. After that, there was an in-office round. This involved about 90 minutes of discussion, split between meeting with 3 directors about the position and then 3 other directors about the company culture. I thought each step went well and I kept pursuing the role, but I guess I was wrong somewhere because I didn't get an offer. It's okay though, life! The office itself was nice and most of the interviewers were friendly. It seems like a pretty young company and a cool, hip place to work. During a walk-around, people were at their desks playing catch and listening to rap music, which was cool. It would have been more upsetting if the pay was good and I didn't get the position.

I applied through a job listing I found on The Muse and heard back within a week about scheduling a call. The first interview was a quick 20-minute chat where we went over my resume, my interest in the role, salary expectations, and some general information. Soon after, I was invited for an in-person interview. This second interview had two parts: the first part was with the hiring managers and the director of the department, focusing on my experience and what the job entails, and the second part was a culture fit interview, mostly about my personality and interests. Make sure you know why you want to join the company, why you'd be great in the role, and be ready to talk about what you do in your free time!

We started with one or two phone screens that checked out basic software engineering skills. The main part of the process was the onsite interviews. These included: - A standard engineering interview round. We talked about Node and other frameworks, networking, and application architecture. It's pretty standard stuff, but they focus less on typical compsci whiteboarding and more on practical skills, which is good for bootcamp grads. - A culture round where you met a panel from different teams. They wanted to see if you'd fit in with everyone. It was relaxed but serious, so just be yourself. - A round where we talked about a project you finished recently. You should be ready to defend your technical choices and explain how your solution worked.

The interview process had 3 parts. First, there was an online coding test. After that, the head engineer screened me. Then, I had an on-site interview that included a code review of a project I built, a software skills interview, and a culture interview. They said I'd hear back in a few days, but after 10 days with no word, I reached out and was told they chose someone else. It was unprofessional not to contact me back. The software people seemed unprepared, asking very basic questions about my project, not the kind of questions I'd expect from future coworkers. It was an interesting company, but they need to improve their professionalism.