
Morning Consult Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 10 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Morning Consult.
Software Engineer
Went through an initial phone screen, then a video call technical test, and finally a 3-4 hour in person interview. It was pretty standard stuff, covering behavioral questions, some background inquiries, and a backend-focused JavaScript teaser. Pretty surprised by how they declined though. I mentioned I'd be open to a less senior role because pay/position isn't my main goal, but they still said I wouldn't be happy in a lesser role. I'd also asked for feedback earlier and didn't get any. They didn't even give me a formal rejection; they just told the recruiter and never spoke to me directly. It was amusing but also frustrating.
No confirmed questions were included in this interview report.
Software Engineer
I first connected with Morning Consult via a recruiting partner who did an initial screen. Then, the interviews started: First, a 45-min Zoom chat with the Engineering Manager, just a casual get-to-know-you about my background and aspirations. Next, a remote technical exercise. They sent the assignment beforehand so I could prep my dev environment. The live coding part lasted about an hour, including intros, coding, and discussing the exercise. After that, I had about 3 hours total of virtual on-sites spread out, talking with different teams about technical and behavioral stuff. It's smart to have examples ready from your past work about tech challenges, how you decide things, any conflicts you've had, and so on, to see if it's a mutual fit. Also a great chance to ask them questions. The whole thing was pretty nice. Everyone was polite and professional. They communicated well and on time. I was juggling interviews with my current job, and they were really flexible with my schedule. From the first contact to getting the offer, it took about a month.
- Tell me about a time you made a change that helped your team.
- Can you share your work history and what your goals are?
- Describe a technical challenge you've encountered.
Software Engineer
The interview process was fair and not excessively long. It began with a phone screen, followed by a meeting with the hiring manager. Subsequently, there was a technical assessment focusing on system design. The process concluded with two one-hour interviews: one delving into my previous work in a technical capacity, and the other being more behavioral.
- Can you share an instance of failure and the lessons you took away from it?
Morning Consult Software Engineer Interview Questions
Quoted word for word from Morning Consult interview reports.
“How could we make the parser more efficient?”
Read reports →“What modifications would be necessary for the parser if the input data's format changed?”
Read reports →“Regarding consuming large data, can you describe why readFileSync() would be used to read it in parts instead of all at once?”
Read reports →“If you had the opportunity to build anything, what would it be?”
Read reports →“Is Golang or JS your preferred language?”
Read report →“Could you tell me about the team's agile practices?”
Read report →“How do you approach making decisions on technical matters?”
Read report →“Can you share an instance of failure and the lessons you took away from it?”
Read report →“How do you determine if this role and company are a good match for you?”
Read report →Formats, difficulty and experience
Across all 10 Morning Consult interview reports.