Management works hard to be tuned into both product and engineering needs. Excellent institutional knowledge across all the domains they work in. Smart, passionate colleagues across the board. Excellent work/life balance. People here work hard but don't over-work; that balance is hit really well culturally.
Codebases are a bit slow to work in. This is par for the course for big tech; I can't fault Adobe too hard here.
The process was pretty straightforward. I had a telephone call with the computer scientist, followed by an onsite discussion with four other team members. They did not ask any difficult questions, sticking instead to very general inquiries.
The hiring process started with a phone interview with the hiring manager. I was then invited on-site for face-to-face interviews with four engineers on the team, the recruiter, and the hiring manager. The interviews were straightforward, mostly con
Present research work in detail. QA with interview questions about the research details, such as model and problem definition, and publications. Follow with a coding round featuring a medium-level LeetCode problem.
The process was pretty straightforward. I had a telephone call with the computer scientist, followed by an onsite discussion with four other team members. They did not ask any difficult questions, sticking instead to very general inquiries.
The hiring process started with a phone interview with the hiring manager. I was then invited on-site for face-to-face interviews with four engineers on the team, the recruiter, and the hiring manager. The interviews were straightforward, mostly con
Present research work in detail. QA with interview questions about the research details, such as model and problem definition, and publications. Follow with a coding round featuring a medium-level LeetCode problem.