Sr. Software Engineer - Kubernetes & Observability (Contract) at CloudZero
Massachusetts, Massachusetts, USA -
Full Time


Start Date

Immediate

Expiry Date

10 Jul, 25

Salary

0.0

Posted On

11 Apr, 25

Experience

2 year(s) or above

Remote Job

Yes

Telecommute

Yes

Sponsor Visa

No

Skills

Python, New Relic, Aws, Kubernetes

Industry

Information Technology/IT

Description

YOU WILL

  • Be responsible for building out a backend that can query leading observability solutions (New Relic, Datadog, and more.)
  • Create a data pipeline to transform that data into CloudZero’s proprietary internal data layout.
  • Prototype quickly to test out various technical approaches to these problems.
  • Work closely with our Product Management team to understand what outcomes this feature should drive.
  • Bring other engineers on board to the project as technical approaches show merit.

REQUIREMENTS

  • At least 2 years of experience with Python
  • At least 8 years of experience building backend systems for a B2B SaaS company.
  • Experience and proficiency building on AWS, preferably with good experience with AWS Lambda
  • Experience programmatically retrieving data from top observability solutions in the market (Datadog or New Relic preferred)
  • Proficiency with Kubernetes constructs
Responsibilities

CloudZero is a leading cloud cost management company, and our SaaS platform excels at driving profitable innovation in some of the best engineering organizations in the world. We achieve those results with the CloudZero platform, which can ingest more data than our competitors and organize it to allow savings across any fast-moving organization.
We are seeking a talented & experienced backend engineer to help build out an exciting new piece of platform technology. This project will help customers connect their Kubernetes metrics natively from their observability platform of choice. You’ll help us build out a framework to pull in metrics from the customer’s observability vendor to allow them to get deep insight into what is driving their Kubernetes cluster spending.

Loading...