How to Crack Adobe: The Intern Interview, From Real Experiences
How the Adobe intern interview works: online assessment, technical interview, puzzles and a final round, with real candidate experiences and a prep plan.
On this page
How to Crack Adobe: The Intern Interview, From Real Experiences
Last reviewed November 20, 2026 · 20 min read · For Adobe product, software engineer and customer engineering interns
Built by the Codinzhub team. This guide is built from Adobe intern interview experiences that candidates shared, including posts on Codinzhub. The process changes by year, level and team, so treat this as a map, not a promise.
The 30-second version. Most intern reports start with an online assessment (OA, a timed test). Older campus reports describe a 90 to 120 minute HackerRank test with MCQs, coding, pseudocode and an essay, while 2022 to 2026 reports describe 2 or 3 coding questions. After that comes one technical interview, from 30 minutes to about 1.25 hours, often by phone or video, mixing a coding problem, CS fundamentals, puzzles and a project discussion. Some candidates then have a final behavioral round. The habit that matters most: explain your approach and complexity out loud, because candidates said interviewers cared about approach over typing speed.
What this guide is, and what it is not
This guide is built from 23 candidate experiences of Adobe's intern interviews, from 2018 to 2026 (the older GeeksforGeeks posts are the most detailed), mostly for product intern and software engineer intern roles in India and the US. Terms used: DBMS is database management systems, OOP is object-oriented programming, and MTS-1 is Adobe's entry-level full-time engineering title. Full-time reports are in a separate guide.
It is:
- A map of the process, stage by stage, as candidates described it
- The question patterns that keep coming back, and the follow-ups to expect
- A six-week plan and practice problems matched to those patterns
It is not:
- A list of leaked questions or a promise of what you will be asked
- An official description of Adobe's process
- An offer rate. Outcomes in candidate posts are self-reported and are not a statistical sample.
Important things to know before you start
These are the Adobe-specific facts that change how you prepare.
The OA format changed over time. Older reports (stated years 2018 to 2021, plus several undated posts) describe 90 to 120 minutes on HackerRank with MCQs on probability and matrices, coding, pseudocode for printing a matrix in spiral order, and an essay. Reports from 2022 to 2024 describe 2 or 3 coding questions, and one 2024 report added 30 MCQs. Check which format you receive.
The interview is short and conversational. Candidates described a single interview from 30 minutes to about 1.25 hours, often by phone, Skype, Teams or BlueJeans. One 2026 email said 30 to 45 minutes with about 20 minutes of live coding, and the rest on experience and projects. Two 2026 posts mention a debugging and a code-review section in the interview.
Puzzles and projects count. Four reports included puzzles, and five included a project discussion, which took about 25 minutes in one 2020 interview. One candidate was told afterwards to practise puzzles and logical thinking.
Most of the detailed question lists are old. Of the 18 reports with a stated year, 14 are from 2024 to 2026, but those are mostly short process notes. The detailed question lists come from 2018 to 2021 posts and several undated ones, so treat the specific questions as examples of style.
Round-by-round breakdown
Candidates described five stages: application, shortlisting, an online assessment, the interview, and a decision with offer or team matching.
Stage 1: Application, where candidates applied
Most reports are campus drives in India; reports from the US, Europe and a few from India describe applying on Adobe's careers page.
| Channel | What candidates said |
|---|---|
| Campus drives | 13 reports. Three older posts mention a CGPA cutoff (7.0 or 7.5) and branches such as CSE, IT and ECE. One 2024 campus drive took 6 students from 45 shortlisted for interviews. |
| Careers site | 8 reports. One Summer 2023 intern applied early on the careers page after polishing the resume; one Summer 2025 intern applied cold. |
| SheCodes programme | One 2021 report for a women-in-technology internship route, with a resume upload and a virtual session about Adobe before the interview. |
What helped. One candidate who received an offer credited polishing the resume and applying early. A 2026 candidate got a candidate kickoff call before the interview.
Stage 2: Shortlisting, how candidates moved forward
In most intern reports, shortlisting was the online test, and for some it was a short call or resume review.
- Online assessment. Described in Stage 3. In one 2020 report, about 90 students took the test and 7 were shortlisted; in another, 134 took it and 21 were shortlisted. A 2024 report for the 2025 internship, from Europe, described choosing Java, JavaScript or ML tests, with the interview on only one of them.
- Resume review and team matching. One 2022 intern said the resume was reviewed again after the OA, then candidates were invited to an Interview Forum with up to 4 interviews on the same day for different teams.
- Short HR call. One 2024 campus drive included a telephonic HR round after the online test.
What candidates advised. Practise LeetCode mediums for the OA, and prepare your projects.
Stage 3: Online assessment or phone screen
Most intern reports (15 of 23) described an OA, and none described skipping it. The telephonic call with an interviewer is the technical interview, described in Stage 4.
Online assessment
How it works. Older campus tests ran 90 to 120 minutes on HackerRank, or on CoCubes for one 2021 route, with no negative marking in several posts. Sections reported were MCQs (probability, matrices, eigenvalues, aptitude, CS fundamentals), one or two coding questions, a pseudocode question and an essay, and for two routes a gamified section. Reports from 2022 to 2026 describe 3 LeetCode-style questions on HackerRank (twice), or 2 coding questions with 30 MCQs (once), and a 2024 invitation for a 60-minute test with a choice of Java, JavaScript or ML. No report stated an AI-tool policy.
At a glance
- Length: 90 to 120 minutes in 4 older reports; 60 minutes in one 2024 report
- Questions: 1 to 3 coding questions in older tests; 2 or 3 in 2022 to 2024 reports
- What was asked: Dynamic programming, sorting and greedy, string matching, digit counting, matrix traversal, an essay
- Most common: The 250-word essay (4 reports), then the umbrella-cover problem and spiral-order pseudocode (3 reports each)
| Question | What it tests | Level |
|---|---|---|
| Write 250 words on IoT or on your favourite project | Written communication | Product Intern |
| Minimum number of umbrellas that cover exactly a target number of people | Coin-change style DP | Intern |
| Print a matrix in spiral order as pseudocode | Boundary traversal | Product Intern |
| Tallest new tower at each empty position given its neighbours | Sorting and greedy | Product Intern |
| Lexicographic rank of a string | Combinatorics on strings | Product Intern |
| Number that contains the digit K the most times | Digit counting | Not reported |
| Wildcard matching | String DP | Not reported |
See all Adobe OA questions in the question bank. Adobe OA questions shared on Codinzhub:
| Question | Drive | Topic |
|---|---|---|
| Maximum Value on Tree Paths | Hackathon 2026 | Tree paths |
| Pair Sum (Easy Version) | Hackathon 2026 | Hashing |
| Exactly K Distinct Contaminants | Hackathon 2026 | Counting, sliding window |
| Closest Numbers | ACS Applied AI Engineer, off-campus | Sorting, two pointers |
| Frequency Calculator | ACS Applied AI Engineer, off-campus | Hashing |
| Beautiful String (Regex) | IIT Roorkee | Strings, regex |
| Maximum Score 2 | 2025 PYQ, IIT-preferred | DP |
| Good Binary Strings | 2025 PYQ, IIT-preferred | Strings, DP |
Full Adobe interview experiences on Codinzhub: Product intern, NSUT (2026), Product intern, IIT Kanpur, Summer intern, Product Analyst, IIT Hyderabad, SDE intern, IIT Guwahati.
More Codinzhub questions: Browse Adobe questions.
Stage 4: The interview
Reports describe one technical interview, sometimes two, of about 30 to 60 minutes. Formats include phone, Skype, MS Teams and BlueJeans, and one 2024 on-campus drive added an HR round. In several reports the order was introductions, a project discussion, a coding problem and some fundamentals, with a puzzle in 4. The 2022 intern had 2 interviews in an Interview Forum. Four reports describe interviewers who asked for the approach first, then for code and a dry run.
Technical interview: coding and data structures
At a glance
- Length: About 40 minutes in two reports, 30 to 45 minutes in a 2026 email, up to 1.25 hours in one
- Questions: 1 to 4 coding problems in the reports that listed them
- What was asked: Arrays, sorted data, linked lists, trees, DP and one bit manipulation question
- Most common: No single repeated question
Interviewers asked for the naive approach, then the optimised one, then complexity. In one report the interviewer asked for 2 or 3 approaches to a single problem, taking most of an hour. In another, the first solution passed 3 of 15 test cases and reached 12 of 15 after a dry run and feedback.
| Question | Follow-up | Level |
|---|---|---|
| Kadane's algorithm | Not reported | Customer Engineering Intern |
| Merge two sorted arrays, explaining both approaches | Not reported | Product Intern |
| Minimum swaps to balance a set of parentheses | Not reported | Product Intern |
| Pattern printing, a medium array question and a string question | Not reported | Intern |
| Count triplets that can form a triangle | Not reported | Product Intern |
| Reverse a linked list | Not reported | Product Intern |
| Inorder traversal, recursive then iterative | Iterative solution | Product Intern |
| Find Pythagorean triplets in an array | Not reported | Product Intern |
Technical interview: CS fundamentals, puzzles and projects
At a glance
- Length: Shares the same 30 to 60 minutes
- Questions: 3 to 6 fundamentals, puzzles or project questions
- What was asked: OOP and C++, OS, DBMS and SQL, JavaScript for one role, puzzles and project discussion
- Most common: A project walk-through, in 5 reports
In two reports the interview spent 25 to 30 minutes on projects and fundamentals before or around the coding. In one report the interviewer changed the project's ideal assumptions and asked how to adapt it. Puzzles were asked in 4 reports.
| Question | Follow-up | Level |
|---|---|---|
| Walk through a project: stack, your contribution, challenges and changed assumptions | How would you improve it for more users | Product Intern |
| Explain normalisation in DBMS | Not reported | Product Intern |
| What is sharding in a database? | Not reported | Customer Engineering Intern |
| JavaScript closures and the scope chain | Not reported | Customer Engineering Intern |
| SQL questions based on your project | Not reported | Customer Engineering Intern |
| SQL joins, distinct, DDL versus DML and virtual tables | Not reported | Intern |
| Can a destructor be virtual? What are constructors and destructors? | Not reported | Product Intern |
| What is swap memory? | Not reported | Product Intern |
Final behavioral or HR round
At a glance
- Length: Not reported
- Questions: Not reported as a count
- Themes: Goals, strengths, leadership, motivation, past experience and the team you want
- Most common: Tell me about yourself and your past experiences (2 reports)
Two reports from the 2025 to 2026 US cycle describe a final behavioral round with engineers after the technical interview; a 2024 campus drive had an HR round that ended in rejection for one candidate; and a 2024 US loop had a hiring-manager fit round after a live problem.
Reported questions.
- Tell me about yourself and your past experiences
- Common behavioral questions about past projects and internships
- What are your short-term and long-term goals?
- What are your strengths and weaknesses?
- Describe your leadership experience
- How much experience do you have with HTML and CSS?
- Your background and the team you want to work on
- Why do you want this internship, and why Adobe?
See all behavioral questions in the question bank.
Stage 5: Hiring committee, team match and offer
Decision. Two older reports (one from 2020) got results one to two days after the interview. A 2026 report described an email that said the information had been passed to the hiring team, which candidates read as a hold, and a 2024 report received an email asking to schedule a call after the final round.
Team matching. One 2022 intern filled a preferred-teams form after the Interview Forum and received an offer when a hiring manager was interested. A candidate who received an offer in December 2025 said the recruiter had already found a team by the offer call.
Offer and conversion. Two reports from 2025 and 2026 describe IIT interns who received an MTS-1 pre-placement offer after a product internship. Compensation is left out here.
Adobe experiences shared on Codinzhub
These are intern experiences candidates posted on Codinzhub. Public links to the original posts are Not stated.
| College | Role and result | What was asked |
|---|---|---|
| NIT Kurukshetra | Customer Engineering Intern, on-campus, rejected | 4 rounds reported with a medium level: Kadane's algorithm, SQL questions from the project, JavaScript closures and scope chain, normalisation and sharding. |
| IIT BHU | Product Intern, rejected | One round of about 1.25 hours: projects and core CS (polymorphism) for 30 minutes, then one HackerRank problem (minimum cost for tickets) taken through recursion, memoisation and tabulation. |
| Not stated | Product Intern, on-campus, outcome not reported | An OA with 2 coding questions and 30 MCQs on C, DBMS and OOP; one interview with projects, merge two sorted arrays and minimum swaps to balance parentheses. |
| Not stated | Software Engineer Intern, selected for Summer 2023 | A HackerRank OA with 3 LeetCode-style questions, then an Interview Forum with 2 interviews on past experience and basic CS, then a team-preference form. |
The Codinzhub Next-Round Playbook
Candidates who moved on kept explaining their approach, and ran their code against their own examples.
To get past the OA
- Check the format first. Older reports had MCQs, pseudocode and an essay; 2022 to 2026 reports described coding only.
- Practise easy-to-medium LeetCode problems on HackerRank. One candidate in the 2026 US cycle called the OA question about 5 minutes of LeetCode easy.
- Write the essay clearly if the section exists: it was in 4 of the older reports.
To get past the technical interview
- Explain your approach before coding. One 2020 candidate wrote that the interview was meant to see approach rather than coding skill.
- Give the naive approach, the optimised approach and the complexity, then dry-run. One candidate raised a solution from 3 to 12 of 15 test cases after a dry run.
- Say what you do not know. Two candidates said they had not studied a topic and carried on.
- Be ready to solve a puzzle aloud and ask for time.
To get past the final round
- Prepare "tell me about yourself", your goals, a leadership example and why you want this internship.
- Know your projects: one US candidate said the final round had very little technical content, with minor questions on past projects and internships followed by common behavioral questions.
To get through team matching and the decision
- Reply quickly to scheduling emails and fill in team-preference forms.
- Expect waiting: some 2026 candidates received a hold email rather than a decision.
How the loop differs by level
The loop is similar for all interns, and what changes is the role track and the cycle.
| Level | What candidates describe |
|---|---|
| Product Intern (India campus) | 9 reports. OA, then 1 telephonic or video interview of 40 to 75 minutes with coding, fundamentals, puzzles and projects. No system design was reported. |
| Software Engineer Intern (US, Europe, India) | 9 reports. A HackerRank OA of 3 LeetCode-style questions or 60 minutes with a language choice; a 30 to 45 minute technical interview with about 20 minutes of live coding; a behavioral final round in 2025 and 2026 US reports. No system design was reported. |
| Customer Engineering Intern and campus CE-DX | 2 reports. One had DSA, SQL, JavaScript, normalisation and sharding questions; one campus drive had pattern printing, array and string questions, OOP in Java and SQL, then an HR round. No system design was reported. |
Most-asked topics
Across 11 reports that described technical rounds, questions concentrated in a few clusters. Arrays and strings led, followed by dynamic programming.
| Topic | What it means | Seen in | Reported examples |
|---|---|---|---|
| Arrays, strings, sorting and searching | Working with lists, text, sorted data and search. | 9 of 11 reports | Spiral order; Merge two sorted arrays; Search a sorted matrix |
| Dynamic programming | Building an answer from smaller answers. | 6 of 11 reports | Minimum umbrellas for an exact total; Minimum cost for tickets; Kadane's algorithm |
| CS fundamentals: OOP, OS, DBMS and SQL | Core computer science theory and database queries. | 5 of 11 reports | Normalisation; Sharding; Paging; Virtual destructors |
| Puzzles and aptitude maths | Logic puzzles and maths solved aloud or on paper. | 5 of 11 reports | Two-dice days of the month; Three candles; Lighter-ball box |
| Linked lists, trees and stacks | Pointer structures and traversal. | 4 of 11 reports | Reverse a linked list; Inorder traversal; Merge point of two lists |
The question patterns that keep coming back
Most questions fell into a handful of patterns. Learn to recognise the pattern under the story.
1. Arrays, strings, sorting and searching
The largest cluster, in 9 of 11 reports. If the data is sorted, think two pointers or binary search; if the question asks for a count over triples, sort first. The most repeated question in this cluster was spiral-order pseudocode (3 reports).
Reported examples. Print a matrix in spiral order as pseudocode; Merge two sorted arrays; Count triplets that form a triangle; Search a row-wise and column-wise sorted matrix; Search for an element in an infinite sorted array; Tallest new tower at each empty position.
2. Dynamic programming
6 of 11 reports. The same umbrella-cover problem appeared in 3 reports across years. If the answer is built from smaller answers, define the state, then the recurrence, then move from recursion to memoisation to a table.
Reported examples. Minimum umbrellas for an exact total; Minimum cost for tickets; Kadane's algorithm; Wildcard matching; Lexicographic rank of a string.
3. CS fundamentals: OOP, OS, DBMS and SQL
5 of 11 reports. If the question is a definition, give the definition, one example and one reason it matters.
Reported examples. Can a destructor be virtual; What is swap memory; Explain normalisation; What is sharding; What is paging; SQL joins, distinct, DDL and DML.
4. Puzzles and aptitude maths
5 of 11 reports. If it is a puzzle, say your plan out loud and ask for time; one interviewer offered to skip a geometry puzzle.
Reported examples. Days of the month with two dice; Finger-counting puzzle; Lighter-ball box with one weighing; Three candles; Five-digit reverse number.
5. Linked lists, trees and stacks
4 of 11 reports. If it is a tree, state the traversal order and write both the recursive and iterative versions.
Reported examples. Reverse a linked list; Inorder traversal, recursive then iterative; Merge point of two linked lists; Preorder from inorder and postorder; Minimum swaps to balance brackets.
Preparing for the project discussion and puzzles
Adobe's intern interview has no named values round, so this section prepares you for the project and behavioral questions in the technical interview and the final round.
Build your project story. Be ready for 5 to 25 minutes on one project. Cover the themes candidates were asked about:
| Theme | Reported prompt (paraphrased) | Follow-up to expect |
|---|---|---|
| Your stack | Which technologies, and how you implemented them | Not reported |
| Your contribution | What you built and the objectives | Specific networking or domain questions |
| Changed assumptions | How would you adapt the product if the ideal assumptions change | How to handle real-world problems |
| Goals | Short-term and long-term goals | Not reported |
| Motivation | Why this internship, and why Adobe | Not reported |
| Leadership | A leadership experience | Not reported |
Structure each story. State the situation in one line, what you did (say "I"), the result with a number, and what you would change.
Expect depth. One interviewer spent 25 minutes on a single project. Use real experiences only.
A six-week plan
The plan follows the patterns above, most common first, and ends with timed mocks that feel like the real round. Plan on two focused hours a day.
- Week 1: Arrays, strings, sorting and searching. Spiral order, merge sorted arrays, triplets, sorted-matrix search, binary search. Habit: write the naive approach and its complexity first.
- Week 2: Dynamic programming. Umbrella cover (coin-change style), minimum cost for tickets, Kadane. Habit: move from recursion to memoisation to a table.
- Week 3: CS fundamentals. C++ constructors and virtual destructors, OS paging and memory, DBMS normalisation and sharding, SQL joins; for customer engineering add JavaScript closures. Habit: answer with definition, example, why it matters.
- Week 4: Puzzles and aptitude maths. Solve puzzles aloud; revisit probability and matrix basics for older-style OAs. Habit: say your plan before the answer.
- Week 5: Linked lists, trees and stacks. Reverse a list, iterative inorder, merge point, balanced brackets. Habit: dry-run on a small input.
- Week 6: Mocks. Four timed 45-minute interviews, each with one coding problem, one fundamentals question and a project discussion, plus one 2-hour HackerRank-style OA. Rehearse your project and behavioral answers out loud.
Interns can spend less time on advanced topics, and customer engineering candidates should add JavaScript and SQL.
Only two weeks? Spend 4 days on arrays, strings and searching, 3 days on dynamic programming, 3 days on CS fundamentals and SQL, 2 days on linked lists, trees and puzzles, and 2 days on timed mocks and project rehearsal. That is 14 days.
Practice problems that match these experiences
These are well-known practice problems that match the patterns above. They are not claims about Adobe's question bank unless a row says the problem was asked as-is.
| # | Practice problem | Pattern | Seen in these experiences as |
|---|---|---|---|
| 1 | Spiral Matrix | Boundary traversal | Print a matrix in spiral order. Asked as-is in 3 reports |
| 2 | Coin Change | Coin-change DP | Minimum umbrellas for an exact total (similar technique) |
| 3 | Minimum Cost For Tickets | DP with memoisation then tabulation | Asked as-is in one report |
| 4 | Maximum Subarray | Running best sum (Kadane) | Asked as-is in one report |
| 5 | Merge Sorted Array | Two pointers | Merge two sorted arrays, asked as-is in one report |
| 6 | Valid Triangle Number | Sorting and two pointers | Count triplets that form a triangle. Asked as-is in one report |
| 7 | Search a 2D Matrix II | Staircase search | Search a row-wise and column-wise sorted matrix (similar) |
| 8 | Intersection of Two Linked Lists | Pointer alignment | Merge point of two linked lists. Asked as-is in one report |
| 9 | Reverse Linked List | Pointer reversal | Asked as-is in one report |
| 10 | Binary Tree Inorder Traversal | Tree traversal, recursive then iterative | Asked as-is in one report |
| 11 | Construct Binary Tree from Inorder and Postorder Traversal | Tree reconstruction | Preorder from inorder and postorder (similar) |
| 12 | Wildcard Matching | String DP | Wildcard matching (similar) |
How to handle a question you have never seen
Most interview rounds are one problem plus follow-ups, so a repeatable method matters more than memorised solutions.
- Repeat the problem and one example. On a shared screen or codeshare page, write the example down.
- Say the brute force and its complexity. Interviewers in several reports asked for the naive solution first, and one asked for 2 or 3 approaches to the same problem.
- Name the bottleneck. Repeated lookups suggest a hash map; sorted input suggests two pointers or binary search; overlapping subproblems suggest DP.
- Say when you are stuck. One candidate said they had not studied a topic, and the interview continued with other questions.
- Code in small pieces while talking. If the interviewer does not want a run, write clean code with comments and trace it by hand.
- Dry-run one case and fix the wrong line. One candidate moved from 3 to 12 of 15 test cases after a dry run. Leave a few minutes for it.
Common preparation mistakes
Only 3 reports in the data were rejections and none gave a recruiter reason, so this section is advice drawn from what candidates described, not a list of reasons.
- Assuming a passing solution is enough. One candidate passed all test cases and explained recursion, memoisation and tabulation, and was still rejected; they put it down to luck, so do not rely on test cases alone.
- Skipping the fundamentals. Candidates were asked about normalisation, closures, paging, destructors and SQL; one reported being rejected at the HR round of a campus drive after an easy technical round.
- Treating puzzles as optional. Four reports included them, and a 2021 candidate was told to practise puzzles.
- Not explaining the approach. A candidate wrote that the interviewer wanted to see the approach more than the code.
Selected vs. rejected: do this, not that
No successful candidate described a perfect interview; what repeated were a few habits.
| Do this | Not that | What the reports show |
|---|---|---|
| Explain approach and complexity first | Start typing silently | One 2020 candidate wrote that the interview was about approach, not coding skill. |
| Dry-run and fix | Submit the first attempt | One candidate moved from 3 to 12 of 15 test cases after a dry run and feedback. |
| Solve puzzles aloud and ask for time | Go quiet | Four reports had puzzles; one candidate asked for more time and one was told to practise. |
| Know your project end to end | Give a one-line summary | Five reports included a project discussion; one lasted about 25 minutes. |
| Admit gaps and move on | Bluff | Two candidates said they had not studied a topic and the interview continued. |
If you remember only five things
- The process in one line. An OA, then one technical interview of 30 to 60 minutes, and sometimes a final behavioral round.
- The round format. One coding problem, some fundamentals, a puzzle or a project discussion.
- The core habit. Explain your approach and complexity out loud.
- The core topics. Arrays and strings, dynamic programming, CS fundamentals and puzzles are the core.
- The practice surface. Practise on HackerRank-style editors and on a shared screen with a naive then optimised solution.
FAQ
Is there an online assessment?
Yes, in most reports (15 of 23), and none described skipping it. The older ones were 90 to 120 minutes with MCQs and an essay, and the 2022 to 2024 ones described 2 or 3 coding questions.
Is system design asked?
No report described system design for an intern.
How long does it take?
From one to two days between the interview and the result in two older reports, to an unresolved hold email in a November 2026 report. One candidate in the 2025 US cycle said it took about a month to get an interview after the OA.
Will the interviewer help?
Reports varied. One interviewer was kind and told the candidate to relax during a demo problem; another asked the candidate to move quickly through a single problem.
Is there team matching?
Reports differ by cycle. A 2022 intern filled a teams form after an Interview Forum, and a candidate in the 2025 cycle said the recruiter had already found a team by the offer call.
Do interns get full-time offers?
Two product intern reports (2025 and 2026) describe pre-placement offers for MTS-1, so conversion exists, but the data cannot show a rate.
Other company and role guides
- Adobe software engineer interview guide
- Google software engineer intern guide
- Amazon software engineer intern guide
- Microsoft software engineer intern guide
- Intuit software development engineer intern guide
About this guide
The Codinzhub team researched and wrote this guide from 23 Adobe intern interview experiences, from 2018 to 2026, including experiences shared on Codinzhub. We kept only what candidates described. The questions are our own short summaries, and the practice links are similar problems, not the exact interview questions. If you interviewed recently, share your experience on Codinzhub and we will update this guide.
Disclaimer. Adobe's process changes by role, year and office. Use this guide to build a foundation, and confirm the current format with your recruiter.
Search the question bank
The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.
Showing 20 of 91 questions
Maximum Value on Tree Paths
A Adobe online assessment question shared on Codinzhub (Hackathon 2026).
Pair Sum (Easy Version)
A Adobe online assessment question shared on Codinzhub (Hackathon 2026).
Exactly K Distinct Contaminants
A Adobe online assessment question shared on Codinzhub (Hackathon 2026).
Closest Numbers
A Adobe online assessment question shared on Codinzhub (ACS Applied AI Engineer, off-campus).
Frequency Calculator
A Adobe online assessment question shared on Codinzhub (ACS Applied AI Engineer, off-campus).
Beautiful String (Regex)
A Adobe online assessment question shared on Codinzhub (IIT Roorkee).
Maximum Score 2
A Adobe online assessment question shared on Codinzhub (2025 PYQ, IIT-preferred).
Good Binary Strings
A Adobe online assessment question shared on Codinzhub (2025 PYQ, IIT-preferred).
Write 250 words on IoT or on your favourite project
Level: Product Intern.
Minimum number of umbrellas that cover exactly a target number of people
Level: Intern.
Print a matrix in spiral order as pseudocode
Level: Product Intern.
Tallest new tower at each empty position given its neighbours
Level: Product Intern.
Lexicographic rank of a string
Level: Product Intern.
Number that contains the digit K the most times
Level: Not reported.
Wildcard matching
Level: Not reported.
Kadane's algorithm
Level: Customer Engineering Intern.
Merge two sorted arrays, explaining both approaches
Level: Product Intern.
Minimum swaps to balance a set of parentheses
Level: Product Intern.
Pattern printing, a medium array question and a string question
Level: Intern.
Count triplets that can form a triangle
Level: Product Intern.
Keep preparing on Codinzhub
- Adobe interview questions and experiences — OA questions and interview experiences candidates shared for Adobe.
- Browse Adobe online assessment questions — filter the Codinzhub question bank by company.
- Amazon Software Engineer interview guide — the Amazon process, rounds and question patterns.
- Google Software Engineer interview guide — the Google process, rounds and question patterns.
- Flipkart Software Engineer interview guide — the Flipkart process, rounds and question patterns.
- All company interview guides — every guide on the Codinzhub blog.
Keep track of what you’ve learned.