About G-Tek
G-Tek Corporation Pvt. Ltd. is a 37-year-old industrial technology company headquartered in Vadodara, Gujarat. We design and manufacture industrial monitoring devices — sensors, data loggers, controllers — used in pharma manufacturing, vaccine cold chain, blood banks, laboratories, and process industries. Our devices are deployed across thousands of sites in India and internationally, and trusted to keep medicines viable, laboratories compliant, and processes safe.
We are a profitable, debt-free, founder-led Pvt Ltd company. We are not venture-funded. We do not lay off engineers when the market wobbles. We have customers who have stayed with us for 20+ years because we deliver on our commitments. We have employees who have stayed with us for 25+ years because we treat them as professionals, not as resources.
We are now investing seriously in our next-generation software platform — Java / Spring Boot / MQTT / microservices, deployable both as a single on-prem installer for regulated pharma customers and as a multi-tenant SaaS for enterprise customers. The foundational architecture (MODBUS communication, MQTT broker integration, CI/CD pipeline) is built and tested with 200+ simultaneous devices. The remaining services, the frontend, the on-prem installer engineering, and the cloud SaaS deployment are the work we are hiring for.
This is not a greenfield project, and it is not a maintenance project. It is the building of a new platform on a proven foundation, with the backing of a profitable parent business and the involvement of the original architect as a part-time advisor. It is, in short, the kind of project that doesn't come along often in industrial software.
G-Tek Leadership Constitution
Before describing the role, we want you to read what we stand for. If you read this and feel "that's how I work," keep reading. If you read this and feel "that's not how I want to work," we'd rather you find out now than after we both invest in interviews.
We reward
- Ownership — taking responsibility for outcomes, not just tasks
- Technical honesty — saying what is true, especially when it is uncomfortable
- Solving without excuses — finding paths forward, not reasons why something can't be done
- Long-term thinking — building for years, not for the next demo
- Respect for quality — taking pride in what leaves your hands
- Humility with competence — strong opinions, lightly held; willing to learn from anyone
We reject
- Ego without output
- Politics and positioning
- Blame shifting when things go wrong
- Urgency without discipline
- Shortcut mindset that creates tomorrow's problems
- Dependency culture — waiting to be told what to do
Non-negotiables
- Customer trust — earned slowly, lost instantly
- Product reliability — our devices keep medicines viable; software that supports them must be just as reliable
- Design integrity — architecture decisions made for the right reasons, defended honestly
- Delivery commitment — when we say we will ship, we ship
If you have ever felt choked by big-company silos, by political games, by smart people whose work doesn't ship — we built G-Tek precisely to be the opposite of that. We are small enough that your work matters, profitable enough that you have real resources, and serious enough that what you build will be used by people who depend on it.
The Role at a Glance
We are hiring a DevOps / Platform Engineer to own the infrastructure and build systems for our next-generation industrial monitoring platform. The platform must ship in two very different modes from the same codebase: as a single Windows installer for on-prem pharma customers (often air-gapped) AND as a cloud-hosted SaaS for enterprise customers.
This is not a sysadmin role. This is not a release manager role. If you spend your days clicking through AWS consoles or manually pushing releases, please don't apply. We need someone who codes infrastructure — Terraform, Helm, Python automation, CI/CD pipelines that actually do something — and who understands that the on-prem installer for a pharma customer is just as serious an engineering problem as cloud deployment.
What You Will Own
- CI/CD pipelines that produce, from the same Git tag: (a) a single-installer Windows artifact bundling all services as Docker containers, and (b) cloud-deployable container images for the SaaS environment. You'll inherit a basic GitLab CI/Jenkins setup that needs to be hardened and extended
- Infrastructure as Code for the SaaS environment — Terraform (or equivalent) for AWS provisioning, Helm charts or Kustomize for Kubernetes deployments
- The on-prem installer engineering problem — design and build the installer that wraps Docker, orchestrates services via Compose, handles upgrades, manages certificates, and gives the customer's IT team a single artifact to install and validate. This is the hardest and most distinctive problem in the role
- Observability platform — Prometheus/Grafana, centralized logging (Loki or ELK), distributed tracing. Design dashboards that mean something — device health, MQTT broker health, gap-recovery success rates, audit trail integrity
- Secrets and certificate management — Vault or equivalent for SaaS, a secure-but-installable equivalent for on-prem
- Build reproducibility and artifact signing — critical for our 21 CFR Part 11 compliance story. Every artifact we ship must be traceable and signed
- Internal tooling — the small Python/Go/Bash tools that make the team 3x more productive (customer environment health-checks, log collection for on-prem support, license management, deployment audit reports)
- Production support partnership — when something breaks in a customer environment at 2 AM, you partner with the on-call backend engineer. You don't own application bugs, but you own the platform's debuggability
What You Bring/Must-have
- 5+ years in DevOps / Platform / SRE roles with at least 3 of those writing significant code, not just configuring tools
- Strong scripting/coding skills in Python, Go, or Bash (one strong + one passable). You can show us a non-trivial automation script you wrote
- Infrastructure as Code — hands-on Terraform, Pulumi, or CloudFormation. You can show us a module you designed and explain the trade-offs
- Container expertise — Docker fundamentals, multi-stage builds, image security, Docker Compose for local and on-prem orchestration
- Kubernetes or equivalent orchestrator — Helm or Kustomize, deployments, services, ingress, persistent volumes. You don't need a CKA, but you can debug a CrashLoopBackOff without Googling every step
- CI/CD pipeline development — GitLab CI, Jenkins, GitHub Actions, or similar. You've written pipelines, not just edited them
- Observability setup — Prometheus + Grafana minimum; bonus for distributed tracing and log aggregation
- Linux fundamentals — you can debug a misbehaving systemd service or a network issue without panic
What Separates Great Candidates from Good Ones for Our Context
- You have shipped software that runs on customer infrastructure, not just SaaS. You understand what "no internet egress" and "Windows with corporate antivirus" mean for your design
- You have built a single-installer bundle for a multi-service application before, or you have strong opinions on how you would
- You have worked in regulated software (pharma, medical, finance) and understand why build reproducibility and artifact signing matter
- You are comfortable with Windows as a deployment target even if your daily driver is Linux
Why This Role Might NOT Be Right for You
- If you have only worked in pure-cloud SaaS environments, the on-prem half of this role will be unfamiliar. We're upfront about this — half your work is solving deployment problems most DevOps engineers never see
- If you want to manage a team of DevOps engineers, this isn't the role. You'll be the only platform person for the first 12-18 months
- If you don't enjoy writing code, you will be miserable. 60% of your time is in an editor
Benefits:
- Paid time off
- Provident Fund
Work Location: In person
