Senior Salesforce Administrator (6-month contract)

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Workato" and "Why join us?" but those are not required sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. The posting includes "About Workato" (company description) and "Why join us?" (culture/benefits). Also "Responsibilities", "Requirements Qualifications / Experience / Technical Skills". There's no explicit Benefits, Pay, Schedule. So we should not create those sections. We need to preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO etc. There's none. Also remove duplicated lines. There's a line "Also, Feel Free To Check Out Why Business Insider named us an “enterprise startup to bet your career on” Forbes’ Cloud 100 recognized us as one of the top 100 private cloud companies in the world Deloitte Tech Fast 500 ranked us as the 17th fastest growing tech company in the Bay Area, and 96th in North America Quartz ranked us the #1 best company for remote workers". That's part of "Why join us?" maybe. We'll keep it. We need to format: Use

for each section heading. Use

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

  for prose. We need to not repeat job title as heading. No job title given. We need to include sections: About Workato? The instruction says section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list About Workato but we could treat "About Workato" as a section heading? It says use

  for section headings (e.g. About the role, Responsibilities...). It implies we can use similar headings for sections present. So we can have

  About Workato

  and

  Why join us?

  maybe. But they said "e.g. About the role". Not strict list. Probably okay to include those. But we need to ensure we only include sections when posting has real specific content. Yes. We need to preserve all substantive information. So include the paragraphs. We need to turn lists into
  • . The responsibilities are a list of bullet points? The posting uses sentences separated by line breaks but not explicit bullet characters. However we can treat each sentence as a list item? The instruction: Use
    • for any list of duties/requirements/benefits. The responsibilities section contains multiple duties; we should format as a list. Similarly requirements/qualifications/technical skills is a list. Thus we need to parse responsibilities into items. Responsibilities text: "We are seeking a senior, hands-on Salesforce contractor to provide operational ownership and reliable coverage for our Salesforce environment during an employee’s parental leave (6 months). This person will independently administer, support, enhance, and deploy changes across Salesforce and its connected applications. The role is centered on keeping critical revenue processes running: resolving production issues, managing releases, maintaining platform health, and delivering well-scoped improvements. The contractor will have authority appropriate to these responsibilities and will partner with an Enterprise Architect for material architecture, security, integration, or cross-system decisions. In This Role, You Will Also Be Responsible To Own day-to-day Salesforce administration, including user access, permissioning, security settings, configuration, data quality, and platform support. Triage, prioritize, and resolve Salesforce bugs, incidents, and operational requests with clear stakeholder communication. Build, test, document, and deploy Salesforce configuration changes, including flows, validation rules, custom objects and fields, page layouts, reports, dashboards, and automations. Manage Salesforce releases across environments, following sound change-control, testing, and rollback practices. Support and protect high-impact revenue processes, including deal approvals, quote-to-cash workflows, CPQ, forecasting/reporting, and connected-system data flows. Administer and troubleshoot Salesforce capabilities and connected applications, including Sales Cloud, Salesforce CPQ, Certinia, Vivun, and other Salesforce-integrated tools. Investigate and resolve Salesforce-side integration issues, including data mappings, API-related configuration, permissions, field changes, and error triage. Partner with business stakeholders to clarify operational needs and deliver practical, maintainable solutions. Escalate material architecture, security, integration, or cross-system design decisions to the Enterprise Architect for review and guidance. Maintain clear documentation of configurations, releases, known issues, and operational processes to ensure continuity throughout the engagement. Take on limited, well-scoped enhancements when operational coverage is stable, and capacity allows." We can break into logical items: maybe each sentence after "In This Role, You Will Also Be Responsible To" is a bullet. But we can just make each sentence a
    • . Simpler: split by periods that start new capital letter? Might be messy but okay. Similarly Requirements Qualifications / Experience / Technical Skills block: "5+ years of hands-on Salesforce administration in a complex production environment. Salesforce Administrator certification; Advanced Administrator certification is preferred. Proven experience administering Sales Cloud and supporting revenue-critical processes. Strong practical experience with Salesforce configuration, Flow, validation rules, security and permissions, reporting, dashboards, deployments, sandboxes, and change management. Experience supporting Salesforce CPQ and complex connected applications; Certinia and Vivun experience is strongly preferred. Experience troubleshooting Salesforce integrations and understanding APIs, data flows, field mappings, and integration failure patterns. Demonstrated ability to diagnose and resolve production issues independently while balancing urgency, risk, and business impact. Availability to work full-time during US business hours. Soft Skills / Personal Characteristics Strong written communication and documentation skills. Comfortable working autonomously, making routine production decisions, and escalating appropriately when a decision carries material technical or business risk." We can treat each line as list item. The "Soft Skills / Personal Characteristics" could be a subheading? But we can just include as list items. We also need to include "What Success Looks Like" section? That's also substantive. Could be a section heading maybe "What Success Looks Like". It contains bullet-like sentences. We could make a section. Thus sections: About Workato, Why join us?, Responsibilities, What Success Looks Like, Requirements Qualifications / Experience / Technical Skills. We should not include Benefits, Pay, Schedule. Now produce HTML fragment. We need to wrap each section:

      Section Title

      then content: either

      for prose or

      • for lists. For About Workato: it's a paragraph(s). Could be two paragraphs: first about Workato, second "Why join us?" Actually "Why join us?" is separate. Thus:

        About Workato

        Workato is the leading Control and Execution Platform for Enterprise AI — the neutral platform enterprises trust to put AI to work across their business. Workato unifies data, applications, and processes into a single platform so AI can reliably orchestrate business processes in production at enterprise scale. Built on more than a decade of running mission-critical processes for over half the Fortune 500 — including Nasdaq, Amazon, Cisco, Vodafone, Atlassian, and Lucid Motors — Workato turns over 14,000 enterprise systems AI needs to act on into one governed execution layer. For more information, visit workato.com.

        Why join us?

        Ultimately, Workato believes in fostering a flexible, trust-oriented culture that empowers everyone to take full ownership of their roles. We are driven by innovation and looking for team players who want to actively build our company. But, we also believe in balancing productivity with self-care. That’s why we offer all of our employees a vibrant and dynamic work environment along with a multitude of benefits they can enjoy inside and outside of their work lives. If this sounds right up your alley, please submit an application. We look forward to getting to know you! Also, Feel Free To Check Out Why Business Insider named us an “enterprise startup to bet your career on” Forbes’ Cloud 100 recognized us as one of the top 100 private cloud companies in the world Deloitte Tech Fast 500 ranked us as the 17th fastest growing tech company in the Bay Area, and 96th in North America Quartz ranked us the #1 best company for remote workers

        Now Responsibilities: we need list. We'll create

        Responsibilities

        then
        with each duty as
        • . We need to split responsibly. Let's create items: - Provide operational ownership and reliable coverage for our Salesforce environment during an employee’s parental leave (6 months). - Independently administer, support, enhance, and deploy changes across Salesforce and its connected applications. - Keep critical revenue processes running: resolving production issues, managing releases, maintaining platform health, and delivering well-scoped improvements. - Have authority appropriate to these responsibilities and partner with an Enterprise Architect for material architecture, security, integration, or cross-system decisions. - Own day-to-day Salesforce administration, including user access, permissioning, security settings, configuration, data quality, and platform support. - Triage, prioritize, and resolve Salesforce bugs, incidents, and operational requests with clear stakeholder communication. - Build, test, document, and deploy Salesforce configuration changes, including flows, validation rules, custom objects and fields, page layouts, reports, dashboards, and automations. - Manage Salesforce releases across environments, following sound change-control, testing, and rollback practices. - Support and protect high-impact revenue processes, including deal approvals, quote-to-cash workflows, CPQ, forecasting/reporting, and connected-system data flows. - Administer and troubleshoot Salesforce capabilities and connected applications, including Sales Cloud, Salesforce CPQ, Certinia, Vivun, and other Salesforce-integrated tools. - Investigate and resolve Salesforce-side integration issues, including data mappings, API-related configuration, permissions, field changes, and error triage. - Partner with business stakeholders to clarify operational needs and deliver practical, maintainable solutions. - Escalate material architecture, security, integration, or cross-system design decisions to the Enterprise Architect for review and guidance. - Maintain clear documentation of configurations, releases, known issues, and operational processes to ensure continuity throughout the engagement. - Take on limited, well-scoped enhancements when operational coverage is stable, and capacity allows. That seems comprehensive. Now What Success Looks Like: we can make a section. Content: "Critical Salesforce and revenue operations continue without disruption during the coverage period. Production incidents, bugs, access requests, and configuration changes are handled promptly and transparently. Salesforce releases are predictable, tested, documented, and low-risk. Stakeholders have a clear operational owner for Salesforce questions and issues. The Salesforce environment remains secure, well-maintained, and easy to transition back at the end of the engagement." We can make as

          or list. It's a list of outcomes; we can make

          • . Thus

            What Success Looks Like

            • ...
            ...
            Now Requirements Qualifications / Experience / Technical Skills: we can make

            Requirements

            maybe. The instruction includes Requirements as a possible heading. We'll use

            Requirements

            and list items. Items: - 5+ years of hands-on Salesforce administration in a complex production environment. - Salesforce Administrator certification; Advanced Administrator certification is preferred. - Proven experience administering Sales Cloud and supporting revenue-critical processes. - Strong practical experience with Salesforce configuration, Flow, validation rules, security and permissions, reporting, dashboards, deployments, sandboxes, and change management. - Experience supporting Salesforce CPQ and complex connected applications; Certinia and Vivun experience is strongly preferred. - Experience troubleshooting Salesforce integrations and understanding