What is the hiring process at Adobe?

The hiring process at Adobe is multifaceted and intense, taking between one to two months.

Although Adobe hires employees for a range of categories, from engineering and IT to finance, marketing, and customer experiences, its hiring process is fairly similar across departments, with the exception of leadership positions, which have different requirements and can take up to three months.

Even though it may take a month or two from start to finish, be prepared for an intensive, fast-moving interview experience. Typically, you will have six to eight hours of back-to-back panel sessions, each lasting about 45 minutes.

If you're applying for a technical role, expect four additional technical rounds of interviews with very job-specific questions. The last interview is usually done with HR. Each round is an elimination round; if you're dismissed early, that means no offer will come your way.

The interview questions themselves will be very different depending on the position that you are applying for. Some general questions that are usually asked in interviews across the board, such as, "Why do you want to work at Adobe?" or, "What are your experiences using Adobe products and services?"

Below are a few examples of interview question topics matched with specific positions at Adobe.

A UI programmer may be asked:

• JS-related questions, like how to create an excel in JS

• To participate in mock scenarios with pseudo-code related to some array manipulation

• How to create a debounce function

A project manager may be asked:

• About their favorite product and product management strategies

• About their methods for working with engineering, to assess how they would deal with developers

• Product design questions, including some qon innovative approaches with AI/ML interventions

A Software engineer may be asked:

• DBMS and prog lang-related questions

• To participate in mock scenarios using Javascript and other programming-related knowledge

• About their understanding of concepts such as OS, DBMS, DSA, and OOPs

• About the basics of system design, such as how to design a URL shortener

• To discuss projects and their involvement in tech stack

A financial analyst may be asked:

• About their accounting experience

• What software they are comfortable using, and to what extent

• Personality gauging questions (e.g., If you were a CEO, what would be the three things that keep you awake at night?)

A marketing specialist may be asked: