ZipRecruiter

Log In

1

Home Based Observability Engineer Jobs in Utah (NOW HIRING)

MX Technologies, Inc.

Sr. Observability Engineer

Lehi, UT · On-site

$98K - $134K/yr

... feel at home at MX. At MX, reliability is a product. Our infrastructure powers financial ... This role is based in Lehi, Utah. We believe in empowering our team members to deliver exceptional ...

NRG

Staff, AI Platform Engineer

Lehi, UT · On-site

Vivint Smart Home, an NRG owned company, is a leading smart home company in the United States ... Develop observability for model quality, latency, cost, drift, safety, and customer impact.

Taxbit

Agentic AI Engineer

Salt Lake City, UT · Hybrid

$130K - $170K/yr

... observability tooling; iterate rapidly based on real user behavior and feedback * Collaborate cross ... Hybrid working model: 3 days in-office, 2 days WFH/flexible * Monday team lunches, snacks and ...

Taxbit

Agentic AI Engineer

Salt Lake City, UT · On-site

$130K - $170K/yr

... observability tooling; iterate rapidly based on real user behavior and feedback * Collaborate cross ... Hybrid working model: 3 days in-office, 2 days WFH/flexible * Monday team lunches, snacks and ...

TaxBit

Agentic AI Engineer

Salt Lake City, UT · Hybrid

$130K - $170K/yr

... observability tooling; iterate rapidly based on real user behavior and feedback * Collaborate cross ... Hybrid working model: 3 days in-office, 2 days WFH/flexible * Monday team lunches, snacks and ...

LVT

Senior DevOps Engineer I

American Fork, UT · On-site

$116K - $149K/yr

This role is based out of our headquarters in American Fork, Utah. It will operate on a hybrid ... System Observability: Develop, implement, and maintain advanced observability, monitoring, and ...

Canopy

Senior Application Security Engineer

South Jordan, UT · Remote

$109K - $149K/yr

Build out the security observability stack: audit logging, cloud posture monitoring, runtime threat ... based detection techniques * Embed security into the SDLC -- CI/CD gates, secret scanning, threat ...

Canopy

Senior Application Security Engineer

South Jordan, UT · Remote

$109K - $149K/yr

Build out the security observability stack: audit logging, cloud posture monitoring, runtime threat ... based detection techniques * Embed security into the SDLC -- CI/CD gates, secret scanning, threat ...

Canopy

Senior Application Security Engineer

South Jordan, UT · Remote

$109K - $149K/yr

Build out the security observability stack: audit logging, cloud posture monitoring, runtime threat ... based detection techniques * Embed security into the SDLC - CI/CD gates, secret scanning, threat ...

TAB Bank

Software Engineer IV

Ogden, UT · On-site

System-level thinking (resiliency, observability, performance) * Modernization and cloud-native ... Hands-on experience integrating AI/ML components or LLM-based services into production environments ...

next page

Showing results 1-20

All JobsHome Based Observability Engineer JobsHome Based Observability Engineer Jobs in Utah

Home Based Observability Engineer information

What is the difference between Home Based Observability Engineer vs Network Operations Center (NOC) Technician?

AspectHome Based Observability EngineerNetwork Operations Center (NOC) Technician
CredentialsRelevant certifications like Cisco CCNA, CompTIA Network+Similar certifications often required, such as Cisco CCNA
Work EnvironmentRemote, home-based setup with monitoring toolsOn-site or remote, monitoring network systems in a control room
Industry UsageIT, cloud services, software companiesTelecommunications, internet service providers
Job FocusMonitoring, troubleshooting, and optimizing observability toolsNetwork monitoring, incident response, and system maintenance

While both roles involve monitoring network and system health, the Home Based Observability Engineer focuses on software observability tools and cloud environments remotely, whereas the NOC Technician primarily manages network infrastructure on-site or remotely. Both require similar certifications and are vital in maintaining system uptime, but their daily tasks and work settings differ.

What are the most commonly searched types of Observability Engineer jobs in Utah? The most popular types of Observability Engineer jobs in Utah are:
What are popular job titles related to Home Based Observability Engineer jobs in Utah? For Home Based Observability Engineer jobs in Utah, the most frequently searched job titles are:
What job categories do people searching Home Based Observability Engineer jobs in Utah look for? The top searched job categories for Home Based Observability Engineer jobs in Utah are:
What cities in Utah are hiring for Home Based Observability Engineer jobs? Cities in Utah with the most Home Based Observability Engineer job openings:
Home Based Observability Engineer jobs near you

Sr. Observability Engineer

MX Technologies, Inc.

Lehi, UT • On-site

$98K - $134K/yr

Full-time

Posted 5 days ago

Job description

MX is a fintech company on a mission to empower the world to be financially strong. We build technology that helps banks, credit unions, and fintechs deliver smarter, more intuitive financial experiences to millions of people.
Like many startups, we've navigated real growth challenges - and we've come out stronger on the other side. Today, MX is in a phase ofrenewed momentum and scale, with a solid foundation and a clear vision for what's next. This is a place where thoughtful execution matters, innovation is encouraged, and individuals have real ownership over their work.
Our culture values curiosity, accountability, and impact. We give people the space to question assumptions, design better solutions, and help shape how the company grows. If you're looking to do meaningful work, influence outcomes, and grow alongside a company that's ready to move fast, you'll feel at home at MX.
At MX, reliability is a product. Our infrastructure powers financial applications used by millions of people and processes billions of transactions for major financial institutions, and customers feel every second of downtime.
We're building a new observability function that runs the way we run incident response: the system does the heavy lifting, and people handle judgment, customers, and the exceptions. As a Senior Observability Engineer, you build and operate an observability control plane. You scaffold baselines, score coverage, and turn every real incident into the detection the platform should have caught. This is a multiplier role: you raise the bar for every team through standards and automation instead of building each team's dashboards by hand.
We call it the shepherd model. You shepherd Datadog and partner with our product engineering teams so they observe the right signals for their products. Service owners get real signal instead of noise, and leadership gets coverage and health as a program metric.
This role shares the team pager. Observability and incident response run one on-call roster. You take shifts with the rest of the team and act as Incident Commander when an incident needs one. It is core to the role, not an afterthought.
Engineering at MX runs hybrid infrastructure (AWS and bare metal) with services in Ruby, Go, and Java, messaging over NATS and RabbitMQ, and data on PostgreSQL and Redis. Datadog is our observability platform and incident.io is our incident response platform.
What you'll do:
  • Build and operate an observability control plane: automate baseline monitors, dashboards, and tagging standards through the Datadog API and Terraform.
  • After significant incidents, produce detection and dashboard gap packs grounded in Datadog and MX investigation patterns, with queries ready to apply.
  • Define what "good" looks like for a Ruby, Go, or Java service on Datadog (tags, golden signals, alert quality, dashboard contracts), then audit services against that standard and accept or reject readiness.
  • Validate, don't own. Service owners keep their alerts and dashboards; you confirm they are complete and correct, then move on. Escalate to engineering managers when coverage fails or an owner is missing.
  • Own the monthly observability and service-catalog health report: departed owners, stale dashboards, services with no monitors, SLO gaps, and coverage trends.
  • Run maturity assessments (baseline through SLO, launch-ready, self-serve) and track them over time.
  • Tune alerting toward zero false SEV1/2 pages and actionable SEV3/4 alerts, and coach teams on Datadog cost and cardinality.
  • Build self-serve onboarding so new services get baseline observability on day one, without a multi-week embed.
  • Share the team pager. Rotate on the shared IR & Observability on-call, triage and investigate live incidents with Datadog and MX investigation patterns, and take Incident Commander or supporting technical roles as the incident needs.
  • After incidents, close the detection loop (gap packs, new monitors, dashboards) so the pager gets quieter over time.
  • Run high-value launch and production-readiness reviews as a checkpoint, not a permanent staffing model.

Basic Requirements
  • BS in Computer Science or equivalent experience
  • 5+ years running production observability, SRE, or DevOps
  • 5+ years automation-first engineering in Python, Bash, Go, and/or Terraform, plus Kubernetes proficiency
  • AI- and workflow-literate. You've used or built scripted and AI-assisted workflows to scale reviews, audits, and docs
  • Distributed-systems debugging across microservices: latency, connection pools, queues, and cascading failure on Kubernetes and bare metal, with NATS, RabbitMQ, Postgres, and Redis
  • Shared on-call, Incident Commander-capable

Preferred Requirements
  • Fintech experience with MX-like architectures
  • Datadog preferred; strong Grafana/Prometheus, Splunk, or New Relic experience counts if you can ramp on Datadog fast
  • Google SRE practices: toil elimination, incident management, automation for self-healing
  • Cross-functional influence without authority. You've improved teams that don't report to you
  • Governance and reporting: you can produce a monthly health and compliance report leadership reads (orphans, stale entries, gaps, trends)
  • OpenTelemetry instrumentation
  • Incident response platforms (incident.io, PagerDuty, OpsGenie); prior formal Incident Commander experience
  • Golang and Ruby on Rails (the MX stack)

At MX, we are a high-performance organization that thrives on trust and results. This role is based in Lehi, Utah. We believe in empowering our team members to deliver exceptional outcomes while taking advantage of our incredible office space when it best supports their work. Our Utah office features onsite perks such as company-paid meals, a sports simulator, gym, mother's lounge, and meditation room and meaningful interactions with amazing people. We encourage team members to come together in the office to collaborate, kick off key projects, or strategize cross-functionally, fostering connection and innovation.
MX is proudly committed to recruiting and retaining a diverse and inclusive workforce. As an Equal Opportunity Employer, we never discriminate based on race, religion, color, national origin, gender (including pregnancy, childbirth, or related medical conditions), sexual orientation, gender identity, gender expression, age, military or veteran status, status as an individual with a disability, or other applicable legally protected characteristics. We particularly welcome applications from veterans and military spouses. All your information will be kept confidential according to EEO guidelines. You may request reasonable accommodations by sending an email to hr@mx.com.

Apply