Salesforce Solution Engineer (Developer)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. From posting: - "What You Will Do" corresponds to Responsibilities (list of duties). So we need

Responsibilities

with

• items. - "What You Will Need" corresponds to Requirements/Qualifications/Skills. The posting includes many bullet-like sentences. We need to decide how to split. Could have Requirements (education, experience), Qualifications (certifications, clearance), Skills (technical). But we can also combine into one section if content is thin? The instruction: Prefer a few substantive sections over many thin ones. But we need to follow headings list: we can use multiple if they have substantive content. We have: Bachelor's degree required. Preferred in CS, IS, Engineering, or related technical discipline. Minimum of FIVE (5) years of hands-on Salesforce development experience, including at least two full implementation delivered to production. Demonstrated Apex proficiency: trigger frameworks, asynchronous processing, SOQL/SOSL optimization, bulkification, exception handling, and governor limit management. Lightning Web Component development with solid modern JavaScript fundamentals (ES6+, promises, async/await, DOM); Aura exposure is a plus for legacy support. Working command of the Salesforce data and security model: objects and relationships, record types, profiles and permission sets, org-wide defaults, sharing rules and apex sharing, and field-level security. Declarative automation depth; Flow in its current forms and the judgment to choose configuration over code and defend that choice. Integration experience with REST/JSON APIs, OAuth 2.0 and JWT bearer flows, and Named Credentials. Source-driven development practice: Salesforce DX, Git, pull-request-based code review, and a CI/CD toolchain (Gearset, Copado, Jenkins, GitHub Actions, or equivalent). Agile delivery experience using Jira or a comparable tool. Salesforce Platform Developer I certification, or ability to obtain within 90 days of hire. U.S. citizenship, and ability to obtain and maintain a U.S. federal security clearance. Ability to write clearly and explain technical decisions to non-technical government stakeholders. That's a lot; could be split into Requirements (education, experience, certifications, clearance) and Skills (technical). But we can also have Qualifications (certifications, clearance) and Skills (technical). Let's decide: - Requirements: Education (Bachelor's degree required, preferred fields) and Experience (minimum 5 years, two full implementations). Also maybe citizenship/clearance? That could be Qualifications. - Qualifications: Salesforce Platform Developer I cert or ability to obtain, U.S. citizenship and ability to obtain/maintain federal security clearance. - Skills: All the technical skill bullets (Apex proficiency, LWC, data model, Flow, integration, source-driven dev, Agile, communication). We also have "What Would Be Nice To Have" which is optional nice-to-have; we could include under Skills or a separate section? The instruction: include a section only when posting has real specific content. Nice-to-have is specific content; we could add a section "Preferred Qualifications" but not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Nice-to-have could go under Skills or Qualifications as part of "Skills" maybe as bullet list. But we could also add a separate section "Preferred Qualifications" but not allowed. So we incorporate into Skills or Qualifications. We have Pay: The annual salary range for this position is $106,000.00-$176,000.00. So we need a Pay section with that info. Benefits: "What We Offer Guidehouse offers a comprehensive, total rewards package that includes competitive compensation and a flexible benefits package..." then list benefits. So Benefits section with list. Schedule: Not mentioned. Travel Required Up to 10% is mentioned under Job Family line? Actually at top: "Job Family SAAS/PAAS/Cloud Consulting Travel Required Up to 10% Clearance Required Ability to Obtain Public Trust". Travel required up to 10% could be considered Schedule? Not exactly schedule but maybe travel requirement. There's no explicit schedule (e.g., full-time, remote). So we should not create Schedule section because no specific content. About the role: Not explicitly given; we have a brief intro maybe "Job Family SAAS/PAAS/Cloud Consulting Travel Required Up to 10% Clearance Required Ability to Obtain Public Trust". That's not a description. Could treat as About the role? But it's minimal. Might be better to omit About the role if no substantive content. The instruction: include a section ONLY when posting has real, specific content. So we skip About the role. Thus we will output sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to use

  for each heading. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet point as separate

  • items, preserving the text exactly (maybe minor punctuation). Ensure we don't lose any detail. Let's extract responsibilities list from "What You Will Do". It's a paragraph with sentences separated by periods. We'll split each sentence into a
  • . Ensure we keep all content. Responsibilities sentences: 1. Write clean, bulkified Apex triggers with a handler framework, service and selector layers, Queueable/Batch/Schedulable, Platform Events with governor limits accounted for in design, not discovered in UAT. 2. Build Lightning Web Components with modern JavaScript, and Experience Cloud pages and portals for constituent, supplier, and partner audiences. 3. Design and build integrations: REST/SOAP callouts, Named Credentials and External Credentials, External Services, Platform Events, and MuleSoft or agency ESB patterns, including authentication, retry, and error-handling design. 4. Write meaningful Apex unit tests and Jest tests for LWC, assertions that verify behavior, not coverage padding to clear the 75% floor. 5. Participate fully in Agile ceremonies: backlog grooming, estimation, sprint planning, daily standups, demos, and retrospectives with government product owners in the room. 6. Partner with solution architects, business analysts, testers, and release engineers; translate user stories into technical design and flag ambiguity before the sprint, not during it. 7. Support source-driven development and release management: Salesforce DX, Git branching and pull requests, code review, automated deployment pipelines, and sandbox/data seeding strategy across a multi-environment path to production. 8. Produce the technical documentation federal delivery requires, design specs, interface control documentation, configuration workbooks, and deployment runbooks. Now Requirements: we need to list items. Could be bullet list. From "What You Will Need": we have multiple sentences; we can split each sentence into
  • . Let's list: - Bachelor's degree required. Preferred in Computer Science, Information Systems, Engineering, or a related technical discipline. - Minimum of FIVE (5) years of hands-on Salesforce development experience, including at least two full implementation delivered to production. - Demonstrated Apex proficiency: trigger frameworks, asynchronous processing, SOQL/SOSL optimization, bulkification, exception handling, and governor limit management. - Lightning Web Component development with solid modern JavaScript fundamentals (ES6+, promises, async/await, DOM); Aura exposure is a plus for legacy support. - Working command of the Salesforce data and security model: objects and relationships, record types, profiles and permission sets, org-wide defaults, sharing rules and apex sharing, and field-level security. - Declarative automation depth; Flow in its current forms and the judgment to choose configuration over code and defend that choice. - Integration experience with REST/JSON APIs, OAuth 2.0 and JWT bearer flows, and Named Credentials. - Source-driven development practice: Salesforce DX, Git, pull-request-based code review, and a CI/CD toolchain (Gearset, Copado, Jenkins, GitHub Actions, or equivalent). - Agile delivery experience using Jira or a comparable tool. - Salesforce Platform Developer I certification, or ability to obtain within 90 days of hire. - U.S. citizenship, and ability to obtain and maintain a U.S. federal security clearance. - Ability to write clearly and explain technical decisions to non-technical government stakeholders. Now Qualifications: maybe we separate certifications and clearance? But we already included them in Requirements. However we could move certifications and clearance to Qualifications. But we need to avoid duplication. The instruction: preserve ALL substantive information; we can split but must not lose info. Let's decide to put certifications and clearance in Qualifications, and keep education/experience in Requirements. But then we would duplicate some sentences if we move them. Better to keep Requirements as education and experience only, and Qualifications as certifications and clearance. However the posting lumps them together; we need to decide a logical split. Let's define: Requirements: Education and Experience. Qualifications: Certifications, clearance, citizenship, communication ability. Skills: Technical skill bullets (Apex, LWC, data model, Flow, integration, source-driven dev, Agile). Also maybe communication ability? Already in Qualifications. Thus we need to extract accordingly. Education sentence: "Bachelor's degree required. Preferred in Computer Science, Information Systems, Engineering, or a related technical discipline." Experience sentence: "Minimum of FIVE (5) years of hands-on Salesforce development experience, including at least two full implementation delivered to production." Now Qualifications sentences: - Salesforce Platform Developer I certification, or ability to obtain within 90 days of hire. - U.S. citizenship, and ability to obtain and maintain a U.S. federal security clearance. - Ability to write clearly and explain technical decisions to non-technical government stakeholders. Also maybe "Preferred in Computer Science..." is part of Requirements; we keep. Now Skills sentences: all the technical proficiency bullets. List them: - Demonstrated Apex proficiency: trigger frameworks, asynchronous processing, SOQL/SOSL optimization, bulkification, exception handling, and governor limit management. - Lightning Web Component development with solid modern JavaScript fundamentals (ES6+, promises, async/await, DOM); Aura exposure is a plus for legacy support. - Working command of the Salesforce data and security model: objects and relationships, record types, profiles and permission sets, org-wide defaults, sharing rules and apex sharing, and field-level security. - Declarative automation depth; Flow in its current forms and the judgment to choose configuration over code and defend that choice. - Integration experience with REST/JSON APIs, OAuth 2.0 and JWT bearer flows, and Named Credentials. - Source-driven development practice: Salesforce DX, Git, pull-request-based code review, and a CI/CD toolchain (Gearset, Copado, Jenkins, GitHub Actions, or equivalent). - Agile delivery experience using Jira or a comparable tool. We could also include "Preferred in Computer Science..." but that's education. Now Benefits: list from "What We Offer". The paragraph: "Guidehouse offers a comprehensive, total rewards package that includes competitive compensation and a flexible benefits package that reflects our commitment to creating a diverse and supportive workplace." Then list: - Medical, Rx, Dental & Vision Insurance - Personal and Family Sick Time & Company Paid Holidays - Position may be eligible for a discretionary variable incentive bonus - Parental Leave and Adoption Assistance - 401(k) Retirement Plan - Basic Life & Supplemental Life - Health Savings Account, Dental/Vision & Dependent Care Flexible Spending Accounts - Short-Term & Long-Term Disability - Student Loan PayDown - Tuition Reimbursement, Personal Development & Learning Opportunities - Skills Development & Certifications - Employee Referral Program - Corporate Sponsored Events & Community Outreach - Emergency Back