Salesforce Administrator

We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Do"), Requirements, Benefits, Pay, Schedule? The posting includes compensation: "$75k - $85k Base + Bonus". That's pay. Also location remote, based in US. No schedule given. So we include Pay section. Benefits section present. No schedule. Also maybe "About Quilt Software" is intro but not a section heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings for sections that have content. We have "About The Role" (but they said do NOT repeat the job title as a heading; but "About The Role" is okay as heading). We have "What You'll Do" which is responsibilities. We have "Requirements". We have "Benefits". We have "Compensation:" which is Pay. No schedule. Also maybe "About Quilt Software" is company description; not required as heading but could be included as a paragraph before sections? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid a company overview heading. But they gave examples of headings; we can include "About Quilt Software" as a

if we want, but not required. Probably better to include it as a

intro. The instruction: "Prefer a few substantive sections over many thin ones." So we can include About Quilt Software as a paragraph before sections. We must remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes notices about visa, scam warnings. Remove those. We must preserve all substantive information. So include details about role, responsibilities, requirements, benefits, compensation. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need to convert each bullet into
• . The responsibilities are described in paragraphs with bullet-like sentences. We'll need to extract list items. Let's parse responsibilities section: "Delivery & Configuration - Build assigned work from business requirements documents within the sprint, including Flows, validation rules, page layouts, permission sets, record types, reports and dashboards, data loads, and field cleanup. - Work across both clouds: leads, opportunities, products and price books on the Sales Cloud side; cases, queues, Omni-Channel routing, entitlements, and knowledge on the Service Cloud side. - Own the full change cycle for your work: sandbox configuration, regression testing, production verification after release, and a rollback plan before you deploy. - Assess the impact of a proposed change across existing automation, integrations, security model, reporting, and downstream business processes before you begin the build. - Participate in requirements sessions and sprint planning, and question a requirement before building it. We want someone who asks whether this is the right way to solve the problem and offers a better route when there is one." "Administration & System Health - Share the inbound support queue with the team, resolve what reaches you, and provide full coverage in the support slack channel. - Own day to day administration: user management, profiles, permission sets, page layouts, and record types. - Identify and resolve configuration issues, data quality gaps, and system inconsistencies with urgency, and judge what to fix now versus what belongs in a sprint. - Follow platform best practice on naming, field creation, automation, and object limits. - Flag technical debt rather than adding to it." "Integrations & Connected Systems - Maintain and troubleshoot the third party tools that sit on top of Salesforce, including telephony, marketing automation, quoting, and commissions platforms. - Diagnose sync failures, integration user errors, and credential issues, and escalate with a clear summary of what you found." "Documentation & Enablement - Write the technical design document for every item you build, and keep standard operating procedures, the data dictionary, and release notes current. Documentation is part of the build, not an extra. - Create clear, practical documentation and training materials so teams can self-serve and adopt changes quickly. - Keep stakeholders and teammates updated on status, blockers, and realistic timelines before a deadline slips, not after." We can combine these into a single responsibilities list, but maybe better to keep subheadings? The instruction only says use

  for section headings; we could have subheadings as

  ? Not specified. Safer to just have one Responsibilities section with a

  containing all duties as
  • . We'll need to capture each bullet. Similarly Requirements: list of items. Let's extract requirements bullet points: "What You'll Bring - 3+ years of hands-on Salesforce administration in a single org of meaningful complexity, not a portfolio of small builds. - Strength across Sales Cloud and Service Cloud. - Real depth in one and solid working knowledge of the other, with the appetite to close the gap quickly. - Exposure to only one cloud is not enough for this role. - Automation judgement, not just Flow building. - Proven ability to design, build, and troubleshoot complex, interdependent Flows across multiple objects and automation layers. - More importantly, you understand the Salesforce order of execution, you can recognize and prevent recursion in layered automation, and you evaluate the impact of a change before you make it rather than after. - You know where declarative work stops and code should start. - A collaborative working style. You are comfortable sharing workstreams, giving and receiving feedback, and keeping teammates informed without being asked. - The ability to manage your own load: you plan your sprint, you know what is at risk, and you raise it in time to reprioritize. - A track record of writing your own documentation, including technical design documents, standard operating procedures, and process notes. - Strong diagnostic skills. You can identify what is wrong quickly and fix it without breaking other things. - Salesforce Certified Administrator required; Advanced Administrator, Platform App Builder, or Sales Cloud or Service Cloud Consultant preferred. - Trailblazer Profile: Please include your Trailhead/Trailblazer Profile URL in your application for streamlined certification verification. - Excellent communication with technical and non-technical audiences, and the judgement to raise a workload or scope issue early. - Experience with GTM and adjacent tooling such as DealHub CPQ, DocuSign, RingDNA or similar sales engagement platforms, HubSpot, CaptivateIQ, or workflow automation tools such as Make.com, Power Automate or Zapier is a plus." Also "What Success Looks Like" maybe could be part of responsibilities or separate? It's about expectations; could be included in Responsibilities or a separate section? The instruction: include a section ONLY when posting has real, specific content. This is specific content. Could be a separate section like "What Success Looks Like". But they didn't list that as example heading; but we could still use

    for it. However they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not exhaustive. We could add a section for "What Success Looks Like". But maybe better to incorporate into Responsibilities or Requirements? It's about success metrics; could be its own section. However to keep few sections, maybe we incorporate into Responsibilities as part of what you'll do? But it's about outcomes. I'd keep a separate section "What Success Looks Like" as it's substantive. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we can merge Success Looks Like into Responsibilities or Requirements? It's distinct. I'd keep it as a separate section but maybe we can avoid too many sections. Let's count: About Quilt Software (intro paragraph), About The Role (maybe we can skip heading and just have paragraph?), Responsibilities, Requirements, Benefits, Pay, What Success Looks Like. That's 6 sections plus intro. Could be okay. But we need to follow instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings for each section we include. For "About The Role" we can use

    About The Role

    . For responsibilities:

    Responsibilities

    . For requirements:

    Requirements

    . For benefits:

    Benefits

    . For pay:

    Pay

    . For what success looks like: maybe

    What Success Looks Like

    . That's fine. We must not include job title heading. Not include Job ID etc. We must remove boilerplate: the notices about visa, scam warnings, etc. Also remove "Notice: Applicants must be authorized..." and "Notice - Employment Scams". Also remove "Supervisory responsibilities: None". Also remove "Location: Remote, Based in the United States" maybe we keep location as part of Pay? Actually location is not Pay or Benefits; we could include location in a short paragraph maybe under About The Role? But instruction: we can include minor metadata into a short

    or drop it. Location is minor metadata; we could include a short

    after About The Role. But we already have About The Role heading; we could put location paragraph there. However they said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. So location can be a short

    . We'll include location after About The Role maybe. Also "Compensation: $75k - $85k Base + Bonus" is Pay. Now we need to ensure we preserve all substantive information: include details about Quilt Software intro, role description, responsibilities list, requirements list, benefits list, pay, success looks like. Let's craft HTML. We'll start with a

    for Quilt Software intro. Then

    About The Role

    then a

    with the role description paragraph(s). The role description includes multiple paragraphs: "Our Salesforce platform runs the revenue engine..." etc. We'll combine into a

    maybe multiple

    s. We'll keep as

    for each paragraph. Then location

    Remote, Based in the United States

    . Then

    Responsibilities

    then
    with
    • for each duty bullet. We need to ensure we capture all duty bullets from the four subsections. Let's list them: Delivery & Configuration: 1. Build assigned work from business requirements documents within the sprint, including Flows, validation rules, page layouts, permission sets, record types, reports and dashboards, data loads, and field cleanup. 2. Work across both clouds: leads, opportunities, products and price books on the Sales Cloud side; cases, queues, Omni-Channel routing, entitlements, and knowledge on the Service Cloud side. 3. Own the full change cycle for your work: sandbox configuration, regression testing, production verification after release, and a rollback plan before you deploy. 4. Assess the impact of a proposed change across existing automation, integrations, security model, reporting, and downstream business processes before you begin the build. 5. Participate in requirements sessions and sprint planning, and question a requirement before building it. We want someone who asks whether this is the right way to solve the problem and offers a better route when there is one. Administration & System Health: 6. Share the inbound support queue with the team, resolve what reaches you, and provide full coverage in the support slack channel. 7. Own day to day administration: user management, profiles, permission sets, page layouts, and record types. 8. Identify and resolve configuration issues, data quality gaps, and system inconsistencies with urgency, and judge what to fix now versus what belongs in a sprint. 9. Follow platform best practice on naming, field creation, automation, and object limits. 10. Flag technical debt rather than adding to it. Integrations & Connected Systems: 11. Maintain and troubleshoot the third