Skip to content

Adobe Software Testing Interview Questions & Answers

Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.

About Adobe hiring for Software Testing roles

Adobe makes creative, document and marketing software including Photoshop, Acrobat, Premiere Pro, Adobe Express and Adobe Experience Cloud. Its Noida and Bengaluru centres are among its largest engineering sites globally. It hires in India for software engineers, quality engineers, data scientists and analysts working on product analytics, marketing data and AI features such as Firefly.

For Software Testing roles, this Adobe practice set focuses most on Agile, SQL and API Testing (6), Accessibility & Usability Testing (5), Automation Basics for Manual Testers (5), Performance and Security Basics (5). It has 1 easy, 27 medium, 12 hard questions, so you can start easy and work up to the harder ones.

Company type
Product
Headquarters
San Jose, California, USA
Main India offices
Noida, Bengaluru, Gurugram

Adobe Software Testing interview process

  1. Online assessment (aptitude + coding)
  2. Technical round 1 (DSA)
  3. Technical round 2 (DSA + CS fundamentals)
  4. Hiring manager round
  5. HR round

Typical pattern based on public candidate experiences. Rounds vary by role, team and year.

Solved for AdobeStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
01

What is the difference between quality assurance and quality control?

Save to ▾
Show answer
Quality assurance is process-oriented and preventive: it sets standards, reviews and checklists so defects are not introduced in the first place. Quality control is product-oriented and detective: it checks the actual build through testing and inspection to find defects. For example, introducing a requirement review checklist is QA, while executing test cases on a release build is QC. Software testing is one activity inside quality control.
02

What is TDD vs BDD?

Save to ▾
Show answer
TDD writes unit tests before code to drive design; BDD describes behaviour in business language scenarios that become automated acceptance tests.
03

How do you test touch target size and gestures for accessibility in a mobile app?

Save to ▾
Show answer
Check that buttons and icons are large enough to tap without hitting neighbours: Android guidance is 48 by 48 dp and iOS is 44 by 44 points. Test with large font settings and one-handed use. Any action using complex gestures, such as swipe to delete or pinch, must have a simple tap alternative. Then turn on TalkBack and VoiceOver and confirm each control can be focused, named and activated.
04

Write test cases for a signup form.

Save to ▾
Show answer
Mandatory fields, email format, password rules, duplicate email, terms checkbox, captcha, confirmation email and field length limits.
05

How do you break a requirement into testable conditions?

Save to ▾
Show answer
Read the requirement and identify inputs, outputs, business rules, user roles and states. Turn each rule into a condition with an expected result, then add negative and boundary conditions. For example, 'users can withdraw up to 10,000 per day' becomes: withdraw below the limit, exactly at the limit, above the limit, multiple withdrawals adding up to the limit, and the limit resetting the next day. Each condition then becomes one or more test cases.
06

A manager wants 100 percent test automation. How do you respond?

Save to ▾
Show answer
I agree with the goal of faster and more reliable testing, but explain that 100 percent is neither possible nor useful. Exploratory testing, usability, visual judgement and brand-new features need people, and some flows like real payments or OTP are costly to automate reliably. I would propose clear targets instead, such as automating all critical regression and smoke flows, with metrics like regression time cut from three days to four hours.
07

How do you plan testing for a two-week sprint?

Save to ▾
Show answer
In sprint planning, review each story's acceptance criteria and estimate test effort, including test data and regression. Write test cases in the first days while development starts. Ask for early builds so testing is spread across the sprint, not crowded at the end. Keep time for regression and bug retesting in the last two or three days. Track progress on the board and raise risks in stand-up.
08

The app crashes only on one older Android version. What are your steps?

Save to ▾
Show answer
Reproduce it on that exact OS version, using a real device or an emulator image, and note the device model and app build. Capture the crash log and stack trace. Check if the code uses an API or library not supported on that version, or a permission or storage behaviour that changed. Log the bug with logs and the minimum supported version from the requirement, so the team can decide to fix it or raise the minimum version.
09

A load test shows good response times but a 15 percent error rate. How do you interpret it?

Save to ▾
Show answer
The result is a failure, not a pass. Failed requests often return quickly, so they make response times look better than they are. Check which requests fail and with which errors, such as 500, 503 or timeouts, and when errors started relative to the load level. Look at server logs, connection pool and thread limits. Also confirm the script is not wrong, for example expired tokens or bad test data.
10

How do you chain requests in Postman by passing a token from login to the next call?

Save to ▾
Show answer
// Tests tab of the Login request const body = pm.response.json(); pm.environment.set('authToken', body.token); // Next request header: // Authorization: Bearer {{authToken}} // Postman replaces {{authToken}} with the saved value
11

A training portal is adding recorded video lessons and podcasts. What accessibility checks do you run?

Save to ▾
Show answer
Check that prerecorded videos have accurate, synchronised captions, not just auto-generated ones with errors, and that audio-only content like podcasts has a transcript. Important visual information that is not spoken should have audio description or be covered in the transcript. Media should not autoplay with sound, and player controls must work by keyboard and be announced by screen readers. Also check that nothing flashes more than three times per second.
12

What is the difference between statement coverage and branch coverage?

Save to ▾
Show answer
Statement coverage measures the percentage of code statements executed by tests. Branch coverage measures whether every decision outcome, true and false, has been executed. Branch coverage is stronger: for 'if (amount > 1000) applyDiscount()', one test with 1500 gives 100 percent statement coverage, but you need a second test with 500 to cover the false branch. 100 percent branch coverage implies 100 percent statement coverage, not the other way round.
13

How do you capture screenshots, videos and traces when an automated test fails?

Save to ▾
Show answer
Most frameworks support this through configuration. In Playwright, set screenshot to only-on-failure, video to retain-on-failure and trace to on-first-retry in the config, then open the trace viewer to step through actions, network calls and the page state. In Selenium, call save_screenshot in a teardown hook when a test fails. Store these artefacts in CI so anyone can debug the failure without rerunning it.
14

What is the difference between a bug and an enhancement?

Save to ▾
Show answer
A bug is behaviour that deviates from agreed requirements; an enhancement is a new or improved capability beyond the current requirements.
15

Your backlog has 200 low-priority bugs and it is becoming unmanageable. How do you handle it?

Save to ▾
Show answer
Run a backlog grooming session with the product owner. Close bugs that are obsolete, no longer reproducible or for retired features. Merge duplicates. Group the rest by module and user impact, and ask whether a few related bugs can be fixed together as one story. Agree to reserve a small share of each sprint for bug fixes. Set an ageing rule, for example review any bug older than 90 days.
16

A manager says the app has 50,000 daily users, so the load test must run 50,000 virtual users at once. How do you respond?

Save to ▾
Show answer
Explain that daily users are not concurrent users. Of 50,000 users a day, only a fraction are active at the same moment, and even they pause between actions because of think time. Use analytics to find the real peak concurrency and request rate, for example 1,500 concurrent users at peak hour, and model that with a safety margin. Running 50,000 users clicking at once tests a load that never happens and wastes effort.
17

What is configuration testing?

Save to ▾
Show answer
Verifying the application works across different hardware, software and settings combinations.
18

An automated test keeps failing because an element's ID is generated differently on every build. What do you do?

Save to ▾
Show answer
Stop using the dynamic ID. Look for a stable alternative: the element's role and visible name, its label, a stable attribute, or a relative locator based on a nearby fixed element. The best long-term fix is asking developers to add a data-testid attribute. Avoid partial matches on random strings, which can break again. Then update the locator in the page object so every test using it is fixed at once.
19

What is accessibility testing?

Save to ▾
Show answer
Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.
20

Write a SQL query to find duplicate records.

Save to ▾
Show answer
SELECT email, COUNT(*) FROM users GROUP BY email HAVING COUNT(*) > 1;
21

A security scan says your login page can be loaded inside a frame on other sites. What is the risk and how do you confirm it?

Save to ▾
Show answer
Clickjacking tricks a user into clicking something on your site while it is hidden inside a frame on an attacker's page, for example a hidden Transfer button under a fake Play button. A tester checks whether sensitive pages can be loaded in an iframe on another site, and inspects response headers for Content-Security-Policy frame-ancestors or X-Frame-Options set to DENY or SAMEORIGIN. If the page loads in the frame, log it.
22

How do you test a mobile app's offline mode and data sync?

Save to ▾
Show answer
Turn off the network and perform supported actions, such as creating, editing and deleting records, and check they are saved locally with a pending status. Reconnect and verify everything syncs once, in order, with no duplicates. Test conflicts, where the same record is changed on two devices, and confirm the agreed rule applies. Test sync after app restart, on a slow network and when the server rejects a change.
23

A developer asks you to test a feature that has no acceptance criteria. How do you proceed?

Save to ▾
Show answer
First ask the product owner or business analyst for the expected behaviour and write down the answers as draft acceptance criteria. Meanwhile, explore the feature, compare it with similar existing features and list assumptions. Share the assumptions in the story so everyone agrees before you sign off. Raise the missing criteria in the next refinement so future stories are not picked up without them.
24

How would you test rate limiting on a public API?

Save to ▾
Show answer
Find the documented limit, for example 100 requests per minute per key. Send requests just below and above the limit and check that extra requests get 429 Too Many Requests with a Retry-After header. Verify the counter resets after the window and that limits apply per key or per IP as designed. Check that one user hitting the limit does not block others, and that normal traffic is not throttled.
25

A client needs WCAG 2.2 AA compliance before launch in two weeks. How do you plan the testing?

Save to ▾
Show answer
Agree on scope: key user journeys and page templates, not every page. Day one, run automated scans on all templates to fix easy issues fast. Then do manual checks of each journey with keyboard, NVDA, VoiceOver on mobile, zoom and contrast. Log issues with WCAG references and severity, and get blockers fixed first. Retest fixes and deliver a conformance summary with known issues. Be honest if full compliance is not realistic.
26

Write test cases for an online money transfer.

Save to ▾
Show answer
Valid transfer, insufficient balance, daily limit, wrong beneficiary, OTP failure, network drop mid-transaction, duplicate click and statement update.
27

Write a simple Playwright test in TypeScript that logs in and checks the dashboard heading.

Save to ▾
Show answer
import { test, expect } from '@playwright/test'; test('valid user can log in', async ({ page }) => { await page.goto('https://qa.example.com/login'); await page.getByLabel('Email').fill('qa.user@test.com'); await page.getByLabel('Password').fill('Secret@123'); await page.getByRole('button', { name: 'Login' }).click(); await expect(page.getByRole('heading', { name: 'Dashboard' })).toBeVisible(); });
28

Notifications arrive late, and some screens look broken, only on certain Android phone brands. Why can this happen and what do you test?

Save to ▾
Show answer
Android phone makers ship their own skins and settings on top of Android, so the same app can behave differently. Common problems are aggressive battery savers that kill background tasks and delay notifications, different permission screens, custom fonts and display scaling, camera differences and modified WebViews. Pick devices from the brands most used by your audience and test background work, notifications, camera and layout on each.
29

How would you test a login page for security?

Save to ▾
Show answer
Check SQL injection, brute-force lockout, password masking, session timeout, HTTPS, cookie flags, error messages not revealing users and password reset flow.
30

Product is running an A/B test on the checkout button. What does QA need to verify?

Save to ▾
Show answer
QA does not decide which version wins, but makes sure the experiment is trustworthy. Verify both variants work end to end, users are split in the agreed ratio, each user sees the same variant consistently across sessions, and analytics events fire correctly for each group. Also check that turning the experiment off returns everyone to the default. A broken tracking event can make the whole experiment's result wrong.
31

How would you add basic security testing to a team that has no security process?

Save to ▾
Show answer
Start with low-cost steps. Add an OWASP-based security checklist to the definition of done for stories touching login, payments or personal data. Train testers on access control, injection and session checks. Add automated dependency and vulnerability scans to the CI pipeline. Include negative authorization tests in API suites. Arrange a penetration test before major releases and track security bugs separately with clear severity rules.
32

A report shows duplicate rows after a new release. How do you investigate in the database?

Save to ▾
Show answer
Run the report query with GROUP BY on the business key and HAVING COUNT(*) > 1 to find which records repeat. Then check whether the duplicates exist in the base table or are created by the query, usually a new join to a one-to-many table such as addresses. Compare the query before and after the release. Include the duplicate keys, the count and the suspected join in the bug report.
33

A screen reader announces 'button, button, button' on a toolbar. What is the bug and how do you report it?

Save to ▾
Show answer
The toolbar uses icon-only buttons without accessible names, so users hear the role but not the purpose. Report it with the page, the screen reader and browser versions, the exact announcement and the expected one, such as 'Bold, toggle button, not pressed'. Reference WCAG 4.1.2 Name, Role, Value. The fix is an aria-label or visually hidden text on each button, plus a tooltip that also helps sighted users.
34

What are the typical JIRA workflows for bugs?

Save to ▾
Show answer
Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.
35

Write a JQL query for open high or highest priority bugs in the current sprint of project PAY.

Save to ▾
Show answer
project = PAY AND issuetype = Bug AND statusCategory != Done AND priority in (Highest, High) AND sprint in openSprints() ORDER BY priority DESC, created ASC
36

The sprint ends tomorrow and two stories are still in testing. What do you do?

Save to ▾
Show answer
Tell the Scrum Master and product owner today, not at the review. Focus testing on the acceptance criteria and the riskiest paths of the story with the most value, and ask a developer to help with test data or simple checks. If a story cannot be finished with quality, it should be carried over, not marked done with untested parts. Raise the cause in the retrospective, such as late handover.
37

How do you test a web page with a screen reader?

Save to ▾
Show answer
Turn on the screen reader, for example NVDA with a browser, and listen rather than look. Navigate by headings to check the structure is logical, by landmarks to find main regions and by Tab through controls. Each control should announce a clear name, role and state, such as 'Subscribe, checkbox, not checked'. Check images, form errors, dynamic updates like cart counts and dialogs. Note exactly what was announced in bug reports.
38

How do you test an application with no documentation?

Save to ▾
Show answer
Talk to developers and users, explore the product, review similar systems, create notes and mind maps, confirm assumptions and write test cases as you learn.
39

Tell me about a time you worked with developers to make an application easier to automate.

Save to ▾
Show answer
Situation: our UI scripts broke almost every sprint because of generated IDs and CSS class changes. Task: as the QA lead I needed stable tests. Action: I showed developers the failure history, proposed adding data-testid attributes and accessible labels to key components and added a short checklist to the pull request template. Result: within two sprints locator-related failures dropped by most of the previous level and maintenance time fell sharply.
40

How do you test database integrity using SQL?

Save to ▾
Show answer
Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.

Tips to crack the Adobe Software Testing interview

  • Practise DSA and puzzles, which have commonly appeared in Adobe interviews alongside OOP and operating system questions.
  • Use Adobe Acrobat or Express and be ready to suggest a feature or test plan for one of its products.
  • For data roles, read about Adobe Analytics and Experience Platform, since many teams work on customer and marketing data.
  • Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
  • Practise the hard questions on this page aloud; Adobe interviewers usually ask follow-ups on your first answer.

Frequently asked questions

How many rounds are there in the Adobe Software Testing interview?

Candidates usually go through 5 stages: Online assessment (aptitude + coding); Technical round 1 (DSA); Technical round 2 (DSA + CS fundamentals); Hiring manager round; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.

Which topics should I prepare for the Adobe Software Testing interview?

This practice set leans on Agile, SQL and API Testing (6), Accessibility & Usability Testing (5), Automation Basics for Manual Testers (5), Performance and Security Basics (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Adobe interviewers ask you to walk through real work.

Are these the exact questions asked at Adobe?

No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Adobe's. They are not a leaked or verified list of past questions.

Where does Adobe hire Software Testing professionals in India?

Adobe has large teams in Noida, Bengaluru, Gurugram. Openings and locations change often, so check the Adobe careers page and filter by city and experience.

Software Testing questions for similar companies