🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Join Granicas core engineering team to build and scale the infrastructure powering massive data systems, automated deployments, and highreliability AI workloads. This is a deep engineering role not ops, not feature delivery. The infrastructure you build directly enables: exabytescale data systems fast researchtoproduction cycles reliable enterprise AI workloads This role offers deep ownership, high technical impact, and a long horizon. What Youll Do-Design and operate cloud infrastructure supporting petabyteexabytescale systems. Manage and evolve production Kubernetes clusters with high availability and predictable scaling. Build and optimize CI/CD pipelines for faster builds, reliable tests, and safer deployments. Improve developer experience by reducing friction and automating workflows. Contribute to E2E testing and releaseconfidence systems. Strengthen observability across logging, metrics, tracing, and alerting. Collaborate across engineering teams on architecture, reliability, and scaling challenges. Own customerfacing technical integration guide deployments, troubleshoot infralevel issues in customer environments, and ensure Granica runs reliably within diverse cloud, data, and security stacks. Drive operational excellence through reliability, automation, and best practices. What We're Looking For-5+ years in infrastructure, platform, or distributed systems engineering Strong coding skills in Go, Java, Python, or similar Productiongrade Kubernetes experience with strong cloud and containerization skills across AWS/GCP/Azure and Docker. Deep experience with CI/CD systems and cloud infrastructure Proficiency with infrastructureascode (Terraform) Ability to debug complex, crosslayer issues (networking, storage, runtime) Track record of designing scalable, reliable, costefficient systems Thrives in fastpaced startup environments with strong communication and ownership. Nice-to-Haves:Experience with data platforms or lakehouse systems Familiarity with Spark, Trino, Iceberg, Delta, Airflow Exposure to observability stacks (Prometheus, Grafana, ELK, Datadog) Compensation & BenefitsCompetitive salary, meaningful equity, and performance bonus for top performers 401(k) with company match, comprehensive health coverage, and unlimited PTO Daily catered meals in our Mountain View office Support for research, publication, and conference participation At Granica, you'll help build the next generation of enterprise AIfrom exabyte-scale data infrastructure, Large Tabular Models (LTMs), and stateful AI agents. Together, we're creating the infrastructure that enables enterprises to own their data, own the intelligence built on it, and scale both efficiently. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.