Lead Infrastructure Engineer - Remote
Lead Infrastructure Engineer with 8+ years of infrastructure experience to own Kubernetes and core infrastructure for a GPU-focused neocloud platform.
Company Details
NeoHPC is a small, remote-first neocloud provider building a full-stack GPU-focused edge platform from bare metal to inference services.
Requirements
9+ years of experience in infrastructure engineering.
Deep understanding of Kubernetes internals and core components.
Strong production experience designing and operating Kubernetes environments.
Strong Infrastructure as Code and automation experience.
Strong understanding of Kubernetes networking, ingress, DNS, service discovery, load balancing, and storage.
Strong Linux and systems troubleshooting skills.
Experience operating containerized workloads in production.
Ability to debug across Kubernetes, Linux, networking, storage, virtualization, and physical infrastructure.
Experience building reliable, observable, and operable infrastructure.
Ability to own infrastructure problems from architecture through production.
Strong technical leadership and pragmatic decision-making.
Responsibilities
Design, build, and operate production-grade Kubernetes infrastructure.
Design virtualized Kubernetes clusters and tooling for provisioning, upgrades, scaling, security, observability, and troubleshooting.
Build Infrastructure as Code and automation for repeatable provisioning and operations.
Design and operate Kubernetes networking, ingress, DNS, service discovery, load balancing, and network policies.
Design and operate Kubernetes storage, persistent volumes, and CSI-based systems.
Diagnose complex infrastructure problems across multiple layers of the stack.
Build internal platform services that improve reliability or developer experience.
Establish infrastructure standards, operational practices, observability, and reliability mechanisms.
Make pragmatic trade-offs between speed, reliability, simplicity, and maintainability.
Provide technical leadership and shape the platform architecture.
Job Details
Remote
Interview Process
Recruiter Screening
Infrastructure Deep Dive
Kubernetes & Systems Design
Technical Leadership Round
Founder/Team Round
Important Note
ClanX is a recruitment partner, helping NeoHPC hire Lead Infrastructure Engineer.
Skills
As published by recruitee · 16 questions · 6 written answers
Basics
Full name, Email, CV, Phone
Short answers (3)
- Please share the figures for your current CTC breakup: Fixed, Variable, ESOPs (with vesting), and any other components
- What is your expected annual CTC? (INR)
- Help us with your LinkedIn profile link
Pick from a list (7)
- How many years of experience do you have as a Infrastructure Engineer or similar roles working primarily on Infrastructure?
- Do you have hands-on experience with Kubernetes
- What is your notice period? (We are looking for candidates who can join within 30 days)
- Is your notice period negotiable?
- Do you have experience working at a product-based company?
- Are you a citizen of India and currently based in India?
- What is your current annual CTC range? (INR)
Written answers (6)
- Have you personally or professionally worked on a core infrastructure project involving network, storage, compute, or GPU where you drove the technical direction? If yes, please provide details of the project, your role, what you owned, and the outcome. If no, write NA.
- Have you owned a component or platform end-to-end, from ideation and design to production and customer delivery? If yes, please provide details of the component/platform, your responsibilities, and what you delivered. If no, write NA.
- Are you willing to join an early-stage company where you will be expected to discover problems and lead solutions? If yes, please provide details of any similar experience you have had. If no, write NA.
- Do you understand how Kubernetes works under the hood? If yes, please provide details of your understanding and the Kubernetes components or internals you have worked with. If no, write NA.
- Have you designed and driven the adoption of any tooling around platform engineering, CI/CD, observability (o11y), or automation? If yes, please provide details of the tooling, what you built, your role, and how it was adopted. If no, write NA.
- Where did you find this job opportunity? (e.g., LinkedIn, Twitter, WhatsApp, etc). If someone referred you, please mention their name and contact number so we can thank them. (Write NA if not applicable).