Guidehouse logo

Guidehouse Software Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Guidehouse.

Showing 3 of 15
Guidehouse logo
Guidehouse

Senior Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

The recruiter was very arrogant and asked irrelevant questions, expecting specific answers. They judged my fit despite lacking technical expertise and misrepresenting the job description regarding frontend technologies (React, Angular, Vue). They emphasized a lack of learning opportunities and had a generally unpleasant demeanor.

Confirmed questions1 question
  • Could you explain xyz and the reasoning behind it?
Guidehouse logo
Guidehouse

Software Developer

Engineering · a year ago

Intern Difficult Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Technical

The interview experience was disappointing. They asked DevOps-related questions to a fresher intern software developer. There was no response from the recruiter, which is disappointing. It's not recommended for freshers to join this company as they only value experienced candidates, even if they post vacancies on job portals and their website. They don't value interviewees.

Confirmed questions5 questions
  • Tell me about cloud computing.
  • What do you know about Kubernetes?
  • Have you worked with Jenkins?
Guidehouse logo
Guidehouse

Software Engineer

Engineering · more than a year ago

Entry Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Behavioral Technical

The interview process was pretty straightforward and not too difficult. They mainly checked if I had most of the skills mentioned in the job application. There were some questions about the requirements, and I explained how I used them in my past projects. The process included a screening and three interviews. The first interview was the toughest, and I think if you can pass that one (not counting the screening), you have a good shot at getting the job. All questions were high-level, and there wasn't any technical assessment.

Confirmed questions2 questions
  • Can you tell me about how you've used Spring Boot in your past projects?
  • Have you worked with APIs before?

Guidehouse Software Engineer Interview Questions

Quoted word for word from Guidehouse interview reports.

What are the recommended practices for designing a process model?

Read reports

Formats, difficulty and experience

Across all 15 Guidehouse interview reports.

Interview formats

Technical 48.5%
Behavioral 30.3%
Coding 9.1%
Group 9.1%
Presentation 3%

Interview difficulty

Easy 13.3%
Average 66.7%
Difficult 20%

Candidate experience

Positive 66.7%
Negative 20%
Neutral 13.3%