Skip to main content

Sr. Software Engineer, DNS and Cloud Infrastructure

Posted today

salesforceWashington (DC)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Overview: As a Backend Software Engineer, you will build and optimize a large-scale, highly available distributed systems platform in Salesforce’s public cloud. You will work on infrastructure automation, microservices, and on-call reliability, partnering with cross-functional teams to deliver secure, fast, and scalable cloud services. This role places you at the core of AI-powered, enterprise-grade CRM infrastructure with a strong emphasis on resilience and performance. You will impact tens of millions of users by shaping core backend systems and deployment practices. Compensation / Benefits time off programs medical/dental/vision mental health support paid parental leave life and disability insurance 401(k) and employee stock purchase program
Responsibilities: Deliver automation tools, frameworks, and validation platforms for public cloud platforms Design, develop, debug, and operate resilient distributed systems across data centers Contribute to open source technologies used in-house Develop Infrastructure-as-Code and microservices on Kubernetes/Docker/Mesos Address complex technical issues to improve availability, resilience, and performance Balance live-site management, feature delivery, and technical debt retirement Participate in on-call rotation to keep services operational and highly available
Key requirements: Minimum 5+ years of backend software development experience (Python) Hands-on Linux systems administration and troubleshooting Proficiency in Python and strong knowledge of OOP, design patterns, data structures, algorithms, and concurrency Public cloud experience on GCP/AWS/Azure and cloud-scale provisioning/migration Experience with container/orchestration (Kubernetes, Docker) Infrastructure automation tools (Terraform, Puppet, Spinnaker, Git) Network fundamentals (DNS, Load Balancing, SSL, TCP/IP, HTTP) CI/CD experience (Jenkins, Travis CI) Experience delivering large infrastructure projects Strong communication, collaboration, and continuous learning ethos Open to diversity and inclusion in workspace Configuration management with open-source tools (Puppet, Chef, Salt, Ansible) Monitoring with Grafana Agile development and Test Driven Development Continuous learner Critical thinker Team player with excellent communication Python Linux system administration Public cloud (GCP/AWS/Azure)

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this