Everpure
Software Engineer
About this role
Join the Core Engineering team to build and maintain the foundational systems of an Enterprise Data Cloud platform, ensuring six 9s reliability for global enterprises. You'll own distributed systems components end-to-end, tackle complex challenges in consensus and fault tolerance, and collaborate with cross-functional teams to ship features from design through production.
What you'll do
- Design and build resilient, high-throughput distributed algorithms for six 9s uptime
- Lead platform initiatives from architectural design through production deployment
- Evaluate and resolve multi-faceted engineering issues in distributed consensus and resource allocation
- Conduct rigorous design reviews and code reviews with peer engineers
- Debug and optimize performance under high workloads and failure scenarios
- Work in-office from Santa Clara, CA in compliance with company policies
What they're looking for
- C++ systems programming
- Distributed systems design
- Linux and operating system internals
- Database engine knowledge
- Containerized environments
- Analytical problem-solving and debugging
- Concurrent programming
- Cross-functional 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.
Everpure
Everpure builds cloud-native storage and data infrastructure solutions, including Kubernetes platforms and enterprise SSD products for mission-critical environments. The company is hiring technical support engineers, validation engineers, and solutions specialists to diagnose complex infrastructure issues, qualify storage hardware, and deliver customer support across cloud and storage technologies.
- Website
- everpure.com
Likely interview questions
- Describe your experience designing or debugging distributed consensus algorithms and how you approach ensuring reliability at scale.
- Walk us through a complex production incident you resolved involving distributed systems—what was your debugging process?