
Discover Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 62 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Discover.
Senior Software Engineer
The interview process was pretty straightforward. It began with an HR call. If your skills and experience aligned with what they were looking for, your application moved to the next stage. This screening round involved a technical manager who asked about Java, Spring Boot, AWS, and Kafka, along with questions about past projects. After that, I scheduled three interviews with senior developers. Two of these involved behavioral questions and some straightforward technical questions, mostly based on my resume. The final interview was a coding round, which for me, turned out to be a system design challenge. I wasn't ready for it, so I didn't get past that one. Overall, it was a good experience; the interviewers were friendly and helpful throughout.
- HR: What tech stacks do you use, and what about relocation, compensation, and sponsorship?
- Dev Round: Questions concerning OOP, SpringBoot, Databases, and AWS.
- Dev Round 2: Primarily behavioral questions about challenging projects, plus some tech questions focused on Java and Spring Boot.
Applications Developer
The interview process was really bad. I had an interview with the tech lead who didn't even turn on his camera, which was pretty rude since he asked me to keep mine on. He asked questions about service configurations in Java and AWS, which felt like a school exam and wasn't what I expected. Then, he asked me to share my screen and open my local IDE to run a program. I wish Discover would invest in tools like Hackensack or Coderpad. The tech lead kept muting himself and stayed off camera, and his voice wasn't clear. It was a terrible experience, and I wouldn't recommend it unless there are no other options.
- Can you detail the new features introduced in Java 8?
- Could you explain the configuration aspects of AWS S3?
Principal Software Engineer
I applied for a job I was qualified for. Recruiter called 3-4 weeks later and set up a 30-min first tech interview. It went well, and they said they'd continue. Then, silence for a week despite my follow-ups. A week later (2 weeks after positive feedback), they said they wanted to move forward but then revealed they wanted to promote internally and the role was closed, offering me a different opening for the same position. Next, I had a 4-hour interview block with 3 managers asking the same behavioral/situational questions. One tech interview involved rapid-fire React and Java questions for an hour, which I handled well. No recruiter follow-up after that. I stopped trying to work with the recruiter and didn't follow up as I had other offers with higher pay. I would have considered it for the benefits, but that wasn't an option.
- How would you approach troubleshooting application slowness, and what steps would you take to enhance page load speeds?
Discover Software Engineer Interview Questions
Quoted word for word from Discover interview reports.
“Regarding memory usage, which occupies more space: static or dynamic variables/methods?”
Read reports →“What does it mean for something to be thread safe?”
Read reports →“Can you calculate a sequence of numbers that go up and then down?”
Read reports →“Can you detail the new features introduced in Java 8?”
Read reports →“Can you explain the difference between monolith and microservices based systems and what are the advantages using microservices?”
Read report →“Is the data structure we discussed thread safe, and what's your reasoning?”
Read report →“Could you explain the configuration aspects of AWS S3?”
Read report →“What steps would you take if a developer rejects a bug you found?”
Read report →“What steps do you take to get code ready for production?”
Read report →Formats, difficulty and experience
Across all 62 Discover interview reports.