Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About GlobalLogic hiring for Software Testing roles
GlobalLogic, a Hitachi Group company, is a digital engineering services firm working on product development, embedded software, cloud and data for clients in automotive, healthcare, media and telecom. Its India engineering centres are among its largest. It hires for software engineers, test engineers, data engineers and embedded developers.
For Software Testing roles, this GlobalLogic practice set focuses most on Manual Testing Basics (6), Agile, SQL and API Testing (6), Bug Life Cycle and Jira (5), Testing Types (5). It has 20 easy, 20 medium questions, so you can start easy and work up to the harder ones.
Company type
IT services
Headquarters
San Jose, California, USA
Main India offices
Noida, Bengaluru, Gurugram, Hyderabad, Nagpur
GlobalLogic Software Testing interview process
Online assessment (aptitude + coding)
Technical round 1
Technical round 2
HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for GlobalLogicStart 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
Design EP and BVA tests for a password that must be 8 to 16 characters and contain at least one digit.
Length partitions: below 8 (invalid), 8 to 16 (valid), above 16 (invalid). Boundaries: 7, 8, 9, 15, 16 and 17 characters. Digit partitions: contains a digit (valid), no digit (invalid). Sample tests: 'abc1234' with 7 characters is rejected, 'abcdefg1' with 8 is accepted, a 16-character value with a digit is accepted, 17 characters is rejected, and 'abcdefgh' with no digit is rejected. Also test empty input and spaces.
02
What are components, labels and fix versions in Jira?
Components are fixed sub-parts of a project, such as Payments or Login, often with a default owner. Labels are free-text tags, such as regression or ui, that anyone can add for grouping. Fix version is the release in which the issue is planned to be fixed, while affects version is where the bug was found. Testers use these fields to filter bugs and to build release-wise reports.
A test harness is the setup of drivers, stubs, test data, scripts and tools needed to run tests on a component and collect results, especially when the full system is not available. For example, to test a pricing module, a harness can feed it input files, stub the tax service and compare outputs with expected values. In automation, the framework, runner and reporting together are often called the harness.
04
Difference between black box, white box and grey box testing?
-- Orders cannot be placed in the future
SELECT id, order_date, status
FROM orders
WHERE order_date > CURRENT_TIMESTAMP;
-- Expected result: no rows. If rows appear, check time zone handling and input validation.
Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.
A high-level test case states what to test without detailed steps or exact data, for example 'Verify user can reset password using registered email'. A low-level test case gives exact steps, test data and expected results for each step. High-level cases are quick to write and suit experienced testers or changing features. Low-level cases suit regulated projects, new team members and cases that will later be automated.
SELECT status, COUNT(*) AS total
FROM orders
WHERE created_at >= CURRENT_DATE
AND created_at < CURRENT_DATE + INTERVAL '1 day'
GROUP BY status
ORDER BY total DESC;
12
What is the difference between path parameters, query parameters and the request body?
Path parameters identify a specific resource and are part of the URL, as in /users/42. Query parameters filter, sort or paginate and come after a question mark, as in /users?city=Pune&page=2. The request body carries data for creating or updating, usually JSON, in POST, PUT or PATCH. Testers check invalid values in each: a wrong ID in the path, unknown query parameters and missing body fields.
13
How do you test location-based features in a mobile app?
Test with location permission allowed, denied and approximate only. Use mock location tools to simulate different cities and moving routes. Verify the app shows nearby results correctly, updates location while moving and handles GPS turned off. Check accuracy indoors and with weak GPS, battery impact of continuous tracking and that background location is used only if needed and explained to the user.
The test basis is the set of documents and knowledge from which test cases are derived. It includes requirement specifications, user stories with acceptance criteria, design documents, wireframes, API contracts, business rules and even existing system behaviour. A good test basis lets you trace each test case back to a requirement. If the test basis is weak or missing, testers must clarify it before or while testing.
15
When should you reopen a bug and when should you log a new one?
Reopen the bug when the same issue, with the same steps and expected result, still fails after the fix. Log a new bug when the fix works but a different problem appears, even in the same screen, or when the original bug has already been closed in a past release. Link the new bug to the old one. Mixing different problems in one reopened ticket confuses tracking and metrics.
16
What happens in the requirement analysis phase of STLC?
In requirement analysis, the testing team studies the requirements to understand what needs to be tested. They identify testable requirements, clarify doubts with the business analyst or client, decide test types needed, note automation candidates and look at environment needs. The outputs are a list of questions, a requirement traceability matrix draft and an automation feasibility note. Problems found here are the cheapest to fix.
17
What is the difference between authentication and authorization?
Authentication checks who you are, for example by password, OTP or biometrics. Authorization checks what you are allowed to do after you are identified, such as whether you can view reports or delete users. Authentication comes first. Testers check authentication with wrong credentials and expired sessions, and authorization by trying actions with a lower-privilege account or by calling restricted URLs and APIs directly.
18
Explain three usability heuristics with examples from a web app.
Visibility of system status: after clicking Pay, show a progress indicator so users do not click again. Error prevention: disable the Submit button until required fields are valid, or ask for confirmation before deleting an account. Recognition rather than recall: show recently searched items and saved addresses instead of making users remember them. Other heuristics include consistency, user control with undo, and clear help for recovering from errors.
Three Amigos is a short meeting where a business person or product owner, a developer and a tester discuss a story before development. The business explains the need, the developer considers how to build it and the tester asks what could go wrong and how it will be verified. The output is clear acceptance criteria and example scenarios. It prevents misunderstandings and reduces bugs found late.
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.
24
How do you test API error handling for invalid input?
Send requests with missing required fields, wrong data types, values beyond limits, invalid formats such as a bad email, unknown fields and an empty or malformed JSON body. The API should return a 4xx code such as 400 or 422, a clear error message that names the field, and no stack trace or database details. Also check that nothing was partly saved in the database after the failed request.
End-to-end testing checks a complete business flow from the user's first action to the final result, across all connected parts: UI, APIs, database, third-party services and notifications. For example, in online shopping: search a product, add to cart, pay, receive the confirmation email and see the order in the account. It finds integration issues that module-level testing misses, but it is slower and needs stable environments.
26
What sensitive data checks do you do in API responses and logs?
Check that responses return only needed fields, with no passwords, password hashes, full card numbers, full ID numbers or internal keys. Verify personal data is masked where required, for example only the last four digits of a phone number. Look at application and browser console logs for tokens or personal data. Check error responses do not expose stack traces, SQL or server versions. Raise any leak as a high-severity bug.
A deep link opens a specific screen inside the app from a URL, email, SMS, QR code or notification. Test that each link opens the correct screen with the right data when the app is installed, closed or running in background. If the app is not installed, it should open the store page or a web fallback. Test links that need login, expired or invalid links, and that parameters cannot be tampered with to access other users' data.
28
How do you test session management in a web application?
Check that a new session ID is created after login, and that the session expires after the defined idle time. Verify logout invalidates the session on the server, so pressing back or reusing the old cookie does not work. Check that cookies use Secure, HttpOnly and SameSite flags. Test concurrent logins if they are limited, and that changing the password ends other sessions. Session IDs must not appear in URLs.
29
What is the difference between a build and a release?
A build is a compiled version of the software created from the latest code, often many times a day, and given to QA for testing. A release is a tested, approved version delivered to customers or production, usually with release notes and a version number. Many builds can go through testing before one of them is promoted as a release. Testers always note the build number in bug reports.
30
How do you do cross-browser testing and choose which browsers to cover?
Use analytics to pick browsers and versions that most real users have, plus the ones listed in the requirement, usually the latest two versions of major desktop and mobile browsers. Run the main flows on each and check layout, fonts, forms, date pickers, file upload and JavaScript errors in the console. Use responsive mode for screen sizes, and real devices or a cloud device lab for mobile browsers.
Situation: while testing a leave application form, every test case passed. Task: I still felt the flow was confusing. Action: I noticed the date picker started on Sunday and the half-day option was hidden under 'More', so I asked two colleagues to apply for leave while I watched; both made mistakes. I logged a usability suggestion with notes. Result: product moved the option and support queries dropped.
34
A form saves names with an apostrophe, like O'Brien, incorrectly or fails to save them. What do you test?
This suggests the input is not handled safely, possibly string-built SQL, which is also a SQL injection risk. Test names with apostrophes, double quotes, Hindi and other Unicode text, emojis, leading spaces and maximum length. Query the database to confirm the exact stored value and character encoding. Then check the value displays correctly everywhere it is read back. Log a high-severity bug and mention the possible injection risk.
Retest the change itself, then run a focused regression on every page type that uses the header: home, listing, detail, checkout and account. Check navigation links, search, login and logout state, cart count and the mobile menu. Do cross-browser and responsive checks because layout changes affect all sizes. A quick visual comparison against the previous build helps spot alignment issues across many pages.
38
What is a database view and what do you verify when testing it?
A view is a saved query that behaves like a virtual table, often used for reports or to hide sensitive columns. When testing it, compare its output with the same query run on the base tables, check filters and joins return the right rows, confirm hidden columns such as salary are really absent, check behaviour when base data changes and verify that users without permission on the base tables can still read the view if intended.
A locator tells the automation tool how to find an element on the page so it can click, type or check it. Common types are ID, name, CSS selector, XPath, link text, and in modern tools role-based locators such as a button with name Login, plus label, placeholder and test ID locators. A good locator is unique, readable and unlikely to change when the page design changes.
Tips to crack the GlobalLogic Software Testing interview
Revise OOP, data structures and one programming language in depth, as GlobalLogic interviews focus on engineering fundamentals.
Learn about its Hitachi Group ownership and work in automotive and embedded software if you have that interest.
Prepare to discuss testing practices, including unit tests and automation, for both developer and QA roles.
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; GlobalLogic interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the GlobalLogic Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + coding); Technical round 1; Technical round 2; 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 GlobalLogic Software Testing interview?
This practice set leans on Manual Testing Basics (6), Agile, SQL and API Testing (6), Bug Life Cycle and Jira (5), Testing Types (5). Revise those first, then practise explaining one or two of your own projects end to end, because most GlobalLogic interviewers ask you to walk through real work.
Are these the exact questions asked at GlobalLogic?
No. These are curated practice questions that match the skills and difficulty usually tested in it services interviews like GlobalLogic's. They are not a leaked or verified list of past questions.
Where does GlobalLogic hire Software Testing professionals in India?
GlobalLogic has large teams in Noida, Bengaluru, Gurugram, Hyderabad, Nagpur. Openings and locations change often, so check the GlobalLogic careers page and filter by city and experience.