The Knot Worldwide Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at The Knot Worldwide.
The Knot Worldwide
Software Engineer
Mid Difficult Neutral experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical
The interview process involved a recruiter call, then a chat with the Team Manager. After that, there was a technical interview with some team members. Finally, I had an interview with the Product Owner, Quality, and Design folks. There was some downtime between interviews, and the whole thing took about a month.
Confirmed questions2 questions
- Tell me about your previous experience.
- What are your expectations?
The Knot Worldwide
Software Developer
Entry Easy Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical
I recently had the pleasure of interviewing with [Company Name], and I'm happy to share my experience. From the moment I walked in, I was impressed by the welcoming and professional atmosphere. My interview was one of the best I've had.
Confirmed questions5 questions
- What's your motivation for joining us and what drew you to this role?
- Can you share a key project or accomplishment from your career that showcases your relevant skills and abilities?
- How do you keep up with the latest developments in your field?
The Knot Worldwide
Senior Software Engineer
Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding System Design
So, I got contacted by a recruiter and we had a decent chat for about 45 minutes. After that, she set up an interview with a team lead. I asked if it would be technical and if I needed to prep, but she said it was just an intro and he'd probably just ask about my tech background. Anyway, I interviewed with the EM a few days later. We talked about the job and the company, and he hit me with some basic React questions and then a pretty complex OOP system design question. This was unexpected given what I was told and the fact that we only had 30 mins, and we were already 25 mins in. I think I handled the design question okay considering the time crunch, and he seemed fine with it. But then... nothing. They totally ghosted me, even after I followed up to say thanks and ask for feedback. It's super unprofessional to ghost candidates who take time to interview, but it's unfortunately common in tech. Just a bummer.
Confirmed questions5 questions
- Can you explain what a React component is?
- What distinguishes a class component from a functional component?
- For games like poker and blackjack, what classes and functions would you design to represent a standard 52-card deck, including a shuffle method?
The Knot Worldwide Software Engineer Interview Questions
Quoted word for word from The Knot Worldwide interview reports.
“What distinguishes a class component from a functional component?”
Read reports →“Given 10 tables each needing 10 decks, is it necessary to create every single card object in memory?”
Read reports →“What are the advantages and disadvantages of Node.js?”
Read reports →“For games like poker and blackjack, what classes and functions would you design to represent a standard 52-card deck, including a shuffle method?”
Read reports →“Could you explain what RESTful APIs are?”
Read report →“Can you explain variable hoisting?”
Read report →“Can you explain what a React component is?”
Read report →“Regarding the back-end, is it better suited for image processing or for sending messages?”
Read report →“Could you implement a linked list?”
Read report →Formats, difficulty and experience
Across all 12 The Knot Worldwide interview reports.