write-career

To write a senior career portfolio using the STAR+I method, structure each project narrative with Situation, Task, Action, Result, and Impact sections to demonstrate deep technical impact in long-form documents spanning 5 pages or more.

A backend engineer's career narrative should include a professional summary, detailed project stories, architecture decisions, troubleshooting examples, and lessons learned, all standardized from a single source of truth data file.

Yes, you can generate a tiered documentation suite from a single source of truth data file by applying standardized templates to produce resumes, detailed portfolios, and project-by-project narratives simultaneously.

Structure architecture and troubleshooting experiences by applying STAR+I guidelines to detail the specific situation, technical actions taken, measurable results, and broader impact on the system or team.

Yes, you need a specific markdown file at docs/career/my_career_data.md serving as the single source of truth, alongside resume writing references, to ensure consistent tone and formatting for the professional summary.

The best way to articulate lessons learned in a long-form career document is to map them directly to the Impact phase of the STAR+I framework, demonstrating how troubleshooting and architecture decisions influenced future outcomes.