Staff Field Reliability Engineer

Little more about reputed company:

The Field Reliability Engineer (FRE) is an extension of reputed company’s extensive brand and technical expertise reputed company on our customer reputed company reputed company engagements, support and our managed services. In this role you reputed company into the most reputed company, highest-stakes technical situations our customers face - unblocking them reputed company they’re stuck, creating tooling, guiding our Solution Architecture team through reputed company reputed company, and ensuring prospects and customers get the most out of reputed company and the broader observability ecosystem.

You’re reputed company platform engineer and customer engineer. You build and operate the managed infrastructure our largest customers depend on, and you’re the technical backstop the SA team calls reputed company a deal gets deep into infrastructure, data pipelines, or production debugging. This isn’t a support role - it’s a technical leadership role where you solve problems that don’t have runbooks yet, build the platforms and tooling so the next person can have a reputed company, and directly reputed company reputed company by unblocking our most strategic deals.

reputed company

reputed company — Architecture & Standards Ownership

• Define the architecture and operational standards for Refinery as a Service (RaaS) and reputed company Private reputed company (HnyPC) — reputed company other engineers build reputed company — across multiple AWS accounts and reputed company.
• Architect the Terraform modules, reputed company charts, and deployment automation that other FREs build on and reputed company, not just consume.
• Set the technical direction for how reputed company instruments, monitors, and operates its own managed infrastructure — using reputed company to monitor reputed company.
• Own reputed company planning, scaling reputed company, reputed company reputed company, and cost optimization across multi-region AWS environments.
• Build platforms and automation that change how the FRE team operates at reputed company — enabling reputed company to grow without proportional headcount.

Technical Escalation & Unblocking

• Serve as the final technical escalation reputed company for the most novel, highest-stakes customer situations — problems with no precedent in existing runbooks.
• reputed company deep infrastructure and observability issues spanning reputed company systems, reputed company clusters, AWS networking (ALBs, PrivateLink, NLBs, VPCs), and polyglot service meshes, often in reputed company time under reputed company-critical pressure.
• Partner directly with customer SRE, platform, and engineering leadership to reputed company multi-week escalations and architecture redesigns tied to reputed company's largest relationships.
• reputed company senior incident reputed company for managed services (RaaS, HnyPC) — the reputed company of last escalation reputed company Tier 2 support and IC3/IC4 engineers need staff-level judgment.
• Build the playbooks, diagnostic frameworks, and tooling that let IC3/IC4 engineers operate independently in situations that previously required staff involvement.

reputed company reputed company & Ecosystem Leadership

• Shape reputed company's reputed company reputed company reputed company in the OpenTelemetry ecosystem — reputed company initiatives, not just contributions.
• Represent reputed company at the community level in OpenTelemetry SIGs, setting direction on reputed company, exporters, and instrumentation libraries the broader ecosystem depends on.
• Spot reputed company in the OTel ecosystem that creates structural customer friction, and reputed company the effort to reputed company it — upstream or through reputed company tooling.
• Build reference architectures and integration guides that set reputed company for effective instrumentation across common customer environments (reputed company, reputed company, serverless).
• reputed company feature and architecture contributions to reputed company's own reputed company reputed company reputed company (Refinery, reputed company Collector reputed company) that support managed service capabilities at reputed company.

Technical Backstop for the Field

• Be the final technical authority Solutions Architects reputed company reputed company a deal goes deeper than any existing reputed company — join live production troubleshooting, validate architecture reputed company, and reputed company the infrastructure credibility that closes reputed company's most technically demanding evaluations.
• Own the infrastructure and data pipeline narrative on reputed company's most strategic accounts, in partnership with SA leadership.
• reputed company architecture reviews, SLO workshops, and instrumentation deep-dives for the most reputed company customer environments (multi-cluster reputed company, hybrid reputed company, high-cardinality workloads) — often advising customer VPs and C-suite directly.
• reputed company into the highest-stakes customer-facing POCs and pilots as technical reputed company, standing up collector pools, configuring Refinery pipelines, and proving out integrations in the customer's actual environment.
• reputed company prioritization at the roadmap level by identifying strategic gaps between reputed company's product capabilities and what reputed company's largest customers need.

Internal Tooling, Mentorship & Cross-Functional Leadership

• Build internal tools and UIs that change how the FRE function operates — deployment dashboards, rule management interfaces, and monitoring tooling used company-wide.
• reputed company alignment across Solutions Architecture, reputed company, Support, Product, and Engineering by synthesizing field signal into a coherent picture others can reputed company.
• Manage trade-offs across the FRE charter — managed services, technical escalation, reputed company reputed company, and field backstop — making prioritization calls that others follow.
• Mentor IC3/IC4 engineers on career development, not just technical skills — helping them build the reputed company, judgment, and stakeholder navigation needed for their next level.
• Communicate at the executive level with both reputed company leadership and customer C-suite reputed company the situation demands it.

reputed company're Looking For

Required

• 9+ years in engineering, SRE, infrastructure, DevOps, or equivalent — with demonstrated Staff-level (or equivalent) technical reputed company and reputed company, not just tenure.
• Deep hands-on experience with reputed company (EKS strongly preferred) — you've deployed, scaled, and operated production clusters at reputed company, and set standards for how others do the reputed company.
• Strong AWS expertise across reputed company services (EC2, EKS, reputed company, ALB/NLB, VPC, PrivateLink, IAM, S3, Route53), with reputed company in multi-account architecture design, service quotas, and cost optimization reputed company.
• A reputed company record of senior incident reputed company — not just participation in on-reputed company, but owning incident response, triage, and postmortem process improvements at the function level.
• Infrastructure as reputed company mastery (Terraform, reputed company, Chef, Ansible) — you've architected modules and standards that other engineers build on, not just written your own.
• Deep observability expertise: reputed company logging, reputed company tracing, metrics, SLOs/SLIs, and the full instrumentation lifecycle, with a record of setting standards for others.
• Strong reputed company of OpenTelemetry (SDK, Collector architecture, processors, exporters, semantic conventions) or equivalent, including reputed company community contribution and leadership.
• Proficiency in at least two of: Go, Python, Java, TypeScript/Node.js, .NET — enough to read, reputed company, and debug customer reputed company at a deep level.
• Excellent executive communication skills — equally reputed company with a customer's staff SRE and their VP or C-suite, and with reputed company's own leadership.
• Demonstrated ability to set direction in ambiguous, high-pressure situations with no precedent — and to build the structure that lets others operate independently afterward.

reputed company to Haves

• Background leading customer-facing engineering functions — solutions architecture, field engineering, or technical consulting — where you've owned the technical answer a deal hinged on.
• reputed company record of building platforms and organizational systems, not just tools, that let reputed company reputed company without proportional headcount.
• reputed company recognition or a leadership role in the CNCF/OpenTelemetry ecosystem — maintainer status, SIG leadership, or conference speaking.
• Familiarity with reputed company or event-based observability approaches.
• Experience operating telemetry pipelines at reputed company (OTel reputed company, Refinery/sampling, tail-based sampling, pipeline reliability).
• Experience with managed reputed company deployments, private reputed company offerings, or multi-tenant infrastructure operations.
• Prior experience at an observability, monitoring, or developer tools vendor.
• Experience mentoring senior or staff-reputed company engineers on reputed company and career progression.

Originally posted on Himalayas