2

Remote Open Source Jobs in Oregon (NOW HIRING)

Quartz ranked us the #1 best company for remote workers We are hiring a Senior Infrastructure ... Patch and optimize open-source components for performance and security. * Build iPaaS and AI ...

Senior Software Engineer

Portland, OR · On-site +1

$150K - $190K/yr

Remote Department Engineering Compensation: $150K - $190K At Confluent, we are committed to ... Contribute to open-source projects and leverage open-source technologies to drive business impact.

$150K - $250K/yr

Remote Worker must live within USA or Canada Travel: 5% / year Experience: 5 - 8 years as senior ... experience using open source technologies * Experience building an SOA (Software Oriented ...

Upsunners are a remote, global workforce, and we thrive in a multicultural team. We are committed to open source and an open, welcoming environment. Our team spans the globe and the experience ...

Staff Software Engineer

OR · On-site +1

$230K/yr

... other open source languages (e.g., Python, Go, Node.js) * Staff-level engineering experience ... We are remote-first with a dedicated NYC office and reimbursement options for co-working spaces.

next page

Showing results 1-20

Remote Open Source information

See Oregon salary details

$16

$29

$39

How much do remote open source jobs pay per hour?

As of Jun 9, 2026, the average hourly pay for remote open source in Oregon is $29.26, according to ZipRecruiter salary data. Most workers in this role earn between $22.88 and $35.10 per hour, depending on experience, location, and employer.

What are some common challenges faced in remote open source roles and how can I overcome them?

Common challenges in remote open source roles include coordinating across time zones, managing asynchronous communication, and staying engaged with a globally distributed team. To overcome these, it’s important to develop strong written communication skills, regularly participate in project discussions or chat channels, and proactively seek feedback on your contributions. Leveraging project management tools, setting clear personal goals, and establishing a regular work schedule can also boost your productivity and integration with the community. By staying organized and engaged, you’ll be able to contribute effectively while building your reputation within the open source community.

What are the key skills and qualifications needed to thrive in the Remote Open Source position, and why are they important?

To thrive in a Remote Open Source role, you need strong programming skills, proficiency with version control systems (such as Git), and experience contributing to open source projects. Familiarity with open source collaboration platforms like GitHub or GitLab and, in some cases, knowledge of specific tech stacks or languages are highly valued. Excellent communication, self-motivation, and the ability to work independently across distributed teams are vital soft skills. These abilities help ensure effective collaboration, code quality, and sustained contributions to open source initiatives from a remote environment.

What is a Remote Open Source job?

A Remote Open Source job involves working on open-source projects while being geographically independent. These roles can range from software development and documentation to project management and community engagement. Employees or contributors collaborate with a global community, often using platforms like GitHub and communication tools like Slack or Discord. Many companies fund open-source work directly or hire developers to contribute to relevant projects.

What are the most commonly searched types of Open Source jobs in Oregon? The most popular types of Open Source jobs in Oregon are:
What are popular job titles related to Remote Open Source jobs in Oregon? For Remote Open Source jobs in Oregon, the most frequently searched job titles are:
What cities in Oregon are hiring for Remote Open Source jobs? Cities in Oregon with the most Remote Open Source job openings:
Staff Backend Engineer - Databases Tempo | US | Remote

Staff Backend Engineer - Databases Tempo | US | Remote

Grafana Labs

OR • Remote

Other

Posted 12 days ago


Job description

This is a remote position. We are seeking candidates in US and Canada. 

The Opportunity: 

We build Tempo, the open-source distributed tracing backend behind Grafana Cloud Traces and Grafana Enterprise Traces (GET). Tempo makes it easy to search traces, generate metrics from spans, and connect tracing data with logs, metrics, and profiles across the Grafana stack.

2026 is an inflection point for Tempo. After a major architectural upgrade and the launch of TraceQL metrics, we are shifting from foundational work to product and operational excellence, and evolving Tempo from a SaaS database into a platform that powers Grafana's next generation of observability products (App Observability, Asserts, Traces Drilldown, and AI-driven assistants).

Over the next year, you will help us:

  • Make Grafana Cloud Traces "just work" for customers by eliminating rough edges, confusing limits, and hidden failure modes.
  • Achieve operational excellence at scale as we grow from close to 50 cells today into triple digits this year, with autoscaling, parameterized rollouts, and aggressive toil reduction.
  • Evolve Tempo into a platform enabler: higher-density APIs, trace aggregation, TraceQL metrics math, and machine/LLM-friendly interfaces that downstream products and agents can build on.
  • Push performance further: faster query latency at hundreds of MB/s ingestion and performant 30-day query ranges to match competitors.
  • Prepare Tempo for an agent-driven world: larger, burstier, higher-cardinality workloads, and new categories of AI-powered workflows, such as assistant-driven triage and "why is this slow?"- style investigations.
What You'll Be Doing: 

As a Staff Engineer on Tempo, you will set technical direction on the hardest problems in our roadmap and raise the bar across the team.

  • Lead multi-quarter technical initiatives from problem framing through rollout, e.g., trace aggregation APIs, Limitless Tempo, autoscaling cells and customer limits, or query engine improvements.
  • Own the architecture of core Tempo components: ingestion, storage, query, and metrics generation. Drive design reviews, make sharp trade-offs on performance, cost, and complexity, and document the "why" for the team.
  • Design APIs for humans and agents. Shape the next generation of Tempo's interfaces (structured, deterministic, discoverable) so that Act 3 products, LLM-driven assistants, and external integrators can build on Tempo reliably.
  • Drive operational excellence. Own outcomes against concrete SLOs (P99 write latency, incident recurrence, TCO per ingested GB) and push the team toward Zero Ops through automation, parameterized rollouts, and actionable alerts.
  • Partner with Product and sibling teams. Work closely with PMs and with App Observability, Asserts, Drilldown, and Grafana Assistant teams to understand how Tempo gets consumed and to ship what unblocks them.
  • Mentor engineers. Raise the engineering bar through code review, design feedback, pairing on hard problems, and writing that leaves the team smarter than you found it.
  • Participate in on-call for the services you help build, and be a force multiplier in incident response and post-incident learning.
  • Contribute to open source. Tempo is OSS. You will engage the community, review external contributions, and help steer the project in the open.

We invest heavily in developer productivity. You can use modern AI coding assistants as part of your daily workflow (your choice of tools, within security guidelines), backed by a company-funded usage budget so you can iterate quickly without unnecessary friction.

We encourage pragmatic AI-assisted development: faster prototyping, test generation, refactors, documentation, and incident follow-ups-always paired with strong code review and quality standards.

You'll also have access to frontier models (e.g., GPT-Codex 5/3, Claude Opus 4.6, Gemini 3 Pro).

Example problems you could work on

These are the kinds of projects landing in 2026. Any one of them is a Staff-sized problem:

  • Trace aggregation and higher-density APIs: extend TraceQL metrics, design LLM-friendly response types, and make Tempo a first-class data source for Grafana's AI assistant.
  • Autoscaling end to end: customer limits and Tempo cells, with hysteresis, predictive scaling for spikes, and safe scale-down.
  • Agent-scale ingestion and query: guardrails for bursty, high-cardinality, agent-generated workloads.
  • Query performance: new data formats, smarter query pipelines, targeted optimizations for common Drilldown and Traces workflows, and 30-day query ranges.
  • Rollouts and multi-cell operations: parameterized rollouts, push-button deploys, and the tooling to grow safely into triple-digit cell counts without a proportional increase in alert noise.
  • Limits and self-service: drive customer-facing configuration and observability so escalations trend toward zero.
What Makes You a Great Fit: 
  • Technical leadership. A track record of leading complex, multi-quarter initiatives that spanned design, delivery, and operations, and made the teams around you better.
  • Deep systems experience. Substantial hands-on experience building and operating distributed data systems in production: ingestion pipelines, storage engines, query execution, or similar.
  • Strong software craftsmanship. You write clean, robust, performant software that others can maintain, and you know when to optimize vs. when to ship.
  • Strong Go, or a path to it. We write Tempo in Go. Deep experience in other systems languages (Rust, C, C++) translates well.
  • Operational mindset. You've owned production services, carried a pager, reduced toil, and treated SLOs as a product feature, not a chore.
  • Customer focus and pragmatism. You break complex problems into short feedback loops: analyze, design, deliver an MVP, learn, iterate.
  • Leadership through writing and collaboration. You lead through design docs, reviews, and shipped code, not hierarchy. You communicate clearly in a fully remote, asynchronous environment.
Bonus Points For: 
  • Experience with tracing, OpenTelemetry, or large-scale observability systems.
  • Experience designing query languages, SQL/TraceQL-like engines, or APIs intended to be consumed programmatically (by services or agents).
  • Experience with columnar storage formats (e.g., Parquet) or purpose-built on-disk formats for analytical workloads.
  • Experience operating multi-tenant, multi-cell SaaS infrastructure at scale on Kubernetes.
  • Experience building for AI/LLM consumers: structured APIs, metadata/discovery endpoints, deterministic outputs, evaluation harnesses.
  • Open-source contribution or maintainership, and comfort engaging a community in the open.
  • Experience as an on-call user of Grafana, Prometheus, Loki, or Tempo in a previous role (or on a homelab).
  • Experience in a fully remote, globally distributed team.
How we work

We are a remote-first team that meets regularly over video and does most of our work asynchronously, in writing. We value creativity, diverse perspectives, and clear communication. Tempo is relied upon by prominent global organizations to monitor critical applications and infrastructure, and we expect everyone on the team, including our Staff engineers, to contribute ideas that make it a more reliable, more useful, and more loved product.

In the United States, the compensation range for this role is $174,986 - $209,983 USD.  Actual compensation may vary based on level, experience, and skillset as assessed throughout the interview process. All of our roles include Restricted Stock Units (RSUs), giving every team member ownership in Grafana Labs' success. We believe in shared outcomes-RSUs help us stay aligned and invested as we scale globally.