Manual Testing Interview Questions
100 Interview Questions for Freshers 1 -2 Experienced Candidates
Manual Testing Interview Questions
1. What is Exploratory Testing?
Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution.
The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2-hour) time-boxed test effort, and the objectives and possible approaches to be used.
The test design and test execution activities are performed in parallel typically without formally documenting the test conditions, test cases, or test scripts.
This does not mean that other, more formal testing techniques will not be used.
For example, the tester may decide to use boundary value analysis but will think through and test the most important boundary values without necessarily writing them down.
Some notes will be written during the exploratory-testing session so that a report can be produced afterward.
2. What is “use case testing”?
To identify and execute the functional requirement of an application from start to finish “use case” is used and the techniques used to do this are known as “Use Case Testing.”
3. What is Software Testing?
Software Testing is a process used to identify developed software’s correctness, completeness, and quality.
It includes a series of activities conducted to find software errors so that they can be corrected before the product is released to the market.
4. Why is Software Testing Required?
Software testing is a mandatory process that guarantees that the software product is safe and good enough to be released to the market.
Here are some compelling reasons to prove testing is needed:
- It points out the defects and errors that were made during the development phases.
- Reduces the coding cycles by identifying issues at the initial stage of development.
- Ensures that software application requires lower maintenance cost and results in more accurate, consistent, and reliable results.
- Testing ensures that the customer finds the organization reliable and that their satisfaction with the application is maintained.
- Make sure that the software is bug-free and that the quality of the product meets the market standard.
- Ensures that the application doesn’t result in any failures.
5. What are the two main categories of software testing?
Software testing is a huge domain but it can be broadly categorized into two areas such as :
- Manual Testing – This is the oldest type of software testing where the testers manually execute test cases without using any test automation tools. It means the software application is tested manually by QA testers.
- Automation Testing – This is the process of using the assistance of tools, scripts, and software to perform test cases by repeating pre-defined actions. Test Automation focuses on replacing manual human activity with systems or devices that enhance efficiency.
Become certified in automation testing and enroll in the Selenium online training.
Learn Manual Testing From Our Expert Trainer
6. What is quality control? Is it similar to Quality Assurance?
Quality control is a product-oriented approach to running a program to determine if it has any defects, as well as making sure that the software meets all of the requirements put forth by the stakeholders.
7. What is a traceability matrix?
The relationship between test cases and requirements is shown with the help of a document. This document is known as a traceability matrix.
8. What is the difference between the STLC (Software Testing Life Cycle) and SDLC (Software Development Life Cycle)?
SDLC deals with the development/coding of the software while STLC deals with the validation and verification of the software
9. What is a test scenario?
A test scenario is derived from a use case. It’s used to test an application’s features from beginning to end.
Multiple test cases can be accommodated by a single test scenario. When there is a time constraint during testing, scenario testing comes in handy.
10. What is a test plan?
A test plan is a formal document that specifies the scope of testing, the method to be used, the resources needed, and the estimated time to complete the testing process.
It is derived from the specifications (Software Requirement Specifications).
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
11. What is test data?
Test data is information that is used to test software with various inputs and determine whether the resulting output matches the intended result. This data is generated based on the needs of the company.
12. What is a test script?
An automated test case created in any programming or scripting language is known as a test script.
These are essentially a collection of instructions for evaluating an application’s functionality.
13. What types of manual testing are there? Break them down.
Manual testing is broken down into:
- Black Box
- White Box
- Integration
- Unit
- System
- Acceptance
14. What is black box testing, and what are the various techniques?
Software testers employ black-box testing when they do not know the internal architecture or code structure. The techniques are:
- Equivalence Partitioning
- Boundary value analysis
- Cause-effect graphing
15. What is white box testing and its various techniques?
Unlike black-box testing, white box involves analyzing the system’s internal architecture and/or its implementation, in addition to its source code quality. Its techniques are:
- Statement Coverage
- Decision Coverage
So far, if you have any doubts about these Manual testing interview questions/ software testing interview questions, please ask in the comment section below.
Learn Manual Testing From Our Expert Trainer
16. What kind of skills are needed for someone to become a software tester?
Software testers need skills such as:
- Problem-solving skills
- Excellent written and verbal communication skills
- Detail-oriented
- Able to handle the pressure
- Can work solo or as a team member equally well
- Organizational skills
- Related technical skills
17. Explain what SDLC is.
This is an acronym for Software Development Life Cycle and encompasses all of the stages of software development, including requirement gathering and analysis, designing, coding, testing, deployment, and maintenance.
18. What is a test case?
A test case is used to check whether an application complies with its requirements. It is a documented set of circumstances including prerequisites, input values, and expected outcomes.
19. In white box testing, what do you verify?
In white box testing, the following steps are verified.
- Verify the security holes in the code
- Verify the incomplete or broken paths in the code
- Verify the flow of structure according to the document specification
- Verify the expected outputs
- Verify all conditional loops in the code to check the complete functionality of the application
- Verify the line-by-line coding and cover 100% testing
20. What do you mean by Synchronization in Tosca?
Static testing: During the Static testing method, the code is not executed, and it is performed using the software documentation.
Dynamic testing: To perform this testing the code is required to be in an executable form.
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
21. What is the test configuration parameter in Tosca?
Verification is a process of evaluating software during the development phase.
It helps you to decide whether the product of a given application satisfies the specified requirements.
Validation is the process of evaluating software after the development process and checking whether it meets the customer’s requirements.
22. What is Integration testing?
Integration testing is a level of software testing process, where individual units of an application are combined and tested. It is usually performed after unit and functional testing.
23. What Test Plans consist of?
Test design, scope, test strategies, and approaches are various details that the Test plan document consists of.
- Test case identifier
- Scope
- Features to be tested
- Features not to be tested
- Test strategy & Test approach
- Test deliverables
- Responsibilities
- Staffing and training
- Risk and Contingencies
24. What is the difference between UAT (User Acceptance Testing) and System testing?
System Testing: System testing is finding defects when the system undergoes testing as a whole; it is also known as end-to-end testing. In such a type of testing, the application suffers from the beginning till the end.
UAT: User Acceptance Testing (UAT) involves running a product through a series of specific tests which determine whether the product will meet the needs of its users.
25. Mention the difference between Data Driven Testing and Retesting?
Retesting: It is a process of checking bugs that are actioned by the development team to verify that they are fixed.
Data Driven Testing (DDT): In the data-driven testing process, the application is tested with multiple test data. The application is tested with a different set of values.
Learn Manual Testing From Our Expert Trainer
26. What’s the difference between a bug and a defect?
A bug is a fault in the software that’s detected during testing time, while a defect is a variance between expected results and actual results, detected by the developer after the product goes live.
27. What about the difference between an error and a failure?
If a program can’t run or be compiled during development, it’s an error. If an end-user discovers an issue with the software, it’s a failure.
28. What’s GUI testing?
This tests the interface between the software and the end user. Short for Graphics User Interface.
29. When should testing end?
There are a few criteria for ending testing:
- The bug rate has fallen below an agreed-upon level
- The testing or release deadlines have arrived
- The testing budget is out of funds
- A certain percentage of test cases have passed
- The alpha or beta testing periods have ended
- Code, functionality, or requirements coverage have been met at a declared point
30. What are the different types of Software testing?
Software testing is classified into two main categories.
- Functional testing
- Non-Functional testing
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
31. Explain Functional Testing
Functional testing is a type of black-box testing. It focuses on the software’s functional requirements rather than its internal implementation.
A functional requirement refers to the system’s needed behavior in terms of input and output.
It checks the software against the functional requirements or specifications, ignoring non-functional characteristics like performance, usability, and dependability.
The purpose of functional testing is to ensure that the software is up to snuff in terms of functionality and to solve the difficulties of its target users.
Some of the types of functional Testing are –
- Unit Testing
- Integration Testing
- Regression Testing
- System Testing
- Smoke Testing
- Performance Testing
- Stress Testing
32. What is Test Harness?
A test harness is a collection of software and test data used to put a program unit to the test by running it under various conditions such as stress, load, and data-driven data while monitoring its behavior and outputs.
33. What is a Critical Bug?
A critical bug has the potential to affect the bulk of an application’s functioning. It indicates that a significant portion of functionality or a critical system component is utterly broken, with no way to proceed. The application cannot be delivered to end users until the critical bug has been fixed.
34. What is Test Closure?
Test Closure is a document that summarizes all of the tests performed throughout the software development life cycle, as well as a full analysis of the defects fixed and errors discovered.
The total number of experiments, the total number of experiments executed, the total number of flaws detected, the total number of defects settled, the total number of bugs not settled, the total number of bugs rejected, and so on are all included in this memo.
35. What is the function of the software testing tool “phantom”?
Phantom is a freeware and is used for windows GUI automation scripting language. It allows us to take control of windows and functions automatically.
It can simulate any combination of keystrokes and mouse clicks as well as menus, lists, and more.
Learn Manual Testing From Our Expert Trainer
36. What is mutation testing?
Mutation testing is a technique to identify if a set of test data or test cases is useful by intentionally introducing various code changes (bugs) and retesting with original test data/ cases to determine if the bugs are detected.
37. Explain what Test Deliverables is?
Test Deliverables are a set of documents, tools, and other components that have to be developed and maintained in support of testing.
There are different test deliverables at every phase of the software development lifecycle
- Before Testing
- During Testing
- After the Testing
38. What all things you should consider before selecting automation tools for the AUT?
- Technical Feasibility
- Complexity level
- Application stability
- Test data
- Application size
- Re-usability of automated scripts
- Execution across environment
39. What is Acceptance testing?
Acceptance testing is a type of testing done by a possible end-user or customer to see if the software meets the business requirements and can be used.
40. Differentiate between bug leakage and bug release
Bug Leakage – When tested software is pushed into the market and the end-user discovers defects, this is known as bug leakage. These are bugs that the testing team overlooked throughout the testing phase.
Bug Release – When a certain version of the software is launched into the market with some known bugs that are expected to be fixed in later versions, this is known as a bug release.
These are low-priority issues that are highlighted in the release notes when sharing with end-users.
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
41. What do you mean by Defect Triage?
Defect triage is a procedure in which defects are prioritized depending on a variety of characteristics such as severity, risk, and the amount of time it will take to fix the fault.
The defect triage meeting brings together several stakeholders – the development team, testing team, project manager, BAs, and so on – to determine the order in which defects should be fixed.
42. What is Integration Testing? What are its types?
Integration testing is performed after unit testing. We test a group of linked modules in integration testing. Its goal is to identify faults with module interaction.
The following are the types of integration testing –
- Big Bang Integration Testing — After all of the modules have been merged, big bang integration testing begins.
- Top-down Integration Testing — In top-down integration, testing and integration begin at the top and work their way down.
- Bottom-up Integration Testing — In bottom-up integration testing, lower-level modules are tested before moving up the hierarchy to higher-level modules.
- Hybrid Integration Testing — Hybrid integration testing combines top-down and bottom-up integration testing techniques. The integration with this approach starts at the middle layer, and testing is done in both directions.
43. What is a stub?
Many times, when top-down integration testing is performed, lower-level modules are not produced until top-level modules are tested and integrated.
Stubs or dummy modules are used in these circumstances to emulate module behavior by delivering a hard-coded or predicted result based on the input variables.
44. What is code coverage?
The quantity of code covered by the test scripts is referred to as code coverage. It conveys the scope of the test suite’s coverage of the application.
45. What is a cause-effect graph?
A cause-effect graph testing technique is a black-box test design technique that uses a graphical representation of the input (cause) and output (effect) to construct the test.
This method employs a variety of notations to describe AND, OR, NOT and other relationships between the input and output conditions.
Learn Manual Testing From Our Expert Trainer
46. Explain equivalence class partitioning.
Equivalence class partitioning is a black-box testing technique based on specifications.
A set of input data that defines multiple test conditions is partitioned into logically comparable groups in equivalence class partitioning so that utilizing even a single test data from the group for testing can be considered similar to using all the other data in that group.
47. What is boundary value analysis?
The border values of the classes of the equivalence class partitioning are used as input to the test cases in boundary value analysis, which is a software testing technique for designing test cases.
48. What is your approach towards a severely buggy program? How would you handle it?
In such cases, the best course of action is for testers to go through the process of reporting any flaws or blocking-type issues that arise, with an emphasis on critical bugs.
Because this sort of crisis might result in serious issues such as insufficient unit or integration testing, poor design, wrong build or release methods, and so on, management should be contacted and given documentation as proof of the problem.
49. What if an organization's growth is so rapid that standard testing procedures are no longer feasible? What should you do in such a situation?
This is a very prevalent issue in the software industry, especially with the new technologies that are being used in product development. In this case, there is no simple answer; however, you could:
- Hire people who are good at what they do.
- Quality issues should be ‘fiercely prioritized’ by management, with a constant focus on the client.
- Everyone in the company should understand what the term “quality” implies to the end user.
50. When can you say for sure that the code has met its specifications?
Most businesses have coding “standards” that all developers are expected to follow, but everyone has their own opinion on what is best, as well as how many regulations are too many or too few.
There are many methods available, such as a traceability matrix, to guarantee that requirements are linked to test cases. And when all of the test cases pass, that means the code satisfies the requirement.
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
51. What are the common mistakes which create issues?
- Matching resources to the wrong projects
- Test manager lack of skills
- Not listening to others
- Poor Scheduling
- Underestimating
- Ignoring the small problems
- Not following the process
52. What does a typical test report contain? What are the benefits of test reports?
A test report contains the following things:
- Project Information
- Test Objective
- Test Summary
- Defect
The benefits of test reports are:
- The current status of the project and the quality of the product are informed
- If required, stakeholders and customer can take corrective action
- A final document helps to decide whether the product is ready for release
53. What is a test management review and why is it important?
Management review is also referred to as Software Quality Assurance or SQA. SQA focuses more on the software process rather than the software work products.
It is a set of activities designed to make sure that the project manager follows the standard process. SQA helps the test manager to benchmark the project against the set standards
54. Explain what the difference between latent and masked defects is?
- Latent defect: A latent defect is an existing defect that has not caused a failure because the sets of conditions were never met
- Masked defect: It is an existing defect that has not caused a failure because another defect has prevented that part of the code from being executed
55. Mention what bottom-up testing is?
Bottom-up testing is an approach to integration testing, where the lowest level components are tested first, then used to facilitate the testing of higher level components.
The process is repeated until the component at the top of the hierarchy is tested.
Learn Manual Testing From Our Expert Trainer
56. Mention what the different types of test coverage techniques are?
Different types of test coverage techniques include
- Statement Coverage: It verifies that each line of source code has been executed and tested
- Decision Coverage: It ensures that every decision in the source code is executed and tested
Path Coverage: It ensures that every possible route through a given part of the code is executed and tested
57. Mention what the meaning of breath testing is?
Breath testing is a test suite that exercises the full functionality of a product but does not test features in detail
58. Mention what the basic components of defect report format are?
The essential components of the defect report format include
- Project Name
- Module Name
- Defect detected on
- Defect detected by
- Defect ID and Name
- Snapshot of the defect
- Priority and Severity status
- Defect resolved by
- Defect resolved on
59. Explain what the meaning of Code Walk Through is?
Code Walk Through is the informal analysis of the program source code to find defects and verify coding techniques
60. Mention what the meaning of breath testing is?
Breath testing is a test suite that exercises the full functionality of a product but does not test features in detail
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
61. Mention what the purpose behind doing end-to-end testing is?
End-to-end testing is done after functional testing. The purpose behind doing end-to-end testing is that
- To validate the software requirements and integration with external interfaces
- Testing application in real-world environment scenario
- Testing of interaction between application and database
62. Explain what it means by test harness?
A test harness is configuring a set of tools and test data to test an application in various conditions, and it involves monitoring the output with expected output for correctness.
63. Explain in a testing project what testing activities would you automate?
In testing project testing activities, you would automate are
- Tests that need to be run for every build of the application
- Tests that use multiple data for the same set of actions
- Identical tests that need to be executed using different browsers
- Mission critical pages
- A transaction with pages that do not change in a short time
64. What is the MAIN benefit of designing tests early in the life cycle?
It helps prevent defects from being introduced into the code.
65. What is risk-based testing?
Risk-based Testing is the term used for an approach to creating a Test Strategy that is based on prioritizing tests by risk.
The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first.
Learn Manual Testing From Our Expert Trainer
66. What is the KEY difference between preventative and reactive approaches to testing?
Preventative tests are designed early; reactive tests are designed after the software has been produced.
67. What is the purpose of exit criteria?
The purpose of exit criteria is to define when a test level is completed.
68. What determines the level of risk?
The likelihood of an adverse event and the impact of the event determine the level of risk.
69. When is Decision table testing?
Decision table testing is used for testing systems for which the specification takes the form of rules or cause-effect combinations. In a decision table, the inputs are listed in a column, with the outputs in the same column but below the inputs.
The remainder of the table explores combinations of inputs to define the outputs produced.
70. Why do we use decision tables?
The techniques of equivalence partitioning and boundary value analysis are often applied to specific situations or inputs.
However, if different combinations of inputs result in different actions being taken, this can be more difficult to show using equivalence partitioning and boundary value analysis, which tend to be more focused on the user interface.
The other two specification-based techniques, decision tables, and state transition testing are more focused on business logic or business rules. A decision table is a good way to deal with combinations of things (e.g., inputs).
This technique is sometimes also referred to as a ’cause-effect’ table. The reason for this is that there is an associated logic diagramming technique called ’cause-effect graphing’ which was sometimes used to help derive the decision table
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
71. We use the output of the requirement analysis, the requirement specification as the input for writing …
User Acceptance Test Cases
72. Repeated Testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software component:
Regression Testing
73. A wholesaler sells printer cartridges. The minimum order quantity is 5. There is a 20% discount for orders of 100 or more printer cartridges. You have been asked to prepare test cases using various values for the number of printer cartridges ordered. Which of the following groups contain three test inputs that would be generated using Boundary Value Analysis?
4, 5, 99
75. What is functional system testing?
Testing the end-to-end functionality of the system as a whole is defined as functional system testing.
Learn Manual Testing From Our Expert Trainer
76. What are the benefits of Independent Testing?
Independent testers are unbiased and identify different defects at the same time.
77. In a REACTIVE approach to testing when would you expect the bulk of the test design work to be begun?
The bulk of the test design work begins after the software or system has been produced.
78. What are the different Methodologies in Agile Development Model?
There are currently seven different agile methodologies that I am aware of:
- Extreme Programming (XP)
- Scrum
- Lean Software Development
- Feature-Driven Development
- Agile Unified Process
- Crystal
- Dynamic Systems Development Model (DSDM)
79. Which activity in the fundamental test process includes evaluation of the testability of the requirements and system?
A ‘Test Analysis’ and ‘Design’ includes an evaluation of the testability of the requirements and system.
80. What is typically the MOST important reason to use risk to drive testing efforts?
Because testing everything is not feasible.
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
81. Consider the following techniques. Which are static and which are dynamic techniques?
- Equivalence Partitioning.
- Use Case Testing.
- Data Flow Analysis.
- Exploratory Testing.
- Decision Testing.
- Inspections.
Data Flow Analysis and Inspections are static; Equivalence Partitioning, Use Case Testing, Exploratory Testing, and Decision Testing are dynamic.
82. Why are static testing and dynamic testing described as complementary?
Because they share the aim of identifying defects but differ in the types of defects they find.
83. What are the phases of a formal review?
In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process consists of six main steps:
- Planning
- Kick-off
- Preparation
- Review meeting
- Rework
- Follow-up.
84. What is the role of moderator in the review process?
The moderator (or review leader) leads the review process. He or she determines, in cooperation with the author, the type of review, approach, and composition of the review team.
The moderator performs the entry check and the follow-up on the rework, to control the quality of the input and output of the review process.
The moderator also schedules the meeting, disseminates documents before the meeting, coaches other team members, paces the meeting, leads possible discussions, and stores the data that is collected.
85. Which review is normally used to evaluate a product to determine its suitability for the intended use and to identify discrepancies?
Technical Review.
Learn Manual Testing From Our Expert Trainer
86. Faults found should be originally documented by whom?
By testers.
87. Which is the current formal world-wide recognized documentation standard?
There isn’t one.
88. Which of the following is the review participant who has created the item to be reviewed?
Author
89. A number of critical bugs are fixed in software. All the bugs are in one module, related to reports. The test manager decides to do regression testing only on the reports module.
Regression testing should be done on other modules as well because fixing one module may affect other modules.
90. Why does the boundary value analysis provide good test cases?
Because errors are frequently made during the programming of the different cases near the ‘edges’ of the range of values.
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version
Learn Manual Testing From Our Expert Trainer
91. What makes an inspection different from other review types?
It is led by a trained leader and uses formal entry and exit criteria and checklists.
92. Why can testers depend on configuration management?
Because configuration management assures that we know the exact version of the testware and the test object.
93. What is V-Model?
A software development model that illustrates how testing activities integrate with software development phases
94. What is maintenance testing?
Triggered by modifications, migration, or retirement of existing software
95. What is test coverage?
Test coverage measures in some specific way the amount of testing performed by a set of tests (derived in some other way, e.g., using specification-based techniques).
Wherever we can count things and can tell whether or not each of those things has been tested by some test, then we can measure coverage.
Learn Manual Testing From Our Expert Trainer
96. Why do we split testing into distinct stages?
We split testing into distinct stages because of the following reasons,
- Each test stage has a different purpose
- It is easier to manage to test in stages
- We can run different tests in different environments
- Performance and quality of the testing are improved using phased testing
97. What is DRE?
To measure test effectiveness, a powerful metric is used to measure test effectiveness known as DRE (Defect Removal Efficiency) From this metric we would know how many bugs we have found from the set of test cases. The formula for calculating DRE is
DRE=Number of bugs while testing/number of bugs while testing + number of bugs found by a user
98. What are Test comparators?
Is it a test if you put some inputs into some software, but never look to see whether the software produces the correct result? The essence of testing is to check whether the software produces the correct result and to do that, we must compare what the software produces to what it should produce.
A test comparator helps to automate aspects of that comparison.
99. What is Rapid Application Development?
Rapid Application Development (RAD) is formally a parallel development of functions and subsequent integration.
Components/functions are developed in parallel as if they were mini projects, the developments are time-boxed, delivered, and then assembled into a working prototype. This can very quickly give the customer something to see and use and provide feedback regarding the delivery and their requirements.
Rapid change and development of the product are possible using this methodology. However the product specification will need to be developed for the product at some point, and the project will need to be placed under more formal controls before going into production.
100. What is Boundary value testing?
Test boundary conditions on, below, and above the edges of input and output equivalence classes.
For instance, let’s say a bank application where you can withdraw a maximum of Rs.20,000 and a minimum of Rs.100, so in boundary value testing we test only the exact boundaries, rather than hitting in the middle.
That means we test above the maximum limit and below the minimum limit.
Want to download these Manual Testing Interview Questions and Answers in the form of a readable and printable PDF for your interview preparation?
Click the download button below for the PDF version