Judy Mosley transitions from a stay-at-home mom and special education teacher to tech via a coding bootcamp, leveraging community-driven QA and inclusivity as a Moverse ambassador. She emphasizes QA’s undervalued role, the need for inclusive leadership, and systemic changes to recognize underrepresented voices in tech.

Into The MoTaverse

Rosie Sherry interviews people involved in testing. Video only interviews. Available on youtube or the homepage. Each episode has a full transcript if you find it on the main site.

• https://www.ministryoftesting.com/podcasts/into-the-motaverse
• https://www.youtube.com/playlist?list=PLbdLjg29s9lCY4hspzj3AGdAL7Vr2ys1B

Episode Details

• Show Notes: https://www.youtube.com/watch?v=PLsD-1o3oC4
• Published: 2026-03-18T16:32:26Z
• Duration: 00:00:00
• Author: MoTaverse

Overview

The podcast discusses Judy Mosleys role as a quality engineer and Moverse ambassador, emphasizing the importance of community-driven initiatives like call for insights to foster collaboration and credibility through one-on-one conversations. Her career journey highlights a transition from a decade-long hiatus as a stay-at-home mom and special education teacher into tech via a coding bootcamp (Code Louisville), which provided free training and job placement support. Initially entering QA as a stepping stone, Judy discovered her strength in critical questioning and later shifted to a community-focused ambassador role, leveraging her technical and interpersonal skills. The bootcamps emphasis on diversity and inclusion, along with mentorship from figures like Becky Steele, played a pivotal role in her confidence and career growth, though the programs recent shutdown is noted as a bittersweet moment for the community.

The discussion also explores challenges faced by underrepresented groups in tech, including the need for inclusive leadership and visible representation. Judy reflects on the disparity in recognition for QA work, the struggles of being a lone tester in environments where trust and communication are critical, and the importance of balancing adaptability with the need for clear, human-centered bug reporting practices. The evolution of QA practicesfrom rigid, detailed reporting to concise, context-driven documentationis highlighted, alongside the growing use of AI in code reviews and bug logging. Judy underscores the value of community for support and shared learning, advocating for intentional inclusion of QA voices in projects and recognition of their contributions to ensure equitable team dynamics and project success.

Key themes include the intersection of personal storytelling in sparking interest in tech, the challenges of self-advocacy for visibility in leadership roles, and the cultural shift toward blunt, inclusive communication in tech teams. Judy also addresses the exhaustion of constant self-advocacy for underrepresented individuals and the need for systemic changes to prioritize diversity and recognition. Her work emphasizes the importance of documentation, collaborative quality engineering, and tools like Slack for centralized logging and transparency, while balancing AI efficiency with human authenticity in workflows. The narrative concludes with a focus on fostering visibility for QA roles and creating equitable spaces for all contributors, ensuring their efforts are celebrated and integrated into team success.

What If

• What if you started a “Call for Insights” program to build community credibility?
  Move: Host biweekly 1:1 video calls with developers or testers in your network to discuss challenges, share workflows, and gather feedback.
  Why now: As a solo operator, building trust through personal connections is critical for collaboration and long-term reliability.
  Expected upside: Strengthened relationships with stakeholders, increased visibility of your work, and a pipeline for community-driven improvements.

• What if you advocated for your role as a lone tester by embedding yourself in early project discussions?
  Move: Proactively request to be included in sprint planning and design reviews, even when not explicitly invited. Frame your input as “risk mitigation.”
  Why now: Systemic exclusion as a lone tester risks oversight of critical QA needs. Early inclusion ensures your insights shape project direction.
  Expected upside: Higher team trust, reduced rework, and recognition of your role in preventing failures.

• What if you automated repetitive bug reporting tasks using AI tools with a human-readable tag?
  Move: Use AI to generate bug reports (steps, screenshots, context) and add a #AI-Assisted tag to tickets. Share updates in Slack lists for transparency.
  Why now: Manual reporting is time-consuming, but developers may dismiss vague or inconsistent logs. AI tools ensure consistency.
  Expected upside: Faster issue resolution, reduced friction with developers, and a documented knowledge base for future troubleshooting.

Takeaway

• Leverage Community-Driven Initiatives for Visibility: Actively participate in or start “call for insights” campaigns within your industry to foster collaboration, share knowledge, and build credibility as a thought leader, even as a solo operator.
• Document Processes and Observations Systematically: Use tools like Slack lists or shared channels to log bug reports, questions, and project updates in a centralized, searchable format, ensuring transparency and reducing redundant work.
• Refine Bug Reporting with Context and Clarity: Prioritize detailed, reproducible bug reports by including steps to reproduce, context, and resolved flags, while avoiding vague or intermittent issues to maintain developer trust and efficiency.
• Advocate for Inclusion in Team Dynamics: Proactively request invitations to project meetings and discussions to ensure your input is valued, and use personal storytelling or public recognition (e.g., saved compliments) to highlight your contributions.
• Utilize AI Tools Strategically: Automate repetitive tasks like bug report generation with AI, but maintain transparency by tagging AI-assisted work and balancing efficiency with a personal, human-centric tone in documentation.