Senior / Staff Backend Engineer (Java, EKS, DynamoDB, Splunk, & DataDog)
What you will be doing
• Tech Stack: Java, AWS, EKS (Kubernetes), Microservices architecture, DynamoDB, SQS, Splunk, and DataDog.
• Design, build, and operate Java-based microservices running on AWS and EKS.
• Own services end-to-end, from design through deployment, monitoring, and incident response.
• Participate in a shared on-call rotation across the team.
• Collaborate closely with engineers across multiple time zones and partner teams.
• Contribute to architectural decisions and help raise the technical bar on the team.
On-Call Service
• Daily on-call rotation shared across all team members, including weekends in the rotation.
• On-call applies during a defined window within core working hours. Engineers are not expected to sit at a computer for the entire shift.
• Weekends are not working time. The engineer is only engaged if paged for an incident.
• Primary expectation when paged: acknowledge in Slack, then move the ball. That can mean looping in teammates who can help, or pulling in our operations team to start a Zoom call and walk through the obvious first steps (why now, which other services are involved, etc.).
• Shift swaps and backup coverage are fully supported and encouraged. Coordinate with teammates and give the team lead a heads-up.
• If the engineer plans to be fully unreachable for a stretch during their shift, they should give the team a heads-up in advance and swap the shift.
• Being on the on-call schedule is not separately compensated. If active incident response is required on a weekend, the time spent can be compensated either monetarily or as time off on a mutually agreed date. This applies only to active incident work, not to simply being on the rotation.
• Design, build, and operate Java-based microservices running on AWS and EKS.
• Own services end-to-end, from design through deployment, monitoring, and incident response.
• Participate in a shared on-call rotation across the team.
• Collaborate closely with engineers across multiple time zones and partner teams.
• Contribute to architectural decisions and help raise the technical bar on the team.
On-Call Service
• Daily on-call rotation shared across all team members, including weekends in the rotation.
• On-call applies during a defined window within core working hours. Engineers are not expected to sit at a computer for the entire shift.
• Weekends are not working time. The engineer is only engaged if paged for an incident.
• Primary expectation when paged: acknowledge in Slack, then move the ball. That can mean looping in teammates who can help, or pulling in our operations team to start a Zoom call and walk through the obvious first steps (why now, which other services are involved, etc.).
• Shift swaps and backup coverage are fully supported and encouraged. Coordinate with teammates and give the team lead a heads-up.
• If the engineer plans to be fully unreachable for a stretch during their shift, they should give the team a heads-up in advance and swap the shift.
• Being on the on-call schedule is not separately compensated. If active incident response is required on a weekend, the time spent can be compensated either monetarily or as time off on a mutually agreed date. This applies only to active incident work, not to simply being on the rotation.