The Washington Post Fullstack Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at The Washington Post.
The Washington Post
Full Stack Software Engineer
Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Behavioral Technical
I had an interview with two guys, and it was actually a pretty good interview. Very friendly, they asked a set of open ended questions pertaining to my experience. Afterwards I got to ask my questions then I was told I get the next steps in about a week. Three weeks later and I’ve heard nothing from them. I think it’s pretty rude to just blatantly disregard someone applying for a position. Even a generic rejection email would be better than just have someone waiting and continuously looking out for a reply that’s never coming. Which is why even though the actual interview and interviewers were good the process as a whole gets a negative from me.
Confirmed questions1 question
- Describe a situation where you had to compromise your coding standards due to a project deadline.
The Washington Post
Full Stack Engineer
Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Technical Behavioral
So I had a recruiter screen first, then a take-home coding challenge, followed by an in-person technical interview with the dev team, and then a behavioral interview with management. The initial recruiter call was mostly to check if my skills matched the job description. The take-home coding part involved building a REST API app within 48 hours. For the technical interview, we discussed my approach to the coding challenge and my technical expertise relevant to the team. The behavioral interview was about assessing team fit and my motivations. Honestly, the whole process was pretty quick and fair, though challenging. The recruiter screen was surprisingly the hardest part.
Confirmed questions1 question
- Can you share an example of a successful project you worked on and explain how you determined it was a success?
The Washington Post
Full Stack Engineer
Mid Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Onsite Take home
Interview formats
Behavioral Technical Coding
It was a lengthy process, but it's good for meeting potential teammates. There were 4 rounds in total. The first was a phone call with HR to discuss your reasons for applying. The second was a phone call with the Director of Engineering to review your technical skills. The third was a 2-hour video call with the Director of Product and senior engineers to assess team fit. The last round was a take-home exercise that should take about 7-8 hours to complete; you have a week to submit it.
Confirmed questions1 question
- Tell me about your Nodejs experience.
The Washington Post Fullstack Engineer Interview Questions
Quoted word for word from The Washington Post interview reports.
“What's the difference between an id and a class?”
Read reports →“What is the difference between client-side and server-side rendering?”
Read reports →“How would you design an LRU Cache?”
Read reports →“Can you explain Threads?”
Read reports →“Could you explain what MVC backend is?”
Read report →“How would you approach setting up a schema for X?”
Read report →“Describe a situation where you had to compromise your coding standards due to a project deadline.”
Read report →“Tell me about your Nodejs experience.”
Read report →“Can you share an example of a successful project you worked on and explain how you determined it was a success?”
Read report →Formats, difficulty and experience
Across all 5 The Washington Post interview reports.