Key skills
PythonC#CRubySQLReactNext.jsASP.NETAWSNew RelicKibana
About this role
Mindbody is a company that equips wellness entrepreneurs with technology to support thriving businesses and create exceptional experiences. In this role, you will lead technical execution across teams, design microservices, and enhance the reliability and performance of backend services.
Responsibilities:
- Lead cross-team technical execution, aligning architecture and delivery across multiple squads and core domains
- Design and evolve microservices patterns that improve reliability, performance, and maintainability
- Drive cloud and deployment improvements across AWS, Mindbody’s cloud platform, and our containerized deployment environment
- Partner with engineering and product leaders to turn ambiguous problems into clear technical plans and milestones
- Establish and socialize standards for service design, APIs, and relational data modeling (SQL)
- Strengthen monitoring and operational visibility using New Relic and Kibana, turning insights into durable system improvements
- Mentor and unblock engineers through design reviews, pairing, and practical guidance
- Reduce technical risk and complexity while balancing near-term delivery with long-term architecture health
Requirements:
- 10+ years of software engineering experience, including leading technical direction across teams through architecture proposals and design reviews
- Experience building and operating microservices in production environments with a focus on reliability, performance, and maintainability
- Hands-on experience with AWS and containerized deployment environments
- Working knowledge of monitoring and logging practices using New Relic and Kibana
- Strong SQL skills and experience with relational data modeling for high-integrity systems
- Comfort working across a multi-language backend ecosystem (ASP.NET, Python, C#, Ruby)
- Ability to collaborate effectively with web teams and front-end technologies (Next.js, React)
- Ability to navigate ambiguity, make thoughtful tradeoffs, and communicate clearly with technical and non-technical partners