# P20
**Role:** Software Engineer · **Level:** Software Engineer 2
**Company:** [Adobe](https://scaleengineer.com/companies/adobe)
**Difficulty:** Medium to Hard
**Salary:** US$110000 - US$150000
**Experience:** 2 - 5
**Timeline:** ~14 days
This interview process is designed to assess candidates for a Software Engineer 2 position at Adobe, focusing on core technical skills, problem-solving abilities, and cultural fit. The process typically involves multiple rounds, including technical assessments, behavioral interviews, and a final hiring manager discussion.
Canonical: https://scaleengineer.com/interviews/adobe/software-engineer-2-software-engineer
---
## Overall evaluation

- Technical Skills
- Communication
- Behavioral and Cultural Fit

## Questions asked

- Given an array of integers, find the contiguous subarray with the largest sum.
- Design a system to handle real-time notifications for a social media platform.
- Explain the difference between a process and a thread.
- Tell me about a time you failed and what you learned from it.
- How would you optimize a slow database query?
- Describe your experience with version control systems like Git.
- What are the trade-offs between monolithic and microservices architectures?
- How do you handle technical debt?
- Write a function to reverse a linked list.
- Describe a challenging project you worked on and your role in it.

## Preparation tips

### lists

- Review fundamental computer science concepts (data structures, algorithms, operating systems, databases).
- Practice coding problems on platforms like LeetCode, HackerRank, or AlgoExpert, focusing on medium to hard difficulty.
- Study system design principles and common design patterns.
- Prepare behavioral examples using the STAR method (Situation, Task, Action, Result).
- Research Adobe's products, mission, and values.
- Understand the specific technologies and programming languages mentioned in the job description.
- Prepare thoughtful questions to ask the interviewers.
- Practice explaining your thought process clearly and concisely.

### studyPlan

- {"title":"Data Structures and Algorithms","longDescription":"Weeks 1-2: Focus on core data structures (arrays, linked lists, trees, graphs, hash maps) and fundamental algorithms (sorting, searching, recursion, dynamic programming). Practice implementing these from scratch and analyze their time and space complexity. Solve 2-3 problems per day.","shortDescription":"Weeks 1-2: Data Structures & Algorithms fundamentals. Practice 2-3 problems/day."}
- {"title":"System Design","longDescription":"Weeks 3-4: Dive into system design concepts. Study topics like scalability, availability, databases (SQL vs. NoSQL), caching, load balancing, and microservices. Work through common system design case studies and practice designing systems like Twitter feed, URL shortener, etc.","shortDescription":"Weeks 3-4: System Design concepts. Study scalability, databases, caching. Practice case studies."}
- {"title":"Behavioral Preparation","longDescription":"Week 5: Prepare for behavioral interviews. Identify key experiences from your resume that demonstrate leadership, teamwork, problem-solving, and conflict resolution. Practice articulating these using the STAR method. Also, research Adobe's culture and values.","shortDescription":"Week 5: Behavioral preparation. Use STAR method. Research Adobe culture."}
- {"title":"Mock Interviews and Refinement","longDescription":"Week 6: Mock interviews. Conduct mock interviews with peers or mentors to simulate the actual interview environment. Focus on receiving and incorporating feedback on both technical and behavioral aspects. Review any weak areas identified.","shortDescription":"Week 6: Mock interviews. Practice explaining thought process. Get feedback."}

## Location differences

- {"location":"San Jose, CA","differences":{"tips":["Research Adobe's recent product launches and industry trends.","Prepare specific examples demonstrating your problem-solving process.","Be ready to discuss your contributions to past projects in detail.","Familiarize yourself with common interview questions for software engineers at major tech companies."],"interviewFocus":["Emphasis on practical application of data structures and algorithms.","Assessment of system design capabilities for scalable solutions.","Evaluation of collaboration and communication skills within a team.","Understanding of Adobe's product suite and its impact."],"commonQuestions":["Discuss a challenging technical problem you solved in a previous role.","How do you approach debugging complex issues?","Describe your experience with cloud platforms (AWS, Azure, GCP).","Tell me about a time you had to work with a difficult stakeholder."]}}
- {"location":"Seattle, WA","differences":{"tips":["Practice coding problems on platforms like LeetCode and HackerRank.","Review fundamental computer science concepts.","Prepare to discuss your career goals and how they align with Adobe's mission.","Be prepared to ask insightful questions about the team and the role."],"interviewFocus":["Strong focus on data structures and algorithms, with a preference for optimal solutions.","Evaluation of coding proficiency and clean code practices.","Assessment of adaptability and willingness to learn new technologies.","Understanding of software development lifecycle and best practices."],"commonQuestions":["Explain the principles of object-oriented programming.","How would you design a URL shortener service?","Describe a situation where you had to mentor a junior engineer.","What are your thoughts on agile development methodologies?"]}}
- {"location":"Austin, TX","differences":{"tips":["Brush up on your knowledge of common data structures and algorithms.","Prepare to explain your thought process clearly during coding exercises.","Research Adobe's values and culture to demonstrate alignment.","Have specific examples ready for behavioral questions."],"interviewFocus":["Assessment of problem-solving skills through coding challenges.","Evaluation of system design thinking, particularly for distributed systems.","Understanding of software architecture and design patterns.","Behavioral questions to gauge teamwork and communication."],"commonQuestions":["How do you ensure code quality and maintainability?","Describe a time you disagreed with a technical decision and how you handled it.","What are your favorite programming languages and why?","How do you stay updated with new technologies?"]}}

## Round 1: Data Structures and Algorithms
**Type:** Technical Interview (Coding) · **Difficulty:** Medium · **Duration:** 45 min
Coding challenge focused on data structures and algorithms.
This round typically involves a coding challenge, often conducted via a shared online editor. The interviewer will present a problem, and you'll be expected to write code to solve it, explaining your thought process as you go. The focus is on your ability to apply data structures and algorithms to solve practical problems efficiently and write clean, maintainable code.
**Interviewers look for:** Strong grasp of data structures and algorithms.; Ability to translate a problem into code.; Logical thinking and problem-solving skills.; Clear communication of technical ideas.
**Evaluation criteria:** Correctness of the solution.; Efficiency of the solution (time and space complexity).; Code clarity and organization.; Ability to explain the approach and trade-offs.
**Common rejection reasons:** Inability to articulate thought process clearly.; Suboptimal or incorrect algorithmic solutions.; Poor coding practices (e.g., unreadable code, lack of error handling).; Lack of understanding of fundamental data structures and algorithms.
## Questions

- Given a binary tree, find its inorder traversal.
- Implement a function to find the kth smallest element in an unsorted array.
- Write a program to detect a cycle in a linked list.

## Preparation tips

- Practice coding problems on platforms like LeetCode.
- Focus on understanding time and space complexity.
- Write clean, well-commented code.
- Practice explaining your solutions out loud.

## Round 2: System Design
**Type:** System Design Interview · **Difficulty:** Hard · **Duration:** 60 min
Design a complex software system, focusing on scalability and reliability.
This round assesses your ability to design complex software systems. You'll be given an open-ended problem (e.g., design a URL shortener, a social media feed, a rate limiter) and expected to propose a high-level design. The discussion will cover aspects like data modeling, API design, scalability, performance, and fault tolerance. You should be prepared to justify your design choices and discuss alternatives.
**Interviewers look for:** System design thinking.; Knowledge of distributed systems.; Ability to make reasoned technical decisions.; Understanding of trade-offs.; Experience with large-scale systems.
**Evaluation criteria:** Scalability of the proposed design.; Availability and reliability considerations.; Choice of appropriate technologies and data stores.; Understanding of trade-offs and constraints.; Ability to handle edge cases and failures.
**Common rejection reasons:** Inability to design scalable and robust systems.; Lack of understanding of distributed systems concepts.; Poor trade-off analysis.; Not considering edge cases or failure scenarios.
## Questions

- Design a system like Twitter's news feed.
- Design a distributed cache system.
- How would you design an API rate limiter?

## Preparation tips

- Study common system design patterns and principles.
- Review case studies of popular systems.
- Practice designing systems on paper or whiteboard.
- Be prepared to discuss trade-offs for different design choices.

## Round 3: Behavioral and Cultural Fit
**Type:** Behavioral Interview · **Difficulty:** Medium · **Duration:** 45 min
Assesses past experiences, work style, and cultural fit.
This round focuses on your past experiences, work style, and how you collaborate within a team. You'll be asked behavioral questions designed to understand how you've handled various situations in previous roles. The interviewer wants to gauge your problem-solving approach, your ability to work with others, and whether you'd be a good cultural fit for Adobe.
**Interviewers look for:** Evidence of collaboration and teamwork.; Ability to handle challenges and setbacks.; Self-awareness and reflection.; Alignment with Adobe's culture.; Motivation and passion for software engineering.
**Evaluation criteria:** Teamwork and collaboration skills.; Problem-solving approach in past projects.; Adaptability and learning agility.; Communication and interpersonal skills.; Cultural fit with Adobe's values (e.g., innovation, customer focus, integrity).
**Common rejection reasons:** Lack of alignment with company values.; Poor communication or interpersonal skills.; Inability to provide specific examples for behavioral questions.; Lack of enthusiasm or interest in the role/company.
## Questions

- Tell me about a time you had a conflict with a team member and how you resolved it.
- Describe a project where you had to learn a new technology quickly.
- What motivates you as a software engineer?

## Preparation tips

- Prepare examples using the STAR method for common behavioral questions.
- Reflect on your strengths and weaknesses.
- Understand Adobe's company values and culture.
- Be ready to discuss your career aspirations.