Assemble the AI Service-Desk Administrator Portfolio

Tier: Advanced · Workflow area: Career elevation · ~45 minutes to assemble; the track built the contents

This playbook serves UC-56 and UC-61. The role it evidences barely existed three years ago, so hiring managers have no reliable signal for it yet — which is exactly the opportunity: verifiable artifacts beat keyword claims in a market that cannot yet tell the difference on paper.

When to use

• You have completed the core labs and playbooksthe portfolio assembles existing work; if the artifacts don't exist yet, this playbook is your gap list, in priority order.
• A role change is in sightinternal promotion case, external applications, or the formalization conversation pb-50 set up. Portfolios take an evening to assemble and a quarter to build; start from wherever you are.
• Appraisal seasoneven without a job change, the portfolio converts a year of invisible verification work into reviewable evidence.

When NOT to use

• With employer data in the artifactsnothing leaves with real ticket text, user data, client names, internal hostnames or screenshots of production consoles. Rebuild every public artifact in your lab tenant with synthetic data; the skill demonstrated is identical.
• As a certificate walla page of badges with no built things reads as a learner, not an operator. Certifications go in one resume line; artifacts get the pixels.
• Padded with claimed-but-unshown work"improved deflection by 40%" with no methodology attached is exactly the vendor math this track taught you to distrust. Show the workbook or drop the number.

The recipe

1. 1.

   Inventory against the four-pillar checklist. The portfolio needs one strong artifact per pillar; the track built each:

   Pillar	Artifact	Built in
   Deployed assistant	Working bot with escalation design	m6 labs, pb-40
   RAG engineering	KB-grounded chatbot repo with eval set	m6 labs, pb-46's golden set
   Honest measurement	Deflection report with strict definitions	pb-44 workbook
   Governance	Auto-resolve matrix + DPIA + policy pack	pb-43, pb-45, pb-49

   Missing pillars become your build queue — a lab-tenant rebuild of each is one focused weekend.

2. 2.

   Make the RAG chatbot repo the technical centerpiece. A public GitHub repo with: the ingestion and retrieval code from the labs, a synthetic KB (write 20 articles for a fictional company — an LLM drafts them in an hour), the confidence-gate and refusal logic from pb-40, the golden question set with scored results (pb-46's method), and a README that leads with the decisions — why this chunking, why this threshold, what the wrong-answer rate is and how you measured it. A hiring manager who reads only the README should meet an operator, not a tutorial-follower.

3. 3.

   Publish the honest deflection report as the differentiator. One page, lab or anonymized data, pb-44's structure: strict definition stated, four buckets, vendor-number reconciliation, review-loop findings. Nobody else's portfolio has this — measurement honesty is the rarest skill in the market and the easiest to demonstrate, precisely because everyone else publishes the inflated number.

4. 4.

   Assemble the governance pack as one PDF. The signed-format auto-resolve matrix (pb-43, synthetic environment), the DPIA summary (pb-45), the AI-usage policy (pb-49), and pb-41's refusal-test screenshots — the agent failing to exceed its permissions. For senior and MSP-market roles this pack outweighs the code: it proves you can be handed a tenant without a lawyer in the room.

5. 5.

   Stand up the portfolio site — simple, fast, self-hosted-or-GitHub. Structure: one landing page (who you are, the four pillars, one screenshot each), each pillar linking to its artifact, and a short "how I work" page describing your verification discipline — sampling audits, golden sets, human-on-the-send-button. Plain GitHub Pages is fine; the artifacts are the design.

6. 6.

   Rewrite the resume from duties to evidence. Run each bullet through the transformation:

   Copy

   Rewrite these resume bullets for an "AI Service Desk Administrator"
   target role. Rules: lead with the built thing or the measured
   outcome; name the mechanism (sampling audit, golden set, strict
   deflection, least-privilege agent actions); no vague AI claims
   ("leveraged AI", "familiar with LLMs" are banned); every number
   must be one I can defend with an artifact. My raw bullets and
   artifact list: [paste]
   

   Before: "Used AI tools to improve ticket handling." After: "Ran AI triage over a 400-ticket/week queue with a daily 10-ticket sampling audit; misroute rate published weekly, cut from 14% to 6% via routing-rule fixes." Then verify the rewrite the pb-48 way — every claim traces to something you can show.

7. 7.

   Add the interview layer: one story per pillar. For each artifact, prepare the 90-second narrative — the problem, the decision you'd defend, the failure you caught, the number you measured. The portfolio gets you the conversation; the stories convert it. Rehearse them against an LLM playing a skeptical hiring manager: "Ask me five hard follow-ups about this deflection report."

Make it yours

• Internal promotion trackswap the public site for an internal wiki pack, keep real (permitted) data, and frame the four pillars against pb-50's new role definition; the portfolio is the business case for the title.
• MSP / consulting marketlead with the governance pack and the vendor-POC scorecard (pb-46); clients buy trust and measurement discipline before they buy code.
• Bridging onward (pb-52)reuse the skeleton: the cloud bridge swaps in IaC repos, the security bridge swaps in log-triage and IAM artifacts, but the honest-measurement report stays — it travels across every destination role.

Quality check

• Every artifact runs or reads today. Click every link, clone and run the repo on a clean machine, reread the PDFs. A broken demo is worse than no demo.
• Zero employer or personal data. Grep the repo and the site for your employer's domain, real names, internal hostnames and ticket numbers before anything goes public — git history included; rebuild the repo rather than scrub-committing.
• Numbers survive hostile questioning. For each figure on the site or resume, you can produce the artifact and the method in under a minute. Anything you can't defend, delete tonight.
• The README-only test passes. Someone reading just the landing page and one README should correctly conclude you operate these systems. Ask a colleague to try; fix whatever they misread.