Mindset Operating System (MOS)
  • MOS Handbook
    • Values
    • Teams
    • Roles
    • General Meeting Etiquette
    • Cadence
  • Vision, Mission and Strategy
    • Mindsets Mission & Purpose
    • Mindset Vision
    • Mindset Strategy
    • Strategic Flywheels
  • Recruitment
  • Teams
    • Core Team
    • Operations Team
    • Sales & Marketing Team
    • Marketing Team
    • Design Team
    • Customer Success Team
    • Product Team
      • Release Management Team
    • Data & Integrations Team
    • AI Team
    • Delivery Team
      • QA Team
      • FE team
      • BE Team
      • Integrations Team
      • DevOps Team
Powered by GitBook
On this page
  1. Teams
  2. Delivery Team

QA Team

Mandate

The QA team is responsible for ensuring the quality, stability, and performance of the software product. This team verifies the functionality of completed work, raises and prioritizes defects, and ensures that the software meets business and customer expectations. Beyond functional validation, the team also considers non-functional quality concerns, such as performance, security, and overall system stability, and contributes to the wider SDLC process relating to quality process and procedure.

Key Responsibilities

  • Functional Testing – Manually test new features and bug fixes to verify expected behavior as per acceptance criteria.

  • User Experience (UX) Testing - Ensure that the product is intuitive or easy to use and meets the end-user’s expectations.

  • Cross-platform Testing - Ensure that the feature work is tested across different platforms including Web, tablets and mobile devices.

  • Defect Management – Identify, document, prioritize, and track defects found in testing or reported by the business and customers.

  • Backward Compatibility Testing - Ensure that the applications continues to function properly on older versions during releases.

  • Performance & Stability Testing – Ensure that the application performs efficiently under expected loads and remains stable over time.

  • Collaboration with Developers – Work closely with engineers to understand implementation details, suggest improvements, and validate fixes.

  • Test bashes- Coordinating and managing test bashes effectively, while thoroughly evaluating all the feedback and points received.

  • Automation & Scripting – Develop and maintain automated tests to improve regression coverage and efficiency.

  • Security Testing – Identify vulnerabilities and ensure the application adheres to security best practices.

  • Process Improvement – Continuously refine QA practices and introduce new tools and methodologies to enhance efficiency.

Cadence

  • Biweekly QA Team Sync (Every Two Weeks) – A recurring meeting to discuss testing strategies, share insights on ongoing issues, and review upcoming work assignments.

  • Cross-Functional Check-ins – Ad hoc discussions with development teams to align on feature readiness and testing requirements.

  • Retrospective Sessions – Periodic reviews to assess testing effectiveness and refine QA processes.

Leader:

Deepak Totlani

Members:

  • Tanvi Khanduja

  • Tarun Sogani

  • +2 new hires

Contributors:

We don’t just find bugs, we prevent them. By testing, iterating, and optimizing, we ensure that every product we touch is ready for the real world. Quality is our commitment, and we design it into every step of the process.

PreviousDelivery TeamNextFE team

Last updated 13 days ago