Software Development Engineer
Interview Date
Late November & up to mid-December (Year Not Specified)
Result
Pending
Difficulty
Medium to Hard
Rounds
3 main rounds (with 4 interviews in the virtual on-site)
Drive Type
Full-Time
Topics asked
Detailed experience
College: Not Specified
Interview Date: Late November & up to mid-December (Year Not Specified)
Interview Type: Full-Time
Result: Pending
Difficulty: Medium to Hard
Rounds: 3 main rounds (with 4 interviews in the virtual on-site)
Topics Asked: General questions, Majority Element, Resume, Technical, Behavioral, Valid Anagrams, Two Sum variant, Build an Index, Asteroid Collision, Garden Leveling, Anagrams in sentences
Round 1 was an HR Phone Call (~30 mins) with general questions and a briefing about the position and company.
Round 2 was with the Hiring Manager (~70 mins) and included a coding question on finding the Majority Element.
Round 3 was a Virtual On-site (~4 hrs) comprising four separate interviews.
Interview 1 (~1 hour) focused on Resume, Technical, and Behavioral questions. Technical questions included Valid Anagrams, a variant of Two Sum where all pairs had to be returned, and building an index given a series of pages and a list of words to ignore.
Interview 2 (~1 hour) was also Resume and Technical focused. The interviewer initially prepared for a front-end interview but realized it was a backend position. The technical question was Asteroid Collision (approach, implementation, complexity analysis).
Interview 3 (~45 minutes) involved Resume and Technical questions. The problem was to "Level a garden" (given a garden as a matrix with cell levels, find how much dirt to add to each cell to make the garden level even).
Interview 4 (~60 minutes) covered Resume and Technical aspects. The question was: given a list of sentences and a wordset, find anagrams in the wordset and use them to determine how many sentences are possible if every word in a sentence could be replaced by its anagram. The candidate had to code within a skeleton code provided to match input/output requirements.