2

Remote Observability Engineer Jobs in Ohio (NOW HIRING)

Sr Software Engineer

Strongsville, OH · On-site +1

$113K - $149K/yr

Hybrid (3days Office / 2days Remote) Duration: Contract to Hire Years Of Exp Required: 10+ Years ... observability tools (Splunk, Dynatrace, or similar) • Prior experience working in large-scale ...

Staff Software Engineer

Columbus, OH · On-site +1

$174K - $262K/yr

Posting Type Hybrid/Remote Job Overview Who We Are Relativity is a leading legal data intelligence ... Engineering Culture:Continuous delivery, strong observability, and end-to-end ownership.

... observability/monitoring, SDKs/APIs/UIs, and low-code/no-code agent platforms * Provide in-depth ... Remote Pay Transparency and Benefits * The stated salary range represents the entire span ...

Senior Software Engineer

Cleveland, OH · On-site +1

$118K - $156K/yr

Own services in production, from deployment through to monitoring, observability, and operational ... that allow remote work or office attendance An attractive compensation and benefits package ...

Senior AI Engineer

Cleveland, OH · On-site +1

$101K - $139K/yr

Establish comprehensive model observability and guardrail systems to monitor real-time performance ... Apply today or check out all our opportunities! #LI-Remote #LI-Hybrid #LI-Onsite By submitting your ...

Senior Software Developer

Columbus, OH · On-site +1

$131K - $218K/yr

This role will allow for remote working. We are unable to provide sponsorship for this role ... CI/CD, and observability. * Ability to drive your work independently while collaborating ...

Senior Software Developer

Columbus, OH · On-site +1

$131K - $218K/yr

This role will allow for remote working. We are unable to provide sponsorship for this role ... CI/CD, and observability. * Ability to drive your work independently while collaborating ...

next page

Showing results 1-20

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 the most commonly searched types of Observability Engineer jobs in Ohio? The most popular types of Observability Engineer jobs in Ohio are:
What job categories do people searching Remote Observability Engineer jobs in Ohio look for? The top searched job categories for Remote Observability Engineer jobs in Ohio are:
What cities in Ohio are hiring for Remote Observability Engineer jobs? Cities in Ohio with the most Remote Observability Engineer job openings:
Sr Software Engineer

Sr Software Engineer

System One Holdings, LLC

Strongsville, OH • On-site, Remote

$113K - $149K/yr

Other

Posted 29 days ago


Job description

Tittle: Sr. Software Engineer
Location:
Strongsville, OH or Pittsburgh, PA
Work Mode : Hybrid (3days Office / 2days Remote)

Duration: Contract to Hire
Years Of Exp Required: 10+ Years
Function of the Group:
Payment Center team creates "one stop shop" for businesses to manage their payment activity.
Industry Background: Financial/Banking experience. Micro App experience is a major benefit
Job Responsibilities:
• Design, build, and maintain inner/orchestration microservices that integrate multiple backend systems (payments, accounts, vendors) to support Payment Center capabilities
• Develop and enhance API layers and service-to-service interactions, ensuring secure, scalable, and reliable data aggregation across systems
• Collaborate closely with the front-end Payment Center team and Business to build and integrate UI components (e.g., Payroll tile) and ensure seamless end-to-end user experiences
• Troubleshoot and optimize performance, resiliency, and fault tolerance across distributed services, including debugging production issues
• Participate in Agile ceremonies and cross-team coordination to align backend orchestration logic with business flows (ACH, Bill Pay, Payroll, etc.) and ensure timely delivery
Required Skills
• Strong experience building and integrating microservices (Spring Boot / Java preferred)
• Hands-on experience with backend service design for complex domains (APIs, orchestration, service-to-service communication)
• Solid understanding of event-driven architecture (Kafka or similar messaging platforms)
• Experience with containerization and deployment (Docker, Kubernetes/OpenShift)
• Expertise in API design and integration patterns (REST, secure APIs, contract-first design)
• Familiarity with enterprise authentication/authorization patterns (CIAM, OAuth, JWT)
• Experience working with distributed systems, including resiliency, scaling, and fault tolerance
• Strong debugging and performance tuning skills across microservices
• UI development experience (Angular or similar) to support front-end integration-specifically for building and integrating UI components like the Payroll tile
Flex Skills/Nice to Have:
• Experience with financial services or payments platforms (billing, payroll, account servicing)
• Exposure to Payroll integrations (ADP or similar providers)
• Familiarity with enterprise data platforms (BDC, FNW, or similar transaction/data systems)
• Experience with CI/CD pipelines and DevOps practices
• Knowledge of feature toggles and rollout strategies for phased releases
• Experience working in Agile delivery models with cross-functional teams
• Understanding of UI/UX best practices for customer-facing applications
• Exposure to observability tools (Splunk, Dynatrace, or similar)
• Prior experience working in large-scale enterprise environments with multiple dependent systems
Ref: #404-IT Pittsburgh