The Knot Worldwide Senior Software Engineer Interview interview questions
based on 1 rating - Updated Nov 17, 2021
Averageinterview difficulty
Very negativeinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
1 interviews
The Knot Worldwide interviews FAQs
Candidates applying for Senior Software Engineer Interview roles take an average of 2 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at The Knot Worldwide overall takes an average of 23 days.
Common stages of the interview process at The Knot Worldwide as a Senior Software Engineer Interview according to 1 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 days. I interviewed at The Knot Worldwide
Interview
I had a similar experience to one of the posts listed previously (and I wish I had read it before I had my interview):
I had an initial call with a Recruiter that went as expected. I was told I would speak to the Director and a newly hired Manager in my next round, and that at The Knot, "they didn't do technical interviews with coding challenges or whiteboarding, and I didn't need to prepare for anything technical." So I came prepared to talk about my current job, tech stack, etc. (Spoiler: I wasn't asked about any of that.)
I don't know if it was the vague, extremely broad architectural back-end questions (that were a bit irrelevant for a Senior Engineer Job if I'm being honest--I would save those types of questions for an Architect position, or even a Managerial one if you're trying to justify the cost of switching your tech stack to shareholders, etc), or if I was caught off guard because I wasn't prepared for a literal oral exam about topics I haven't given much thought to in years, but all-in-all it was an awkward experience where I felt ill-prepared and knew I wouldn't get invited to the next round as such.
The Manager asked mostly React questions that were actually relevant, and treated me like a normal human, so that part of the interview felt aligned to how a technical interview should run. I don't know if the Director was pulled in because the Manager was new, but I honestly don't think it's beneficial to include Directors in the interview process for positions like this--maybe for Managers, but definitely not Individual Contributors. I'm shocked he even had the bandwidth.
I wasn't asked about my current job, my day-to-day, the kinds of projects I work on, examples of problem solving, etc, aside from some behavioral questions meant to determine if I was a "team player" or not. Instead, I felt that the Director made up his mind (negatively) about me from the very beginning.
I'm not sure if TKWW is a misogynistic workplace, but it definitely feels like one. While the interview experience wasn't great and it was a bit of a bummer that I wasn't given another opportunity to prove myself, I'm glad I dodged a bullet if it's a toxic environment.
If I felt unwelcome as a female engineer in the interview process--I can't even imagine what the actual workplace must feel like for female engineers.
Interview questions [1]
Question 1
What are the pros/cons of Node.js?
What can you tell me about RESTful APIs?
Is it the back-end better for image processing or sending messages?