# CV Positioning & Marketability Audit — Sarah Jenkins ## Executive assessment **Overall view:** This is a **strong, highly targeted senior networking CV**, with credible evidence for Senior Network Engineer and Network Architect roles. The combination of **10+ years' experience, principal-level responsibility, SD-WAN architecture, data-centre migration, BGP optimisation and recognised networking certifications** gives the candidate a strong professional foundation. The biggest issue is not lack of capability. It is that the CV is **too compressed for someone claiming Principal Network Engineer / Strategic Network Architect level**. It gives several excellent headline achievements but provides relatively little evidence about **scope, leadership, architectural decision-making, technical breadth and business impact**. --- # STEP 1 — Recruiter First Impression ### Apparent professional identity Senior/Principal Network Engineer with an architectural focus, specialising in enterprise/global networking and SD-WAN. ### Apparent career level **Senior to Principal level.** The current title is Principal Network Engineer, while the opening describes the candidate as a Strategic Network Architect. ### Strongest selling point The strongest feature is the combination of **senior-level experience + architecture + measurable network outcomes**. The three strongest pieces of evidence are: * SD-WAN implementation with **30% latency reduction** * Data-centre migration involving **500+ physical and virtual servers** * BGP optimisation producing **$50k annual transit savings** These are considerably stronger than generic claims such as "experienced network engineer." ### Weakest first impression The CV is **very short relative to the seniority claimed**. A recruiter may initially think: > "This looks impressive, but I need more evidence." There is not enough information to understand the candidate's full technical scope or leadership responsibilities. ### Clarity of target direction **Excellent.** The headline and experience clearly point toward senior networking/architecture positions. ### First impression **Strong and immediately relevant.** A recruiter would quickly understand that Sarah is an experienced enterprise network professional operating at a senior/principal level. ### Recruiter takeaway > **"Principal-level network engineer/architect with strong enterprise networking, SD-WAN and data-centre migration experience, backed by measurable results."** ### Main positioning problem **Insufficient depth of evidence for the level being claimed.** The CV establishes seniority, but doesn't fully *prove* the breadth expected from a Principal Network Engineer / Network Architect. --- # STEP 2 — Professional Positioning ### Current professional identity **Principal Network Engineer / Network Architect** The evidence supports both descriptions. ### Likely market level **Senior → Principal / Architect** The candidate is clearly beyond a standard Network Engineer position. ### Strongest professional positioning The strongest positioning is: **Enterprise Network Architect / Principal Network Engineer specialising in WAN, data-centre and SD-WAN architecture.** This is stronger than simply marketing Sarah as a "Senior Network Engineer." ### Under-positioned? **Slightly, potentially.** The actual title is Principal Network Engineer, but the CV doesn't fully communicate the strategic/architectural responsibilities associated with that level. ### Correctly positioned? **Yes, broadly.** ### Over-positioned? **No obvious evidence of over-positioning.** The 10+ years of experience, Principal title, architecture work and major infrastructure projects provide reasonable support. ### Does the evidence support the target? **Yes — strongly.** The candidate has: * 10+ years' networking experience * Principal Network Engineer experience since 2019 * SD-WAN architecture * BGP/OSPF/EIGRP * MPLS * firewall experience * F5 load balancing * Nexus 9K/7K * Python network automation * major data-centre migration * measurable infrastructure improvements * CCIE Enterprise Infrastructure * JNCIP-ENT The target of **Senior Network Engineer / Network Architect is realistic and well supported**. --- # STEP 3 — Five Strongest CV Elements ## 1. Principal-level experience **Evidence:** Principal Network Engineer, Global Connect Corp, 2019–Present. **Why it matters:** This immediately establishes seniority and responsibility. **Marketability:** Very high. Recruiters searching for senior/principal candidates can immediately recognise the level. --- ## 2. Quantified SD-WAN outcome **Evidence:** "Designed and implemented a multi-site SD-WAN solution reducing latency by 30%." **Why it matters:** This goes beyond saying "worked with SD-WAN." It demonstrates **ownership + technology + outcome**. **Marketability:** Excellent. The 30% figure makes the achievement much more credible and memorable. --- ## 3. Large-scale migration experience **Evidence:** "Lead architect for data center migration involving 500+ physical and virtual servers." **Why it matters:** 500+ servers communicates meaningful infrastructure scale. **Marketability:** Very high for Network Architect and Principal Network Engineer positions. It also suggests exposure to complex infrastructure transformation rather than purely operational networking. --- ## 4. Direct financial impact **Evidence:** "Optimized BGP peering relationships resulting in $50k annual cost savings on transit." **Why it matters:** This is particularly valuable because it translates technical networking expertise into a **business outcome**. **Marketability:** Excellent. Many network CVs describe configurations. Far fewer demonstrate direct financial impact. --- ## 5. Strong technical/certification combination **Evidence:** * BGP * OSPF * EIGRP * SD-WAN/VeloCloud * MPLS * F5 * Nexus 9K/7K * Python * Palo Alto * Check Point * CCIE Enterprise Infrastructure * JNCIP-ENT **Why it matters:** The candidate combines advanced networking technologies with respected certifications. **Marketability:** High, particularly for enterprise networking and architecture positions. --- # STEP 4 — Five Most Important Weaknesses ## 1. Too little evidence of leadership **Evidence:** The CV establishes a Principal title but contains almost no explicit leadership evidence. **Impact:** A recruiter may question whether "Principal" means technical leadership, architecture leadership, or simply a senior individual contributor title. **Improvement:** If truthful, explain things such as: * teams led * engineers mentored * architecture ownership * technical governance * design reviews * stakeholder engagement * vendor management * standards ownership --- ## 2. Technical breadth is underdeveloped **Evidence:** The technical skills section is strong but extremely compressed. For example, "Python for Network Automation" tells the recruiter the technology but not what Sarah actually automated. **Impact:** The candidate may be underestimated against competing Principal/Architect candidates. **Improvement:** Add specific examples of automation, architecture or operational tooling **only where Sarah genuinely has that experience**. --- ## 3. The professional summary is too generic **Evidence:** > "Strategic Network Architect with 10+ years of experience designing and optimizing global WAN/LAN infrastructures." This is reasonable, but "strategic" and "global" aren't supported with enough detail in the CV. **Impact:** The summary sounds senior, but doesn't immediately communicate Sarah's strongest differentiators. **Improvement:** Lead with the strongest evidence: enterprise networking, SD-WAN, architecture, large-scale migration and measurable outcomes. --- ## 4. Career progression is under-explained The CV shows: **Network Engineer → Principal Network Engineer** That is good progression, but there is a five-year period at DataSafe followed by the current Principal role, with no explanation of increasing responsibility. **Impact:** The progression is visible but shallow. **Improvement:** Show increasing scope/responsibility within each role rather than merely listing tasks. --- ## 5. Some bullets are responsibilities rather than achievements For example: > "Managed firewalls (Palo Alto, Checkpoint) across 5 regional offices." and > "Implemented MPLS backbone for high-availability enterprise services." These are useful, but they don't communicate the outcome. **Impact:** They are less persuasive than the 30% latency reduction and $50k savings examples. **Improvement:** Where truthful, explain the scale, reason for the project and result. --- # STEP 5 — Achievement & Impact Analysis ## Strongest quantified achievements ### 1. 30% latency reduction **SD-WAN implementation** This is probably the strongest operational achievement. ### 2. 500+ servers **Data-centre migration** This demonstrates project scale. ### 3. $50k annual savings **BGP peering optimisation** This is the strongest direct business-impact metric. ### 4. Five regional offices **Firewall management** This demonstrates geographic/operational scope, although it isn't an outcome. --- ## Strongest unquantified achievements * Lead architect for a data-centre migration * Implementation of an MPLS backbone * Management of enterprise firewalls * Design and implementation of multi-site SD-WAN These show meaningful technical responsibility. --- ## Responsibilities that could potentially become achievements ### Firewall management Current: > Managed firewalls across 5 regional offices. Potentially stronger if Sarah can truthfully establish: * number of users/sites supported * availability improvement * security/risk reduction * migration or upgrade delivered * incidents reduced * throughput/traffic scale ### MPLS implementation Current: > Implemented MPLS backbone for high-availability enterprise services. Potential additional evidence: * number of sites * availability target * business-critical services supported * redundancy achieved * downtime reduction ### Network automation Current: > Python for Network Automation Potential additional evidence: * what was automated * time saved * number of devices * error reduction * frequency of automation * deployment/validation improvements --- ## Missing evidence of scale The CV would benefit from additional evidence around: * network/device count * number of sites * users supported * traffic volume * team size * project budgets * vendors managed * uptime/availability * architecture ownership * implementation timelines * business-critical services supported These are **requests for evidence**, not figures Sarah should invent. --- # STEP 6 — Skills Positioning ## Core skills Clearly supported: * Enterprise networking * WAN/LAN architecture * BGP * OSPF * EIGRP * SD-WAN * MPLS * Data-centre networking * Firewall administration * F5/load balancing * Cisco Nexus * Network automation with Python These form a strong senior networking foundation. ## Differentiating skills The strongest combinations are: ### SD-WAN + enterprise architecture Particularly valuable because the candidate has demonstrated an actual SD-WAN implementation and measurable result. ### BGP + commercial impact The $50k transit saving makes the BGP experience much more compelling. ### Networking + automation Python gives the candidate some automation capability rather than purely manual infrastructure expertise. ### Network architecture + major migration The 500+ server data-centre migration helps establish transformation experience. ## Supporting skills * Palo Alto * Check Point * F5 * MPLS * EIGRP Useful technologies, but individually they are less differentiating than the architectural achievements. ## Potential gaps For a Senior Network Engineer / Network Architect target, the CV could potentially benefit from evidence around areas such as: * network architecture/design methodologies * cloud networking * security architecture * automation depth * infrastructure-as-code * hybrid networking * technical leadership **However, these should only be presented as gaps where they are genuinely relevant to the jobs Sarah targets.** The CV does **not** provide enough information to conclude that Sarah lacks these capabilities. --- # STEP 7 — ATS & Keyword Clarity ## ATS clarity score: **8/10** The CV is relatively ATS-friendly. ### Strengths * Clear conventional job titles * Clear employer names * Dates are easy to identify * Technical skills are explicitly listed * Major networking technologies appear as searchable terms * Certifications are clearly stated * No unnecessary keyword stuffing ### Improvements The biggest opportunity is **keyword depth rather than keyword quantity**. For example: > SD-WAN (VeloCloud) is good. But where truthful, specific experience could potentially include terms such as the exact SD-WAN functionality, architecture responsibilities, implementation activities or operational responsibilities. Similarly: > Python for Network Automation would be stronger if the employment history showed what Python was actually used to accomplish. ### ATS terminology The CV already uses highly searchable terms: **BGP, OSPF, EIGRP, SD-WAN, VeloCloud, MPLS, F5, Nexus, Palo Alto, Check Point, Python.** That's good. No need to turn the CV into a keyword list. --- # STEP 8 — Career Story & Progression ## Does progression exist? **Yes.** The story is straightforward: **Network Engineer → Principal Network Engineer** This is a credible progression. ## Does the candidate appear to be developing? **Yes, but the CV doesn't fully demonstrate it.** The current role shows substantially greater architectural responsibility, particularly: * SD-WAN * data-centre migration * BGP optimisation However, the CV doesn't explicitly explain how Sarah progressed from operational engineering into architecture/technical leadership. ## Unexplained gaps No obvious employment gaps are shown. The dates are: * 2014–2019 * 2019–Present So the timeline appears continuous. ## Potential confusion The headline says: > Senior Network Engineer The summary says: > Strategic Network Architect The current job title says: > Principal Network Engineer The target is: > Senior Network Engineer / Network Architect All are related, but the CV would be stronger if it established **one primary professional identity**. I'd recommend positioning Sarah primarily as: **Principal Network Engineer / Network Architect** rather than leading with "Senior Network Engineer." --- # STEP 9 — Missing Evidence ## Critical missing evidence ### 1. Architectural scope For a Network Architect target, the CV should ideally establish: * What did Sarah design? * What architecture decisions did she own? * Did she produce high-level/low-level designs? * Did she establish standards? * Did she own technical architecture? Only add this if true. ### 2. Leadership scope The Principal title needs supporting evidence. Useful evidence could include: * engineers mentored * teams led * architecture forums * design authority * technical decision-making * stakeholder leadership ### 3. Network scale The CV provides **500+ servers**, but not network scale. If known, useful evidence could include: * number of sites * number of devices * number of users * geographic footprint ### 4. Automation depth Python is listed but not demonstrated. This is particularly important because automation can differentiate senior candidates. --- ## Useful additional evidence If genuinely available: * major vendors * cloud/hybrid networking * project budgets * implementation timelines * availability improvements * incident reduction * team size * vendor negotiations * customer/stakeholder exposure * additional certifications * specific network platforms * network security architecture --- # STEP 10 — CV Positioning Recommendation ## Recommended professional positioning **Principal Network Engineer / Network Architect specialising in enterprise WAN, SD-WAN and data-centre networking, with a track record of delivering measurable performance, cost and infrastructure outcomes.** This is stronger than positioning Sarah simply as a "Senior Network Engineer." --- ## Recommended CV headline # Principal Network Engineer | Network Architect | Enterprise WAN, SD-WAN & Data Centre This immediately aligns seniority, specialism and target direction. --- ## Recommended professional summary > Principal Network Engineer and Network Architect with 10+ years of experience designing and optimising enterprise WAN/LAN infrastructures. Experienced in BGP, OSPF, SD-WAN, MPLS, firewalls, load balancing and Cisco Nexus environments, with additional capability in Python-based network automation. Delivered a multi-site SD-WAN implementation that reduced latency by 30% and served as lead architect for a data-centre migration involving 500+ physical and virtual servers. Also optimised BGP peering relationships to achieve $50k in annual transit cost savings. Holds CCIE Enterprise Infrastructure and JNCIP-ENT certifications. This stays within the evidence supplied and avoids inventing additional responsibilities. --- ## Three possible positioning options ### Option 1 — Principal Network Engineer **Best if targeting senior technical IC positions.** Emphasise: * BGP * SD-WAN * enterprise networking * data centres * network optimisation * automation ### Option 2 — Network Architect **Best if targeting architecture/design roles.** Emphasise: * architectural ownership * SD-WAN design * migration architecture * design standards * technical decision-making The CV needs more evidence of these activities if Sarah genuinely performed them. ### Option 3 — Enterprise Network Architect **Best for large enterprise/global infrastructure organisations.** Emphasise: * WAN/LAN * SD-WAN * MPLS * data-centre networking * security * large-scale transformation * business impact **My preferred option:** Option 1/2 hybrid — **Principal Network Engineer / Network Architect**. --- # STEP 11 — Prioritised Improvement Plan | # | Improvement | Why it matters | Impact | What to change | | ------ | ------------------------------------------------ | ------------------------------------------------- | ---------- | ---------------------------------------------------------------------------------------------- | | **1** | Strengthen evidence of architectural ownership | Principal/Architect claims need proof | **High** | Explain genuine architecture/design responsibilities | | **2** | Expand leadership evidence | Establishes Principal-level scope | **High** | Add teams mentored/led, technical leadership and stakeholder responsibilities where applicable | | **3** | Add more measurable outcomes | Makes experience commercially credible | **High** | Add genuine performance, availability, cost, efficiency or risk metrics | | **4** | Expand network scale | Shows complexity | **High** | Add genuine device/site/user/geographic scale | | **5** | Demonstrate Python automation | Currently only a skills-list claim | **High** | Add real automation examples and outcomes | | **6** | Strengthen the professional summary | Better communicates differentiation | **High** | Lead with architecture, SD-WAN, migration and measurable results | | **7** | Clarify the seniority/identity | Avoids Senior vs Principal vs Architect ambiguity | **Medium** | Use a consistent primary positioning | | **8** | Convert responsibility bullets into outcomes | Makes experience more persuasive | **Medium** | Add business/technical results where genuinely known | | **9** | Expand relevant technical depth | Helps recruiter/hiring-manager assessment | **Medium** | Add technologies and responsibilities actually used | | **10** | Add carefully selected context to major projects | Helps establish complexity | **Medium** | Include project objective, scope, responsibility and outcome | Notice that **formatting is deliberately low priority**. The CV doesn't primarily have a cosmetic problem; it has an **evidence-density problem**. --- # STEP 12 — Final Marketability Assessment ### Overall CV marketability ## **8/10** This is already a strong CV foundation. The candidate has several genuinely marketable achievements rather than relying entirely on generic claims. ### Professional positioning ## **Strong** The target direction is realistic and supported. ### Recruiter readiness ## **Competitive** The CV should attract attention for relevant Senior/Principal networking positions, although the lack of detail could weaken it against exceptionally strong competing Architect candidates. ### Biggest strength **Demonstrated enterprise networking impact.** The combination of: **30% latency reduction + 500+ server migration + $50k annual savings** is considerably stronger than the average networking CV. ### Biggest weakness **The CV doesn't provide enough evidence to fully substantiate the breadth and seniority implied by "Principal Network Engineer / Network Architect."** ### Biggest missed opportunity **Leadership and architecture scope.** The CV says "Lead architect" once, but doesn't explain the candidate's broader architectural authority, decision-making, leadership or influence. ### Most important improvement **Add evidence demonstrating the scale and scope of Sarah's Principal-level architectural responsibility.** --- # FINAL VERDICT ### 1. Does this CV clearly communicate what the candidate is good at? **Yes.** It clearly communicates strong enterprise networking, WAN/LAN, BGP, SD-WAN and infrastructure architecture capability. ### 2. Is the candidate positioned at the right professional level? **Yes, broadly.** Principal Network Engineer / Network Architect is supported by the experience and achievements presented. The CV could, however, **prove the Principal/Architect level more convincingly**. ### 3. Does the CV support the target role or career goal? **Yes — strongly.** Senior Network Engineer and Network Architect are logical targets based on the evidence provided. ### 4. What is most likely to make a recruiter keep reading? The combination of: > **10+ years + Principal Network Engineer + 30% latency reduction + 500+ server migration + $50k annual savings + CCIE** That is a strong opening value proposition. ### 5. What is most likely to make a recruiter lose interest? The CV becomes **too sparse after the initial achievements**. A recruiter may wonder: > "What else has this Principal Engineer actually owned?" The lack of leadership, architectural scope, network scale and detailed technical evidence could cause a recruiter to move on to a competing candidate whose CV provides more proof. ### 6. What is the single most important change the candidate should make? ## **Turn the CV from a concise list of impressive achievements into evidence of Principal-level scope.** Don't simply add more bullets. Instead, add **high-value evidence** around: **architecture → scale → leadership → technical complexity → outcome.** That would make the existing achievements much more powerful. --- ## Overall scorecard | Area | Assessment | | ---------------------- | ---------- | | Professional identity | **9/10** | | Seniority positioning | **8.5/10** | | Target-role alignment | **9/10** | | Technical credibility | **9/10** | | Achievement evidence | **8.5/10** | | Business impact | **8.5/10** | | Leadership evidence | **5/10** | | Architectural evidence | **7/10** | | Career progression | **8/10** | | ATS clarity | **8/10** | | Recruiter clarity | **8.5/10** | | Overall marketability | **8/10** | ### Bottom line **Sarah already has the ingredients of a highly marketable Senior/Principal networking CV.** The problem isn't that the CV lacks impressive material; it's that **too much of the candidate's potential value remains unstated**. The three existing quantified achievements are particularly valuable. The next iteration should focus on extracting the *scope and context behind those achievements* rather than adding generic technical keywords or making the CV substantially longer.