Job title not found: careers beyond the label
Categories: Podcasts , Into The MoTaverse
The conversation examines the shift from traditional testing roles to hybrid quality engineering positions that blend development, design, and operations skills. It highlights how AI tools and interactive portfolios are becoming essential for standing out in a competitive market where job titles are increasingly fluid.
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=IqkK4VkzQ-s
- Published: 2026-11-18T16:48:35Z
- Duration: 01:00:38
- Author: MoTaverse
Overview
The conversation traces a QA engineer’s fourteen-year career path, beginning at age seventeen in Brazil through a government tax-incentive program that placed engineering students on Lenovo desktop-software testing projects at a public university. The journey progressed through manual testing, a social network called Zing, the dating app Bumble, and now Volkswagen Digital Hub, spanning manual testing, mobile automation, and web automation across B2C and automotive contexts.
A central theme is the evolving landscape of quality job titles and career identity. The discussion notes a shift from “tester” or “test automation” roles to “quality engineer” as the dominant title, with “QA” as a secondary label. The speaker describes struggling to name her own role amid overlapping skills - backend, DevOps, frontend, design - drawing on a Venn-diagram exercise that produced five intersection points rather than one clean label.
The conversation also addresses the AI revolution’s impact on hiring and career development. Hiring processes range from old-school CV uploads with zero-to-ten skill grading to AI-agent-driven matching. The speakers discuss the shrinking pipeline of junior positions, the difficulty college students face entering the field, and the possibility of using AI-generated portfolio pages or interactive “bot versions” of oneself to sell skills beyond a static CV.
What If
-
What if you vibe-code an interactive portfolio page from your existing professional profile data?
- Move: Use an AI tool (e.g., Lovable) to generate a small interactive page that lets a visitor ask you questions in real time, drawing on your logged events, courses, and project history.
- Why Now?: The source notes recruiters now “expect like a portfolio style page” beyond a CV, and the speaker suggests using a Ministry of Testing profile as a base for this exercise.
- Expected Upside: A proposal - recruiters or collaborators interact with a “bot version of you” that conveys skills a static CV omits, potentially surfacing matches you would miss through keyword filters alone.
-
What if you map your cross-specialty skills as a five-circle Venn diagram before updating your public title?
- Move: List every skill area you actively use (e.g., backend, DevOps, frontend, design, community), plot overlaps, and identify which intersections you want discoverable in keyword-based searches.
- Why Now?: The source describes a Venn exercise that yielded “five different intersection points” and warns that skipping a keyword to avoid “over-polluting” a title can cause missed opportunities.
- Expected Upside: A possibility - you retain a coherent personal brand while ensuring each intersection keyword is present somewhere in your profile, reducing the risk of being filtered out.
-
What if you designate yourself as a “guiding quality” connector across your solo projects?
- Move: After each project sprint, write a one-page learnings summary and cross-reference it against other active projects so patterns and pitfalls transfer without a manager or team meeting.
- Why Now?: The source describes a gap where QA people on different projects (mobile, backend, CRM) share no standardized process, and the speaker proposes a role that helps teams “observe the learnings from the other QA” without managing people.
- Expected Upside: A proposal - reducing duplicated mistakes across projects and building a reusable quality-principles library that compensates for the absence of a dedicated QA budget.
Takeaway
- Generate an interactive portfolio page with an AI tool using your existing professional profile as the data source, so recruiters can query your skills conversationally rather than scanning a static CV.
- Plot your active skill areas as overlapping circles and ensure each intersection keyword appears somewhere in your public profile to avoid being filtered out by keyword-based applicant systems.
- After every project or sprint, write a short cross-project learnings note so knowledge transfers between your own work streams without waiting for a formal review.
- Periodically feed your professional profile into an AI tool and ask it to describe you back, checking whether it surfaces skills you forgot to list and catching gaps before a recruiter does.
- When evaluating a role or project, match on demonstrated skills and eagerness to learn rather than insisting on a prior job-title keyword, since the source notes a candidate without a “tester” title may still “perfectly execute” the work.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.