### **Possible Interview Questions and Answers**

---

#### **Technical & Role-Specific Questions**

1. **Q: Can you describe your experience with JIRA and how you used it in your previous role?**

**A:** At Kounsel, I used JIRA extensively for bug tracking, sprint planning, and workflow
management. I created and prioritized tickets, assigned them to developers, and tracked their
resolution. For example, during a regression testing phase, I documented 15+ critical bugs in JIRA,
collaborated with developers to resolve them, and retested fixes to ensure closure.

2. **Q: How do you approach creating test cases and test plans?**

**A:** I start by reviewing requirements and user stories to identify test scenarios. For the AB
Pharmacy app, I created test cases covering user flows like product search, cart functionality, and
order placement. I prioritize edge cases (e.g., empty cart behavior) and ensure alignment with
business requirements. I also update test plans iteratively as features evolve.

3. **Q: Explain a time when you found a critical bug. How did you handle it?**

**A:** During API testing at Kounsel, I discovered a bug where user authentication tokens expired
prematurely. I documented it in JIRA with steps to reproduce, logs, and screenshots. I escalated it to
the dev team, collaborated on a fix, and retested after deployment. This prevented a major user
access issue post-release.

4. **Q: What’s the difference between regression testing and smoke testing?**

**A:** Regression testing ensures new changes don’t break existing functionality, while smoke
testing is a quick check to confirm the build is stable enough for further testing. At Kounsel, I ran
smoke tests after each deployment and regression tests before major releases.

5. **Q: How familiar are you with SQL? Can you write a query to fetch data from two tables?**

**A:** I’ve used SQL for data validation during testing. For example, to verify user registration, I
wrote:

```sql

SELECT Users.name, Orders.total

FROM Users

INNER JOIN Orders ON Users.id = Orders.user_id

WHERE Users.email = '[email protected]';

 ```

6. **Q: You’ve worked on automation testing. When do you prefer automation over manual testing?
**

**A:** Automation is ideal for repetitive tasks (e.g., regression tests) or large-scale data validation.
At Kounsel, I automated login and checkout flows to save time. However, I use manual testing for
exploratory or UI/UX-focused scenarios.

---

#### **Behavioral & Situational Questions**

7. **Q: Describe a time you faced a tight deadline. How did you prioritize tasks?**

**A:** During a sprint at Kounsel, we had to test a feature in 2 days. I prioritized test cases based
on risk (critical user paths first), delegated some tasks to teammates, and used automation for
repetitive checks. We completed testing on time with no major post-release issues.

8. **Q: How do you handle disagreements with developers about a bug’s severity?**

**A:** I focus on data. For instance, a developer once argued a UI bug was low priority. I
demonstrated how it affected 30% of users via analytics. We compromised by scheduling the fix for
the next sprint while monitoring user feedback.

9. **Q: How do you stay updated with QA trends?**

**A:** I follow blogs like Ministry of Testing, take Udemy courses on automation tools, and
participate in QA communities on LinkedIn. Recently, I explored AI-driven testing tools for a personal
project.

10. **Q: Why do you want to join our team as a Junior SQA Engineer?**

**A:** I admire your focus on collaboration and mentorship. My experience with JIRA, manual
testing, and problem-solving aligns with your needs. I’m eager to grow under experienced QA pros
and contribute to delivering bug-free software.

---

#### **Project & CV-Based Questions**

11. **Q: Your CV mentions SEO optimization for your portfolio. How does that relate to QA?**
 **A:** SEO required meticulous attention to metadata, links, and performance—skills that
translate to QA, like detail-oriented testing and optimizing user experience. For example, I tested
page load speeds during SEO audits, which overlaps with performance testing.

12. **Q: Tell us about your Skin Cancer Detection publication. How does it demonstrate QA skills?**

**A:** The project involved validating a deep learning model’s accuracy on edge devices. This
required rigorous testing of false positives/negatives, data preprocessing, and edge cases—similar to
validating software functionality under constraints.

13. **Q: Walk us through your AB Pharmacy app. What testing challenges did you face?**

**A:** The app integrated WhatsApp and Google Sheets. Testing real-time API interactions was
challenging. I used Postman for API validation and manual testing for UI flows. I also wrote test cases
for offline scenarios (e.g., cart persistence).

14. **Q: You solved 450+ LeetCode problems. How does this help in QA?**

**A:** Problem-solving sharpens my analytical skills. For instance, understanding algorithms helps
me design test cases for edge scenarios, like testing sorting functions in a data-heavy application.

---

#### **Closing Questions to Ask the Interviewer**

- What’s the biggest QA challenge your team is currently facing?

- How do you measure success for a Junior SQA Engineer in the first 6 months?

- Can you describe the team structure and mentorship opportunities?

---

**Tips:**

- Use the STAR method for situational questions.

- Highlight **collaboration** (e.g., working with devs at Kounsel) and **attention to detail** (e.g.,
GPA 5.0, 450 LeetCode problems).

- Relate non-QA experiences (e.g., SEO, graphic design) to QA skills like process optimization and
user-centric testing.
Good luck! 🚀
Based on your CV and the job description, here are possible interview questions and answers
for the Junior Software QA Engineer role:

1. General Questions

Q1: Tell us about yourself.

A:
"I’m a Software Engineering graduate from Delhi Technological University with experience
in QA and web development. I have worked as a Software QA Engineer at Kounsel, where I
conducted quality assurance, developed automated test plans, and managed bug tracking
using Jira. I also have experience as a Software Engineer at Kingsley Engineering Service,
where I worked on website redesign, SEO, and micro web applications. My skills include
manual and automation testing, API testing, and version control using Git. I’m excited about
this role because it aligns with my passion for software quality and continuous learning."

2. QA Fundamentals

Q2: What is the difference between Verification and Validation?

A:

 Verification ensures that the product is being built correctly (meeting requirements,
specifications, and design). It is a static process (e.g., reviews, walkthroughs).
 Validation ensures that the right product is built (meeting user expectations). It is a
dynamic process (e.g., testing the application).

Q3: What are the different types of software testing?

A:

1. Functional Testing (Unit, Integration, System, UAT)

2. Non-Functional Testing (Performance, Security, Usability)
3. Manual vs. Automation Testing
4. Black Box vs. White Box Testing

Q4: What is Regression Testing?

A:
Regression Testing ensures that new changes do not break existing functionalities. It involves
re-running previously executed test cases after code modifications.

Q5: What is Smoke Testing?

A:
Smoke Testing is a quick test performed to check if the basic functionality of an application
is working after a new build.

3. Bug Reporting & Tools

Q6: How do you report a bug in Jira?

A:

 Step 1: Create a new issue and select "Bug."

 Step 2: Provide a clear summary and description (steps to reproduce, expected vs.
actual results).
 Step 3: Attach screenshots/logs (if needed).
 Step 4: Set priority/severity and assign it to the relevant team.
 Step 5: Track bug progress and re-test once fixed.

Q7: What is the difference between Severity and Priority in Bug Tracking?

A:

 Severity (Impact of the defect)

o Critical: System crash, data loss
o Major: Core functionality broken
o Minor: UI misalignment, typo
 Priority (Business importance)
o High Priority: Fix immediately
o Low Priority: Can be fixed later

4. SQL & API Testing

Q8: What SQL queries would you use for testing?

A:

 SELECT * FROM users WHERE email = '[email protected]'; (Check if user

exists)
 UPDATE orders SET status = 'Shipped' WHERE order_id = 101; (Verify data
updates)
 DELETE FROM logs WHERE created_at < '2024-01-01'; (Check database
cleanup)

Q9: How do you test an API?

A:
  Using Postman or cURL:
1. GET Request: Fetch user data (GET /users/{id})
2. POST Request: Create a new record (POST /users)
3. PUT Request: Update a record (PUT /users/{id})
4. DELETE Request: Remove a record (DELETE /users/{id})
 Check Response Codes: 200 OK, 400 Bad Request, 401 Unauthorized, 500
Internal Server Error

5. Scenario-Based Questions

Q10: What will you do if you find a bug just before a release?

A:

1. Assess Impact (Is it critical?)

2. Communicate with Team (PM, Devs, QA Lead)
3. Check Workarounds (Temporary fixes?)
4. Decision Making (Fix now or document for next release?)
5. Re-test & Deploy

Q11: If a developer disagrees with a bug report, how do you handle it?

A:

1. Provide Evidence (Screenshots, logs, test cases)

2. Explain Impact (How it affects users)
3. Collaborate (Discuss with Dev, PM)
4. Retest & Document

6. Automation & Future Growth

Q12: Have you worked with automation testing?

A:
"I have experience with manual testing but am eager to learn automation using Selenium and
Python. I have a solid foundation in programming and am currently exploring automated test
frameworks."

Q13: Where do you see yourself in 3-5 years?

A:
"I see myself as a skilled QA Engineer with expertise in automation testing and performance
testing, contributing to the delivery of high-quality software."
Would you like me to refine any answers based on your strengths? 🚀
Congratulations on applying for the Junior Software Quality Assurance Engineer role!
Based on the job description and your CV (assuming a typical entry-level CV with a
Bachelor’s degree in Computer Science or a related field, basic technical skills, and
some familiarity with testing concepts), I’ll outline possible interview questions and
provide sample answers tailored to this position. Since I don’t have your exact CV, I’ll
assume you have foundational knowledge and skills aligned with the job requirements. If
your CV includes specific experiences or projects, feel free to adapt these answers
accordingly.
The interview will likely cover your technical knowledge, problem-solving abilities,
teamwork skills, and enthusiasm for the role. Below are common questions divided into
categories, along with suggested answers.

1. General/Behavioral Questions
These assess your background, motivation, and fit for the role.
Q: Tell us about yourself.

 Answer: "I’m a recent graduate with a Bachelor’s degree in Computer Science

from [Your University]. During my studies, I developed a strong interest in
software quality assurance because I love solving problems and ensuring that
technology works seamlessly for users. I’ve worked on academic projects where I
tested small applications, wrote test cases, and identified bugs, which sparked
my passion for QA. I’m excited to join your team in Dhaka because I want to grow
my skills in a real-world environment and contribute to delivering high-quality
software."

Q: Why do you want to work as a Junior SQA Engineer?

 Answer: "I’m drawn to QA because it combines my attention to detail with my

passion for technology. I enjoy the challenge of finding issues before they reach
users and ensuring software meets its requirements. This role at your company
excites me because it offers hands-on experience, mentorship, and the chance to
collaborate with a talented team—perfect for starting my career in QA."

Q: What do you know about our company?

 Answer: "From what I’ve researched, your company focuses on delivering

innovative software solutions, and quality is a top priority. I admire your emphasis
on teamwork and growth opportunities, like the training and mentorship you offer.
I’m excited to contribute to your QA team and help maintain the high standards
you’re known for."
Q: How do you handle working in a team?

 Answer: "I enjoy collaborating with others because it brings different

perspectives together. In university group projects, I worked with developers and
analysts to test applications. I made sure to communicate clearly about bugs I
found and listened to feedback to improve our process. I’m looking forward to
working with your developers and QA pros to ensure we deliver the best product
possible."

2. Technical Questions
These test your understanding of QA concepts and tools mentioned in the job
description.
Q: What is the Software Development Life Cycle (SDLC), and where does QA fit
in?

 Answer: "The SDLC is the process of developing software, consisting of phases

like planning, design, development, testing, deployment, and maintenance. QA
fits primarily in the testing phase, where we validate that the software meets
requirements and works as expected. However, QA also plays a role throughout
the SDLC by reviewing requirements early to catch potential issues and ensuring
quality at every step."

Q: What’s the difference between functional and regression testing?

 Answer: "Functional testing checks if the software performs its intended

functions correctly, like verifying a login feature works with valid credentials.
Regression testing ensures that new changes or updates haven’t broken existing
functionality. For example, after adding a new feature, I’d re-run old test cases to
confirm everything still works."

Q: How do you write a test case?

 Answer: "A test case includes a title, objective, preconditions, steps, input data,
expected result, and actual result. For example, to test a login page, I’d write:
Title: Verify successful login. Objective: Ensure valid credentials log the user in.
Preconditions: User has an account. Steps: Enter username and password, click
login. Expected Result: User is directed to the homepage. I’d then execute it and
document the outcome."

Q: What would you do if you find a bug?

  Answer: "First, I’d reproduce the bug to confirm it’s consistent. Then, I’d
document it in a tool like JIRA with details like steps to replicate, screenshots,
severity, and environment. I’d report it to the development team, collaborate with
them to verify the fix, and retest it once resolved to ensure it’s gone."

Q: What’s the purpose of Smoke Testing?

 Answer: "Smoke testing is a quick check to verify the basic functionality of a

system works before deeper testing. It’s like a ‘sanity check’—for example,
ensuring a web app loads and major features like login or navigation work. If it
fails, there’s no point in proceeding with detailed testing until the core issues are
fixed."

Q: Can you write a basic SQL query to validate data?

 Answer: "Sure! If I needed to check if a user’s record exists in a database, I’d

write: SELECT * FROM users WHERE username = 'testuser';. This would return
the user’s details if they exist, helping me validate data against test
expectations."

Q: What tools have you used for bug tracking or test management?

 Answer: "I’ve used JIRA in a university project to log bugs and track their status.
I also explored TestRail in a personal project to organize test cases and report
results. I’m eager to learn more about the tools your team uses and adapt
quickly."

3. Scenario-Based Questions
These evaluate your problem-solving and practical application skills.
Q: If a developer says a bug you reported isn’t reproducible, what do you do?

 Answer: "I’d start by double-checking my steps to ensure they’re clear and

repeatable. Then, I’d ask the developer to walk me through their environment to
spot any differences, like browser version or data used. I’d provide more details—
like logs or a video recording—and work together to isolate the issue.
Collaboration is key to resolving it."

Q: How would you test a new feature on a mobile app?

 Answer: "I’d begin by reviewing the feature’s requirements to understand its

purpose. Then, I’d create test cases covering functionality (does it work?),
usability (is it user-friendly?), and edge cases (what happens with invalid
 inputs?). I’d execute these manually on different devices and OS versions, log
any bugs, and validate the fix once resolved."

Q: What if a product requirement is unclear?

 Answer: "I’d reach out to the business analyst or product owner to clarify it,
asking specific questions about expected behavior. For example, if a field’s
validation isn’t defined, I’d ask what inputs should be allowed. I’d document the
clarification to ensure my test cases align with the intent."

Q: How do you prioritize which tests to run if time is limited?

 Answer: "I’d focus on high-priority areas like core functionality that users rely on,
using risk-based testing. For example, I’d prioritize login over a minor UI tweak.
I’d also run smoke tests first to catch major issues, then move to critical
regression tests based on recent changes."

4. Questions About Your Fit and Growth

These assess your alignment with the company’s offerings and long-term potential.
Q: How do you stay updated on QA best practices?

 Answer: "I follow QA blogs, like those on Ministry of Testing, and watch tutorials
on platforms like YouTube or Udemy. I also experiment with tools like Postman
for API testing in my spare time. I’m excited to learn from your team’s experience
and grow my skills further."

Q: What excites you about our training and mentorship program?

 Answer: "I love that you offer structured training because it’ll help me build a
strong QA foundation quickly. Mentorship from experienced pros is a huge bonus
—it means I can learn real-world tricks, avoid common pitfalls, and grow into a
skilled QA engineer with your guidance."

Q: Where do you see yourself in 5 years?

 Answer: "In 5 years, I’d like to be a seasoned QA engineer, possibly leading a

small team or specializing in automation testing. Starting as a Junior SQA
Engineer here, I see myself growing with the company, contributing to process
improvements, and helping deliver even better software."
5. Wrap-Up Questions
These are typically asked at the end of the interview.
Q: Do you have any questions for us?

 Answer: "Yes! What does a typical day look like for a Junior SQA Engineer
here? Also, how does the team collaborate between QA and development to
ensure quality? I’d love to hear more about how I can contribute and grow in this
role."

Tips to Prepare
1. Review Your CV: Be ready to explain any projects, coursework, or skills listed
(e.g., SQL, JIRA, testing experience).
2. Practice Technical Concepts: Brush up on SDLC, STLC, testing types, and
basic SQL queries.
3. Show Enthusiasm: Highlight your excitement for QA and eagerness to learn.
4. Mock Interview: Practice these answers aloud to sound confident and natural.

These questions and answers should give you a solid foundation. If you’d like me to
refine them further based on specific details from your CV or the company, let me know!

Good luck—you’ve got this!