Warby Parker Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Warby Parker.
Warby Parker
Software Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Phone screen Technical screen Onsite
Interview formats
Technical Behavioral
The whole process took about a week. I had 2 phone screens and then 2 in person visits. I was juggling two offers so they really rushed things. After my phone screens they had me come in to see 4 different people, each for 30 minutes. They didn't ask me the same questions but it was to see if I would be a good fit. Not many tech questions. There was a test that was super easy if you have basic experience.
Confirmed questions1 question
- What tech publications do you usually read?
Warby Parker
Software Engineer
Senior Average Positive experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral
I was made an offer but declined. Before interviewing, some colleagues warned me about the tech leadership, but I wanted to see for myself since Warby Parker has a good company reputation. I was excited about the people I spoke with. However, one of the heads was surprisingly uninformed and asked rapid-fire questions, boasting about their skills instead of letting me answer. This person seemed out of touch and asked questions they didn't know the answers to. This seemed to be the same person previous employees mentioned in reviews. This experience was the opposite of the general perception of Warby Parker and ultimately led me to decline the offer. It seems like if you don't have to work directly with this person, the engineering role is good, as others enjoyed working with their colleagues and their ability to execute.
Confirmed questions1 question
- I was given a pattern matching exercise and asked some basic questions on data structures and algorithms, which were spread across interviews with different engineers.
Warby Parker
Software Engineer
Entry Difficult Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical
I applied online and a recruiter from Warby Parker reached out through email for a quick chat. We talked about what I was looking for in a role, how much I expected to make, and my timeline. Later on, I had a short 15-minute technical call with one of their engineers. I wasn't completely ready for it, and honestly, the interviewer wasn't the most friendly, seeming a bit cold and distant. When I asked for more details on some questions, they seemed annoyed, which was a bit off-putting. Apart from that interaction, all my other dealings with Warby Parker were great, so maybe it was just a bad day for that particular engineer. It took about two weeks after the technical screen to hear back that I didn't get the job, which happened during the holidays.
Confirmed questions2 questions
- Can you explain the difference between compiled and scripting languages?
- Regarding CSS, what is a pseudo-element and what is its purpose?
Warby Parker Software Engineer Interview Questions
Quoted word for word from Warby Parker interview reports.
“Regarding CSS, what is a pseudo-element and what is its purpose?”
Read reports →“Can you explain the difference between compiled and scripted languages?”
Read reports →“Can you explain the difference between compiled and scripting languages?”
Read reports →“Can you explain what a CSS pseudo element is?”
Read reports →“Could you define what a javascript closure is?”
Read report →“You're given two lists: one of patterns and one of paths separated by slashes. Your task is to determine, for each path, which pattern it best matches. A pattern is a sequence of fields separated by commas. For a pattern to match a path, each field in the pattern must correspond exactly to the field in the path. This also means a pattern and a path must have the same number of fields. Keep in mind that leading and trailing slashes in paths should be disregarded, so `/x/y/` is the same as `x/y`. A special field, a single asterisk (*), acts as a wildcard and can match any string within a path. For instance, the pattern `A,*,B,*,C` has five fields (three strings and two wildcards) and matches paths like `A/foo/B/bar/C` and `A/123/B/456/C`, but not `A/B/C`, `A/foo/bar/B/baz/C`, or `foo/B/bar/C`. What is the time complexity of your algorithm as the number of patterns and paths grows? Would your solution perform well with hundreds of thousands of patterns and paths? Can you think of a more efficient solution?”
Read report →“Can you explain what a REST API is?”
Read report →“Can you explain the differences between cookie, local storage, and session storage?”
Read report →“How would you go about improving webpage performance?”
Read report →Formats, difficulty and experience
Across all 14 Warby Parker interview reports.