Software Engineer- GovCloud

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must extract content from posting. First, remove boilerplate: "To get the best candidate experience..." etc. Also remove "Job Category Software Engineering". Remove "Applications will be accepted until 03/29/2027." maybe not needed? It's metadata; we can fold minor metadata into a short

or drop it. Probably drop. We need to preserve substantive info: About Salesforce description, role description, responsibilities, required skills, qualifications, benefits, pay range. Let's parse. Posting includes: - About Salesforce: description paragraph. - "Software Engineer - GovCloud" description: responsibilities bullet-like sentences. - "Your Impact" list of responsibilities. - "Required Skills" list. - "Unleash Your Potential" maybe benefits description. - Benefits: list of benefits (time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), employee stock purchasing program). Also link. - Pay: typical base salary range $117,200 - $176,700 annually; in select cities $141,200 - $194,200 annually. - Schedule: not mentioned. So we should not include Schedule section. - Qualifications: maybe "A related technical degree required", "3+ years backend software development experience", etc. Those could be under Qualifications or Requirements. We need to decide sections: Use headings as per list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. "About the role": could be the description of role (Software Engineer - GovCloud) and maybe the Salesforce intro? Usually "About the role" is role description. We'll put the paragraph describing the role: "Our Public Cloud engineering teams are responsible for innovating and maintaining a large scale distributed systems engineering platform..." etc. "Responsibilities": the bullet list under "Your Impact". Also maybe "Designing, developing, debugging, and operating resilient distributed systems..." etc. Those are responsibilities. "Requirements": maybe citizenship requirement? But that's more metadata. Could include "Must be a U.S. Citizen operating on U.S. Soil with ability to meet customer and government screening standards..." but that's a requirement. However we might fold minor metadata into short p. But we can include under Requirements. "Qualifications": education and experience: "A related technical degree required", "3+ years backend software development experience", "Deep knowledge of programming in Java, Golang, Python, or Ruby", etc. Could be qualifications. "Skills": maybe the list of skills like "Experience owning and operating multiple instances of a critical service", "Experience with Agile development methodology and Test Driven Development", etc. Also "Advanced prompt engineering skills". Could be skills. "Benefits": list of benefits. "Pay": salary ranges. "Schedule": none -> omit. We must not repeat job title as heading. So no heading for "Software Engineer - GovCloud". Already not. We must not include Job ID etc. We must not include boilerplate like EEO, accommodations, privacy statement, etc. Remove those. We must preserve all substantive info; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Let's craft. We'll have sections:

About the role

Our Public Cloud engineering teams are responsible for innovating and maintaining a large scale distributed systems engineering platform that ships hundreds of features to production for tens of millions of users across all industries every day. Our users count on our platform to be highly reliable, lightning fast, supremely secure, and to preserve all of their customizations and integrations every time we ship.

Maybe also include the Salesforce intro? Could be part of About the role? The intro about Salesforce is more about company; maybe could be under About the role as well. But we can keep it as part of About the role. Better: combine both: first paragraph about Salesforce, then role description. But we must not duplicate lines. We'll include both. So:

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.

Our Public Cloud engineering teams are responsible for innovating and maintaining a large scale distributed systems engineering platform that ships hundreds of features to production for tens of millions of users across all industries every day. Our users count on our platform to be highly reliable, lightning fast, supremely secure, and to preserve all of their customizations and integrations every time we ship.

Now Responsibilities: list from "Your Impact". Let's extract each bullet: - Deliver cloud infrastructure automation tools, frameworks, workflows, and validation platforms on our public cloud platforms such as AWS, GCP, Azure, or Alibaba - Designing, developing, debugging, and operating resilient distributed systems that run across thousands of compute nodes in multiple data centers - Build and ship high-quality, production-grade software using modern engineering practices, with AI as a core part of your development workflow by pushing the boundaries of AI development tools (Cursor, Windsurf, Claude, OpenAI API) to deliver secure, optimized, and high-quality code. - Using and contributing to open source technology (Spinnaker, Zookeeper, etc.) - Developing Infrastructure-as-Code using Terraform - Writing microservices on containerization frameworks such as Kubernetes, Docker, Mesos - Design and orchestrate complex systems where AI agents integrate seamlessly into human workflows, driving efficiency and innovation at scale. - Contribute to building and maintaining the shared system context, an explicit repository of system designs, constraints, and standards that enables AI to operate accurately and reliably. - Critically evaluate code (Human or AI-generated) for correctness, quality, security, and performance - Resolving complex technical issues and drive innovations that improve system availability, resilience, and performance - Eat, sleep, and breathe services. You have experience balancing live-site management, feature delivery, and retirement of technical debt - Participate in the team’s on-call rotation to address complex problems in real-time and keep services operational and highly available We'll put each as

inside

. Now Requirements: maybe citizenship requirement and maybe "Applications will be accepted until 03/29/2027." but we can drop date. Also "Must be a U.S. Citizen operating on U.S. Soil with ability to meet customer and government screening standards applicable to this role, including a Criminal Justice Information Services screening with fingerprint scan. Due to the citizenship requirement for this role, which supports U.S. federal, state, and/or local government customers, citizenship will be verified through two of the following REAL ID Act documents: U.S. Passport, Passport Card, REAL Driver's License, Global Entry Card, U.S. Government CAC/PIV." We'll put that as a

under Requirements. Qualifications: education and experience: "A related technical degree required", "3+ years backend software development experience", "Deep knowledge of programming in Java, Golang, Python, or Ruby", "Experience owning and operating multiple instances of a critical service", "Experience with Agile development methodology and Test Driven Development", "Experience with critical infrastructure services including, monitoring, alerting, logging, and reporting applications", "Experience with distributed database system and relational databases like postgres is a plus.", "A demonstrated, genuine AI-first approach to engineering. Using AI to move faster, build fluency across the stack, and contribute well beyond your core specialty.", "Experience using AI tools (e.g., Claude Code, GitHub Copilot, Codex, Cursor, etc.) in development workflows", "Advanced prompt engineering skills and the ability to write precise, structured prompts and cultivate the system context that makes AI outputs reliable, secure, and production-ready." We could split some into Skills but we have Skills section separate. Let's decide: Qualifications could be degree and years experience. Skills could be technical skills list. But the instruction says use headings as per list; we can allocate. Better: Qualifications: "A related technical degree required", "3+ years backend software development experience". Maybe also "Deep knowledge of programming in Java, Golang, Python, or Ruby" could be skill. But we can keep in Qualifications. Skills: list of specific technical proficiencies: programming languages, Agile, TDD, monitoring, logging, distributed databases, AI-first approach, AI tools, prompt engineering, etc. Let's do: Qualifications:

• A related technical degree required
• 3+ years backend software development experience
Skills:
• Deep knowledge of programming in Java, Golang, Python, or Ruby
• Experience owning and operating multiple instances of a critical service
• Experience with Agile development methodology and Test Driven Development
• Experience with critical infrastructure services including monitoring, alerting, logging, and reporting applications
• Experience with distributed database system and relational databases like postgres (plus)
• A demonstrated, genuine AI-first approach to engineering. Using AI to move faster, build fluency across the stack, and contribute well beyond your core specialty.
• Experience using AI tools (e.g., Claude Code, GitHub Copilot, Codex, Cursor, etc.) in development workflows
• Advanced prompt engineering skills and the ability to write precise, structured prompts and cultivate the system context that makes AI outputs reliable, secure, and production-ready.
Benefits: list from posting: "time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also maybe link but we can omit link as it's just reference; but we should preserve substantive info; the link is not substantive? It's a reference; we could include as

More details at https://www.salesforcebenefits.com. but maybe we can drop as it's just a link. The instruction: preserve ALL substantive information; the link is not substantive but could be considered. Safer to include as a

with the link. We'll do:

Benefits

• time off programs
• medical
• dental
• vision
• mental health support
• paid parental leave
• life and disability insurance
• 401(k)
• employee stock purchasing program

More details about company benefits can be found at https://www.salesforcebenefits.com.

Pay: salary ranges. We'll do:

Pay

The typical base salary range for this position is $117,200 - $176,700 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $141,200 - $194,200 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.

Schedule: none -> omit. Now we need to ensure we didn't include any boilerplate like EEO, accommodations, privacy statement,