ZipRecruiter

Log In

2

Remote Observability Engineer Jobs in Oregon (NOW HIRING)

Gnostech LLC

Software Engineer (US-Remote)

OR · Remote

Software Engineer (US-Remote) ID: 1191 Location: US-Remote or Marlton, NJ area Description A ... Monitor and troubleshoot applications in distributed environments using logging, observability, and ...

Upstart

Senior Software Engineer, Site Reliability

OR · On-site +1

$57 - $75.75/hr

... observability platform * Experience leveraging LLM/GenAI to improve SRE efficiency and processes Position Location - This role is available in the following locations: Remote, San Mateo, Columbus ...

Embrace

Solutions Engineer - US Remote

OR · Remote

$130K - $160K/yr

At Embrace, we're the only user-focused observability solution built on OpenTelemetry, providing ... Communicate directly with customers, product and engineering teams, and work together towards a ...

Upstart

Senior DevOps Engineer, Ephemeral Platform

OR · On-site +1

$129K - $166K/yr

Enhance observability, incident response, and operational practices to improve platform health and ... Remote Time zone requirements The team operates on the East/West coast time zones. Travel ...

Terzo

(Sr/Staff) Platform Engineer

OR · On-site +1

US - Remote Level : Senior Individual Contributor Team : Engineering The Opportunity Terzo ... Comfort with observability systems including monitoring, alerting, logging, tracing * Strong SRE ...

Grafana Labs

Staff AI Engineer | US | Remote

OR · Remote

This is a remote opportunity and we are looking for candidates from the U.S. The Opportunity ... Implement observability and feedback loops including logging, performance metrics, prompt iteration ...

Parachute Health

Senior Platform Engineer

OR · Remote

$165K - $210K/yr

Improve production observability: work with product teams to ensure they are equipped to ... We are remote-first with a dedicated NYC office and reimbursement options for co-working spaces.

Grafana Labs

Senior AI Engineer | US | Remote

OR · Remote

$55.25 - $71.25/hr

This is a remote opportunity and we are looking for candidates from the U.S. The Opportunity ... Implement observability and feedback loops including logging, performance metrics, prompt iteration ...

Parachute Health

Staff Software Engineer, Applied AI

OR · Remote

$200K - $260K/yr

Improve production observability: accuracy signals and feedback loops. * Contribute to architecture ... We are remote-first with a dedicated NYC office and reimbursement options for co-working spaces.

next page

Showing results 1-20

All JobsObservability Engineer JobsRemote Observability Engineer JobsRemote Observability Engineer Jobs in Oregon

Remote Observability Engineer information

What are the typical collaboration patterns for a Remote Observability Engineer working with distributed teams?

Remote Observability Engineers frequently collaborate with software developers, DevOps teams, and IT operations to ensure systems are monitored effectively and issues are detected early. Working remotely, you'll often use communication tools like Slack, Jira, and video conferencing to coordinate incident response, discuss monitoring strategies, and review system health dashboards. Regular sync meetings and asynchronous updates are common, and you'll likely contribute to documentation and knowledge sharing to keep all stakeholders informed. Building strong communication habits is important, as much of the troubleshooting and improvement work hinges on clear coordination with multiple teams.

What are the key skills and qualifications needed to thrive as a Remote Observability Engineer, and why are they important?

To thrive as a Remote Observability Engineer, you need strong expertise in monitoring, logging, and tracing systems, along with a background in computer science or related technical fields. Familiarity with tools like Prometheus, Grafana, ELK Stack, Datadog, and cloud platforms is typically required, as well as relevant certifications such as AWS Certified Cloud Practitioner or Google Cloud Professional DevOps Engineer. Excellent problem-solving abilities, communication skills, and a proactive mindset help you detect and resolve issues before they impact users. These competencies ensure system reliability, enable rapid incident response, and support seamless collaboration in distributed environments.

What is the difference between Remote Observability Engineer vs Site Reliability Engineer?

AspectRemote Observability EngineerSite Reliability Engineer
CredentialsKnowledge of monitoring tools, scripting, cloud platformsSame as Observability Engineer, plus SRE certifications often preferred
Work EnvironmentFocus on monitoring, logging, and tracing systems remotelyBroader scope including system reliability, incident response, and automation
Industry UsagePrimarily in tech, SaaS, cloud servicesWidely in tech, finance, and large-scale online services

The Remote Observability Engineer specializes in monitoring and analyzing system performance remotely, focusing on tools like logs and metrics. In contrast, the Site Reliability Engineer has a broader role, ensuring overall system reliability, automation, and incident management. While both roles require similar technical skills, SREs often have additional responsibilities related to system resilience and scalability.

What is a Remote Observability Engineer?

A Remote Observability Engineer is a professional responsible for designing, implementing, and maintaining systems that monitor the health, performance, and reliability of software applications and infrastructure from a remote location. They use observability tools to collect and analyze logs, metrics, and traces, helping organizations quickly detect and resolve issues. Their work ensures that distributed systems are transparent, reliable, and efficient, often collaborating with development, operations, and security teams. Remote Observability Engineers often work from anywhere, leveraging cloud-based tools and platforms to manage complex IT environments.
What are popular job titles related to Remote Observability Engineer jobs in Oregon? For Remote Observability Engineer jobs in Oregon, the most frequently searched job titles are:
What job categories do people searching Remote Observability Engineer jobs in Oregon look for? The top searched job categories for Remote Observability Engineer jobs in Oregon are:
What cities in Oregon are hiring for Remote Observability Engineer jobs? Cities in Oregon with the most Remote Observability Engineer job openings:
Remote Observability Engineer jobs near you

Cloud Software Engineer - Observability Platform

ClickHouse

OR • Remote

Other

Re-posted 28 days ago

Job description

ClickHouse is looking for an experienced engineer to join our Observability organization. We are hiring across two closely aligned teams: Observability Platform and Internal Observability.

Together, these teams build and operate the systems behind ClickHouse's internal observability and ClickStack Cloud. Our platforms process trillions of events per day, sustaining throughput in the hundreds of millions of events per second. The experience we gain operating observability at ClickHouse scale feeds directly back into the platform and product we provide to customers.

The Observability Platform team builds shared systems for telemetry ingestion, durable buffering, processing, storage, autoscaling, and service provisioning. The Internal Observability team operates ClickHouse's company-wide observability platform and works with engineering teams to improve reliability, debugging, and operational efficiency.

This is a software engineering role at the intersection of distributed systems, cloud infrastructure, and production operations. You will build systems, operate what you build, respond to incidents, and turn recurring operational problems into durable software and automation.

Your background may be in backend engineering, infrastructure, SRE, or systems engineering. What matters most is your ability to solve ambiguous production problems, make sound engineering tradeoffs, and take ownership from design through operation.

What you'll do
  • Design, build, and operate distributed systems that ingest, process, and store telemetry at very high scale.
  • Own the reliability, performance, capacity, and cost-efficiency of telemetry pipelines and storage systems.
  • Participate in the on-call rotation, help resolve production incidents, and drive root-cause fixes through to completion.
  • Build software and automation that eliminate repetitive operational work and make the platform easier to operate.
  • Identify architectural bottlenecks and help shape the roadmap for the next stage of scale.
  • Work closely with product, infrastructure, and service teams across ClickHouse.
  • Contribute to architecture and design reviews and help raise engineering quality across the team.
How you work
  • You take ownership and proactively improve the systems around you.
  • You are comfortable debugging unfamiliar distributed systems in production.
  • You make pragmatic tradeoffs between reliability, performance, delivery speed, and cost.
  • You communicate clearly in a remote, async-friendly environment.
  • You prefer incremental delivery: ship a focused solution, validate it in production, and improve it based on evidence.
  • You address the underlying cause of operational problems rather than repeatedly treating the symptoms.
Technical experience
  • 5+ years of experience building and operating production systems at scale.
  • Strong proficiency in Go.
  • Experience building and operating services on Kubernetes.
  • Experience with infrastructure-as-code and GitOps tooling such as Terraform, Helm, and Argo CD.
  • Production experience with at least one major cloud provider: AWS, GCP, or Azure.
  • Hands-on experience with telemetry systems such as OpenTelemetry, Prometheus, Grafana, or comparable technologies.
Bonus points
  • Experience with ClickHouse.
  • Experience with high-throughput ingestion, streaming, queueing, or storage systems.
  • Experience building multi-tenant cloud services.
  • Experience optimizing infrastructure for both performance and cost.
  • Experience with TypeScript.

#LI-Remote

Apply