01
What is defect density?
Show answer
The number of defects per size of software, for example defects per thousand lines of code or per module, used to compare quality.
Texas Instruments Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Texas Instruments hiring for Software Testing roles
Texas Instruments is an American semiconductor company that designs and manufactures analog chips and embedded processors used in industrial, automotive, personal electronics and communications products. Its Bengaluru centre, set up in 1985, was one of the first multinational R&D centres in India. It hires analog, digital, verification, embedded software and applications engineers.
For Software Testing roles, this Texas Instruments practice set focuses most on Bug Life Cycle and Jira (9), Agile, SQL and API Testing (6), STLC and Test Planning (5), Database Testing (4). It has 2 easy, 26 medium, 12 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Hardware & semiconductors
- Headquarters
- Dallas, USA
- Main India offices
- Bengaluru
Texas Instruments Software Testing interview process
- Online assessment (aptitude + electronics)
- Technical interview 1
- Technical interview 2
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Texas InstrumentsStart 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
02
What is defect leakage?
Show answer
Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.
03
Write a JQL query for open high or highest priority bugs in the current sprint of project PAY.
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
04
What is data masking and why is it used in test databases?
Show answer
Data masking replaces real sensitive values with realistic but fake ones, for example changing real phone numbers to valid-looking dummy numbers and real names to generated names. It lets teams test with production-like data volume and patterns without exposing customer information. It also supports compliance with India's Digital Personal Data Protection Act. Testers should check that masked data still passes validation rules and keeps relationships between tables intact.
05
What is pairwise testing?
Show answer
A technique that tests all pairs of input values instead of every combination, greatly reducing test cases while catching most defects.
06
What is defect removal efficiency?
Show answer
Defect removal efficiency shows how many defects the team found before release. DRE = defects found before release divided by (defects found before release plus defects found after release), multiplied by 100. If QA found 90 bugs and users reported 10, DRE is 90 percent. A falling DRE means testing is missing more defects, and the escaped bugs should be analysed to improve test coverage.
07
A developer changed a shared header component used on every page. What testing do you plan?
Show answer
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.
08
How would you add basic security testing to a team that has no security process?
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.
09
What do you check during UI or visual testing?
Show answer
Check alignment, spacing, fonts, colours and images against the design. Verify text is not cut off or overlapping, buttons and links look clickable and show hover and disabled states, and error messages appear in the right place. Check responsive behaviour on different screen widths and zoom levels. Confirm icons and images load and have alt text. Compare with the design file and take screenshots for any differences.
10
You change the order ID in a URL and see another customer's order. What is this and what do you do?
Show answer
This is an insecure direct object reference, a form of broken access control and a critical security bug, because any user can read other users' data. Stop exploring further beyond what is needed to confirm it, record the request, accounts used and evidence, and log it as a critical bug with restricted visibility. Inform the lead and security contact immediately. The fix is a server-side ownership check on every request.
11
A client needs WCAG 2.2 AA compliance before launch in two weeks. How do you plan the testing?
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.
12
What are test data and how do you prepare them?
Show answer
The inputs used in tests. Prepare using valid, invalid and boundary values from production-like but masked data, spreadsheets or generators.
13
A report shows duplicate rows after a new release. How do you investigate in the database?
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.
14
What does INVEST mean for user stories?
Show answer
INVEST is a checklist for good user stories: Independent, Negotiable, Valuable, Estimable, Small and Testable. For testers, testable is the most important: a story must have clear acceptance criteria so you can say pass or fail. Small stories are easier to test within a sprint. If a story fails INVEST, raise it in refinement rather than discovering the gaps during testing.
15
SQL: check that no user has more than one active subscription.
Show answer
-- Business rule: at most one ACTIVE subscription per user
SELECT user_id, COUNT(*) AS active_count
FROM subscriptions
WHERE status = 'ACTIVE'
GROUP BY user_id
HAVING COUNT(*) > 1;
-- Expected result: no rows
16
A developer asks you to test a feature that has no acceptance criteria. How do you proceed?
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.
17
You join a project in the middle of a release. How do you plan your testing?
Show answer
Spend the first day learning the scope: read the release notes, user stories and test plan, and ask the lead what is at risk. Get access to the environment, tracker and test repository. Pick up a clearly defined module, run its existing test cases to learn the application and note gaps. Ask questions early in stand-up. Within a few days, take ownership of retesting and regression for that module.
18
How do you plan testing for a feature that depends on a third-party service?
Show answer
Identify the integration points and the service's sandbox, limits and test data. Plan to test with a mock or stub early for our logic and error handling, then against the real sandbox for integration. Include failure scenarios: timeout, slow responses, invalid data and the service being down. Add the dependency to the risk list, with contacts and a fallback plan, and confirm production credentials and monitoring before go-live.
19
User reviews say the app drains the battery. How do you investigate?
Show answer
Collect details from reviews and support: devices, OS versions and app version when it started. Compare battery usage of the current and previous versions on the same devices over a typical session and while idle in background. Use profiling tools to look for background location, wake locks, frequent sync or network polling. Share measurements with developers, verify the fix with the same method, and add a battery check to release testing.
20
What is the difference between DELETE and TRUNCATE?
Show answer
DELETE removes selected rows and can be rolled back; TRUNCATE quickly removes all rows and resets the table.
21
SQL: find duplicate emails.
Show answer
SELECT email, COUNT(*)
FROM users
GROUP BY email
HAVING COUNT(*) > 1;
22
Write test cases for an online money transfer.
Show answer
Valid transfer, insufficient balance, daily limit, wrong beneficiary, OTP failure, network drop mid-transaction, duplicate click and statement update.
23
How do Selenium, Playwright and Cypress differ at a high level?
Show answer
Selenium is the oldest, uses the WebDriver standard, supports many languages like Java, Python and C# and every major browser, and is common in older enterprise suites. Playwright supports TypeScript, Python, Java and .NET, runs Chromium, Firefox and WebKit, and has built-in auto-waiting, tracing and parallel runs. Cypress runs inside the browser with JavaScript or TypeScript, has a friendly runner and is popular with front-end teams.
24
Tell me about a time you organised or ran a bug bash before a release.
Show answer
Situation: a new seller onboarding flow was due in a week and only two testers had seen it. Task: I wanted wider coverage quickly. Action: I set up a one-hour bug bash with developers, product and support, shared test accounts, focus areas and a simple bug form, then triaged findings with the lead. Result: we found 18 issues, including two blockers on low-end phones, and fixed them before launch.
25
What are the main testing differences between Android and iOS?
Show answer
Android has many manufacturers, screen sizes and OS versions with custom skins, so device fragmentation and background-kill behaviour need more coverage. iOS has fewer devices but strict permission, privacy and store review rules. Navigation differs: Android has a system back button or gesture, iOS relies on in-app navigation and swipe back. Notification, permission and file-access behaviours also differ, so test cases need platform-specific steps.
26
The developer says "it's not a bug". What do you do?
Show answer
Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.
27
What is JSON schema validation in API testing?
Show answer
JSON schema validation checks that a response has the expected structure: required fields are present, data types are correct, formats like email or date are valid and no unexpected fields appear. Instead of checking only one value, it protects against contract changes that break the app. In Postman you can validate a response against a schema in the test script, and run it on every request in a collection.
28
A screen reader announces 'button, button, button' on a toolbar. What is the bug and how do you report it?
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.
29
What is a stored procedure and how do you test it?
Show answer
A stored procedure is a named block of SQL logic saved in the database and called with parameters, for example a procedure that calculates monthly interest. To test it, call it with valid, boundary and invalid inputs, check the returned values or result sets, verify the rows it inserts or updates, check error handling for bad parameters and confirm it rolls back on failure. Also check its run time with realistic data volumes.
30
Explain three-point estimation for testing with an example.
Show answer
Three-point estimation uses an optimistic (O), most likely (M) and pessimistic (P) estimate for each task. The weighted formula is (O + 4M + P) divided by 6. If testing a module would take 4 days at best, 6 days most likely and 14 days at worst, the estimate is (4 + 24 + 14) / 6 = 7 days. It includes uncertainty in a single number and is often combined with a work breakdown of test activities.
31
What is a bug bash and how do you run one?
Show answer
A bug bash is a short, time-boxed session where people from across the team, including developers, product and support, test the product together to find as many issues as possible before a release. To run one, share a build, scope and test accounts, assign focus areas, give a simple bug template and a shared board, then triage findings at the end. It brings fresh eyes and finds usability issues formal tests miss.
32
What is defect prevention and what practical techniques does a QA team use?
Show answer
Defect prevention focuses on stopping defects from being introduced instead of only finding them. Practical techniques include requirement reviews and clear acceptance criteria, Three Amigos sessions, design and code reviews, unit testing standards, coding checklists from past bugs, root cause analysis of escaped defects, and training on common mistakes. Track whether repeated defect types fall over time to prove the effort works.
33
What is idempotency in APIs and how do you test it?
Show answer
An operation is idempotent if repeating the same request gives the same result as doing it once. GET, PUT and DELETE should be idempotent; POST usually is not. To test, send the same request several times and check the server state does not change after the first call. For payments, check that retrying with the same idempotency key does not create a second charge, which protects users during network retries.
34
What is JQL?
Show answer
JIRA Query Language, used to search issues, for example project = ABC AND status = Open AND priority = High.
35
How do you test an application with no documentation?
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.
36
Write SQL to verify an order was saved correctly.
Show answer
SELECT status, amount FROM orders WHERE order_id = 'ORD123';
-- compare with the UI, then check the matching rows in order_items
37
How do you estimate testing effort?
Show answer
Break the work into modules and test cases, use past velocity or three-point estimation (optimistic, likely, pessimistic), add time for test data, environment issues, retesting and regression, and keep a risk buffer.
38
A web app gets slower the longer a user keeps it open. How do you check for a memory leak as a manual tester?
Show answer
A memory leak happens when an application keeps holding memory it no longer needs, so usage grows the longer it runs. A manual tester may notice the app getting slower over a long session, a browser tab using more and more memory in Task Manager or the browser's memory panel, or a mobile app crashing after repeatedly opening and closing a screen. Report the steps, duration and memory readings over time.
39
How do you test biometric login with fingerprint or face unlock?
Show answer
Test enabling biometrics in app settings after a password login. Verify login with a registered fingerprint or face, and failure with an unregistered one, falling back to PIN or password after the allowed attempts. Remove or add a fingerprint in device settings and check the app asks for re-authentication. Test devices without biometric hardware, disabled biometrics and app behaviour after an OS update or reinstall.
40
What do you check in mobile accessibility testing?
Show answer
Turn on the screen reader, TalkBack on Android or VoiceOver on iOS, and check every button, image and field has a meaningful label and the reading order is logical. Check text scales with system font size, colour contrast is sufficient and touch targets are large enough, about 48 by 48 density-independent pixels. Make sure information is not shown by colour alone and that the app works without complex gestures.
Tips to crack the Texas Instruments Software Testing interview
- Revise analog electronics, op-amps, circuit analysis and semiconductor device basics, which are core topics for many TI roles.
- For digital and embedded roles, revise digital design, microcontrollers and C programming with practical examples from lab work.
- Be ready to solve circuit problems on paper and explain each step clearly, as interviewers often focus on fundamentals.
- 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; Texas Instruments interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Texas Instruments Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + electronics); Technical interview 1; Technical interview 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 Texas Instruments Software Testing interview?
This practice set leans on Bug Life Cycle and Jira (9), Agile, SQL and API Testing (6), STLC and Test Planning (5), Database Testing (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Texas Instruments interviewers ask you to walk through real work.
Are these the exact questions asked at Texas Instruments?
No. These are curated practice questions that match the skills and difficulty usually tested in hardware & semiconductors interviews like Texas Instruments's. They are not a leaked or verified list of past questions.
Where does Texas Instruments hire Software Testing professionals in India?
Texas Instruments has large teams in Bengaluru. Openings and locations change often, so check the Texas Instruments careers page and filter by city and experience.
Software Testing questions for similar companies
Hardware & semiconductors
NVIDIA
Software Testing interview questions
Pune, Bengaluru, Hyderabad
View questionsHardware & semiconductors
Broadcom
Software Testing interview questions
Bengaluru, Pune, Chennai
View questionsHardware & semiconductors
Samsung
Software Testing interview questions
Bengaluru, Noida, Delhi
View questionsHardware & semiconductors
Dell Technologies
Software Testing interview questions
Bengaluru, Hyderabad
View questionsHardware & semiconductors
Apple
Software Testing interview questions
Hyderabad, Bengaluru, Mumbai +1
View questionsHardware & semiconductors
AMD
Software Testing interview questions
Bengaluru, Hyderabad
View questionsMore ways to practise
Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets