Staff Software Engineer, Distributed Data Services - Slack

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Salesforce", "About the Opportunity", "The Distributed Data Services Team", "What you should have", "Bonus points", "Unleash Your Potential", "Accommodations", "Posting Statement". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The posting does not have explicit "Responsibilities" but we have description of role: "About the Opportunity", "The Distributed Data Services Team". Could map to Responsibilities? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings, but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings when applicable. We need to map content to those headings. Let's see what we have: - About the role: we have "About Salesforce" and "About the Opportunity". Could combine as About the role. - Responsibilities: we have description of what the team does, what you'll do: maintain and build performant services, edge caches, etc. Could be responsibilities. - Requirements: "What you should have" list. - Qualifications: maybe same as requirements? Could combine. - Skills: maybe bonus points? Or we could treat "Bonus points" as Skills. - Benefits: we have benefits description. - Pay: we have salary range. - Schedule: not mentioned; we should not include Schedule if no content. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Accommodations" maybe? It's not a standard heading; but we could keep if it's substantive? It's about accommodations request. Might be considered boilerplate? It's not EEO but it's about accommodations. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Accommodations request is not exactly that, but could be considered legal? Might be okay to keep? However they said "Prefer a few substantive sections over many thin ones." Might be better to omit Accommodations as it's thin. Also "Posting Statement" includes EEO statement, which we should remove. So we will omit Accommodations and Posting Statement. We need to preserve all substantive information: details about Salesforce, about the opportunity, team description, what you should have, bonus points, unleash your potential (benefits/culture), benefits, pay. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we can list bullet points. For requirements we can list bullet points. For benefits we can list bullet points. For skills maybe bullet points. We must not invent or summarize away detail. Keep specifics. Let's extract content: About Salesforce: "Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce." About the Opportunity: "We operate at tremendous scale with systems that process millions of events per second. Our team maintains and builds performant services that that include: Edge Caches Enterprise Key Management International Data Residency Image Uploads, Downloads, and Proxying We’ve done our job correctly when none of our users think about us, much like a vital utility. We don’t typically ship new user-facing features, but rather ensure our systems are exceptionally performant, highly available, reliable, and scalable. In other words, we make Slack work seamlessly. Slack's backend services are written in Go and Java, and Slack's API is built on PHP/Hack." The Distributed Data Services Team: "We are a small team building critical services that enable Slack to scale for our largest customers. Our edge caches power the most latency critical queries for our largest entities today. Our other services power Slack’s Enterprise Key Management and Data Residency features. We power core Slack functionality such as shared channels, our privacy-preserving image proxy, and many other key day-to-day parts of our customer’s experience. We have a strong commitment to quality and understand that simplicity and reliability are the foundations of our work. We are actively building the future of edge services at Slack, so we can support a growing number of globally distributed customers with their compliance requirements with minimal latency." What you should have: list: - U.S. Citizenship or Permanent Residency required — we're unable to provide visa sponsorship for this role. - 10+ years building and operating large-scale systems professionally, with concrete examples of what you've shipped and owned. - Hands-on experience managing critical production infrastructure — driving reliability and uptime with a customer-first view of operational safety. - Deep experience with reliable, safe distributed systems, and the judgment to weigh engineering vs. product trade-offs and argue persuasively for either. - A track record of untangling complex issues that demand deep knowledge of a company's existing architecture. - Strong fundamentals in unit testing, code review, design documentation, debugging, and troubleshooting — you've built and operated web applications professionally and can speak in depth about what you and your teams have delivered. - A curious, determined mindset that gets energized (not deterred) by things breaking. Bonus points: - Go programming language exposure. - AWS - Building and releasing software with Docker containers - Kubernetes - Experience in highly regulated environments where FEDRAMP/NIST frameworks were essential. Unleash Your Potential: "When you join Salesforce, you’ll be limitless in all areas of your life. Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best. Together, we’ll bring the power of Agentforce to organizations of all sizes and deliver amazing experiences that customers love. Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." Benefits: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program. More details about company benefits can be found at the following link: https://www.salesforcebenefits.com." Pay: "In the United States, compensation offered will be determined by factors such as location, job level, job-related knowledge, skills, and experience. Certain roles may be eligible for incentive compensation, equity, and benefits. Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program. More details about company benefits can be found at the following link: https://www.salesforcebenefits.com.Pursuant to the San Francisco Fair Chance Ordinance and the Los Angeles Fair Chance Initiative for Hiring, Salesforce will consider for employment qualified applicants with arrest and conviction records. At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions. The typical base salary range for this position is $197,300 - $313,700 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $237,700 - $344,700 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable." We need to avoid duplication: benefits appears twice; we can keep one benefits section. We need to ensure we don't include boilerplate like "Pursuant to the San Francisco Fair Chance Ordinance..." that's maybe legal but it's about fair chance hiring; could be considered EEO? Might be okay to keep? It's not EEO but it's about hiring practice. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is about fair chance hiring, which is a kind of equal opportunity. Safer to remove that sentence. Also remove "At Salesforce, we believe in equitable compensation practices..." maybe keep as part of pay description? It's about compensation practices; could be considered substantive. Might keep. We also need to remove duplicated lines: there is duplication of benefits description in Pay section; we can keep only one benefits section. Now craft HTML:

  About the role

  Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce.

  Responsibilities

  We operate at tremendous scale with systems that process millions of events per second. Our team maintains and builds performant services that include: Edge Caches, Enterprise Key Management, International Data Residency, Image Uploads, Downloads, and Proxying. We’ve done our job correctly when none of our users think about us, much like a vital utility. We don’t typically ship new user-facing features, but rather ensure our systems are exceptionally performant, highly available, reliable, and scalable. In other words, we make Slack work seamlessly. Slack's backend services are written in Go and Java, and Slack's API is built on PHP/Hack.

  The Distributed Data Services Team is a small team building critical services that enable Slack to scale for our largest customers. Our edge caches power the most latency critical queries for our largest entities today. Our other services power Slack’s Enterprise Key Management and Data Residency features. We power core Slack functionality such as shared channels, our privacy-preserving image proxy, and many other key day-to-day parts of our customer’s experience. We have a strong commitment to quality and understand that simplicity and reliability are the foundations of our work. We are actively building the future of edge services at Slack, so we can support a growing number of globally distributed customers with their compliance requirements with minimal latency.

  Could also make bullet list for responsibilities but it's prose; we can keep as

  . The instruction says use

  • for any list of duties/requirements/benefits. Since responsibilities are not a list but prose, it's fine.

    Requirements

    • U.S. Citizenship or Permanent Residency required — we're unable to provide visa sponsorship for this role.
    • 10+ years building and operating large-scale systems professionally, with concrete examples of what you've shipped and owned.
    • Hands-on experience managing critical production infrastructure — driving reliability and uptime with a customer-first view of operational safety.
    • Deep experience with reliable, safe distributed systems, and the judgment to weigh engineering vs. product trade-offs and