Xometry
Site Reliability Engineer II (SRE)
About this role
Xometry is hiring a Site Reliability Engineer II to own infrastructure reliability and system performance across multiple teams. You'll design and maintain cloud platforms, observability tools, and CI/CD systems while mentoring others and driving technical decisions that enable safe feature deployment.
What you'll do
- Own assigned infrastructure and reliability projects from problem definition through completion
- Develop and maintain AWS infrastructure, Kubernetes clusters, and networking configurations
- Build and configure observability, monitoring, and logging systems (Coralogix, Sentry)
- Develop CI/CD tools and automation (GitHub Actions runners, ArgoCD)
- Collaborate across engineering teams to communicate progress, blockers, and technical outcomes
- Write clean, well-documented code and mentor team members on technical improvements
What they're looking for
- Python, JavaScript, or Unix Shell scripting
- AWS infrastructure and cloud operations
- Kubernetes container orchestration
- CI/CD pipeline design and implementation
- Observability and monitoring tools (Coralogix, Sentry)
- Infrastructure as Code and automation
- Networking and system architecture
- Cross-team communication and collaboration
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Xometry
Xometry operates a manufacturing network platform that connects with suppliers and partners to deliver complex projects, particularly in regulated industries like aerospace and defense. The company is hiring analytics engineers to build data infrastructure, and supplier quality and development engineers to optimize partner performance, ensure product quality, and manage manufacturing relationships.
- Website
- xometry.com
Likely interview questions
- Describe your experience managing AWS infrastructure at scale—what workloads have you deployed, monitored, and scaled in production?
- Walk us through how you've designed or improved a CI/CD pipeline. What tools did you use and what impact did it have?