Lee experiencias reales compartidas por candidatos, incluyendo preguntas, descripción del proceso y señales sobre el nivel de dificultad en Adobe.
8 experienciasDificultad 3.3/5Creative Software / Digital Experience
Marketing Manager
virtual
· Dificultad 3/5
Recruiter screen, hiring manager video, marketing case study (build a campaign for Photoshop on iPad targeting prosumers), cross-functional with product marketing, and final with director. They probe whether you can balance brand voice with measurable acquisition.
Tell me about a campaign where the creative bombed. What did you do?
Describe a time you had to pivot a launch mid-cycle.
Walk me through balancing brand-building spend vs. performance marketing.
How do you partner with product on co-marketing for a feature launch?
UX Designer
virtual
· Dificultad 4/5
Portfolio presentation (1 hour, 4 attendees), design exercise (rethink Acrobat's mobile sign flow), critique session, cross-functional with PM and engineering, and director round. Adobe expects craft-level mastery — your portfolio is the single biggest filter.
Walk me through a project where you killed a feature you'd designed. What changed your mind?
Tell me about advocating for a user need against business pressure.
Describe a time you fundamentally changed your approach based on user research.
How do you design for users at every skill level without dumbing things down?
Software Engineer
virtual
· Dificultad 4/5
Recruiter screen, technical phone with two coding problems (one algorithmic, one C++/Rust system question). Virtual onsite was five rounds: coding, system design (collaborative document editing), deep-dive on a past project, cross-functional with a designer, and team-fit. They want engineers who care about creative tools.
Tell me about a perf optimization that required deep understanding of the underlying platform.
Describe collaborating with designers when their vision pushed the limits of what was technically feasible.
Walk me through how you'd architect realtime sync for 100+ collaborators on a single document.
How do you balance shipping new features vs. refactoring debt in a long-lived product?