Pega Certified Senior System Architect Trainer, (1099 Contractor)
Fearless · Baltimore, MD · 3 wk ago
RemoteRemoteEngineeringFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Role: Pega Certified Senior System Architect Trainer (1099 Contractor)
- At Fearless, seeking a 1099 contractor to serve as trainer to deliver a 10-week instructor-led training program preparing participants to develop enterprise Pega applications and earn Senior System Architect certification.
- Combines deep Pega expertise with hands-on teaching, guiding learners through case management, integration, data modeling, security, troubleshooting using structured curriculum.
- Trainer translates technical concepts into practical skills via live instruction, labs, demos, individualized coaching, ensuring participants prepared to implement Pega solutions in complex enterprise environments.
- Fully remote 1099 contractor engagement requiring approx 20–24 hours per week for 10 weeks, with work performed between 9:00 a.m. and 5:00 p.m. EST.
Responsibilities (list):
- Deliver live instructor-led sessions covering Pega application development, case and process logic, data modeling, integrations, and security practices.
- Facilitate hands-on labs where participants configure and extend Pega applications, implement business logic, and troubleshoot implementation challenges.
- Provide real-time technical assistance during lab exercises, diagnosing configuration issues and demonstrating corrective techniques.
- Review participant work, provide individualized feedback, and reinforce difficult concepts to build proficiency in Senior System Architect competencies.
- Conduct knowledge checks and certification-aligned activities to evaluate participant readiness for Pega Senior System Architect certification.
- Collaborate with the Certified Lead System Architect to assess participant progress, identify knowledge gaps, and adjust instruction to strengthen skill development.
- Demonstrate testing, debugging, source control, and deployment practices applicable to enterprise Pega application environments.
Work Experience / Skill and Experience Requirements:
- Minimum of 5 years of hands-on Pega application development experience.
- Current Pega Certified Senior System Architect (PCSSA) certification is required.
- Proven experience performing Senior System Architect-level responsibilities in enterprise Pega implementations.
- Demonstrated expertise in case management, application configuration, data modeling, integrations, security, testing, and debugging.
- Experience supporting enterprise Pega applications throughout the full application lifecycle.
- Demonstrated experience delivering live instructor-led Pega training, hands-on labs, technical demonstrations, mentoring, or developer coaching.
Preferred Experience:
- Experience implementing Pega solutions within federal, financial, tax-processing, or similarly complex regulated environments.
- Experience preparing practitioners for Pega Senior System Architect certification.
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).
Benefits: The "Life at Fearless" paragraph describing culture, Purple Culture, etc. Also "Compensation & Engagement Details" says they offer competitive contract rates, final rates based on experience etc. This position is structured as independent contractor (1099) engagement and is not eligible for employee compensation programs or benefits. Then "Why Partner with Fearless?" bullet list.
We need Benefits section only if posting actually states them. There's a description of culture but not explicit benefits like health insurance etc. The posting says independent contractors not eligible for employee compensation programs or benefits. So there is no benefits offered. Should we include Benefits section? The rule: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Since there is no benefits offered, we should not create Benefits section. However there is a "Life at Fearless" description which is more about culture; could be considered "About the role" or maybe "About Fearless". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have "About the role" containing description of role and maybe culture. But we need to avoid filler. The "Life at Fearless" is substantive but not exactly about the role; still could go under About the role or maybe a separate section like "About Fearless" but not in allowed list. Probably we put it under About the role.
Pay: The posting says "Final rates are determined based on experience, qualifications, project requirements, and market considerations." That's not a specific number; it's vague. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Pay section because it's not specific. Similarly Schedule: they gave approx 20–24 hours per week for 10 weeks, work between 9:00 a.m. and 5:00 p.m. EST. That's specific enough for schedule. So we can include Schedule section with that info.
Requirements: We have skill and experience requirements (mandatory). Could be under Requirements heading. Also there is "Work Experience" heading but we can combine.
Qualifications: Could be same as Requirements? Usually Qualifications separate. But we have both mandatory and preferred experience. Could put mandatory under Requirements, preferred under Qualifications or Skills. But we need to avoid thin sections. Let's think: We have Responsibilities, Requirements (mandatory), Preferred Experience (maybe under Qualifications), Skills (maybe list of skills like case management etc). However the posting already lists skills in requirements. Could combine.
Better to have sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Possibly also Skills if distinct.
But we must not create sections with filler. Let's extract substantive content for each.
About the role: description of role, mission, remote, hours, duration, etc. Also maybe include "Life at Fearless" culture description.
Responsibilities: list as above.
Requirements: mandatory experience and certification etc.
Qualifications: preferred experience (federal etc) and experience preparing practitioners for certification.
Skills: maybe list of specific skills like case management, application configuration, data modeling, integrations, security, testing, debugging, source control, deployment, etc. But those are already in requirements. Could still list under Skills.
But to avoid duplication, we could put skills under Requirements. However the instruction says use sections as appropriate; we can have both Requirements and Skills if content distinct.
Let's decide: We'll have:
- About the role (paragraph(s))
- Responsibilities (ul)
- Requirements (ul) for mandatory
- Qualifications (ul) for preferred
- Schedule (p) for hours/week and time window.
We'll not include Benefits, Pay.
Now ensure we preserve all substantive info: also mention that it's fully remote 1099 contractor, 20-24 hrs/week for 10 weeks, 9-5 EST.
Also mention that independent contractor not eligible for employee benefits.
But we said we won't include Benefits section because no benefits offered. However we could mention that in About the role or maybe a note. The rule: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the statement about independent contractor not eligible for employee compensation programs or benefits. Where to put? Could be under About the role as a note. Or maybe under Requirements? Probably About the role.
Also mention "Compensation & Engagement Details: Final rates are determined based on experience, qualifications, project requirements, and market considerations." This is vague; we decided not to include Pay section because it's not specific. But we still need to preserve that statement somewhere. Could be under About the role as a note about compensation being determined case-by-case. That's substantive but vague. However the rule says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". That refers to headings; but we can still include that sentence in a paragraph under About the role, as it's not a heading with filler. It's okay.
Similarly "Why Partner with Fearless?" bullet list is substantive; we could include under About the role or maybe a separate section like "Why Partner with Fearless?" but not in allowed headings. Could incorporate into About the role.
We must not include boilerplate like EEO, equal opportunity, scam-warning, etc. The posting includes "We're proud to be an equal opportunity organization." That's boilerplate; we should remove. Also "Reasonable Accommodations" etc. That's also boilerplate? Might be considered substantive but it's about accommodations; could be kept? It's not boilerplate exactly but it's a standard statement. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO/equal-opportunity boilerplate. Reasonable Accommodations might be considered legal; but it's about providing accommodations; could be considered legal. Safer to remove it. Also "Independent Contractor Requirements" about W-9, insurance etc. That's application instructions? It's documentation needed prior to start. Might be considered application instructions; we should remove? The instruction says remove application instructions. So we should remove the list of documentation needed (W-9, COI, etc). Also "So, What's Next?" etc about interview process - that's application instructions; remove. Also "Where You Can Partner with Fearless" about states - that's maybe not application instructions but could be considered info about contractor eligibility; might be substantive? It's about where they can engage. Could be kept under About the role? Might be considered relevant. However it's somewhat procedural. The instruction says remove application instructions; this is more about eligibility. Might keep? Not sure. Safer to keep only core role info.
We'll keep: About the role (description, remote, hours, duration, compensation note, culture, why partner). Responsibilities, Requirements, Qualifications, Schedule.
Now craft HTML.
We'll use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Role: Pega Certified Senior System Architect Trainer (1099 Contractor)
- At Fearless, seeking a 1099 contractor to serve as trainer to deliver a 10-week instructor-led training program preparing participants to develop enterprise Pega applications and earn Senior System Architect certification.
- Combines deep Pega expertise with hands-on teaching, guiding learners through case management, integration, data modeling, security, troubleshooting using structured curriculum.
- Trainer translates technical concepts into practical skills via live instruction, labs, demos, individualized coaching, ensuring participants prepared to implement Pega solutions in complex enterprise environments.
- Fully remote 1099 contractor engagement requiring approx 20–24 hours per week for 10 weeks, with work performed between 9:00 a.m. and 5:00 p.m. EST.
Responsibilities (list):
- Deliver live instructor-led sessions covering Pega application development, case and process logic, data modeling, integrations, and security practices.
- Facilitate hands-on labs where participants configure and extend Pega applications, implement business logic, and troubleshoot implementation challenges.
- Provide real-time technical assistance during lab exercises, diagnosing configuration issues and demonstrating corrective techniques.
- Review participant work, provide individualized feedback, and reinforce difficult concepts to build proficiency in Senior System Architect competencies.
- Conduct knowledge checks and certification-aligned activities to evaluate participant readiness for Pega Senior System Architect certification.
- Collaborate with the Certified Lead System Architect to assess participant progress, identify knowledge gaps, and adjust instruction to strengthen skill development.
- Demonstrate testing, debugging, source control, and deployment practices applicable to enterprise Pega application environments.
Work Experience / Skill and Experience Requirements:
- Minimum of 5 years of hands-on Pega application development experience.
- Current Pega Certified Senior System Architect (PCSSA) certification is required.
- Proven experience performing Senior System Architect-level responsibilities in enterprise Pega implementations.
- Demonstrated expertise in case management, application configuration, data modeling, integrations, security, testing, and debugging.
- Experience supporting enterprise Pega applications throughout the full application lifecycle.
- Demonstrated experience delivering live instructor-led Pega training, hands-on labs, technical demonstrations, mentoring, or developer coaching.
Preferred Experience:
- Experience implementing Pega solutions within federal, financial, tax-processing, or similarly complex regulated environments.
- Experience preparing practitioners for Pega Senior System Architect certification.
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).
Benefits: The "Life at Fearless" paragraph describing culture, Purple Culture, etc. Also "Compensation & Engagement Details" says they offer competitive contract rates, final rates based on experience etc. This position is structured as independent contractor (1099) engagement and is not eligible for employee compensation programs or benefits. Then "Why Partner with Fearless?" bullet list.
We need Benefits section only if posting actually states them. There's a description of culture but not explicit benefits like health insurance etc. The posting says independent contractors not eligible for employee compensation programs or benefits. So there is no benefits offered. Should we include Benefits section? The rule: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Since there is no benefits offered, we should not create Benefits section. However there is a "Life at Fearless" description which is more about culture; could be considered "About the role" or maybe "About Fearless". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have "About the role" containing description of role and maybe culture. But we need to avoid filler. The "Life at Fearless" is substantive but not exactly about the role; still could go under About the role or maybe a separate section like "About Fearless" but not in allowed list. Probably we put it under About the role.
Pay: The posting says "Final rates are determined based on experience, qualifications, project requirements, and market considerations." That's not a specific number; it's vague. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Pay section because it's not specific. Similarly Schedule: they gave approx 20–24 hours per week for 10 weeks, work between 9:00 a.m. and 5:00 p.m. EST. That's specific enough for schedule. So we can include Schedule section with that info.
Requirements: We have skill and experience requirements (mandatory). Could be under Requirements heading. Also there is "Work Experience" heading but we can combine.
Qualifications: Could be same as Requirements? Usually Qualifications separate. But we have both mandatory and preferred experience. Could put mandatory under Requirements, preferred under Qualifications or Skills. But we need to avoid thin sections. Let's think: We have Responsibilities, Requirements (mandatory), Preferred Experience (maybe under Qualifications), Skills (maybe list of skills like case management etc). However the posting already lists skills in requirements. Could combine.
Better to have sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Possibly also Skills if distinct.
But we must not create sections with filler. Let's extract substantive content for each.
About the role: description of role, mission, remote, hours, duration, etc. Also maybe include "Life at Fearless" culture description.
Responsibilities: list as above.
Requirements: mandatory experience and certification etc.
Qualifications: preferred experience (federal etc) and experience preparing practitioners for certification.
Skills: maybe list of specific skills like case management, application configuration, data modeling, integrations, security, testing, debugging, source control, deployment, etc. But those are already in requirements. Could still list under Skills.
But to avoid duplication, we could put skills under Requirements. However the instruction says use sections as appropriate; we can have both Requirements and Skills if content distinct.
Let's decide: We'll have:
- About the role (paragraph(s))
- Responsibilities (ul)
- Requirements (ul) for mandatory
- Qualifications (ul) for preferred
- Schedule (p) for hours/week and time window.
We'll not include Benefits, Pay.
Now ensure we preserve all substantive info: also mention that it's fully remote 1099 contractor, 20-24 hrs/week for 10 weeks, 9-5 EST.
Also mention that independent contractor not eligible for employee benefits.
But we said we won't include Benefits section because no benefits offered. However we could mention that in About the role or maybe a note. The rule: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the statement about independent contractor not eligible for employee compensation programs or benefits. Where to put? Could be under About the role as a note. Or maybe under Requirements? Probably About the role.
Also mention "Compensation & Engagement Details: Final rates are determined based on experience, qualifications, project requirements, and market considerations." This is vague; we decided not to include Pay section because it's not specific. But we still need to preserve that statement somewhere. Could be under About the role as a note about compensation being determined case-by-case. That's substantive but vague. However the rule says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". That refers to headings; but we can still include that sentence in a paragraph under About the role, as it's not a heading with filler. It's okay.
Similarly "Why Partner with Fearless?" bullet list is substantive; we could include under About the role or maybe a separate section like "Why Partner with Fearless?" but not in allowed headings. Could incorporate into About the role.
We must not include boilerplate like EEO, equal opportunity, scam-warning, etc. The posting includes "We're proud to be an equal opportunity organization." That's boilerplate; we should remove. Also "Reasonable Accommodations" etc. That's also boilerplate? Might be considered substantive but it's about accommodations; could be kept? It's not boilerplate exactly but it's a standard statement. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO/equal-opportunity boilerplate. Reasonable Accommodations might be considered legal; but it's about providing accommodations; could be considered legal. Safer to remove it. Also "Independent Contractor Requirements" about W-9, insurance etc. That's application instructions? It's documentation needed prior to start. Might be considered application instructions; we should remove? The instruction says remove application instructions. So we should remove the list of documentation needed (W-9, COI, etc). Also "So, What's Next?" etc about interview process - that's application instructions; remove. Also "Where You Can Partner with Fearless" about states - that's maybe not application instructions but could be considered info about contractor eligibility; might be substantive? It's about where they can engage. Could be kept under About the role? Might be considered relevant. However it's somewhat procedural. The instruction says remove application instructions; this is more about eligibility. Might keep? Not sure. Safer to keep only core role info.
We'll keep: About the role (description, remote, hours, duration, compensation note, culture, why partner). Responsibilities, Requirements, Qualifications, Schedule.
Now craft HTML.
We'll use for each section heading.
Inside sections, use
for prose,
- for lists.
We must not repeat job title as heading.
Let's draft.
About the role: combine paragraphs:
- At Fearless, we are seeking a 1099 contractor to serve as a Pega Certified Senior System Architect Trainer to deliver a 10-week instructor-led training program preparing participants to develop enterprise Pega applications and earn Senior System Architect certification.
- This role combines deep Pega platform expertise with hands-on teaching, guiding learners through case management, integration, data modeling, security, and troubleshooting using a structured curriculum designed by Fearless.
- The trainer translates technical concepts into practical skills through live instruction, labs, demonstrations, and individualized coaching, ensuring participants are prepared to implement Pega solutions in complex enterprise environments.
- 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. EST.
- 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.
- At Fearless, we combine technology, people, and organizational development to solve meaningful problems... (the Purple Culture paragraph). Could be shortened but must preserve all substantive info; we need to keep the culture description. It's long but we must keep it all. However we can keep as is; it's substantive.
- Why Partner with Fearless? bullet list: we can include as
- inside About the role or separate? Might be better as its own section but not allowed heading. We'll include as
- under About the role after culture.
We must ensure we don't duplicate lines.
Now Responsibilities: list as given.
Requirements: mandatory