Discover logo

Discover Field / Application Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 25 interview experiences · FREE TO READ

3.8 Rounds average
Average Typical difficulty
48% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Discover.

Showing 3 of 25
Discover logo
Discover

Applications Engineer

Engineering · a year ago

Mid Easy Negative experience No offer 5 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Technical screen
Interview formats
Technical System Design

It started with a technical round, and if I did well, there were four more. I ended up doing all five rounds. I answered everything about technical concepts and system design. The last round with a senior manager was a complete waste of time; they were rude and asked irrelevant personal questions. I got rejected because they said my experience and tech expertise were better suited for a senior applications engineer role. It felt like a waste of time after going through five rounds.

Confirmed questions2 questions
  • Can you explain in detail how indexing works?
  • Describe how you would design an e-commerce application and scale it.
Discover logo
Discover

Application Engineer

Engineering · more than a year ago

Entry Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding System Design Behavioral

I applied via LinkedIn on Feb 13. The recruiter screening went well. Then, I had the first technical interview round. After that, it was a total of 1+4 rounds. The 4 rounds included behavioral questions mixed with architecture and whiteboard tasks. The first round focused on Microservices, SpringBoot, coding syntax, and basic Java. The second round involved designing an architecture for a given scenario and some basic Java questions at the end. The third round was a mix of Microservices and behavioral questions. The fourth round was on the whiteboard, where I had to design an architecture for a scenario, answer questions about it, and write some basic overview code. The fifth round consisted of behavioral questions. Rounds 4 and 5 were on the same day with a 1-hour gap in between. I'm not sure why I was rejected, as I felt I performed well.

Confirmed questions1 question
  • Tell me about Microservices design patterns.
Discover logo
Discover

Applications Engineer

Engineering

Senior Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Technical Behavioral Technical

I was contacted by a recruiter who set up 3 interviews. The first was technical, and the second and third were described as "behavioral" but were also technical. There wasn't any coding except for one impromptu question in the last interview. The questions asked in all the interviews were pretty much the same. Overall, the experience was really bad. The first interviewer was late and uninterested from the start, rushed the interview, and was unhappy with every answer, correcting me constantly even on open-ended questions like describing Object-Oriented programming. The second interviewer was also very late and rushed, finishing early, though they were nice and just apologized for being late. They barely asked any questions. The third interview was similar to the first but worse. The interviewers weren't paying attention, were working or chatting with others on Teams, and scoffed and rolled their eyes every time I spoke, offering corrections in a scolding manner. For example, when asked about converting from React to Angular, after I explained the context and reasons, they dismissed it and implied I didn't understand. They ended the interview with about 10 minutes left by giving me a quick impromptu function to write a unit test for, seemingly doubting my knowledge. My takeaway is to prepare for every interview as if it's technical and to consider leaving if interviewers are rude.

Confirmed questions7 questions
  • Can you describe the tech stack you're currently working with and explain your reasons for choosing those specific technologies?
  • Could you elaborate on Object-Oriented Principles?
  • What are your thoughts on React vs. Angular?

Discover Field / Application Engineer Interview Questions

Quoted word for word from Discover interview reports.

What are the 12 rules for RESTAPI, covering idempotent and non-idempotent HTTP methods?

Read reports

What are the advantages and disadvantages when comparing microservices architecture to a monolithic one?

Read report

Can you explain the circuit breaker pattern in the context of microservices?

Read report

Can you explain anonymous class authentication techniques?

Read report

Formats, difficulty and experience

Across all 25 Discover interview reports.

Interview formats

Technical 38.5%
Behavioral 32.3%
Coding 15.4%
System Design 13.8%

Interview difficulty

Easy 16%
Average 84%
Difficult 0%

Candidate experience

Negative 32%
Positive 48%
Neutral 20%