وظائف مطورين بايثون - الجبيل السعودية
١ وظائف شاغرة
<section><p class="heading jdMain">Job Description</p><p class="heading">Roles & Responsibilities</p><div class="paragraph"><p>Network Engineer L3 — Roles & Responsibilities</p><p>1. Network Design & Architecture</p><ul><li><p>Own HLD/LLD for enterprise LAN/WAN, DC, and cloud connectivity</p></li><li><p>Design redundant, scalable topologies — spine-leaf, hub-spoke, SD-WAN</p></li><li><p>Define IP addressing, VLAN structure, routing domains, and segmentation strategy</p></li></ul><p>2. Escalation & Incident Ownership</p><ul><li><p>Final escalation point for L1/L2 — you close it, not pass it</p></li><li><p>Lead P1/P2 bridge calls, drive RCA, own post-mortem</p></li><li><p>Coordinate with NOC, security, and vendors during major incidents</p></li></ul><p>3. Routing & Switching (Advanced)</p><ul><li><p>Manage and tune BGP policies, OSPF areas, MPLS/VRF, redistribution</p></li><li><p>Handle complex STP issues, VPC/MLAG, LACP, and trunk failures</p></li><li><p>Own inter-DC and ISP peering configurations</p></li></ul><p>4. Security & Compliance</p><ul><li><p>Enforce segmentation — VRF, VLAN isolation, firewall zones</p></li><li><p>Review and approve ACLs, firewall rules, NAC policies</p></li><li><p>Support audits — PCI, ISO 27001, NIST alignment on network layer</p></li></ul><p>5. Cloud & Hybrid Networking</p><ul><li><p>Own AWS/Azure network integration — VPN Gateway, ExpressRoute, Transit Gateway</p></li><li><p>Design and troubleshoot hybrid connectivity — on-prem to cloud routing</p></li><li><p>Collaborate with cloud architects on network policy</p></li></ul><p>6. Automation & Tooling</p><ul><li><p>Build and maintain automation — Python, Ansible, Netmiko</p></li><li><p>Automate config backups, compliance checks, provisioning workflows</p></li><li><p>Integrate with ITSM/IPAM/NMS platforms</p></li></ul><p>7. Monitoring & Performance</p><ul><li><p>Own network observability — NetFlow, SNMP, syslog pipelines</p></li><li><p>Proactive capacity planning — identify bottlenecks before they become incidents</p></li><li><p>Define and track SLAs, latency, packet loss thresholds</p></li></ul><p>8. Documentation & Change Management</p><ul><li><p>Maintain accurate network diagrams, IP plans, and runbooks</p></li><li><p>Author and review RFCs/change records — no undocumented changes</p></li><li><p>Keep post-mortems and lessons-learned documented</p></li></ul><p>9. Vendor & Stakeholder Management</p><ul><li><p>Own TAC cases — Cisco, Palo Alto, Juniper, Fortinet</p></li><li><p>Evaluate new hardware/software — PoC, testing, recommendation</p></li><li><p>Present technical decisions to management and non-technical stakeholders</p></li></ul><p>10. Mentorship & Leadership</p><ul><li><p>Technically guide L3 engineers — knowledge transfer, not just answers</p></li><li><p>Conduct design and config peer reviews</p></li><li><p>Set team standards — naming conventions, hardening baselines, change process</p></li></ul></div></section><section><p class="heading">Desired Candidate Profile</p><p class="paragraph"></p><p>Desired Candidate Profile — Network Engineer L3</p><p>Technical Depth</p><ul><li><p>Can design <strong>end-to-end</strong> — not just configure what's handed to them</p></li><li><p>Understands <strong>why</strong> a protocol behaves a certain way, not just how to configure it</p></li><li><p>Reads packet captures, interprets routing tables, and diagnoses without a runbook</p></li><li><p>Has broken things in production and <strong>fixed them under pressure</strong></p></li></ul><p>Core Technical Profile</p><p>DomainWhat We ExpectRoutingBGP multihoming, path manipulation, OSPF tuning, MPLS L3VPNSwitchingVPC/MLAG, MSTP, Q-in-Q, LACP negotiation issuesFirewallsZone-based policy, NAT hairpin, asymmetric routing issuesSD-WANPolicy-based routing, app-aware steering, overlay/underlay separationCloudExpressRoute, Direct Connect, Transit Gateway, route propagationAutomationScript-first mindset — Python, Ansible, REST APIsMonitoringCan build a dashboard, not just read one</p><p>Experience Profile</p><ul><li><p><strong>5–8 years</strong> hands-on — enterprise, SP, or large MSP environment</p></li><li><p>Has owned a <strong>network migration or redesign</strong> project end to end</p></li><li><p>Has managed <strong>multi-vendor environments</strong> — not just one OEM</p></li><li><p>Has worked <strong>on-call</strong> and handled real P1 incidents alone</p></li></ul><p>Certifications</p><p>LevelCertRequiredCCNP Enterprise / JNCIP / NSE4+Strong PlusCCIE / JNCIE / NSE7BonusAWS/Azure Networking Specialty</p><p>Problem-Solving Style</p><ul><li><p><strong>Structured</strong> — isolates layer by layer, doesn't guess randomly</p></li><li><p><strong>Calm under pressure</strong> — incident bridge calls don't rattle them</p></li><li><p><strong>Data-driven</strong> — uses logs, flows, and captures — not assumptions</p></li><li><p><strong>Owns the problem</strong> — doesn't deflect to another team without evidence</p></li></ul><p>Communication & Soft Skills</p><ul><li><p>Can explain a routing loop to a CISO without using BGP terminology</p></li><li><p>Writes clean, clear documentation — diagrams match reality</p></li><li><p>Pushes back on bad designs — respectfully, with data</p></li><li><p>Comfortable presenting to management and defending technical decisions</p></li></ul><p>Mindset</p><ul><li><p><strong>Security-first</strong> — thinks about attack surface when designing, not after</p></li><li><p><strong>Automation bias</strong> — if done more than twice, it should be scripted</p></li><li><p><strong>Proactive</strong> — monitors trends, flags risks before they become incidents</p></li><li><p><strong>Continuous learner</strong> — tracks CVEs, vendor EOL, protocol RFCs</p></li></ul><p>Red Flags (What disqualifies a candidate)</p><ul><li><p>Can configure but can't explain <strong>why</strong></p></li><li><p>Has never touched a firewall or security policy</p></li><li><p>Relies entirely on GUI — no CLI fluency</p></li><li><p>No experience with change management or documentation discipline</p></li><li><p>Falls apart when the runbook doesn't apply</p></li></ul><p></p></section>