QA Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. We need to decide which sections we have content for.
We have:
- Summary: describes role. Could go under "About the role". That seems appropriate.
- Essential Duties & Responsibilities: map to "Responsibilities".
- Education & Experience: map to "Requirements" or "Qualifications". Could split: Education & Experience includes requirements and qualifications. We could put under "Requirements". Also we have "Skills" maybe from list: hands-on test automation, JavaScript, Playwright, etc. Could put under "Skills". But we need to avoid thin sections. Might combine.
- Travel Requirements: could be under "Schedule"? Actually travel is separate. Not in list. Could maybe put under "Schedule"? Not appropriate. Could omit if not matching headings. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should only output sections that match the allowed headings and have content. If we don't have content for Pay, Schedule, Benefits? We have Benefits (What We Offer). So we can include Benefits.
We have no explicit Pay or Schedule content. There's mention: "It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 2-3 days per week." That's schedule info. So we can include Schedule section with that content.
We have no explicit Pay. So omit Pay.
We have Benefits: "What We Offer" includes list of benefits. So Benefits section.
We have Qualifications: maybe we can put Education & Experience under Qualifications. But we also have Requirements. Could split: Requirements = mandatory experience (5+ years, etc). Qualifications = preferred (Bachelor's degree, etc). But we can keep simple: Use Requirements for the education & experience bullet list. Skills for specific technical skills (JavaScript, Playwright, .NET, JMeter, AI tools). Qualifications maybe for education preference. But we need to avoid thin sections. Might combine.
Let's decide sections:
- About the role: use Summary paragraph.
- Responsibilities: list of essential duties.
- Requirements: list of mandatory experience (5+ years, hands-on test automation, etc). Could include the bullet list from Education & Experience that are required.
- Skills: list of specific technical skills (JavaScript, Playwright, .NET-based frameworks, JMeter, AI/LLM tools, etc). Could also include cross-team communication, etc but that's more qualification.
- Qualifications: education preference (Bachelor's degree preferred) and maybe experience with enterprise platforms, mentoring, etc.
- Benefits: list from What We Offer.
- Schedule: hybrid schedule info.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details.
We need to format lists with - . For prose use
.
We must strip boilerplate: Diversity Commitment (EEO) should be removed. Also "About Us" maybe not needed as heading; we used Summary for About the role. The About Us paragraph about company could be considered boilerplate? It's company description; maybe we keep it as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not exactly boilerplate but it's company overview; could be considered part of About the role? Might keep it as part of About the role? But we already used Summary for About the role. Could combine both About Us and Summary into About the role section. That would preserve company info. Let's do that: About the role includes both company overview and role summary.
Thus About the role section: combine "About Us" paragraph and "Summary" paragraph.
Now Responsibilities: list of essential duties.
Requirements: from Education & Experience: mandatory items: 5+ years experience in software QA/testing, hands-on test automation development experience; JavaScript and Playwright experience preferred (maybe preferred, but still part of requirements). Demonstrated ability to design a test strategy and identify high-risk areas from a solution design or set of requirements. Experience designing and executing load/performance testing (e.g., with JMeter or a comparable tool). Experience using AI/LLM tools to generate or accelerate test cases, scripts, or other QA deliverables. Strong cross-team communication and coordination skills; comfortable acting as a point of contact across multiple stakeholder groups with competing priorities. Self-starter who is comfortable with ambiguity, context-switching across applications, and taking ownership of problems without waiting to be assigned. Demonstrated ability to lead and direct the work of team members on priority and specialized testing initiatives — setting priorities and ensuring the team completes tasks on time. Bachelor's degree in Computer Science, Information Systems, or a related field preferred; equivalent practical experience will also be considered. Experience testing or supporting enterprise platforms such as Salesforce, SAP, or custom-built enterprise applications. Experience building or scaling integration test suites across upstream/downstream systems. Prior experience mentoring or informally leading other QA engineers. Travel up to 25% (maybe schedule? but travel is separate). We'll keep travel maybe under Requirements? But we have Schedule section for hybrid schedule; travel could be separate but not in allowed headings. Could include under Requirements as a bullet.
But we need to avoid thin sections; we have many items; okay.
Skills: maybe we can extract specific technical skills: JavaScript, Playwright, .NET-based frameworks, JMeter, AI/LLM tools (GitHub Copilot, ChatGPT, Claude), load/performance testing, test automation, etc. However many of these overlap with Requirements. To avoid duplication, we could keep Requirements as the list of experience/qualifications, and Skills as a short list of technical proficiencies: JavaScript, Playwright, .NET, JMeter, AI/LLM tools. But we must preserve all substantive information; if we move some items to Skills, we must not lose them. We could keep Requirements as the experience bullets, and Skills as a separate list of specific tools/languages. That seems okay.
Qualifications: maybe education preference and enterprise platform experience, mentoring. But we already have education in Requirements. Could shift education to Qualifications. Let's decide:
- Requirements: mandatory experience (5+ years, hands-on test automation, ability to design test strategy, load/performance testing, AI/LLM tools, cross-team communication, self-starter, lead team, etc). Also travel up to 25% maybe.
- Skills: JavaScript, Playwright, .NET-based frameworks, JMeter, AI/LLM tools (GitHub Copilot, ChatGPT, Claude), test automation development.
- Qualifications: Bachelor's degree preferred (or equivalent), experience with enterprise platforms (Salesforce, SAP, custom-built), experience building/scaling integration test suites, prior mentoring/leading QA engineers.
- Benefits: list from What We Offer.
- Schedule: hybrid schedule (2-3 days in-office/show-site).
Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now produce HTML.
Structure:
About the role
... combined About Us and Summary ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Schedule
... hybrid schedule ...
We must not include any extra text.
Now we need to extract exact sentences.
About Us paragraph: "The Freeman Company is a global leader in events, on a mission to redefine live for a new era. With a data-driven approach and the industry’s largest network of experts, The Freeman Company's insights shape exhibitions, exhibits, and events that drive audiences to action. The integrated full-service solutions leverage a 99-year legacy in event management as well as new technologies to deliver moments that matter."
Summary paragraph: "The QA Lead is a senior, cross-functional quality assurance role overseeing the Application QA group — who handle day-to-day testing, regression, and change validation for their application. This role ensures Application QA consistently follows established process and standards and serves as an escalation point. The QA Lead's other primary responsibility is leading priority and specialized testing — work that falls outside traditional application QA scope or supports new initiatives — either executing it personally or coordinating the right resources depending on scope. The role also builds out the team's load/performance testing capability and champions the use of AI to accelerate test creation and other QA activities. The QA Lead reports directly to the QA Manager. This position will support our Technology Services team. It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 2-3 days per week. The ideal candidate will be based out of any of the following locations: Dallas, TXOrlando, FL"
Note: there is a missing space between TX and Orlando; but we keep as is.
We'll combine these two paragraphs into About the role.
Now Responsibilities list: from "Essential Duties & Responsibilities". Each bullet starts with a verb. We need to capture each bullet exactly.
List:
- Serve as the escalation point for the Application QA team — answering process questions, resolving ambiguity, and providing backfill coverage when team members are unavailable.
- Lead priority and specialized testing initiatives that fall outside traditional application QA scope — whether within an existing application or as part of a new initiative — either executing the work personally or coordinating the right resources depending on scope.
- Partner with QA team members to ensure testing standards, processes, and best practices are consistently understood and followed across all teams.
- Own one-off and ad hoc requests as they arise — either leading the effort by coordinating the right people, or performing the work directly, depending on scope and urgency.
- Evaluate proposed development solutions and technical designs to build a test strategy and approach, identifying high-risk areas and prioritizing test coverage accordingly.
- Work across multiple teams to extract and document how existing functionality works, break complex features into testable components, and coordinate cross-team execution and documentation of end-to-end testing results.
- Design, build, and execute load and performance testing plans to validate system scalability, reliability, and readiness for key events or releases (e.g., using tools such as JMeter).
- Utilize AI tools (e.g., GitHub Copilot, ChatGPT, Claude) to generate test cases, performance test scripts, and other QA artifacts, improving team efficiency and coverage.
- Develop and maintain test automation using JavaScript, Playwright and .NET-based frameworks; contribute to and help scale the team's overall automation practice.
- Hold and participate in regular knowledge-transfer sessions across teams to build shared understanding of integrated applications and reduce single-point-of-failure risk.
- Provide regular status updates and proactively escalate risks, blockers, or process gaps to the QA Manager.
Now Requirements list: from Education & Experience, we need to pick items that are mandatory/experience. Let's list each bullet:
- 5+
. We must strip boilerplate: Diversity Commitment (EEO) should be removed. Also "About Us" maybe not needed as heading; we used Summary for About the role. The About Us paragraph about company could be considered boilerplate? It's company description; maybe we keep it as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not exactly boilerplate but it's company overview; could be considered part of About the role? Might keep it as part of About the role? But we already used Summary for About the role. Could combine both About Us and Summary into About the role section. That would preserve company info. Let's do that: About the role includes both company overview and role summary. Thus About the role section: combine "About Us" paragraph and "Summary" paragraph. Now Responsibilities: list of essential duties. Requirements: from Education & Experience: mandatory items: 5+ years experience in software QA/testing, hands-on test automation development experience; JavaScript and Playwright experience preferred (maybe preferred, but still part of requirements). Demonstrated ability to design a test strategy and identify high-risk areas from a solution design or set of requirements. Experience designing and executing load/performance testing (e.g., with JMeter or a comparable tool). Experience using AI/LLM tools to generate or accelerate test cases, scripts, or other QA deliverables. Strong cross-team communication and coordination skills; comfortable acting as a point of contact across multiple stakeholder groups with competing priorities. Self-starter who is comfortable with ambiguity, context-switching across applications, and taking ownership of problems without waiting to be assigned. Demonstrated ability to lead and direct the work of team members on priority and specialized testing initiatives — setting priorities and ensuring the team completes tasks on time. Bachelor's degree in Computer Science, Information Systems, or a related field preferred; equivalent practical experience will also be considered. Experience testing or supporting enterprise platforms such as Salesforce, SAP, or custom-built enterprise applications. Experience building or scaling integration test suites across upstream/downstream systems. Prior experience mentoring or informally leading other QA engineers. Travel up to 25% (maybe schedule? but travel is separate). We'll keep travel maybe under Requirements? But we have Schedule section for hybrid schedule; travel could be separate but not in allowed headings. Could include under Requirements as a bullet. But we need to avoid thin sections; we have many items; okay. Skills: maybe we can extract specific technical skills: JavaScript, Playwright, .NET-based frameworks, JMeter, AI/LLM tools (GitHub Copilot, ChatGPT, Claude), load/performance testing, test automation, etc. However many of these overlap with Requirements. To avoid duplication, we could keep Requirements as the list of experience/qualifications, and Skills as a short list of technical proficiencies: JavaScript, Playwright, .NET, JMeter, AI/LLM tools. But we must preserve all substantive information; if we move some items to Skills, we must not lose them. We could keep Requirements as the experience bullets, and Skills as a separate list of specific tools/languages. That seems okay. Qualifications: maybe education preference and enterprise platform experience, mentoring. But we already have education in Requirements. Could shift education to Qualifications. Let's decide: - Requirements: mandatory experience (5+ years, hands-on test automation, ability to design test strategy, load/performance testing, AI/LLM tools, cross-team communication, self-starter, lead team, etc). Also travel up to 25% maybe. - Skills: JavaScript, Playwright, .NET-based frameworks, JMeter, AI/LLM tools (GitHub Copilot, ChatGPT, Claude), test automation development. - Qualifications: Bachelor's degree preferred (or equivalent), experience with enterprise platforms (Salesforce, SAP, custom-built), experience building/scaling integration test suites, prior mentoring/leading QA engineers. - Benefits: list from What We Offer. - Schedule: hybrid schedule (2-3 days in-office/show-site). Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now produce HTML. Structure:
About the role
... combined About Us and Summary ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Schedule
... hybrid schedule ...
We must not include any extra text. Now we need to extract exact sentences. About Us paragraph: "The Freeman Company is a global leader in events, on a mission to redefine live for a new era. With a data-driven approach and the industry’s largest network of experts, The Freeman Company's insights shape exhibitions, exhibits, and events that drive audiences to action. The integrated full-service solutions leverage a 99-year legacy in event management as well as new technologies to deliver moments that matter." Summary paragraph: "The QA Lead is a senior, cross-functional quality assurance role overseeing the Application QA group — who handle day-to-day testing, regression, and change validation for their application. This role ensures Application QA consistently follows established process and standards and serves as an escalation point. The QA Lead's other primary responsibility is leading priority and specialized testing — work that falls outside traditional application QA scope or supports new initiatives — either executing it personally or coordinating the right resources depending on scope. The role also builds out the team's load/performance testing capability and champions the use of AI to accelerate test creation and other QA activities. The QA Lead reports directly to the QA Manager. This position will support our Technology Services team. It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 2-3 days per week. The ideal candidate will be based out of any of the following locations: Dallas, TXOrlando, FL" Note: there is a missing space between TX and Orlando; but we keep as is. We'll combine these two paragraphs into About the role. Now Responsibilities list: from "Essential Duties & Responsibilities". Each bullet starts with a verb. We need to capture each bullet exactly. List: - Serve as the escalation point for the Application QA team — answering process questions, resolving ambiguity, and providing backfill coverage when team members are unavailable. - Lead priority and specialized testing initiatives that fall outside traditional application QA scope — whether within an existing application or as part of a new initiative — either executing the work personally or coordinating the right resources depending on scope. - Partner with QA team members to ensure testing standards, processes, and best practices are consistently understood and followed across all teams. - Own one-off and ad hoc requests as they arise — either leading the effort by coordinating the right people, or performing the work directly, depending on scope and urgency. - Evaluate proposed development solutions and technical designs to build a test strategy and approach, identifying high-risk areas and prioritizing test coverage accordingly. - Work across multiple teams to extract and document how existing functionality works, break complex features into testable components, and coordinate cross-team execution and documentation of end-to-end testing results. - Design, build, and execute load and performance testing plans to validate system scalability, reliability, and readiness for key events or releases (e.g., using tools such as JMeter). - Utilize AI tools (e.g., GitHub Copilot, ChatGPT, Claude) to generate test cases, performance test scripts, and other QA artifacts, improving team efficiency and coverage. - Develop and maintain test automation using JavaScript, Playwright and .NET-based frameworks; contribute to and help scale the team's overall automation practice. - Hold and participate in regular knowledge-transfer sessions across teams to build shared understanding of integrated applications and reduce single-point-of-failure risk. - Provide regular status updates and proactively escalate risks, blockers, or process gaps to the QA Manager. Now Requirements list: from Education & Experience, we need to pick items that are mandatory/experience. Let's list each bullet: - 5+