GeeksforGeeks Experience · Nov 2016 · Los Angeles

Great West Interview Experience | Set 1

SWE Phone Screen Easy

Interview Experience

First written round on hirepro platform they asked questions on Quants, verbal, logical and technical mcqs mainly c++ and Java, written was medium level not the easy one o...

Full Details

First written round on hirepro platform they asked questions on Quants, verbal, logical and technical mcqs mainly c++ and Java, written was medium level not the easy one out of 500 they short listed some 250 for the second round that was GD round, they divide 250 in group of 15 each, GD was tougher one they gave us some 4-5 topics they fluctuate the topics in between, and out of 250 they only shortlisted 45 for the interviews round. they were 2 interview rounds 1st round : Itwas technical round two people take this interview they asked questions related to C, C++, DBMS joins and some queries and also asked us to find the errors in the given code. 2nd round: It was panel interview round that was taken by all the 10 members who came for the recruitment in this 2-3 people asked us technical questions and remaining were looking at how we are behaving . After that they selected 11 out 45.

Free preview — 6 questions shown. Unlock all Great West questions →

About This Question

This is a candidate experience report from a great west interview for a swe role during the phone screen round reported in 2016.

Difficulty rating: Easy

About Great West Interview Reports

This question was reported by a candidate who interviewed at Great West. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Great West are the higher-signal extractions to take from this report.

For broader preparation context, the Great West interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Great West reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Great West Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Great West reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.