INTERVIEW SPEAKING SCRIPT

Practice These Responses - Sujitha Rajkamal

SELF INTRODUCTION (60-90 seconds)

Good morning/afternoon. Thank you for this opportunity.
My name is Sujitha Rajkamal, and I am a Lead QA Associate with over 9 years of
experience in software testing and automation.
Currently, I work at Neurealm as a Lead Associate, where I have been leading QA
efforts for ZOLL emsCharts since March 2018. ZOLL emsCharts is a cloud-based
medical charting solution used by EMS providers. In this role, I lead status review
meetings across multiple teams, manage monthly metrics and reporting, and have built
a comprehensive automation framework using Playwright and Python.
My technical expertise includes automation testing with Selenium and Playwright, API
testing using SOAP UI and Postman, CI/CD integration with Jenkins and TeamCity, and
accessibility testing. I have strong domain knowledge in Healthcare and Banking
sectors.
I hold certifications including CSQA Professional, AWS Certified Cloud Practitioner,
Microsoft Azure Fundamentals, and certifications in Selenium and Playwright. I am
excited about this opportunity and look forward to contributing to your team.

ABOUT YOUR CURRENT ROLE

What do you do in your current role?
In my current role as Lead Associate at Neurealm, I wear multiple hats. I conduct
internal status review meetings where I consolidate updates from multiple teams and
present them to onsite managers. I manage our weekly status reports and monthly
metrics tracking. On the technical side, I developed our automation framework from
scratch using Playwright and Python, and I maintain and execute automated test scripts
within our Sprint cycles. I also perform manual testing including functional, regression,
and exploratory testing. Additionally, I mentor team members and conduct knowledge
transfer sessions for new joiners.

AUTOMATION TESTING
Tell me about your automation framework
I built our automation framework using Playwright with Python, following the Page
Object Model design pattern. Let me walk you through the key components:
First, I use fixtures in [Link] to configure browser instances and handle different
browsers like Chrome and Firefox. I have configured command-line parameters so we
can run tests on different browsers and URLs using pytest options.
For locator strategies, I primarily use get_by_role and get_by_text methods as they are
more reliable. For complex scenarios, I use filters and CSS selectors. I have
implemented reusable utility classes for common operations like handling alerts, frames,
dropdowns, and web tables.
I have also integrated API testing into the framework. I create API utility classes that
handle authentication tokens and make API calls using Playwright's request context.
This is particularly useful for setting up test data or validating backend operations.
For test data management, I use JSON files and parametrized testing with
[Link], which allows us to run the same test with different data sets.
Finally, I have integrated the framework with Jenkins and TeamCity for CI/CD. Tests run
automatically on code commits, and we generate HTML reports using pytest-html. We
also use trace generation for debugging failed tests, which is very helpful.

How do you handle flaky tests?

Flaky tests are a common challenge. My approach is first to identify why a test is flaky.
Usually it is due to timing issues, so I use Playwright's auto-waiting feature, which waits
for elements to be actionable before interacting with them. I avoid hard-coded waits and
instead use proper locators with built-in waiting. For API-dependent tests, I use request
interception to mock responses and make tests more stable. I also run tests in isolated
browser contexts to prevent state leakage between tests. When I do encounter flaky
tests, I review the trace files to understand the root cause and fix the underlying issue
rather than just re-running the test.
API TESTING
Describe your API testing experience
I have extensive experience with API testing using multiple tools and approaches.
With Postman and SOAP UI, I create comprehensive API test collections covering
positive and negative scenarios. I validate status codes, response schemas, response
times, and data accuracy. I also test authentication mechanisms, particularly bearer
token authentication.
In my Playwright framework, I have built API utility classes. For example, I have a
method that gets an authentication token by making a POST request to the login
endpoint, then I use that token in subsequent API calls. I also validate API responses
and use assertions to check if responses are not null and contain expected data.
I perform request and response interception testing as well. This helps us test scenarios
where we need to intercept API calls and provide fake payloads or redirect requests to
test error handling and unauthorized access scenarios.
I also work with REST APIs extensively, testing different HTTP methods like GET,
POST, PUT, DELETE, and validating the request and response payloads match the API
contracts.

How do you validate API responses?

I validate API responses at multiple levels. First, I check the HTTP status code to
ensure it matches expectations - 200 for success, 201 for created resources, 400 for
bad requests, 401 for unauthorized, 404 for not found, and so on. Then I parse the
JSON response body and validate the structure and data types match the schema. I
check for required fields, verify data values are within expected ranges, and validate
relationships between different fields. I also check response headers when needed,
particularly for authentication tokens or content types. For performance, I validate
response times are within acceptable limits.

CI/CD & DevOps

What is your CI/CD experience?
I have hands-on experience with Jenkins and TeamCity for CI/CD implementation. I
configure build pipelines that automatically trigger test execution on code commits or
pull requests. The pipeline checks out code from GitHub, sets up the test environment,
runs the automation suite, and generates test reports. I configure email notifications for
test failures and integrate test results into our project dashboard. I also manage different
test environments - development, staging, and production - and configure environment-
specific test data. This ensures continuous feedback to the development team and
helps catch issues early in the development cycle.
LEADERSHIP & TEAM MANAGEMENT
Tell me about your leadership experience
As a Lead Associate, I manage both technical and administrative responsibilities. I
conduct weekly status review meetings where I consolidate updates from multiple QA
teams and present them to management. I prepare and present status reports and
metrics on a monthly basis, tracking test coverage, defect density, automation progress,
and other key quality metrics. I participate in sprint planning and estimation sessions. I
also mentor junior team members, conduct code reviews of automation scripts, and
provide knowledge transfer to new joiners. When issues arise, I coordinate with
development teams and stakeholders to ensure timely resolution. I believe in leading by
example and maintaining open communication with my team.

CHALLENGES & PROBLEM SOLVING

Describe a challenging situation and how you handled it
One significant challenge I faced was when we had to transition from manual testing to
automation for a large healthcare application with complex workflows. The application
had frequent updates, and manual regression testing was becoming time-consuming. I
approached this systematically - first, I analyzed the test cases to identify high-value
scenarios for automation. Then I selected Playwright as our framework because of its
reliability and modern features. I created a proof of concept to demonstrate value to
stakeholders. Once approved, I developed the framework with proper architecture,
implemented it in phases starting with smoke tests, then regression, and gradually
expanded coverage. I conducted training sessions for the team and documented best
practices. Within six months, we achieved 70% automation coverage for regression
tests, reducing testing time from 5 days to 8 hours. This required technical skills,
planning, and stakeholder management.

ACCESSIBILITY TESTING
What is your accessibility testing experience?
During my time on the Wiley JQA project, I specialized in accessibility testing. I
prepared comprehensive test approach documents for accessibility validation. I used
JAWS screen reader to test how visually impaired users would experience the
application - ensuring all content was readable, navigation was logical, and forms were
properly labeled. I used WAVE tool to identify accessibility issues like missing alt text,
poor color contrast, and improper heading structure. I validated WCAG compliance,
tested keyboard navigation to ensure all functionality was accessible without a mouse,
checked that focus indicators were visible, and verified semantic HTML was used
correctly. I also tested with different browser and screen reader combinations to ensure
compatibility. This experience gave me a deep appreciation for building inclusive
applications.
TECHNICAL DEEP DIVE QUESTIONS
What is Page Object Model?
Page Object Model is a design pattern where we create separate classes for each page
of the application. Each class contains locators for elements on that page and methods
to interact with those elements. This makes the code more maintainable because if a
locator changes, we only need to update it in one place. It also makes tests more
readable because test scripts use meaningful method names instead of raw locators.
For example, instead of writing [Link]('#username').fill('test'), we would write
[Link]('test').

Explain fixtures in pytest

Fixtures in pytest are functions that run before tests to set up preconditions and after
tests to clean up. They are defined using the @[Link] decorator. For example, I
use a browser fixture that launches the browser before tests and closes it after. Fixtures
can have different scopes - function scope runs for each test, class scope runs once per
test class, and session scope runs once for the entire test session. Fixtures can also be
parameterized to run tests with different configurations. The [Link] file is special -
fixtures defined there are available to all test files in that directory and subdirectories.

How do you handle dynamic elements in Playwright?

Playwright has built-in auto-waiting that handles most dynamic elements automatically.
It waits for elements to be visible, enabled, and stable before interacting with them. For
elements that load dynamically, I use proper locators like get_by_role or get_by_text
that wait for the element to appear. If I need more control, I can use expect with custom
timeout values. For AJAX requests, I can use page.wait_for_load_state or wait for
specific network responses. Playwright also has wait_for_selector with different states
like 'visible', 'attached', or 'hidden'. The key is using the right waiting strategy rather than
hard-coded sleeps.

What is the difference between Selenium and Playwright?

I have worked with both tools extensively. Here are the key differences:
Playwright has built-in auto-waiting, whereas in Selenium we need to implement explicit
waits manually. This makes Playwright tests more stable.
Playwright supports multiple browser contexts in a single browser instance, which is
great for testing multi-user scenarios. Selenium requires separate browser instances.
Playwright has excellent debugging capabilities with trace viewer that shows
screenshots, network activity, and console logs. Selenium requires additional
configuration for similar features.
Playwright's API is more modern and developer-friendly with features like auto-retries
and better error messages.
However, Selenium has been around longer and has broader community support and
more third-party integrations. Both are excellent tools, and the choice depends on
project requirements.
TESTING METHODOLOGIES
How do you approach testing in Agile?
In Agile, testing is integrated throughout the sprint. I participate in sprint planning to
understand requirements and provide test estimates. During sprint execution, I
collaborate closely with developers - as features are developed, I start testing them
immediately rather than waiting until the end. I write test cases based on user stories
and acceptance criteria. I perform exploratory testing to find edge cases not covered in
formal test cases. For automation, I add new test scripts within the same sprint when
possible. I participate in daily standups to share testing progress and blockers. At the
end of the sprint, I ensure regression testing is complete before the demo. I also
participate in retrospectives to identify process improvements. The key is continuous
testing and collaboration rather than a separate testing phase.

What types of testing have you performed?

I have performed various types of testing throughout my career:
Functional testing to verify features work according to requirements. Regression testing
to ensure new changes do not break existing functionality. API testing to validate
backend services. Integration testing to verify different system components work
together correctly. Smoke testing to verify critical paths before detailed testing.
Exploratory testing to find defects through unscripted exploration. Accessibility testing to
ensure applications are usable by people with disabilities. Cross-browser and
compatibility testing to verify applications work across different browsers and devices.
Performance testing to identify bottlenecks. Security testing for basic vulnerabilities.
User acceptance testing support by preparing test environments and data.

DOMAIN KNOWLEDGE
Tell me about your Healthcare domain experience
I have been working on ZOLL emsCharts for over 7 years, which is a cloud-based
medical charting solution for emergency medical services. This has given me deep
understanding of healthcare workflows, including patient care documentation, vitals
recording, medical device integration, and regulatory compliance requirements like
HIPAA. I understand the critical nature of healthcare applications where data accuracy
and system availability can impact patient care. I have tested complex workflows
involving multiple user roles - paramedics, dispatchers, administrators - each with
different permissions and workflows. I have also worked with medical device
integrations where patient vitals are automatically imported from devices. This
experience has taught me the importance of thorough testing, data privacy, and
regulatory compliance in healthcare applications.

Tell me about your Banking domain experience

During my time at Cognizant, I worked on the Core Banking System for Halifax Bank of
Scotland. I tested large deposit reporting functionality for corporate, business, and
personal accounts. I worked with mainframe systems using CICS and CBS, which gave
me exposure to legacy banking systems. I validated transaction processing, threshold
limit checks, and regulatory reporting. This experience taught me about financial
transaction accuracy, security requirements, audit trails, and regulatory compliance in
banking. I learned to work with complex data validations and understand the critical
nature of financial applications where even small defects can have significant
consequences.
BEHAVIORAL QUESTIONS
Why are you looking for a change?
I have had a great learning experience in my current role and have grown significantly
as a QA professional. However, I am looking for new challenges and opportunities to
expand my skill set. I am particularly interested in working with newer technologies and
contributing to different types of projects. I believe this role offers the opportunity to work
on challenging problems and make a meaningful impact. I am excited about the
possibility of bringing my experience in automation, API testing, and team leadership to
your organization while continuing to learn and grow professionally.

What are your strengths?

My key strengths are my technical expertise in automation testing, my ability to learn
new technologies quickly, and my leadership skills. I am detail-oriented which helps me
find defects others might miss. I am also a good communicator, which is essential when
working with cross-functional teams and presenting status to management. I take
ownership of my work and see projects through to completion. I am proactive in
identifying process improvements and implementing solutions. Additionally, I am a team
player who believes in knowledge sharing and mentoring others.

What are your weaknesses?

One area I am working on is delegating more effectively. As someone who takes
ownership of work, I sometimes tend to do things myself rather than delegating to team
members. I am learning to trust my team more and delegate tasks appropriately, which
not only helps me focus on higher-priority items but also helps team members grow. I
am also working on improving my presentation skills for larger audiences. While I am
comfortable presenting to my immediate team and management, I want to become
more confident when presenting to larger groups or senior leadership.

Where do you see yourself in 5 years?

In five years, I see myself as a QA Architect or Test Manager, leading larger teams and
driving quality strategy for the organization. I want to continue expanding my technical
skills, particularly in areas like AI-driven testing, performance engineering, and cloud-
based testing platforms. I also want to mentor the next generation of QA professionals
and contribute to establishing best practices and quality standards. Ultimately, I want to
be in a position where I can influence quality culture across the organization and make
a significant impact on product quality.

QUESTIONS YOU SHOULD ASK

1. Can you describe the current testing infrastructure and what tools are being used?
2. What are the primary challenges the QA team is currently facing?
3. What does a typical sprint look like in your development process?
4. What is the team structure and who would I be working closely with?
5. Are there opportunities for professional development and learning new technologies?
6. What would success look like in this role in the first 6 months?
7. How does the QA team collaborate with development and product teams?
8. What are the next steps in the interview process?

CLOSING STATEMENT
Thank you for your time today. I am very excited about this opportunity and believe my
experience in automation testing, API testing, team leadership, and domain knowledge
in Healthcare and Banking make me a strong fit for this role. I am confident I can
contribute to your team from day one while continuing to learn and grow. I look forward
to hearing from you about the next steps.

FINAL TIPS FOR SPEAKING

✓ Speak clearly and at a moderate pace - do not rush
✓ Use the STAR method for behavioral questions (Situation, Task, Action, Result)
✓ Give specific examples from your experience, not generic answers
✓ If you do not understand a question, ask for clarification
✓ Show enthusiasm and genuine interest in the role
✓ Make eye contact and smile (if video interview)
✓ Take a brief pause before answering to collect your thoughts
✓ Be honest - if you do not know something, say so and express willingness to learn
✓ Keep answers concise but complete - aim for 1-2 minutes per answer
✓ End strong - thank them and express your interest in the role