Anthropic9 days ago
Руководитель, Корпоративная сетевая инженерия
Salary not specified
MARKET
13,534 ₽median for this role
Tech Lead / Team Lead · 166 jobs with disclosed pay
5,250half of the offers: 9,771–18,1061.2 млн
The employer didn't disclose pay — compare with the market yourself.
San Francisco
Responsibilities
- 01Lead and grow the Corporate Network Engineering team — hiring, development, performance, planning, and prioritization
- 02Set technical direction with the team and own the final call on architecture standards across edge, campus switching, wireless, segmentation, out-of-band management, and telemetry; review designs and risky changes, and step in on the hard problems
- 03Own reliability and operations: monitoring people act on, incident response and post-incident reviews that produce changes, an on-call and escalation model a small team can sustain, change safety, and lifecycle currency
- 04Move the fleet toward network-as-code: templated configuration with change control, staged rollouts, drift detection, and automation that removes operational toil
- 05Partner with Security Engineering and Detection & Response on network authentication, segmentation, and the network as a detection source
- 06Deliver networks for new offices and research facilities and upgrade existing sites through live migrations — with Buildouts, AV, Physical Security, Workplace, Real Estate, and our logistics partners — while keeping interruptions to employees minimal
- 07Own vendor, carrier, and integrator relationships and the network hardware budget: evaluations, contracts, lead times, and multi-year refresh
Requirements
- 01Have 10+ years designing, building, and operating enterprise campus and edge networks, including at least one environment with dozens of sites across regions
- 02Have 5+ years leading engineers, including at least 3 years as a people manager
- 03Lead through technical judgment: whether or not you've been hands-on-keyboard lately, you can go from architecture to protocol behavior to failure modes with your engineers, and your reviews make their designs better
- 04Default to the secure design, then do the creative work to make it painless for the people using it — and can walk an executive or an engineer through the trade-off and make a recommendation
- 05Have run the operational side, not just designed it: out-of-band access, monitoring people act on, an on-call model a small team can sustain, and change safety
- 06Are pragmatic about what to build, buy, or automate, have run vendor evaluations with real money at stake, and chase problems across organizational boundaries to the actual root cause
- 07Communicate clearly with engineers, executives, contractors, and landlords, and can bring a room of senior engineers with strong opinions to a decision they'll commit to
- 08Want real technical ownership with a small team — including if you've led a larger organization before — and care about building infrastructure for an organization trying to get AI right
- 09Have led corporate networking at a company that added offices faster than it added network engineers
- 10Have implemented certificate-based network authentication (802.1X/EAP-TLS or equivalent) and identity- or device-based segmentation at scale
- 11Have shipped network configuration as code and built telemetry pipelines that security and support teams actually use
- 12Have designed dense wireless for large event spaces and high-occupancy floors
- 13Have been through multiple office builds with real estate and construction teams — including networks that physical security systems depend on — and know what to ask for before the walls close
- 14Have managed integrators, MSPs, or smart-hands providers as an extension of a small team while keeping design authority in-house