Sr. Software Engineer – Cloud Infrastructure and Devops
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (job summary). Responsibilities (essential responsibilities). Requirements (maybe minimum qualifications). Qualifications (expected qualifications). Skills (technical stack). Benefits (our benefits). Pay (pay range). Schedule (work model). We must only include sections if there is real specific content.
Let's extract each.
About the role: Job Summary paragraph.
Responsibilities: Essential Responsibilities list (multiple bullet points). Also Additional Responsibilities & Preferred Qualifications includes more responsibilities (Delivers complete solutions spanning all phases of the SDLC, advises immediate management, guides junior engineers, operates with little day-to-day supervision, applies knowledge of technical best practices). Also later "What You'll Do" list (design, build, operate...). Those are responsibilities.
We need to combine all responsibilities into a - list, preserving all details, not summarizing.
Requirements: Might be "Minimum Qualifications: 3+ years relevant experience and a Bachelor's degree OR Any equivalent combination of education and experience." Also "Expected Qualifications: 8+ years relevant experience and a Bachelor’s degree OR Any equivalent combination of education and experience." There's also "Additional Responsibilities & Preferred Qualifications:" but that's more responsibilities.
We could treat Requirements as the minimum qualifications (3+ years). Qualifications as expected qualifications (8+ years). Or we could combine. The instruction: prefer a few substantive sections over many thin ones. But we need to follow headings list; we can include both Requirements and Qualifications if they have distinct content.
Skills: Technical stack list: AWS, AWS CloudFront, CDN, WAF, Envoy, Contour, NGINX, EKS, Docker, Terraform, GitHub Enterprise, GitHub Actions, Datadog, Bash, Python, Go. Also hands-on experience with containers, networking fundamentals, etc. Also "Solid understanding of networking fundamentals: TCP/IP, DNS, TLS/SSL, routing protocols, and load balancing algorithms". Also "Strong communication skills". So we can list skills.
Benefits: The "Our Benefits:" paragraph describing comprehensive programs, generous PTO, healthcare, resources for financial security and mental health. Also "For the majority of employees, PayPal's balanced hybrid work model offers 3 days in the office...". That's schedule actually. Benefits also include "generous paid time off, healthcare coverage for you and your family, and resources to create financial security and support your mental health." Also maybe "flexible, balanced work culture". We'll capture that.
Pay: Pay range details: Primary Location: San Jose, California: ($143,500.00 - $212,850.00 Annually). Additional Location(s): Austin, Texas: ($130,500.00 - $193,600.00 Annually). Scottsdale, Arizona: ($123,500.00 - $183,700.00 Annually). Also mention additional compensation may include annual performance bonus, equity, or other incentive compensation.
Schedule: The hybrid work model: 3 days in office, 2 days flexible. Also maybe "Travel Percent: 0". Also "Visa Sponsorship through PayPal is not available". That's not schedule. So schedule section: mention hybrid work model.
We must not include boilerplate like EEO, scam warnings, etc.
We must not include duplicated lines.
We must not include navigation, cookie, legal, EEO, equal-opportunity, scam-warning boilerplate.
We must not include "Subsidiary: Venmo Travel Percent: 0 Visa Sponsorship through PayPal is not available for this position now or any time in the future." That's not schedule but maybe we could include under Schedule? Travel percent 0 is not schedule. Visa sponsorship not available is not schedule. Probably we should drop that line as it's not relevant to headings. It's not about schedule, benefits, pay, etc. It's a note about visa sponsorship; could be considered metadata but not required. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could drop that line.
Also "Subsidiary: Venmo" maybe not needed.
We need to preserve all substantive information; but we can drop minor metadata like travel percent, visa sponsorship. However "Travel Percent: 0" could be considered schedule? It's about travel requirement. Not schedule. Might be considered a minor metadata; we could drop.
We must not invent or summarize away detail. So we need to keep the exact phrasing? We can keep the substance but not necessarily verbatim? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the details, but we can rephrase slightly as long as we don't lose detail. Safer to keep the original sentences.
We'll produce HTML like:
About the role
This job delivers complete solutions spanning all phases of the Software Development Lifecycle (SDLC). It involves advising management on project-level issues, guiding junior engineers, operating with little supervision, and applying knowledge of technical best practices.
Responsibilities
- Makes technical decisions affecting multiple teams, crossing organizational boundaries
- Establishes conventions & processes to be followed by other employees
- Actions determine the utilization of company resources (people, money, assets) and affect the effectiveness of the company
- Handles multiple, multi-team initiatives simultaneously, using judgement to prioritize among more issues than can be handled individually.
- Understands evolving industry capabilities & practices and can judiciously apply up--to-date information for optimal results
- Competent at communicating technical issues with non-technical audiences
- Spreads their behavior, principles, and knowledge as a means of improving technical results of other employees (via many means – modeling behavior, 1:1s, working sessions, quality documentation)
- Partners with product management, to ideate solutions to business problems & goals
- Delivers complete solutions spanning all phases of the Software Development Lifecycle (SDLC) (design, implementation, testing, delivery and operations), based on definitions from more senior roles.
- Advises immediate management on project-level issues
- Guides junior engineers
- Operates with little day-to-day supervision, making technical decisions based on knowledge of internal conventions and industry best practices
- Applies knowledge of technical best practices in making decisions
- Design, build, and operate cloud network and routing infrastructure across our AWS environment, including VPCs, transit gateways, load balancers, and service mesh
- Build, tune, and operate our cloud CDN and edge delivery using AWS CloudFront to improve performance, availability, and global reach
- Configure and maintain WAF rules and other edge security controls to protect services from DDoS, bot, and application-layer attacks
- Operate and extend Envoy- and Contour-based ingress and service mesh for both north-south and east-west traffic
- Configure and maintain nginx-based reverse proxy and load-balancing services
- Partner with SRE, security, and product engineering teams across the Cloud Platform & Infrastructure org on shared networking and edge initiatives
- Troubleshoot network incidents such as latency, packet loss, routing failures, and TLS/certificate issues; identify root cause and implement fixes and preventive measures
- Develop and improve infrastructure-as-code (Terraform) to manage networking and routing configuration
- Participate in an on-call rotation supporting network, routing, and edge services
- Document designs, runbooks, and operational best practices
Requirements
Minimum Qualifications: 3+ years relevant experience and a Bachelor's degree OR Any equivalent combination of education and experience.
Qualifications
Expected Qualifications: 8+ years relevant experience and a Bachelor’s degree OR Any equivalent combination of education and experience.
Skills
- AWS, AWS CloudFront, CDN, WAF, Envoy, Contour, NGINX, EKS, Docker, Terraform, GitHub Enterprise, GitHub Actions, Datadog, Bash, Python, Go
- Hands-on experience with cloud networking (AWS VPC, Transit Gateway, Route 53, ELB/ALB/NLB, or equivalent)
- Hands-on experience with CDN and edge delivery services (AWS CloudFront or similar)
- Experience configuring and operating WAF or other edge security tooling
- Experience with Envoy, Contour, or similar service mesh / ingress controller technologies
- Experience with nginx or similar reverse proxy and load-balancing technologies
- Solid understanding of networking fundamentals: TCP/IP, DNS, TLS/SSL, routing protocols, and load balancing algorithms
- Hands-on programming and scripting (Python, Go, Bash)
- Hands-on experience with containers and container orchestration (Docker, Kubernetes)
- Strong communication skills with the ability to understand and explain technical issues to a non-technical audience
Benefits
At PayPal, we’re committed to building an equitable and inclusive global economy. And we can’t do this without our most important asset-you. That’s why we offer comprehensive, choice-based programs, to support all aspects of personal wellbeing—physical, emotional, and financial—delivering meaningful value where it matters most. We strive to create a flexible, balanced work culture with a holistic approach to benefits, including generous paid time off, healthcare coverage for you and your family, and resources to create financial security and support your mental health.
Pay
The base pay for this role will depend on where you work and the relevant experience and expertise you bring. The expected range of pay for this role by location is: Primary Location : Pay Range: San Jose, California: ($143,500.00 - $212,850.00 Annually) Additional Location(s) : Pay Range: Austin, Texas: ($130,500.00 - $193,600.00 Annually) Scottsdale, Arizona: ($123,500.00 - $183,700.00 Annually). Additional compensation for this role
or drop it. So we could drop that line. Also "Subsidiary: Venmo" maybe not needed. We need to preserve all substantive information; but we can drop minor metadata like travel percent, visa sponsorship. However "Travel Percent: 0" could be considered schedule? It's about travel requirement. Not schedule. Might be considered a minor metadata; we could drop. We must not invent or summarize away detail. So we need to keep the exact phrasing? We can keep the substance but not necessarily verbatim? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the details, but we can rephrase slightly as long as we don't lose detail. Safer to keep the original sentences. We'll produce HTML like:
About the role
This job delivers complete solutions spanning all phases of the Software Development Lifecycle (SDLC). It involves advising management on project-level issues, guiding junior engineers, operating with little supervision, and applying knowledge of technical best practices.
Responsibilities
- Makes technical decisions affecting multiple teams, crossing organizational boundaries
- Establishes conventions & processes to be followed by other employees
- Actions determine the utilization of company resources (people, money, assets) and affect the effectiveness of the company
- Handles multiple, multi-team initiatives simultaneously, using judgement to prioritize among more issues than can be handled individually.
- Understands evolving industry capabilities & practices and can judiciously apply up--to-date information for optimal results
- Competent at communicating technical issues with non-technical audiences
- Spreads their behavior, principles, and knowledge as a means of improving technical results of other employees (via many means – modeling behavior, 1:1s, working sessions, quality documentation)
- Partners with product management, to ideate solutions to business problems & goals
- Delivers complete solutions spanning all phases of the Software Development Lifecycle (SDLC) (design, implementation, testing, delivery and operations), based on definitions from more senior roles.
- Advises immediate management on project-level issues
- Guides junior engineers
- Operates with little day-to-day supervision, making technical decisions based on knowledge of internal conventions and industry best practices
- Applies knowledge of technical best practices in making decisions
- Design, build, and operate cloud network and routing infrastructure across our AWS environment, including VPCs, transit gateways, load balancers, and service mesh
- Build, tune, and operate our cloud CDN and edge delivery using AWS CloudFront to improve performance, availability, and global reach
- Configure and maintain WAF rules and other edge security controls to protect services from DDoS, bot, and application-layer attacks
- Operate and extend Envoy- and Contour-based ingress and service mesh for both north-south and east-west traffic
- Configure and maintain nginx-based reverse proxy and load-balancing services
- Partner with SRE, security, and product engineering teams across the Cloud Platform & Infrastructure org on shared networking and edge initiatives
- Troubleshoot network incidents such as latency, packet loss, routing failures, and TLS/certificate issues; identify root cause and implement fixes and preventive measures
- Develop and improve infrastructure-as-code (Terraform) to manage networking and routing configuration
- Participate in an on-call rotation supporting network, routing, and edge services
- Document designs, runbooks, and operational best practices
Requirements
Minimum Qualifications: 3+ years relevant experience and a Bachelor's degree OR Any equivalent combination of education and experience.
Qualifications
Expected Qualifications: 8+ years relevant experience and a Bachelor’s degree OR Any equivalent combination of education and experience.
Skills
- AWS, AWS CloudFront, CDN, WAF, Envoy, Contour, NGINX, EKS, Docker, Terraform, GitHub Enterprise, GitHub Actions, Datadog, Bash, Python, Go
- Hands-on experience with cloud networking (AWS VPC, Transit Gateway, Route 53, ELB/ALB/NLB, or equivalent)
- Hands-on experience with CDN and edge delivery services (AWS CloudFront or similar)
- Experience configuring and operating WAF or other edge security tooling
- Experience with Envoy, Contour, or similar service mesh / ingress controller technologies
- Experience with nginx or similar reverse proxy and load-balancing technologies
- Solid understanding of networking fundamentals: TCP/IP, DNS, TLS/SSL, routing protocols, and load balancing algorithms
- Hands-on programming and scripting (Python, Go, Bash)
- Hands-on experience with containers and container orchestration (Docker, Kubernetes)
- Strong communication skills with the ability to understand and explain technical issues to a non-technical audience
Benefits
At PayPal, we’re committed to building an equitable and inclusive global economy. And we can’t do this without our most important asset-you. That’s why we offer comprehensive, choice-based programs, to support all aspects of personal wellbeing—physical, emotional, and financial—delivering meaningful value where it matters most. We strive to create a flexible, balanced work culture with a holistic approach to benefits, including generous paid time off, healthcare coverage for you and your family, and resources to create financial security and support your mental health.
Pay
The base pay for this role will depend on where you work and the relevant experience and expertise you bring. The expected range of pay for this role by location is: Primary Location : Pay Range: San Jose, California: ($143,500.00 - $212,850.00 Annually) Additional Location(s) : Pay Range: Austin, Texas: ($130,500.00 - $193,600.00 Annually) Scottsdale, Arizona: ($123,500.00 - $183,700.00 Annually). Additional compensation for this role