Manager, Site Reliability Engineer (Hybrid in South San Francisco)About the RoleWe are seeking an experienced and hands-on Site Reliability... ...across cloud infrastructure, observability, automation, networking, and pl…
Network Engineer jobs in San Francisco, CA
Network engineers design, build, and maintain the networks that connect an organization — routing, switching, wireless, firewalls, and increasingly cloud and software-defined networking.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open network engineer roles
12 shown of 1,379 · sorted by freshness
recovery, and operation across multiple cloud environments.TDP SQL is Atlassian’s managed relational database platform. It gives engineering teams a supported way to build applications on relational databases without hav…
Our MissionAt Palo Alto Networks, we’re united by a shared mission—to protect our digital way of life. We thrive at the intersection... ..., and automated onboarding services.Senior Principal Software Engineers are:Techn…
efficiency ambitions. Imagine working with world-class supply network capabilities like Smart Factory, Strategy & Innovation, Supply... ...and drive end-to-end transformation of configure-to-order and engineer- to-order…
simply — helping mission-driven organizations achieve more through technology.Required ExperienceB.S. in Computer Science, Software Engineering, MIS, or related field3+ years of professional work experience, preferably i…
Your work days are brighter here.We’re obsessed with making hard work pay off, for our people, our customers, and the world around us. As a Fortune 500 company and a leading AI platform for managing people, money, and ag…
Position Summary Salesforce Life Sciences Cloud Senior ConsultantDeloitte's Sales & Service practice partners with the world's leading life sciences companies to reimagine how their commercial, medical, and field organiz…
ensuring the integrity of access to data.QualificationsRequired:BA/BS Degree in Computer Science, Cyber Security, Information Security, Engineering, Information Technology, Finance, Business, or relevant fields.Overall m…
company provides fixed wireless and fiber solutions for growing connectivity needs. The company is looking for a Senior Wireless Network Engineer to support and improve FTTH and fixed wireless network operations in a gro…
expanding into the United States, with significant investment in high-performance networking and AI-ready data center architecture. The company is looking for a Senior Network Engineer to design, deploy, and support ultr…
Ready to architect the high-speed networks powering the AI era? Join a trailblazing leader in GPU-accelerated computing, designing and operating the network fabric that supports some of the most demanding computational w…
Network Engineer – Distributed & Space Systems Full Time | Bay Area Build the Internet… in Space This is not traditional networking. You’ll be working on a system where satellites behave like a distributed cloud , not is…
What network engineers earn in San Francisco
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $39–$55 | $81k–$115k |
| Mid level | $55–$75 | $115k–$157k |
| Senior | $73–$98 | $151k–$203k |
Adjusted for the San Francisco market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Users at one site report intermittent connectivity. How do you troubleshoot?
Work the layers: physical, then switching, routing, and upstream — using monitoring data to narrow scope. Intermittent issues test patience and method, so show both.
Explain what happens at each OSI layer when a user loads a website.
Keep it crisp and accurate through the layers; this is a fluency check. Tie each layer to a real troubleshooting tool you would use there.
How would you design the network for a new office?
Ask about size and needs first, then cover segmentation, redundancy, wireless coverage, and internet failover. Mentioning documentation and future growth rounds it out.
When would you use BGP versus OSPF?
External versus internal routing in essence — explain it through where each lives in a real network you have run rather than textbook definitions alone.
Tell me about a change you made that caused an outage, and what you learned.
Everyone in networking has one. Show the discipline that came out of it: change windows, peer review, rollback configs staged in advance.
How are you using automation in network operations?
Config templating, compliance checks, or Python/Ansible scripts — even small examples count. The field is moving this way and interviewers check for the trajectory.
Resume tips that move the needle
For network engineers specifically — generic advice costs you here
State network scale: sites, users, devices, and bandwidth managed — it is the first credibility check.
List certifications prominently (CCNA, CCNP) since networking still hires heavily on them.
Name specific platforms (Cisco IOS/NX-OS, Meraki, Palo Alto, Fortinet) rather than 'networking equipment'.
Quantify reliability wins: uptime improved, outage minutes reduced, failover designs that worked when tested.
Include automation and cloud networking experience — it distinguishes you from config-only candidates.
Where this role goes
Typical progression
Applying for network engineer jobs in San Francisco?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.