Salesforce Developer III

We need to output HTML fragment with sections: About the role? The posting includes Summary, Essential Duties & Responsibilities, Requirements (MINIMUM QUALIFICATIONS, Desired Qualifications & Skills), WORK SCHEDULE, TRAVEL, WORK ENVIRONMENT, PHYSICAL DEMANDS, Benefits (Compensation & Benefits). Also maybe Pay and Schedule sections. We must use

for section headings. Do not repeat job title. Do not include Job ID etc. Remove boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Also remove duplicated lines. Must preserve all substantive info. We need to decide which sections to include: About the role (maybe summary), Responsibilities, Requirements, Qualifications (maybe combine?), Benefits, Pay, Schedule. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (summary), Responsibilities (essential duties), Requirements (minimum qualifications), Qualifications (desired qualifications & skills), Benefits (compensation & benefits), Pay (maybe included in Benefits? but they said include Pay section only if posting actually states them. The posting includes Pay: $88,000 - $103,000 annually. So we should have a Pay section. Schedule: they have WORK SCHEDULE Full-time. May be required to work additional hours as needed. So we can have Schedule section. Travel maybe not required as separate heading unless we want to include but not in list; we could incorporate into Schedule or omit. The instruction: include a section ONLY when posting has real, specific content for it. Travel content exists: "The expected travel time is less than 25%." That's specific. Should we create a Travel section? Not in the example headings list but we could add if we think it's substantive. However they gave examples of headings; not mandatory to limit to those. But better to follow examples; but we could add Travel if we think it's needed. However they said "Prefer a few substantive sections over many thin ones." Travel is thin; maybe we can incorporate into Schedule or omit. I'd incorporate travel into Schedule or maybe a separate Travel section but it's thin. I'd omit Travel to keep few sections. Work Environment and Physical Demands also thin; maybe incorporate into Schedule or omit. But they are substantive? Might be considered boilerplate? Might be considered not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Work Environment and Physical Demands are not boilerplate but could be considered generic. However they are specific to role. But we prefer few sections; we could omit them. Thus sections: About the role (summary), Responsibilities, Requirements (minimum qualifications), Qualifications (desired qualifications & skills), Benefits, Pay, Schedule. Now we need to format content. About the role: Use the Summary paragraph: "Build and sustain capabilities on the Enterprise Customer Relationship Management (eCRM) Development, Operations, and Sustainment (DOS) contract." We could also include a bit more? The summary is just that sentence. Use

. Responsibilities: list each duty from "Essential Duties & Responsibilities". We need to preserve all substantive info. Let's extract bullet points: - Analyze new requirements against existing platform capabilities and recommend the simplest solution that meets them - Develop and maintain API integrations with Navy HR systems, including error handling and retry logic - Support authentication and single sign-on integration for eCRM applications - Migrate legacy system functionality and data into eCRM - Deliver changes through the team's CI/CD pipeline under established configuration management and change control - Write unit and automated regression tests, and support integration, performance, and Government acceptance testing - Evaluate each Salesforce release for impacts to eCRM and for new features that can replace custom code - Diagnose and resolve production incidents and defects - Build user-facing features that meet Section 508 accessibility standards - Document designs, interfaces, and releases to support contract deliverables - Apply DoW cybersecurity controls in development work and support system accreditation - Assess automation and AI capabilities, including Agentforce, for Navy HR use cases - Share technical guidance with Government and partner developers working on eCRM - Maintain regular and punctual attendance - Perform other duties as assigned - Supervisory Responsibilities None. (maybe we can omit as it's not a duty; but it's part of responsibilities section. Could include as a note but it's not a duty. Might be considered boilerplate? It's specific. We could include as a

after list: "Supervisory Responsibilities: None." But maybe we can drop as it's not a duty. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Could be a

after list. Requirements: Minimum qualifications list: - Bachelor's degree in Computer Science, Information Systems, Software Engineering, or a related technical field - Five (5) or more years of software development experience, including at least 3 years of hands-on Salesforce development - Demonstrated proficiency in Apex, Lightning Web Components, Flow, SOQL, and Salesforce REST and SOAP APIs - Experience delivering Salesforce work on an Agile team using source control and CI/CD deployment - Active Salesforce Certified Platform Developer credential (formerly Platform Developer I) - Active Secret security clearance (generally, U.S. citizenship required) - Must obtain and maintain any necessary security access and/or background checks We should keep as

• . Qualifications (Desired Qualifications & Skills): - Experience on Navy, DoW, or federal Salesforce programs, especially in IL-4 or higher environments - Clear written and verbal communication skills, including the ability to document technical designs for Government review - Active CompTIA Security+ CE or another DoW 8140-approved certification (IAT Level II or higher) - Service Cloud experience, including case management, Omni-Channel, and Knowledge - Additional Salesforce certifications, such as Platform App Builder, Administrator, Platform Developer II, JavaScript Developer I, or Agentforce Specialist - Experience with Salesforce DevOps tools such as Flosum, Copado, Gearset, or Salesforce DX - Experience migrating data and functionality from legacy systems into Salesforce - Experience with CAC/PKI authentication and SAML or OAuth single sign-on - Experience with automated testing frameworks such as Playwright or Provar We should keep as list. Benefits: From "Compensation & Benefits:" includes Pay and Eligible Benefits. But we will separate Pay section. Benefits section should list eligible benefits: Medical, Dental, Vision, Life & AD&D Insurance, Long-Term & Short-Term Disability Insurance, 401(k) Savings Plan, Employee Assistance Program (EAP), Vacation & Paid Personal Time, 11 Paid Federal Holidays, and Leave of Absence. We need to preserve all. So
  • each. Pay section: Pay: $88,000 - $103,000 annually. Could be a

    . Schedule section: WORK SCHEDULE Full-time. May be required to work additional hours as needed to complete assignment or project. Also maybe include travel? but we omitted. We'll just put that. We should also maybe include note about remote work? That's under WORK ENVIRONMENT. But we omitted. Could incorporate into Schedule? Might be better to add a Work Environment section? But we prefer few sections. However remote work is substantive. Could add a section "Work Environment" but not in examples. Might be okay but risk of many sections. Let's see: we already have 7 sections. Adding Work Environment would be 8. Still okay. But we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." Work Environment is maybe thin but still specific. However we could incorporate remote work note into About the role or Schedule. Probably better to add a brief note in About the role: "Work is expected to be remote; however, the company reserves the right to require onsite work." That's from WORK ENVIRONMENT. So we can add that to About the role paragraph. Similarly Physical Demands: "Position consists of sitting for long periods of time. Frequently uses hands/fingers for manipulation of keyboard and mouse. It is Katmai's business philosophy and practice to provide reasonable accommodations, according to applicable state and federal laws, to all qualified individuals with physical or mental disabilities." Could be added to About the role as well, but that may be too much. Could add a short sentence: "Role involves extended sitting and keyboard/mouse use; reasonable accommodations provided." That preserves substance. Thus About the role can combine summary, work environment, physical demands. Now we need to ensure we don't repeat any info elsewhere. Let's craft HTML. We'll output:

    About the role

    Build and sustain capabilities on the Enterprise Customer Relationship Management (eCRM) Development, Operations, and Sustainment (DOS) contract. Work is expected to be remote; however, the company reserves the right to require onsite work. The role involves extended sitting and keyboard/mouse use, with reasonable accommodations provided for qualified individuals.

    Responsibilities

    • Analyze new requirements against existing platform capabilities and recommend the simplest solution that meets them
    • Develop and maintain API integrations with Navy HR systems, including error handling and retry logic
    • Support authentication and single sign-on integration for eCRM applications
    • Migrate legacy system functionality and data into eCRM
    • Deliver changes through the team's CI/CD pipeline under established configuration management and change control
    • Write unit and automated regression tests, and support integration, performance, and Government acceptance testing
    • Evaluate each Salesforce release for impacts to eCRM and for new features that can replace custom code
    • Diagnose and resolve production incidents and defects
    • Build user-facing features that meet Section 508 accessibility standards
    • Document designs, interfaces, and releases to support contract deliverables
    • Apply DoW cybersecurity controls in development work and support system accreditation
    • Assess automation and AI capabilities, including Agentforce, for Navy HR use cases
    • Share technical guidance with Government and partner developers working on eCRM
    • Maintain regular and punctual attendance
    • Perform other duties as assigned

    Supervisory Responsibilities: None.

    Requirements

    • Bachelor's degree in Computer Science, Information Systems, Software Engineering, or a related technical field
    • Five (5) or more years of software development experience, including at least 3 years of hands-on Salesforce development
    • Demonstrated proficiency in Apex, Lightning Web Components, Flow, SOQL, and Salesforce REST and SOAP APIs
    • Experience delivering Salesforce work on an Agile team using source control and CI/CD deployment
    • Active Salesforce Certified Platform Developer credential (formerly Platform Developer I)
    • Active Secret security clearance (generally, U.S. citizenship required)
    • Must obtain and maintain any necessary security access and/or background checks

    Qualifications

    • Experience on Navy, DoW, or federal Salesforce programs, especially in IL-4 or higher environments
    • Clear written and verbal communication skills, including the ability to document technical designs for Government review
    • Active CompTIA Security+ CE or another DoW 8140-approved certification (IAT Level II or higher)
    • Service Cloud experience, including case management, Omni-Channel, and Knowledge
    • Additional Salesforce certifications