Taro Logo

Principal Software Engineer Interview Experience - San Jose, California

June 1, 2026
Negative ExperienceNo Offer

Process

Pros: The interview questions were relevant to the role, and I was given the opportunity to demonstrate my technical and architectural experience.

Cons: The interview process was a significant investment of time and ultimately left me with serious concerns about fairness and transparency in Adobe’s hiring process.

In addition to the recruiter screening and hiring manager interviews, I interviewed for a Principal Software Engineer position and completed all three onsite interviews. I felt that I performed strongly throughout the process, including the whiteboarding and technical discussions. When I specifically asked for negative feedback or areas where I had fallen short, I was not given any concrete technical or behavioral shortcomings. The only explanation I received was that the team believed I was somewhat below the Principal level.

Given the number of interviews and the lack of specific feedback, I found that explanation difficult to reconcile with my interview experience.

Another aspect of the experience that raised concerns for me was the demographic composition of the interview process. The recruiter and hiring manager were Indian, and two of the three interviewers were also Indian. I also observed that people of Indian background appeared to hold several prominent positions within the organization. I want to be clear that these observations by themselves do not establish discrimination, and I cannot know whether the demographic composition had any effect on my hiring outcome.

However, combined with the absence of substantive feedback about why I was considered below the Principal level, this made me question whether candidates from outside this demographic are evaluated and advanced using the same criteria.

My concern is therefore less about the nationality or background of any individual interviewer and more about the transparency and consistency of the overall evaluation process. If a candidate completes three onsite interviews and is ultimately judged to be below the required level, I believe the company should be able to identify the specific technical, architectural, leadership, or behavioral gaps that led to that conclusion.

The process also left me concerned that candidates may invest substantial time preparing for and completing multiple interviews without having a clear understanding of how Principal-level decisions are actually made. I cannot know whether my experience reflects a broader pattern, but it would be helpful for Adobe to make its evaluation criteria and decision-making process more transparent.

Advice to management: Adobe should ensure that interview outcomes are based on clearly defined and consistently applied criteria. Candidates who complete multiple onsite interviews should receive specific, evidence-based feedback when they are rejected, particularly when the stated reason is that they are below the target level. If a candidate genuinely performed below the Principal level, explain where and why, whether in technical depth, architecture, leadership, scope, communication, or another clearly identified area.

I would also encourage candidates to ask detailed questions about the evaluation criteria and how Principal-level decisions are made before investing substantial time in the process.

Questions

Describe a large-scale software architecture you designed, including the key technical decisions, scalability considerations, trade-offs, and how you would evolve the architecture as the system and business requirements grow.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Adobe Principal Software Engineer role in San Jose, California.

Success Rate

0%
Pass Rate

Adobe's interview process for their Principal Software Engineer roles in San Jose, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Adobe's Principal Software Engineer interview process in San Jose, California.

Adobe Work Experiences