SEC GUY / EXPERIENCE BUILDER / PROJECT LIBRARY

Choose a project. Prove the work.

Start with identity, AI security, or cloud. Then take on two deeper AI engineering builds. Every project ends with a concrete portfolio package.

01 / PLANDefine the scope and success criteria
02 / BUILDImplement in an authorized environment
03 / PROVEShow tests, decisions, and tradeoffs
PORTFOLIO PATHS

Pick the next proof point.

Each path ends with a visible artifact, test evidence, and a short decision narrative—not an automatic badge or a promise of employment.

IDENTITY
PROJECT 01 / FOUNDATIONS

Windows AD lab

Design a lab-only directory, automate test identities, and prove policy boundaries.

Portfolio output / configuration story
Explore project
AI SECURITY
PROJECT 02 / ASSESS

Prompt-injection assessment

Test a controlled AI workflow and document what untrusted text can—and cannot—change.

Portfolio output / assessment report
Explore project
AI DEFENSE
PROJECT 03 / HARDEN

LLM output defense

Keep model output away from privileged SQL and verify the boundary with synthetic data.

Portfolio output / patch and test matrix
Explore project
CLOUD
PROJECT 04 / DEPLOY

Cloud portfolio site

Ship a static site with HTTPS and a private origin, then defend the architecture.

Portfolio output / live site and diagram
Explore project
HOSTED AI
PROJECT 05 / OPERATE

AI control plane

Run Ollama behind an authenticated gateway with model policy, observability, and evals.

Portfolio output / working service and controls
Explore project
PERSONAL AI
PROJECT 06 / PRODUCT

Personal AI assistant

Build a useful Jarvis-inspired assistant that asks before acting and protects private data.

Portfolio output / demo and consent flow
Explore project
Access and cost: Existing interactive labs may require a membership. The two new AI projects are build blueprints, not hosted Sec Guy compute. Learners use systems they own or are authorized to test; hardware or cloud charges vary.
THE EMPLOYER-READY METHOD

Show the decision, not just the screenshot.

01

Define the outcome

Write the goal, constraints, and what success looks like before you build.

02

Keep the receipts

Capture redacted configuration, tests, failures, and fixes in a clear README.

03

Tell the story

Walk through your architecture and tradeoffs in a mock interview.

PRACTICE

Try the work.

Use the guided lab or create your own isolated environment. Never test someone else’s system without authorization.

EXPLAIN

Practice the hiring conversation.

Use the mock interview to explain decisions, validation, and the next improvement. A free account is required for the demo.

YOUR NEXT CONVERSATION

Turn the build into a story.

Present what you built, what failed, how you verified it, and what you would improve.

Practice the interview