Senior Platform Engineer
Summary
Loop, a post-purchase commerce platform for e-commerce merchants, seeks a Senior Platform Engineer to build self-serve infrastructure, safer CI/CD releases, observability/SLOs, and foundations for AI-agent-assisted engineering. Core stack: AWS, Kubernetes, Docker, Terraform, GitLab CI/CD, Datadog, with PHP/Laravel in the app layer.
What You’ll Do:
- Build a platform that helps engineers help themselves.
- Build self-serve workflows that let engineers provision infrastructure, ship services, and recover from failures without waiting on anyone.
- Improve our CI/CD pipelines, deploy checks, progressive delivery, and automated rollback so safe releases take less coordination and manual work.
- Simplify our infrastructure.
- Make production changes safer and easier to recover from.
- Change our AWS and Kubernetes environment by turning the complexity you find into a prioritized plan that balances reliability, security, cost, and upkeep.
- Improve reliability through evidence
- Strengthen our observability, alerting, SLOs, and capacity planning, and use incidents and support trends to decide what to fix next.
- Help build the foundation for agent-assisted engineering.
- Improve the tooling, environments, reusable context, and access boundaries that let engineers direct agents effectively.
- Partner with security colleagues to keep permissions, secrets, and consequential actions appropriately controlled.
- Work across infrastructure and application boundaries.
- Partner with product and data engineers to track down performance and reliability issues across application code, containers, databases, networking, and cloud services.
- Make the team more capable.
- Share your thinking, document decisions, and coach teammates so the systems you touch are understandable to others.
- Join platform on-call and incident response, and work to make those interruptions rarer and lighter.
Your Experience:
- 5+ years of experience in platform engineering, DevOps, SRE, or related infrastructure work, or equivalent demonstrated depth.
- Deep, hands-on Kubernetes experience, including configuration, secrets, deployment, scaling, and production troubleshooting.
- Experience building and operating AWS infrastructure for production systems with meaningful traffic and availability requirements.
- Strong infrastructure-as-code and CI/CD experience, including Terraform and GitLab CI or comparable tools.
- An observability mindset, with experience using metrics, logs, traces, and alerting to understand system behavior.
- The ability to write, read, debug, and maintain automation and tooling, and investigate problems across application and infrastructure boundaries.
- Examples of making delivery safer, reducing operational toil, or enabling engineers to work independently.
- Clear written communication and experience leading technical work across teams without relying on formal authority.
- Experience with cloud security, least-privilege access, secrets management, SOC 2, or GDPR is especially useful.
- Application performance tuning, PHP/Laravel, database operations, and infrastructure for AI agents are additional strengths.
What success looks like:
- More routine infrastructure and delivery tasks happen through self-service.
- Releases become easier to verify and recover from.
- Engineers spend less time waiting on access, coordination, and manual intervention.
- Operational noise and recurring incidents decrease.
- Platform knowledge and ownership become more widely shared.
- Agent-assisted workflows produce better results with appropriate checks and human accountability.
Skills
As published by lever · 8 questions · 3 written answers
Basics
Which location are you applying for?, Resume/CV, Full name, Pronouns, Email, Phone, Current location, Current company
Pick from a list (5)
- Are you currently eligible to work in the United States?
- Do you now or in the future require visa sponsorship to continue working in the United States?
- This role requires you to be physically located and performing work within the United States on a full-time, permanent basis. Are you currently residing in the United States full-time?
- Which of the following is NOT a valid reason a Pod would remain in Pending state?
- How would you describe your current use of AI tools in your work?
Written answers (3)
- Describe a production Kubernetes incident you personally debugged. What was the symptom, the root cause, and what did you change afterward? (note: if there's one place to not use AI in your application, this should be it!)
- Which AI/ML tools, libraries, or platforms have you worked with professionally? For each, briefly describe the context.
- We’d love to hear what inspired you about joining our team. What excites you most about the opportunity to work at Loop? (note: if there's one place to not use AI in your application, this should be it!)
Index Ventures 