1

L2 Support Engineer Jobs in California (NOW HIRING)

Support Engineer (SF)

San Francisco, CA · On-site

$150K - $180K/yr

As one of our Support Engineers, you'll be a clear owner of support during SF hours and a key ... Proactively flag risk early (backlogs building, customer frustration, L2 pressure, product bugs)

Technical Support Engineer - FortiNAC ETAC Team Position overview and Job Responsibilities ... Apply networking knowledge with a focus on L2, L3, L4, and L7. * Debug and troubleshoot networking ...

New

IT Support Engineer

Santa Clara, CA · On-site

$110K - $135K/yr

The IT Support Engineer provides support to employees experiencing technical problems and performs ... Prior experience supporting L1 and L2 requests in IT would be helpful for this position. Job ...

The IT Support Engineer provides support to employees experiencing technical problems and performs ... Prior experience supporting L1 and L2 requests in IT would be helpful for this position. Job ...

IT Support Engineer

Santa Clara, CA · On-site

$110K - $135K/yr

The IT Support Engineer provides support to employees experiencing technical problems and performs ... Prior experience supporting L1 and L2 requests in IT would be helpful for this position. Job ...

IT Support Engineer

Santa Clara, CA · On-site

$110K - $135K/yr

The IT Support Engineer provides support to employees experiencing technical problems and performs ... Prior experience supporting L1 and L2 requests in IT would be helpful for this position. Job ...

Showing results 21-40

L2 Support Engineer information

See California salary details

$16

$39

$67

How much do l2 support engineer jobs pay per hour?

As of Sep 12, 2026, the average hourly pay for l2 support engineer in California is $39.35, according to ZipRecruiter salary data. Most workers in this role earn between $29.18 and $46.01 per hour, depending on experience, location, and employer.

What is an L2 Support Engineer?

L2 Support Engineers, also known as Level 2 Support Engineers, are technical professionals who handle more complex customer issues that cannot be resolved by first-level (L1) support. They are responsible for diagnosing, troubleshooting, and resolving technical problems related to software, hardware, or network systems. L2 Support Engineers often work closely with L1 support teams to escalate and resolve incidents, and may also collaborate with development or engineering teams for deeper technical issues. Their role is critical in ensuring timely and effective solutions to customer problems, maintaining service quality, and minimizing downtime.

What are the key skills and qualifications needed to thrive as an L2 Support Engineer, and why are they important?

To thrive as an L2 Support Engineer, you need strong troubleshooting skills, in-depth knowledge of operating systems and networks, and typically a degree in computer science or a related field. Familiarity with ticketing systems (like ServiceNow or Jira), remote desktop tools, and relevant certifications such as CompTIA, ITIL, or Microsoft Certified Solutions Associate (MCSA) is highly valuable. Excellent problem-solving abilities, effective communication, and customer service orientation are essential soft skills in this role. These skills ensure timely resolution of complex technical issues and high customer satisfaction, which are critical in maintaining IT service quality and business continuity.

How does an L2 Support Engineer typically collaborate with other support tiers and technical teams?

L2 Support Engineers act as a bridge between the frontline (L1) support and more specialized (L3) technical teams. They handle complex issues escalated from L1, performing in-depth troubleshooting and root cause analysis. If an issue requires deeper expertise, L2 will document findings and pass it to the L3 or development teams, often participating in joint problem-solving sessions. This collaborative approach ensures efficient resolution of customer problems and allows L2 engineers to build strong technical and communication skills while learning from both customer interactions and advanced technical challenges.

What is the difference between L2 Support Engineer vs Network Support Technician?

AspectL2 Support EngineerNetwork Support Technician
CertificationsCompTIA Network+, Cisco CCNA, ITILCompTIA Network+, Cisco CCNA, similar certifications
Work EnvironmentCorporate IT, data centers, technical support teamsNetwork operations centers, on-site troubleshooting, client sites
ResponsibilitiesAdvanced troubleshooting, system analysis, escalation handlingNetwork setup, maintenance, basic troubleshooting
Industry UsageIT services, tech companies, enterprise environmentsTelecommunications, ISPs, enterprise networks

While both roles require networking knowledge and certifications like Cisco CCNA, the L2 Support Engineer handles more complex technical issues and system analysis, whereas the Network Support Technician focuses on network setup and basic troubleshooting. The L2 Support Engineer typically works in corporate IT environments, providing escalated support, while the Network Support Technician often works in network operations centers or on-site to maintain network infrastructure.

What are popular job titles related to L2 Support Engineer jobs in California?

For L2 Support Engineer jobs in California, the most frequently searched job titles are:

What job categories do people searching L2 Support Engineer jobs in California look for?

The top searched job categories for L2 Support Engineer jobs in California are:

Infographic showing various L2 Support Engineer job openings in California as of September 2026, with employment types broken down into 50% Full Time, and 50% Contract. Highlights an 50% In-person, and 50% Hybrid job distribution, with an average salary of $81,844 per year, or $39.3 per hour.

Support Engineer (SF)

San Francisco, CA • On-site

$150K - $180K/yr

Full-time

Re-posted 4 days ago


Key responsibilities

  • Be the primary owner of the support queue during SF hours, ensuring timely and thoughtful responses to customers.

  • Represent the voice of support by identifying what works, what doesn't, and what is missing in the product, and drive issues to resolution.

  • Collaborate with Product, Customer Success, and Engineering teams to scope, design, and improve support processes, documentation, and tooling.


Job description

Who are Plain?
Plain is redefining customer support for the next generation of B2B companies. We're building the fastest, most powerful platform to help companies move beyond reactive support and build real customer relationships.
Some of the world's most forward-thinking companies - including Cursor, Ashby, Vercel, and Granola - use Plain to unify customer interactions, collaborate faster, and supercharge their workflows with AI.
We're a small, tight-knit team with offices in San Francisco and London, and teammates across Europe. This role is based in our San Francisco office, with an expectation of 3+ days a week in person. We tend to start our work days earlier to overlap with our EU colleagues (7:30-8am), but we promise to provide the coffee/tea and morning tunes .
The role
This is not a "ticket taker" role.
As one of our Support Engineers, you'll be a clear owner of support during SF hours and a key member of a growing support function. You'll combine technical depth, strong judgment, and proactive communication to ensure customers, and the rest of the company, always feel support is under control.
You'll be joining a small, lean, and mighty CX team distributed across SF and the EU. You'll work directly with Product and Engineering, act as "customer zero" for the product we're building, and help shape how support operates at Plain as we scale.
Many of our customers are technical, so you'll regularly move between APIs, webhooks, SDKs, logs, and architecture discussions and then translate that complexity into clear, confident guidance for customers.
You'll have real ownership and immediate influence in how support and the product itself evolves. If you've ever wanted to build the support experience you wish you'd had at previous companies, this is that opportunity.
What you'll do
  • Be the primary owner of the support queue during SF hours, ensuring customers get timely, thoughtful responses, even when the answer isn't immediately clear.
  • Be "customer zero" for the product: Represent the voice of real support teams. What works, what doesn't, and what's missing?
  • Drive issues end-to-end: investigate, debug, coordinate with engineering, and follow through until resolution.
  • Own clean, visible handover between EU and US timezones so nothing drops on the floor.
  • Proactively flag risk early (backlogs building, customer frustration, L2 pressure, product bugs).
  • Help define and evolve how we do support: ownership models, handover norms, escalation standards, documentation, and tooling.
  • Improve our Help Center and self-serve experience to reduce repeat questions and scale quality.
  • Partner closely with Product, Customer Success, and Engineering as a sounding board when scoping and designing features.
This is a great fit if you...
  • Have experience as a Support Engineer in an early-stage or scaling B2B SaaS company.
  • Are technically strong: you can read logs, write SQL, understand APIs, webhooks, and how systems work under the hood.
  • Take initiative by default - you don't wait to be told what to own. You ask questions, you're curious, and you're constantly looking for opportunities to optimize your own work.
  • Communicate clearly and proactively, especially when things are messy or high-pressure.
  • Have strong opinions about support products and practices, and enjoy improving them.
  • Are commercially minded and understand customer context (Tier, lifecycle stage, sentiment, impact).
  • Thrive in ambiguity and love to solve problems - the power of Plain is the ability to extend it. You think creatively and love finding different ways to solve a customer's use case.
This won't be the right role if you...
  • Prefer to spend most of your day coding rather than working directly with customers.
  • Need well-defined processes before you can operate confidently.
  • Are uncomfortable making judgment calls and owning outcomes.
  • Are looking for a people-management role right now.
  • Expect the pace, perks, or structure of a large, established company.
  • Aren't interested in working in person or up for early mornings - this role is based in SF, and we work together in the office at least 3 days a week. We tend to start earlier in the day (7:30/8am or so).