APPENDIX H: RESUME PORTFOLIO BUILDING CAPSTONE PROJECTS

HOW TO PRESENT IT IN A PORTFOLIO README outline Title and a purpose sentence mentioning supervisor, budgets, retries, and runbook. The kitchen analogy in a few sentences. An architecture diagram in text showing supervisor, three workers, budget, retry, audit log, kill switch, and human queue. How to run the demo and the tests. A table in plain sentences of failure modes and the mechanism that handles each one. Links to runbook.txt and deployment_plan.txt. Honest limits. Next steps. What to screenshot or record Take a screenshot of the terminal showing the five ticket outcomes and the totals. Take a screenshot of audit_log.jsonl showing the retry and redraft events. Take a screenshot of the kill switch run. Record a short video that runs the demo, turns on the kill switch, and then turns it off. Include the runbook and deployment plan as readable pages in the project. Metrics to report honestly Report the totals from the demo, which are five tickets, four done, and one escalated. Report the number of retries and redrafts that occurred, which are one each. Report the number of tests and how many pass. Say that these are results of a scripted prototype on invented tickets, and that no real traffic was involved. How to word a resume bullet truthfully Good example: "Designed and tested a multi-agent support-triage prototype in Python with a supervisor, per-ticket budgets, exponential-backoff retries, a reviewer step, human escalation, and a kill switch; authored an incident runbook and deployment plan." Another good example: "Wrote automated tests proving that retries, budget limits, and an emergency stop behave correctly in a multi-agent workflow." Avoid wording such as "deployed a production AI support system" or "reduced support costs," unless you truly did and can show the evidence. Interview talking points Explain why a supervisor and several small workers can be easier to control than one big agent, and what it costs in complexity. Explain exponential backoff and why waiting longer each time is kinder to a struggling service. Explain why every loop must charge a budget. Explain what belongs in a runbook and why you drilled it. Explain how you would roll out the system gradually and what would make you roll back.