Senior Salesforce Administrator

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description: location remote, role description, why you'll love, your impact (multiple subparts), what you bring (required and preferred). No explicit Benefits, Pay, Schedule. So we should not create those sections. We can have sections: About the role (maybe summarizing location and purpose), Responsibilities (the "Your Impact" sections), Requirements (the "What You Bring" required), Qualifications (maybe preferred? but they said Qualifications separate from Skills? Usually Qualifications includes required and preferred. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include based on content. We have content: location remote, description of role, why you'll love (maybe part of About the role). Your Impact (multiple bullet-like paragraphs) could be Responsibilities. What You Bring (required) could be Requirements. Preferred Additional certifications etc could be Qualifications or Skills. They also mention skills like Flow Builder, Data Loader, security model, etc. Those could be Skills. We must not invent placeholder text. Must preserve all substantive info. So we need to extract bullet points etc. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we can list each bullet as
• . For requirements list each required item. For skills list each skill. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate like cookie/navigation/legal/EEO etc. There's none. We must output only HTML fragment. Let's parse the posting: - Intro: "Help Power The Systems Behind Extraordinary Travel Experiences Location: Remote Vacatia is reinventing the vacation ownership and rental experience across discovery, booking, and stay. Behind the scenes, Salesforce plays a critical role in powering the teams, workflows, and customer experiences that make it all possible. We’re looking for a Senior Salesforce Administrator who knows how to balance flexibility, scalability, and — importantly — sanity. In this role, you’ll own and evolve our Salesforce environment, partner closely with business stakeholders, and help ensure the platform remains intuitive, secure, scalable, and sustainable as Vacatia continues to grow. You’ll be a trusted Salesforce subject matter expert, advocate for platform best practices, and a thoughtful partner who can translate business needs into solutions without creating unnecessary complexity." That's about the role. - "Why You’ll Love Working at Vacatia" bullet list: Own a critical platform..., Make an impact..., Balance innovation..., Work with great people..., Keep learning..., Protect the admin role... These are more like benefits/perks but not explicit Benefits section. Could be part of About the role or separate "Why you'll love". But we only have allowed headings; we could put them under About the role as prose. - "Your Impact" with subheadings: Platform Ownership & Enablement, Automation & Data Management, Security & Access Control, Service Cloud Voice & Telephony, Continuous Improvement. Each with bullet-like sentences. These are responsibilities. - "What You Bring" Required: list of items. - "Preferred": Additional certifications, experience administering Sales Cloud, Experience Cloud, Slack, familiarity with AppExchange managed packages, basic understanding of Apex and LWC, experience supporting multi-org, experience in hospitality etc. We could treat Required as Requirements, Preferred as Qualifications or Skills. But we also have Skills heading allowed. Could put specific technical skills under Skills. We need to decide structure: About the role (intro + why you'll love). Responsibilities (Your Impact). Requirements (What You Bring Required). Qualifications (What You Bring Preferred). Skills (maybe list of specific technical skills like Flow Builder, Data Loader, etc). But we must not create sections with filler. If we put Skills, we need actual content. Let's extract skills: Flow Builder (screen flows, scheduled flows), Data Loader, Import Wizard, ETL tools, profiles, permission sets, sharing rules, OWD, permission-set-driven access, reports and formulas, AWS Connect Call Center technology, Unified Routing, skill-based Omni-Channel routing, troubleshooting telephony functionality, Git and GitHub. Also maybe Apex, LWC (basic understanding). Those are skills. We could put them under Skills. Now ensure we don't repeat content. We'll need to avoid duplication: responsibilities already mention many of those; but it's okay if overlapping? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Overlap is okay as long as we keep info. But we might duplicate same sentences in two sections; that's okay but could be considered redundant. Better to split: responsibilities cover what you'll do; skills cover abilities needed. We'll list skills as bullet list. Now produce HTML:

  About the role

  ... (intro + why you'll love)

  Responsibilities

  • Platform Ownership & Enablement: Own Salesforce configuration across page layouts, flows, permissions, automation, and related platform capabilities; translate business requirements into scalable, intuitive, and maintainable Salesforce solutions; serve as the Salesforce SME and primary owner of Service Cloud Voice with AWS Connect telephony environment; maintain platform usability while balancing immediate business needs with long-term scalability and maintainability; thoughtfully push back when a proposed solution creates unnecessary complexity.
  • Automation & Data Management: Build and maintain robust automation using Flow Builder, including screen flows and scheduled flows; manage data imports, updates, transformations, and integrity using Data Loader, Import Wizard, and ETL tools; establish and maintain data quality and governance standards; identify opportunities to automate manual processes and improve operational efficiency.
  • Security & Access Control: Manage Salesforce security using profiles, permission sets, sharing rules, organization-wide defaults (OWD), and related controls; lead and advocate for best practices around transitioning from profile-heavy access models to permission-set-driven access; ensure users have the access they need while protecting sensitive information and maintaining appropriate governance; help establish scalable access-control practices as the organization grows.
  • Service Cloud Voice & Telephony: Own and support Salesforce Service Cloud Voice integrated with AWS Connect; configure and troubleshoot telephony functionality within Salesforce; support Unified Routing and skill-based Omni-Channel routing; troubleshoot call flows, routing, telephony integrations, and related user issues; partner with stakeholders to continuously improve the customer and agent experience.
  • Continuous Improvement: Stay current on Salesforce releases and evaluate new capabilities for potential adoption; proactively identify opportunities to streamline processes, eliminate technical debt, and improve the user experience; support Salesforce ecosystem participation through Trailblazer groups, Dreamforce, community learning, and other professional development opportunities; collaborate with technical teams on development practices, including Git and GitHub.

  Requirements

  • 5–7 years of hands‑on Salesforce Administration experience, with demonstrated real‑world execution beyond certifications alone.
  • Salesforce Administrator Certification (ADM‑201).
  • Strong proficiency with Flow Builder, including screen flows and scheduled flows.
  • Experience with Salesforce data tools such as Data Loader, Import Wizard, or third‑party ETL solutions.
  • Strong understanding of Salesforce's security model, including profiles, permission sets, sharing rules, and OWD.
  • Demonstrated experience implementing and advocating for permission‑set‑driven access models.
  • Ability to build clear, logical, and easy‑to‑understand reports and formulas.
  • Strong communication skills and the confidence to explain why a requested solution may not be the right long‑term approach.
  • Experience with AWS Connect Call Center technology and Unified Routing.
  • Experience with skill‑based Omni‑Channel routing within Service Cloud Voice.
  • Experience troubleshooting telephony functionality within Salesforce.
  • Experience with, or willingness to become proficient in, Git and GitHub.

  Qualifications

  • Additional Salesforce certifications (e.g., Advanced Administrator) preferred.
  • Experience administering Sales Cloud, Experience Cloud, and Slack.
  • Familiarity with AppExchange managed packages and the complexities that can come with them.
  • Basic understanding of Apex and Lightning Web Components, with the ability to read and troubleshoot code.
  • Experience supporting a multi‑org or enterprise Salesforce environment.
  • Experience in hospitality, real estate, subscription‑based businesses, or other complex customer‑facing environments.

  Skills

  • Flow Builder (screen flows, scheduled flows)
  • Data Loader, Import Wizard, ETL tools
  • Profiles, permission sets, sharing rules, OWD
  • Permission‑set‑driven access models
  • Reports and formulas
  • AWS Connect Call Center technology
  • Unified Routing
  • Skill‑based Omni‑Channel routing
  • Telephony troubleshooting within Salesforce
  • Git and GitHub
  • Apex and Lightning Web Components (basic understanding)
  We need to ensure we didn't include Pay/Benefits/Schedule sections. Good. Check that we preserved all substantive info: The intro, why you love, responsibilities, requirements, preferred qualifications, skills. Did we miss any? The "Why You’ll Love Working at Vacatia" bullet points we incorporated into About the role prose? We didn't list them explicitly; we just included a paragraph that mentions "Own a critical platform — Play a key role...". We need to ensure we included those bullet points. Let's embed them as a list maybe under About the role? But we can include them as part of the paragraph. However we need to preserve all substantive info; we can include them as a
  under About the role? The instruction says use
  • for any list of duties/requirements/benefits. The "Why you'll love" is a list of benefits/perks, so we should use
    • . So we should create a list under About the role. Thus About the role section: first paragraph describing role, then a
      with the why you love points. Let's craft:

      About the role

      Vacatia is reinventing the vacation ownership and rental experience across discovery, booking, and stay. Behind the scenes, Salesforce plays a critical role in powering the teams, workflows, and customer experiences that make it all possible. We’re looking for a Senior Salesforce Administrator who knows how to balance flexibility, scalability, and — importantly — sanity. In this role, you’ll own and evolve our Salesforce environment, partner closely with business stakeholders, and help ensure the platform remains intuitive, secure, scalable, and sustainable as Vacatia continues to grow. You’ll be a trusted Salesforce subject matter expert, advocate for platform best practices, and a thoughtful partner who can translate business needs into solutions without creating unnecessary complexity.

      • Own a critical platform — Play a key role in shaping the Salesforce environment that supports our growing business.
      • Make an impact — Your work will directly influence how teams operate, collaborate, and serve our customers.
      • Balance innovation with practicality — Bring new ideas to the table while protecting the long‑term health of the platform.
      • Work with great people — Partner across technology and business teams to solve meaningful problems.
      • Keep learning — Participate in the Salesforce ecosystem through Trailblazer communities, Dreamforce, certifications, and ongoing development.
      • Protect the admin role — Join a team that understands that good administration means knowing when to build, when