Adobe

Role: Computer Scientist 2

College: Not Specified

Interview Date: June-August (Application), November 9, 2024 (Interview experience published)

Interview Type: Full-Time (Off-campus, recruiter reached out on LinkedIn)

Result: Stepped back from opportunity (due to role alignment)

Difficulty: Easy to Medium (Coding), Medium (System Design, Behavioral)

Rounds: 4 Rounds (3 Technical, 1 Behavioral/Design/Analytical)

Topics Asked: Data Structures, Algorithms, Graphs, Stacks, UX Development (React, TypeScript, JavaScript), System Design, Behavioral Scenarios, Design Principles, Analytical Thinking

Experience:

The candidate was reached out to by a recruiter on LinkedIn for a Computer Scientist 2 role.

Round 1: Technical Round (45 minutes): Focused on Data Structures and Algorithms, specifically Graphs and Stacks. Questions included a graph-based problem similar to the "Island problem" and a pattern similar to the "stock problem". The expectation was to write clean, error-free code covering edge cases. The candidate solved both questions within 30 minutes on Notepad.

Round 2: Technical Round (1 hour): Focused on UX Development skills, including React, TypeScript, and JavaScript. The question was to design and build a complete React-based shopping cart application similar to Amazon's, allowing users to manage products, quantities, and dynamically calculate the total bill, fetching product catalog from an API. The application needed to be responsive, user-friendly, and demonstrate best practices. The candidate delivered error-free code on HackerRank.

Round 3: Technical Round (1 hour): Focused on System Design and Behavioral aspects. Technical Design involved designing a logging and dashboard management system. Experience discussion covered past projects. Behavioral scenarios included handling ambiguous projects, implementing best practices for leading teams, conflict resolution, and lessons learned.

Round 4: Behavioral, Design, Analytical, Coding (Approx. 2 hours): This round involved a career journey discussion, focusing on transitions (e.g., embedded to web development). In-depth analysis and discussion on design principles applied to real-world scenarios were covered. Behavioral scenarios focused on decision-making during career transitions, adapting to new technical domains, and strategic thinking in project design. The candidate ultimately decided to step back from the opportunity due to role alignment.