whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems. About the role Corporate Network Engineering designs,…
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 9,133 · sorted by freshness
improve them until they work at scale. We are roboticists, engineers, operators, and builders. We believe the next great technology... ...do Own reliability and root-cause analysis Lead complex network investigations acr…
most difficult, urgent, and interesting challenge in AI security engineering this decade (for humans, at least): designing and building the... ...years. What you'd work on Designing and operating the network fabric of th…
the future worth building is human, and we're hiring people who want to build it. About the Role We're looking for a network engineer to own the lowest layers of the network stack that our large-scale training and infere…
software agents. We're the makers of Devin, the first AI software engineer. Our team is extremely talent-dense. Among our founding team... ..., apply to join us. About the role We’re looking for a Network Engineer to own…
access to technical problems spanning frontier models, production infrastructure, and emerging hardware. About the role As a Network Engineer, you will build the network infrastructure connecting Gimlet’s compute, storag…
Technician Operations team is the live backbone of Meter’s deployment engine, ensuring that we deliver critical infrastructure on time, to... ..., and with zero friction for our partners and customers. A Network is most…
Network Engineer Location: San Francisco, CA / Remote (US) · Full-Time · Travel up to 25% About Andromeda Andromeda is a market and infrastructure platform to buy, sell, and operate compute. We believe demand for compute…
Do Help to build and scale Lambda's high performance cloud network Work on deploying and configuring networking Hardware for new... ...be part of day2 operations and on-call rotation for Network Engineering team You Have…
About the Team OpenAI’s Network Engineering team within IT and Security advances the mission of deploying artificial general intelligence (AGI) for the benefit of all by delivering secure, scalable, and resilient network…
About Nscale Nscale is the GPU cloud engineered for AI. We provide cost-effective, high-performance infrastructure for AI start-ups and... ...that powers the future. About the Role (Job Purpose) The Network Engineering T…
in full. How you'll make impact Airwallex’s corporate network needs to remain secure, reliable and scalable as our global... ...completing after-action reviews. Partner with CorpSec, ProdSec, Engineering, Product, IT Eng…
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.