Databricks
About this role
Databricks operates one of the largest software platforms in the world, a fleet of millions of virtual machines spread across AWS, Azure and GCP, and the networking team builds the connectivity layer underneath all of it. That means the network paths between customer workloads, the platform's own services and three different cloud providers, each with its own primitives and failure modes. The requirement is 8 or more years of production level experience in Python, Java, Scala, C++ or a similar language, with 4 or more years in a networking specific context, so this is a specialism rather than general backend work. It suits an engineer who has debugged connectivity problems across cloud boundaries and understands why a packet did not arrive. Databricks is building out its Bengaluru site with new teams, so expect early formation rather than an established codebase.
Who this is for
What the posting requires:
- 8+ years of production level experience in one of Python, Java, Scala, C++ or a similar language.
- 4+ years of experience in a networking focused context, which is the specialism this role is hiring for.
- Experience developing large scale distributed systems.
- Hands on experience developing and operating backend systems.
What the work actually looks like, given the team's remit:
- Build and operate the networking layer for a platform running across AWS, Azure and GCP at a fleet size measured in millions of virtual machines.
- Handle the differences between cloud providers' networking primitives, and design so that provider level faults degrade gracefully rather than breaking customer workloads.
- Low level systems debugging and performance measurement on large production clusters.
- Contribute across the project lifecycle from design through implementation and ongoing operation.
The operating context Databricks describes: at its scale the company routinely observes cloud hardware, network and operating system faults, and the software is expected to shield customers from all of them. That is the daily reality of a networking role there rather than an abstract claim.
Location and working pattern: Bengaluru. Databricks says it is standing up new teams from scratch at this site, so expect an in office or hybrid arrangement, with the number of days not stated.
Compliance note in the posting: the standard Databricks export controlled technology clause applies. Where such access is required, applying for a US government licence is at the employer's discretion and it may decline to proceed on that basis.
Honest fit guidance: the 4 years of networking experience is what separates applications here, not the 8 years overall. Cloud networking at multi provider scale is a narrow skill and the people who have it are usually not looking, which is a reason to apply if you do. If your networking exposure is configuring a VPC occasionally, the requirement is deeper than that.
- 8+ years of production level experience in one of Python, Java, Scala, C++ or a similar language.
- 4+ years of experience in a networking focused context, which is the specialism this role is hiring for.
- Experience developing large scale distributed systems.
- Hands on experience developing and operating backend systems.
What the work actually looks like, given the team's remit:
- Build and operate the networking layer for a platform running across AWS, Azure and GCP at a fleet size measured in millions of virtual machines.
- Handle the differences between cloud providers' networking primitives, and design so that provider level faults degrade gracefully rather than breaking customer workloads.
- Low level systems debugging and performance measurement on large production clusters.
- Contribute across the project lifecycle from design through implementation and ongoing operation.
The operating context Databricks describes: at its scale the company routinely observes cloud hardware, network and operating system faults, and the software is expected to shield customers from all of them. That is the daily reality of a networking role there rather than an abstract claim.
Location and working pattern: Bengaluru. Databricks says it is standing up new teams from scratch at this site, so expect an in office or hybrid arrangement, with the number of days not stated.
Compliance note in the posting: the standard Databricks export controlled technology clause applies. Where such access is required, applying for a US government licence is at the employer's discretion and it may decline to proceed on that basis.
Honest fit guidance: the 4 years of networking experience is what separates applications here, not the 8 years overall. Cloud networking at multi provider scale is a narrow skill and the people who have it are usually not looking, which is a reason to apply if you do. If your networking exposure is configuring a VPC occasionally, the requirement is deeper than that.
Apply on company site
Opens databricks.com, the employer's own application page. Applying is always free.