Certified Pega Lead System Architect Trainer, (1099 Contractor)

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's parse posting. Content: - Intro: "Job Requirements Certified Pega Lead System Architect Trainer (1099 Contractor) At Fearless, we are seeking a 1099 contractor to serve as a Certified Pega Lead System Architect Trainer for a 10-week intensive training program preparing participants to design and implement enterprise-ready Pega applications. This role serves as the senior technical lead and primary instructional authority for a cohort advancing through Pega Senior System Architect curriculum, providing advanced instruction in application architecture, case management, data modeling, integration, security, performance optimization, and DevOps practices. The CLSA guides participants through complex demonstrations, architecture discussions, hands-on labs, and scenario-based exercises while collaborating with program leadership to tailor instruction to participant skill levels and maintain alignment with the approved training plan. This is a fully remote 1099 contractor engagement requiring approximately 20–24 hours per week for 10 weeks, with work performed between 9:00 a.m. and 5:00 p.m. ET." That's about the role. Then "Your Responsibilities In This Role" bullet list. Then "Work Experience Project Skill and Experience Requirements" (maybe Requirements). Then list of requirements. Then "Preferred Experience" maybe part of Requirements. Then "Physical Requirements" maybe part of Requirements or separate. Then "Benefits Life at Fearless" with description. Then "Compensation & Engagement Details" includes Pay info: "Fearless is committed to offering competitive contract rates that reflect the expertise, experience, and value our independent contractors bring to client engagements. Final rates are determined based on experience, qualifications, project requirements, and market considerations. This position is structured as an independent contractor (1099) engagement and is not eligible for employee compensation programs or benefits." Thus Pay is present but not specific numbers; it's generic. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The compensation description is generic but not placeholder? It says competitive contract rates, final rates determined based on experience... That's still vague but not exactly placeholder like "commensurate with experience". However it's still not a specific rate. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay info (though vague). Should we include? It says "never emit a heading followed by filler/placeholder text". The text is not exactly filler but it's vague. Might be considered filler? The phrase "competitive contract rates that reflect the expertise, experience, and value" is generic. I'd lean to include Pay section because they mention compensation details. But we must ensure not to include placeholder like "commensurate with experience". This is similar but not exactly that phrase. I'd include Pay with the paragraph. Schedule: They mention "approximately 20–24 hours per week for 10 weeks, with work performed between 9:00 a.m. and 5:00 p.m. ET." That's specific schedule info. So Schedule section should be included. Benefits: They have a Benefits section describing culture etc. That's substantive. So include Benefits. Now we need sections: About the role (intro), Responsibilities, Requirements (maybe combine Work Experience, Skill and Experience Requirements, Preferred Experience, Physical Requirements), Benefits, Pay, Schedule. Possibly Qualifications and Skills could be merged into Requirements. But we should only create sections when there is real specific content. We have content for Responsibilities, Requirements (including experience, certification, etc.), Benefits, Pay, Schedule. Also maybe Skills? The responsibilities already cover skills. But we could have a Skills section if there is explicit list. Not needed. Thus output:

About the role

... intro paragraph ...

Responsibilities

• ... each bullet ...

Requirements

• ... each requirement bullet ...

We need to capture all requirements bullet points: - Minimum of 5 years of Pega Platform experience in senior architecture, technical lead, or comparable roles. - Current Pega Certified Lead System Architect (PCLSA) certification. - Hands-on experience designing and implementing enterprise Pega applications from architecture through deployment. - Demonstrated expertise in Pega application and solution architecture, including case management, data modeling, integrations and APIs, and security implementation. - Proven experience conducting architecture and code reviews and mentoring Pega developers and Senior System Architects. - Demonstrated ability to deliver live, instructor-led technical training, hands-on labs, and individualized coaching in complex technical environments. - Expertise in performance optimization, debugging, deployment processes, and DevOps practices within the Pega Platform. - Preferred Experience: Experience implementing Pega solutions within federal, financial, tax-processing, or similarly complex regulated environments. - Physical Requirements: Ability to sit for extended periods while working on a computer or during meetings. Must be able to travel occasionally to client sites or company meetings, which may involve driving or flying. Ability to communicate effectively via phone, email, and in-person, requiring clear speech, listening, and written communication skills. Ability to move within an office environment, including reaching for files, using office equipment, and occasional light lifting (up to 10 pounds). We could separate Preferred Experience and Physical Requirements as sub-items but still within same ul. Now Benefits: paragraph(s) about Purple Culture etc. We'll capture the Benefits paragraph(s) after "Benefits Life at Fearless". The text includes multiple paragraphs. We'll combine into

maybe multiple

but rule: use

for prose. Could have multiple

under Benefits section. We'll output each paragraph as

. Pay: paragraph(s) from Compensation & Engagement Details. We'll output as

. Schedule: paragraph about hours and time. We'll output as

. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie etc. Also remove "So, What's Next?" etc. Also remove "Independent Contractor Requirements" etc. Also remove "Reasonable Accommodations". Also remove "Where You Can Partner with Fearless". Also remove "Skills Assessment (If Applicable)" etc. Also remove "Why Partner with Fearless?" maybe not needed as it's more marketing but could be considered boilerplate? It's not required to keep. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why Partner with Fearless?" is more marketing but not boilerplate; but could be considered fluff. However it's not duplicated. Might be okay to keep? But we should focus on substantive info. The "Why Partner with Fearless?" includes bullet points about mission-driven work etc. That's somewhat generic but could be considered part of Benefits? Might be okay to include under Benefits? But we already have Benefits section describing Purple Culture. The "Why Partner with Fearless?" is similar. To avoid duplication, we could omit it. The instruction: Prefer a few substantive sections over many thin ones. So we can omit that. Also remove "Independent Contractor Requirements" etc. That's more procedural; maybe not needed. But it's substantive about documentation needed. Could be considered part of Requirements? Might be considered "Requirements" but it's about contractor engagement docs. Could be included under Requirements as additional bullet. However the instruction says to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info. It's about documentation needed prior to start: Form W-9, Proof of General Liability Insurance, COI, compliance with project-specific customer requirements, etc. That's substantive. Should we create a separate section? Could be under Requirements as "Contractor Requirements". But we already have Requirements section for experience etc. Could add a sub-list under Requirements for "Contractor Documentation". However the instruction says use

• for any list of duties/requirements/benefits. So we can include those as list items under Requirements. Similarly "Reasonable Accommodations" is substantive; we could include under Requirements or maybe a separate section? It's about accommodations. Could be under Requirements as a note. But it's not a requirement for the role; it's a policy. Might be considered boilerplate? It's about accommodations for disabled applicants. Might be considered EEO/equal-opportunity boilerplate? It's similar to EEO. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Reasonable Accommodations is related to EEO. So we should remove that. "Where You Can Partner with Fearless" includes states list for W-2 employment footprint. That's not directly about the role; it's about future employment. Could be considered boilerplate? Might be removed. "Skills Assessment (If Applicable)" etc is about process; could be considered application instructions, which we should remove. Thus we keep: About the role, Responsibilities, Requirements (including experience, certification, preferred experience, physical requirements, contractor documentation), Benefits, Pay, Schedule. Now we need to ensure we don't repeat the job title as a heading. Already not. Now produce HTML fragment. Let's craft the About the role paragraph: combine the intro sentences. Intro: "At Fearless, we are seeking a 1099 contractor to serve as a Certified Pega Lead System Architect Trainer for a 10-week intensive training program preparing participants to design and implement enterprise-ready Pega applications. This role serves as the senior technical lead and primary instructional authority for a cohort advancing through Pega Senior System Architect curriculum, providing advanced instruction in application architecture, case management, data modeling, integration, security, performance optimization, and DevOps practices. The CLSA guides participants through complex demonstrations, architecture discussions, hands-on labs, and scenario-based exercises while collaborating with program leadership to tailor instruction to participant skill levels and maintain alignment with the approved training plan. This is a fully remote 1099 contractor engagement requiring approximately 20–24 hours per week for 10 weeks, with work performed between 9:00 a.m. and 5:00 p.m. ET." We could split schedule part out to Schedule section, but we already have schedule info there. However the About the role currently includes schedule; maybe we should move schedule details to Schedule section and keep About the role without schedule. The rule: we should not duplicate content. So we should not repeat schedule in both About and Schedule. So we should remove schedule from About and put it in Schedule section. Thus About the role paragraph: "At Fearless, we are seeking a 1099 contractor to serve as a Certified Pega Lead System Architect Trainer for a 10-week intensive training program preparing participants to design and implement enterprise-ready Pega applications. This role serves as the senior technical lead and primary instructional authority for a cohort advancing through Pega Senior System Architect curriculum, providing advanced instruction in application architecture, case management, data modeling, integration, security, performance optimization, and DevOps practices. The CLSA guides participants through complex demonstrations, architecture discussions, hands-on labs, and scenario-based exercises while collaborating with program leadership to tailor instruction to participant skill levels and maintain alignment with the approved training plan." Now Schedule section: "This is a fully remote 1099 contractor engagement requiring approximately 20–24 hours per week for 10 weeks, with work performed between 9:00 a.m. and 5:00 p.m. ET." Now Responsibilities list: need to extract each bullet from "Your Responsibilities In This Role". Let's list: - Deliver live, instructor-led training sessions covering Pega application architecture, case management, data modeling and integration, application security, and performance optimization. - Lead complex technical demonstrations and facilitate architecture and design discussions that prepare participants to build scalable, secure, and maintainable Pega applications. - Support participants during advanced labs and scenario-based exercises, providing real-time coaching on application