Senior Salesforce Platform Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to extract content. We have a job posting: Senior Salesforce Platform Engineer. We need sections: maybe About the role (intro description), Responsibilities (What You'll Do), Requirements/Qualifications (What You'll Bring), Skills (maybe combine?), Benefits (maybe mention benefits from Washington state: unlimited PTO, holidays, medical dental vision PPO and CDHP plans, company sponsored 401(k) retirement plan). Also Pay: salary ranges for various locations. Schedule? Not mentioned. So we may omit Schedule. We must not include boilerplate like EEO, legal, cookie, navigation, application instructions, fraud warnings, etc. Also remove duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities list, requirements list, benefits specifics, salary ranges. We must not include placeholder text like "commensurate with experience". Not present. We need to format using

headings,

• for lists,

  for prose. We need to decide sections: About the role (intro paragraph summarizing role). Responsibilities (What You'll Do). Requirements (What You'll Bring). Skills maybe separate? Could combine Requirements and Skills but better to follow spec: we can have Requirements and Skills separate if content distinct. The posting includes "What You'll Bring" which includes experience, certifications, education. That's qualifications. Skills maybe include technical skills like Apex, CPQ, etc. Could split but we can put all under Requirements. However spec says we can have Skills section if we have specific skills content. Might be okay to have Skills separate listing technical skills: Salesforce administration, CPQ, Apex, etc. But we must not invent. The posting includes those under What You'll Bring. Could treat as Requirements. We'll have one section: Requirements (or Qualifications). We'll follow spec: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include About the role, Responsibilities, Requirements, Benefits, Pay. Not include Qualifications/Skills if redundant. But we need to avoid empty sections. Let's craft:

  About the role

  Amplitude is seeking a Senior Salesforce Platform Engineer to support the scaling and ongoing evolution of its go-to-market (GTM) systems. You will own end-to-end visibility into the Salesforce platform, from day-to-day configuration and support to long‑term architecture and improvement, partnering with Sales, GTM Operations, Finance, Product & Engineering, and GTM leadership to deliver well‑governed solutions across Salesforce and connected platforms such as CPQ, NetSuite, Amplitude, and Snowflake.

  Responsibilities

  • Hands‑on platform administration, configuration, troubleshooting, maintenance, testing, upgrades, and user support
  • Maintain and optimize CPQ, pricing, quoting, and opportunity workflows to support the quote‑to‑cash process
  • Serve as the escalation line of support for Salesforce, handling escalated issues such as contract, entitlement, and provisioning discrepancies, driving root cause fixes
  • Collaborate cross‑functionally with business stakeholders, gather requirements independently, and serve as a trusted partner for end users across the RevOps and Salesforce ecosystem
  • Define and implement Salesforce standard operating procedures including field hygiene, data retention, integrations, permission sets, validation rules
  • Conduct regular system audits and health checks to proactively identify and resolve data quality issues
  • Manage pre‑production and production environments, deploy changes using change sets or DevOps tooling, and ensure integrity of changes made to production systems
  • Own Salesforce license allocation and forecasting, and monitor data storage against org limits
  • Build integrations, data flows, and install managed packages between Salesforce and external systems
  • Create and maintain system documentation for cross‑team training, and participate in release planning, UAT, and post‑deployment validation
  • Contribute as part of the GTM Engineering team to implement roadmap initiatives, working from design through testing and deployment
  • Stay current with Salesforce platform changes and proactively recommend relevant new features or capabilities

  What You'll Bring (Requirements)

  • 5+ years of Salesforce administration experience, including hands‑on work with Salesforce CPQ and quote‑to‑cash processes in a production revenue organization
  • Hands‑on experience with Salesforce Sales Cloud and a functional understanding of CPQ, pricing rules, and the quote‑to‑contract‑to‑order handoff
  • Hands‑on experience writing and maintaining Apex (triggers, classes, batch/schedulable jobs), with the ability to read, troubleshoot, and safely extend existing code
  • Foundational knowledge of other Salesforce development concepts (Visualforce, Lightning Web Components, SOQL/SOSL, platform limits)
  • Experience integrating Salesforce with third‑party tools via native connectors, managed packages, or integration platforms
  • Strong customer service orientation, with a genuine desire to help users work through problems
  • Certified Salesforce Administrator or similar experience
  • Bachelor's degree in Information Systems, Computer Science, Business Administration, or related field (or equivalent practical experience)

  Nice to Have

  • Salesforce certifications such as CPQ Specialist, CPQ and Billing Consultant Accredited Professional, or Platform Developer I/II
  • Experience supporting Salesforce at a global, publicly traded company under SOX compliance
  • Experience with Salesforce CI/CD and release automation (e.g. Copado, GitHub) across sandboxes and production
  • Proven ability to lead Salesforce initiatives end to end, from solution design through release management and post‑deployment support
  We could treat Nice to Have as Skills or separate. But spec only lists Skills heading; we could put Nice to Have under Skills. However we have to avoid filler. Nice to Have is substantive. We'll put under

  Skills

  maybe. But we already have Requirements; we could rename What You'll Bring as Requirements and Nice to Have as Skills. That matches spec. Thus:

  Requirements

  (list of must-have)

  Skills

  (nice-to-have) Now Benefits: we have Washington state benefits: unlimited PTO, 10 to 13 holidays annually (will vary), medical dental and vision PPO and CDHP plans, company sponsored 401(k) retirement plan. Also maybe other benefits not specified elsewhere. We'll include Benefits section. Pay: we have multiple salary ranges based on location: Colorado range: $144,000 - $216,000 total target cash (inclusive of bonus or commission). New York City salary range: $160,000 - $240,000 total target cash (inclusive of bonus or commission). San Francisco Bay Area of California: $160,000 - $240,000 total target cash. California outside of SF Bay Area: $144,000 - $216,000. Washington state: $144,000 - $216,000 total target cash. We'll include Pay section with these details. Schedule: not mentioned, so omit. We must not include boilerplate like "Based on Colorado law, the following details are for individuals who will work for Amplitude in Colorado." That's substantive? It's location-specific pay disclosure. We should keep the pay ranges but can drop the explanatory sentence? The spec says preserve ALL substantive information; do NOT invent or summarize away detail. The location-based law statements are part of the posting; they are substantive as they explain the ranges. We could keep them as part of Pay section prose. But we can also just list the ranges with location labels. That's preserving info. We must not include the EEO, diversity statement, etc. Also remove the "Learn more at amplitude.com." and the initial paragraph about Amplitude being leading AI analytics platform? That's company description; maybe considered boilerplate? It's not a standard boilerplate but it's about the company. The spec says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview might be considered not required but it's substantive? It's describing the company; could be considered part of About the role? The About the role section we wrote includes a brief description of the role; we could also include a short company overview if we want, but not required. The spec says preserve ALL substantive information; but we can decide to omit generic marketing fluff if not directly about the role? It's ambiguous. Safer to keep a brief About the role that includes the role description; we can omit the generic company marketing paragraph. We must not include the "As an organization, we deliver for our customers by living our values..." That's values; could be considered boilerplate? It's not standard legal but could be considered fluff. Might be okay to omit. The spec says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Values are not explicitly listed; but they could be considered boilerplate? Not sure. Safer to keep them? Might be considered filler. I'd lean to omit because it's not directly about the role. The spec says preserve ALL substantive information; but values could be considered substantive? However they are generic. I'd omit to keep focused. We must not include the "Amplitude’s Commitment to Diversity Equity & Inclusion (DEI):" etc. That's EEO/diversity boilerplate; remove. We must not include the "By applying for this job, you acknowledge that Amplitude processes your personal data..." that's legal; remove. We must not include the "Staying Safe - Protect Yourself From Recruitment Fraud" etc; remove. Now produce HTML fragment. Let's craft:

  About the role

  Amplitude is seeking a Senior Salesforce Platform Engineer to support the scaling and ongoing evolution of its go‑to‑market (GTM) systems. You will own end‑to‑end visibility into the Salesforce platform, from day‑to‑day configuration and support to long‑term architecture and improvement, partnering with Sales, GTM Operations, Finance, Product & Engineering, and GTM leadership to deliver well‑governed solutions across Salesforce and connected platforms such as CPQ, NetSuite, Amplitude, and Snowflake.

  Responsibilities

  • Hands‑on platform administration, configuration, troubleshooting, maintenance, testing, upgrades, and user support
  • Maintain and optimize CPQ, pricing, quoting, and opportunity workflows to support the quote‑to‑cash process
  • Serve as the escalation line of support for Salesforce, handling escalated issues such as contract, entitlement, and provisioning discrepancies, driving root cause fixes
  • Collaborate cross‑functionally with business stakeholders, gather requirements independently, and serve as a trusted partner for end users across the RevOps and Salesforce ecosystem
  • Define and implement Salesforce standard operating procedures including field hygiene, data retention, integrations, permission sets, validation rules
  • Conduct regular system audits and health checks to proactively identify and resolve data quality