ZipRecruiter

Log In

2

Remote Customer Support Engineer Jobs in Oregon (NOW HIRING)

Transmit Security

Senior Technical Support Engineer

OR · On-site +1

$120K - $160K/yr

We're seeking a dedicated and customer-focused Senior Technical Support Engineer to provide ... Flexible Work Environment: Remote work options available for North American candidates.

NICE

Sr AI-Driven Enterprise Support Engineer

OR · On-site +1

Seattle or Hybrid Preferred (Remote Considered) The Future of Enterprise Support Starts Here What ... At NICE, we're building the next generation of enterprise customer support-where AI handles routine ...

Fujifilm

Tech Support Engineer, MI - I

Position Overview The Technical Support Engineer, MI provides remote technical support for HCUS customers. This engineer must be comfortable making critical decisions while working on complex issues.

Fujifilm

Tech Support Engineer, MI - I

Position Overview The Technical Support Engineer, MI provides remote technical support for HCUS customers. This engineer must be comfortable making critical decisions while working on complex issues.

next page

Showing results 1-20

All JobsCustomer Support Engineer JobsRemote Customer Support Engineer JobsRemote Customer Support Engineer Jobs in Oregon

Remote Customer Support Engineer information

See Oregon salary details

$41.2K

$83.1K

$114.7K

How much do remote customer support engineer jobs pay per year?

As of Jul 28, 2026, the average yearly pay for remote customer support engineer in Oregon is $83,070.00, according to ZipRecruiter salary data. Most workers in this role earn between $74,000.00 and $95,200.00 per year, depending on experience, location, and employer.

How does a Remote Customer Support Engineer typically collaborate with other technical teams while working off-site?

As a Remote Customer Support Engineer, collaboration with other technical teams, such as development and product engineering, is often facilitated through digital communication tools like Slack, email, and video conferencing. You’ll regularly participate in virtual meetings to discuss complex customer issues, share feedback, and escalate bugs or feature requests. Building strong relationships and maintaining clear, proactive communication is key to ensuring customer issues are resolved efficiently. Many companies also utilize ticketing systems and shared documentation platforms to streamline workflows and keep all team members aligned.

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

To thrive as a Remote Customer Support Engineer, you need a solid understanding of technical troubleshooting, product knowledge, and a relevant degree or experience in IT or engineering. Familiarity with ticketing systems like Zendesk, remote desktop tools, and CRM platforms is typically required, and certifications such as CompTIA A+ or similar can be beneficial. Outstanding communication, patience, and problem-solving abilities help build trust with clients and efficiently resolve issues. These skills ensure timely, effective support and high customer satisfaction in a remote work environment.

What is a Remote Customer Support Engineer?

A Remote Customer Support Engineer is a technical professional who assists customers in troubleshooting, diagnosing, and resolving issues with a company's products or services, all while working from a remote location. They typically provide support via email, chat, or phone, and may use remote desktop tools to access customers' systems. Their role combines technical expertise with strong communication and problem-solving skills to ensure customer satisfaction. Remote Customer Support Engineers often collaborate with other technical teams to escalate complex problems and help improve products based on customer feedback.

What is the difference between Remote Customer Support Engineer vs Remote Technical Support Specialist?

AspectRemote Customer Support EngineerRemote Technical Support Specialist
CredentialsTechnical certifications, customer service skillsTechnical certifications, troubleshooting skills
Work EnvironmentCustomer service platforms, remote communication toolsHelpdesk software, remote troubleshooting tools
Employer & IndustryTech companies, SaaS providersIT service providers, hardware/software vendors
Search & Comparison IntentUnderstanding roles, job requirementsJob differences, skills needed

The Remote Customer Support Engineer and Remote Technical Support Specialist roles share similar technical skills and work environments, often within tech or SaaS companies. However, the Support Engineer typically focuses more on customer relationship management and proactive support, while the Technical Support Specialist emphasizes troubleshooting and resolving technical issues. Both roles require technical certifications and excellent communication skills, but their primary focus and daily tasks differ slightly.

What are popular job titles related to Remote Customer Support Engineer jobs in Oregon? For Remote Customer Support Engineer jobs in Oregon, the most frequently searched job titles are:
What job categories do people searching Remote Customer Support Engineer jobs in Oregon look for? The top searched job categories for Remote Customer Support Engineer jobs in Oregon are:
What cities in Oregon are hiring for Remote Customer Support Engineer jobs? Cities in Oregon with the most Remote Customer Support Engineer job openings:
Remote Customer Support Engineer jobs near you
Infographic showing various Remote Customer Support Engineer job openings in Oregon as of July 2026, with employment types broken down into 83% Full Time, 15% Part Time, and 2% Contract. Highlights an 94% Physical, 1% Hybrid, and 5% Remote job distribution, with an average salary of $83,070 per year, or $39.9 per hour.
Senior Support Engineer

Senior Support Engineer

Obsidian Security

OR • On-site, Remote

Other

Posted 7 days ago

Job description

Senior Support Engineer

Team: Global Services & Delivery Location: [Remote / Hybrid - specify] Reports to: Head of Customer Support

About the role

Obsidian Security protects organizations against threats across their SaaS and identity environments. This role sits at the technical center of how we deliver support. It has two mandates. First, you own our hardest problems: complex, high-severity, and escalated tickets that require deep technical diagnosis. Second, you help build the systems that will let us scale support through technology rather than headcount, partnering directly with the Head of Customer Support to design and operationalize our agentic support capability.

This is a hands-on individual contributor role for someone who is equally comfortable resolving the toughest customer issue in the queue and turning that resolution into automation that prevents the next one.

What you'll do
  • Own complex, high-severity, and escalated tickets end to end, acting as the top technical escalation point before engineering.
  • Diagnose deep technical issues across APIs, identity and authentication, integrations, telemetry, and product data flows.
  • Partner with the Head of Customer Support to design, build, and continuously tune agentic support systems, including automated triage, resolution, and knowledge retrieval.
  • Convert your own resolution work into reusable automation, playbooks, and knowledge that agentic systems can execute without human involvement.
  • Identify where automation and agentic resolution fail, then close those gaps to raise deflection and automated resolution quality.
  • Interface with Product and Engineering on root cause analysis, bug escalation, and permanent product fixes.
  • Set the technical quality bar for the support function and mentor other engineers on it.
What we're looking for
  • A strong hands-on technical support or support engineering background for a technical B2B SaaS product. Cybersecurity, identity, or SaaS security context is strongly preferred.
  • Depth across APIs, authentication and identity, logs and telemetry, integrations, and systematic debugging.
  • Demonstrated experience building or tuning automation or agentic and LLM-based support tooling, or clear aptitude and appetite for doing so.
  • The ability to translate messy, one-off escalations into repeatable, automatable solutions.
  • Comfort operating with ambiguity in a function that is being actively rebuilt around technology.
Nice to have
  • Scripting or coding ability, for example Python, and comfort debugging at the API level.
  • Experience with LLM and agent frameworks, retrieval-augmented generation, or workflow automation.
  • Familiarity with identity provider and SaaS administrative APIs, such as Microsoft Graph and Entra, or comparable platforms relevant to SaaS security.

Apply