2

Remote Data Platform Engineer Jobs in Portland, OR

Backend Platform Engineer

Portland, OR · On-site +1

$80K - $100K/yr

... USA (Remote-West Coast Only) • Engineering PLEASE NOTE : Applicants should be located in the ... We're building the integration backbone that connects enterprise data systems, moves events at ...

Develop and support cloud-based data pipelines, platform components, and environment setup ... remote client service delivery. Recruiting for this role ends on 06/30/2026. Work you'll do As a ...

Remote work may require approval and is most likely to be considered only for exceptionally aligned ... engineering, analytics, and delivery teams. * Ensure the platform supports enterprise analytics ...

Senior Software Engineer - Database

Vancouver, WA · On-site +1

$111K - $150.80K/yr

... data platform company for the AI era. We are building the enterprise software infrastructure to capture, catalog, refine, enrich, and protect massive datasets and make them available for real-time ...

The practice helps clients modernize technology and data platforms and apply engineering to mission ... remote client service delivery. Recruiting for this role ends on 06/30/2026. Work you'll do As a ...

Our AI & Data practice designs, develops, and operates data and AI platforms, products, insights ... remote client service delivery. Recruiting for this role ends on 06/30/2026. Work you'll do As a ...

Senior Software Engineer

Vancouver, WA · On-site +1

$128.30K - $169.10K/yr

... distributed data platforms. * Note: Experience limited to writing SQL queries or database ... We are seeking engineers with experience in the core engineering of a database system.

Integrate with health data platforms such as Google Health Connect and wearable APIs * Collaborate ... Contribute to architecture decisions and engineering standards What We're Looking For * 3+ years of ...

AI and Data Science Engineer III

Portland, OR · On-site +1

$121.40K - $145.80K/yr

You will work with an AI Data Engineer (data ingestion, curation, governance, platform foundations) and a Lead AI Solutions Architect (end-to-end solution architecture, integration patterns, non ...

Ensure platform stability, performance, data accuracy, privacy, and security configurations ... Remote Actions * Dashboards & Investigations * Campaigns & Alerts * Application Experience ...

next page

Showing results 1-20

Remote Data Platform Engineer information

See Portland, OR salary details

$47.2K

$137.6K

$188.2K

How much do remote data platform engineer jobs pay per year?

As of May 31, 2026, the average yearly pay for remote data platform engineer in Portland, OR is $137,565.00, according to ZipRecruiter salary data. Most workers in this role earn between $121,400.00 and $145,800.00 per year, depending on experience, location, and employer.

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

To thrive as a Remote Data Platform Engineer, you need expertise in data engineering, database management, and cloud platforms, usually supported by a degree in computer science or a related field. Familiarity with tools such as SQL, Python, Spark, AWS, Azure, and certifications like AWS Certified Data Analytics are highly valued. Strong problem-solving, communication, and self-motivation skills help you excel in remote, collaborative environments. These skills and qualities ensure the efficient design, operation, and scaling of robust data platforms that drive business insights and operations.

What are the typical collaboration methods for a Remote Data Platform Engineer working with cross-functional teams?

As a Remote Data Platform Engineer, you will frequently collaborate with data scientists, analysts, and software engineers through virtual meetings, project management tools, and shared documentation platforms. Effective communication is essential, as much of the teamwork happens asynchronously using tools like Slack, Jira, and Confluence. You may participate in regular stand-ups, sprint planning, and code reviews to ensure alignment across the team. Building strong relationships remotely often involves proactive updates and clear documentation to keep all stakeholders informed and projects moving smoothly.

What is a Remote Data Platform Engineer?

A Remote Data Platform Engineer is a professional who designs, builds, and manages large-scale data infrastructure and platforms, while working remotely. They are responsible for ensuring data is efficiently collected, stored, processed, and made accessible for analysis, often using cloud technologies and big data tools. These engineers collaborate with data scientists, analysts, and other engineers to maintain data pipelines and optimize system performance. Their work enables organizations to leverage data for business insights, all while enjoying the flexibility of remote work.

What is the difference between Remote Data Platform Engineer vs Data Engineer?

AspectRemote Data Platform EngineerData Engineer
CredentialsBachelor's in CS, Data Science, or related; experience with cloud platformsBachelor's in CS, Data Science, or related; experience with databases and ETL tools
Work EnvironmentRemote or hybrid, collaborating with data teams and cloud providersOn-site or remote, focusing on data pipelines and infrastructure
Industry UsageTech, finance, healthcare, and other data-driven sectorsSame industries, often overlapping roles
Search & Comparison IntentHigh overlap, often searched together due to similar skills

The Remote Data Platform Engineer focuses on building and maintaining cloud-based data platforms, ensuring scalability and performance. Data Engineers develop and manage data pipelines, databases, and ETL processes. While roles overlap in skills and industries, the Platform Engineer emphasizes cloud infrastructure, whereas Data Engineers concentrate on data processing and storage.

What are the most commonly searched types of Data Platform Engineer jobs in Portland, OR? The most popular types of Data Platform Engineer jobs in Portland, OR are:
What are popular job titles related to Remote Data Platform Engineer jobs in Portland, OR? For Remote Data Platform Engineer jobs in Portland, OR, the most frequently searched job titles are:
What job categories do people searching Remote Data Platform Engineer jobs in Portland, OR look for? The top searched job categories for Remote Data Platform Engineer jobs in Portland, OR are:
Infographic showing various Remote Data Platform Engineer job openings in Portland, OR as of May 2026, with employment types broken down into 1% Internship, 73% Full Time, 15% Part Time, 10% Contract, and 1% Nights. Highlights an 92% Physical, 3% Hybrid, and 5% Remote job distribution, with an average salary of $137,565 per year, or $66.1 per hour.
Backend Platform Engineer

Backend Platform Engineer

ClearlyRated

Portland, OR • On-site, Remote

$80K - $100K/yr

Full-time

Posted 3 days ago


Job description

Backend Platform Engineer
Application Deadline: 2 June 2026
Department: Engineering
Employment Type: Full Time
Location: Portland, Oregon
Compensation: $80,000 - $100,000 / year
Description
Backend Platform Engineer
Java • Spring Boot • Distributed Systems
ClearlyRated • USA (Remote-West Coast Only) • EngineeringPLEASE NOTE :
Applicants should be located in the Pacific Time Zone or be willing to relocate to this time zone at their own expense.
PLEASE NOTE :
Applicants must be authorized to work in the United States without requiring visa sponsorship. We are unable to support Student Visa as well.

We're building the integration backbone that connects enterprise data systems, moves events at scale, and powers survey automation for some of the world's largest professional services firms. If you love distributed systems, API design, and clean backend engineering - read on.
About ClearlyRated
ClearlyRated is a B2B SaaS platform that helps professional services firms - from global engineering consultancies to staffing agencies - measure, understand, and act on client satisfaction data. Our NPS-driven platform processes millions of survey interactions, powers real-time relationship health scoring, and is in the middle of a significant platform evolution: new data integration architecture, event-driven survey automation, and a growing AI/ML capability stack built on Google Cloud.
We're a small, focused engineering team building systems that operate at enterprise scale. That means the problems are real, the stakes are high, and every engineer on the team does work that matters.
Key Responsibilities
What You'll Build
Real systems that enterprise clients depend on. Not greenfield experiments, but a world class brand new platform with production code that has to be correct, observable, and resilient:
- Integration layer that ingests structured data from enterprise sources (Snowflake, BigQuery, SQL databases) and routes it through our platform
- A Snowflake-to-BigQuery bridge over ODBC: custom infrastructure work that will serve as the pattern for all future enterprise integrations
- Webhook-triggered survey automation engine. Business events in the client's system translate into survey sends through a reliable, auditable event pipeline
- REST APIs consumed by our frontend, enterprise integrations, and third-party clients - you'll design contracts that have to last
- Event-driven microservices on GCP Pub/Sub and Kafka - async processing, backpressure handling, dead-letter queues, the full picture
- Security and SSO integration for enterprise clients with complex credential and access models
- Permission and access control systems that reflect matrix organizational hierarchies - the authorization layer is genuinely interesting here
Skills, Knowledge and Expertise
Our Stack
|Java 18+ Spring Boot MySQL / PostgreSQL Kafka GCP Pub/Sub BigQuery Kubernetes REST APIs CI/CD .NET / C#
What We're Looking For
- Java you understand at the JVM level. Concurrency, memory model, garbage collection, exception hierarchy - you can reason about what the runtime is doing, not just what your code says.
- Spring Boot / Spring ecosystem depth. Or deep understanding of dependency injection and IoC from another framework - we care that you understand the pattern, not just the annotations.
- SQL and data modelling confidence. You can write a query with joins, aggregations, and window functions. You think about indexes. You understand what an N+1 problem looks like in production.
- API design instincts. You know what makes an API contract good and what makes it a maintenance nightmare. You've thought about versioning, error semantics, and idempotency.
- Systems thinking under failure. You consider retries, timeouts, idempotency, and consistency before you consider happy paths.
- You've built something that handles real load. Even in a personal or academic context - something where correctness and reliability were actual constraints, not just nice-to-haves.
Bonus Points
- .NET / C# experience is a genuine plus. We maintain services in both ecosystems. Engineers who can move across the Java-.NET boundary are valuable.
- GCP experience: Pub/Sub, Dataflow, BigQuery, Vertex AI
- Kafka or other message queue experience: consumer groups, offset management, partition strategy
- Kubernetes and container orchestration
- Event sourcing or CQRS patterns
- Experience with observability tooling - distributed tracing, structured logging, alerting on the things that matter
Benefits
How We Hire
We hire on ability, not tenure. We don't care whether your experience comes from a top university, a bootcamp, an open-source project, or a side hustle you built at 2am. What we care about is whether you can think clearly, build well, and learn fast.
Our interview process is deliberately hard. If you make it through, you'll know you earned it - and so will we. We test fundamentals, systems thinking, and the ability to reason through problems you haven't seen before. We don't ask you to recite design patterns. We ask you to think.
| | Our backend interview tests: Java fundamentals and JVM reasoning, systems design, API design, SQL, and your ability to think through distributed system failure modes. We give you real-world scenarios, not toy problems. Expect to discuss trade-offs, not just correct answers. .NET/C# candidates will be evaluated on transferable depth, not language syntax.