Senior Salesforce Developer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting: It includes "Who We Are" (company description) - maybe that is not a required heading; we can include as About the role? Actually "About the role" is typical heading for role description. The posting includes "Job Description:" then description of role. Also "Basic Requirements:" and "Additional Qualifications:" and "Responsibilities:" and "Public Trust Clearance" and "Work Location:" and "Why Tria?" etc. We need to extract substantive info and place under appropriate headings. We must not repeat job title as heading. Job title is Senior Salesforce Developer (implied). Not to repeat. We must not include Job ID etc. We must not include boilerplate: EEO, legal, CCPA, etc. Remove those. We must not include duplicated lines. We must not include navigation/cookie etc. We must not create sections like Pay, Schedule, Benefits unless posting actually states them. Benefits: there is mention of "top-tier benefits package" in Who We Are and Why Tria? but not specific details. The instruction: never create Benefits section unless posting actually states them. It says "We offer a top-tier benefits package to invest in your physical, mental, and financial health and wellness". That's a statement but not specific benefits. Is that enough? It says "top-tier benefits package" but not enumerated. The rule: never create a section followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "top-tier benefits package" is vague but not placeholder like TBD. It's a statement that they offer benefits. Might be acceptable to include Benefits section with that statement. However they also say "Tria invests in its employees with a top-tier benefits package to support their physical, mental, and financial well-being." That's similar. So we could include Benefits section with that sentence. Pay: no mention of salary. So omit Pay. Schedule: no mention of work schedule (full-time, etc). Not mentioned. Omit Schedule. We need sections: About the role (maybe from Job Description), Responsibilities, Requirements (maybe combine Basic Requirements and Additional Qualifications?), Qualifications (maybe certifications), Skills (maybe technical skills), Benefits (if we include). Also maybe "Work Location" could be under About the role or separate? Not a standard heading; we could incorporate into About the role as a paragraph. We must not repeat job title as heading. So we will not have a heading for Senior Salesforce Developer. We need to use

for section headings. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO, legal, CCPA, etc. Also remove "Know your rights poster" link, etc. Also remove duplicated lines: e.g., "Public Trust Clearance" appears twice? Actually appears in Basic Requirements and later a section "Public Trust Clearance". We need to keep info but not duplicate. Let's extract substantive content: Company description (Who We Are): multiple paragraphs about Tria Federal delivering digital services, supporting veterans, etc. This is substantive but not role-specific. Could be placed under About the role? Actually About the role usually describes the role, not company. But we have no other heading for company overview. Could we create a section "About the company"? Not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those. The company description could go under About the role as context? Might be okay. Job Description: "We are looking for a highly skilled Senior Salesforce Developer to join our team. The successful candidate has proven capability to develop solutions in Salesforce and will work with business analysts, architects, and other members of the team to help drive innovation using the Salesforce platform." That's role description. Basic Requirements: - Ability to obtain a U.S. Federal Position of Trust clearance designation. - Must reside in and be able to perform work in the United States. - Must have lived in the United States for 3 of the last 5 years. - Bachelor's degree (bachelor's degree in computer science or equivalent preferred). - A minimum of 5 years Salesforce (and 7 years of overall IT industry experience) with customization on the Salesforce Lightning platform. - Including Lightning components using the Lightning Design System, Lightning Web Components, or Lightning Aura Components and Apex (Batch, Controllers, Triggers). - Or, experience with declarative development on Salesforce using Flows and OmniStudio. Additional Qualifications: - Previous experience with Salesforce Sales Cloud, Service Cloud, and Experience Cloud. - Some experience with Salesforce integrations, both point-to-point and middleware. - Deployments using Copado preferred. - Knowledge of GIT and CI/CD is a must. - Strong communication and analytical skills. - Salesforce Certified Administrator. - Salesforce Certified Platform Developer I. - Salesforce Certified Platform Developer II (preferred). - Salesforce Certified JavaScript Developer (greatly preferred). - Salesforce Certified OmniStudio Consultant (greatly preferred). - Salesforce Certified OmniStudio Developer (greatly preferred). Responsibilities: - Develop and maintain Salesforce solutions according to business requirements and goals. - Work with a team of developers and follow the Salesforce best practices. - Perform code reviews. - Help establish the scope and effort estimates for development. - Ensure that development projects meet business requirements and goals, fulfill end-user requirements, and identify and resolve systems issues. - Be adaptable and willing to take on tasks that may fall outside of the typical responsibilities of a developer to help the team meet sprint goals, such as: - Help leads or architects with technical documentation. - Mentor developers blocked with any sprint tasks. - Unit testing and demos. - Propose new Salesforce solutions from recent releases and suggest industry best practices. - Collaborate with cross-functional team members, including product owners, business analysts, developers, and testers, to plan and execute project sprints. Public Trust Clearance: - Many of our roles require the hired candidate to go through public trust clearance. - A minimum of 3 years of stay in the U.S. within the last 5 years is required to be eligible to qualify for public trust clearance sponsorship. Work Location: - Headquartered in Arlington, VA, we also have a primary office in Baltimore, MD for those who prefer to work on-site. - However, with employees spread across 40+ states, we have many remote roles. Why Tria? (culture, benefits): - We offer a top-tier benefits package to invest in your physical, mental, and financial health and wellness so that you can be your best self - at work and in life. - At Tria, we are growth-minded, entrepreneurial in spirit, and committed to fostering a culture of inclusion and opportunity for all. - Whatever your background, your role, your department, or stage in your professional journey, here you will have opportunities to learn new skills, seize new challenges, and advance your career as we grow. Also earlier: "Tria invests in its employees with a top-tier benefits package to support their physical, mental, and financial well-being." Thus Benefits section can include those statements. We need to avoid duplication: The benefits statement appears multiple times; we can include once. We need to avoid boilerplate: EEO, legal, CCPA, etc. Remove those. Now decide sections: - About the role: Could combine company description and job description? Might be too much but okay. However we need to preserve all substantive info; we can put company description under About the role as introductory paragraph, then job description as another paragraph. But the heading "About the role" maybe expects description of the role, not company. However we have no other heading for company overview; we could still include it there as it's substantive and not elsewhere. Alternatively we could omit company description entirely? But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description. So we need to place it somewhere. The allowed headings list does not include "About the company". But we could still include it under About the role as it's still about the role context. I think it's acceptable. Thus About the role section will contain paragraphs: company description (Who We Are) and job description. Responsibilities: as list. Requirements: Could combine Basic Requirements and Additional Qualifications? But we also have Qualifications heading for certifications. The instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have separate Requirements and Qualifications. Likely Requirements = basic requirements (experience, education, clearance). Qualifications = certifications and preferred qualifications. Skills = technical skills (like Lightning components, Apex, GIT, CI/CD, communication, analytical). Benefits = benefits statements. We need to ensure we don't lose any info. Let's extract: Basic Requirements (list): - Ability to obtain a U.S. Federal Position of Trust clearance designation. - Must reside in and be able to perform work in the United States. - Must have lived in the United States for 3 of the last 5 years. - Bachelor's degree (bachelor's degree in computer science or equivalent preferred). - A minimum of 5 years Salesforce (and 7 years of overall IT industry experience) with customization on the Salesforce Lightning platform. - Including Lightning components using the Lightning Design System, Lightning Web Components, or Lightning Aura Components and Apex (Batch, Controllers, Triggers). - Or, experience with declarative development on Salesforce using Flows and OmniStudio. Additional Qualifications (list): - Previous experience with Salesforce Sales Cloud, Service Cloud, and Experience Cloud. - Some experience with Salesforce integrations, both point-to-point and middleware. - Deployments using Copado preferred. - Knowledge of GIT and CI/CD is a must. - Strong communication and analytical skills. - Salesforce Certified Administrator. - Salesforce Certified Platform Developer I. - Salesforce Certified Platform Developer II (preferred). - Salesforce Certified JavaScript Developer (greatly preferred). - Salesforce Certified OmniStudio Consultant (greatly preferred). - Salesforce Certified OmniStudio Developer (greatly preferred). We could split: Requirements = basic requirements (clearance, residency, years, degree). Qualifications = certifications and preferred experience (Sales Cloud, Service Cloud, Experience Cloud, integrations, Copado, GIT/CI-DD, communication, analytical). Skills = technical skills like Lightning components, Apex, Flows, OmniStudio, etc. But there is overlap. Better to follow typical pattern: Requirements = mandatory requirements (clearance, residency, degree, years experience). Qualifications = preferred qualifications (certifications, specific cloud experience, Copado, GIT/CI-DD, communication, analytical). Skills = technical skills (Lightning components, Apex, Flows, OmniStudio, etc). However the posting lumps many technical items under Basic Requirements (Lightning components, Apex, Flows, OmniStudio). Those are technical skills. So we could put them under Skills. Let's decide: Requirements (mandatory): - Ability to obtain a U.S. Federal Position of Trust clearance designation. - Must reside in and be able to perform work in the United States. - Must have lived in the United States for 3 of the last 5 years. - Bachelor's degree (bachelor's degree in computer science or equivalent preferred). - A minimum of 5 years Salesforce (and 7 years of overall IT industry experience). Qualifications (preferred/additional): - Experience with customization on the Salesforce Lightning platform (Lightning components using Lightning Design System, Lightning Web Components, or Lightning Aura Components and Apex (Batch, Controllers, Triggers)). - Or experience with declarative development on Salesforce using Flows