Intern and first-job structure
Lead with education or a tight skills group if work history is short. Two projects should show a full loop: problem, your part, tools, and what changed. Internships go in experience even if they were unpaid.
Avoid a long objective. Name the role family you want. Campus roles, open-source, or freelance gigs count when you can defend them in a screen.
Mid-level structure
Experience leads. Each job needs scope: team size, systems owned, and two or three outcomes. Projects that duplicate your day job can go. Skills should match the last two years, not every workshop you attended.
A short summary can name domain and level — “Product designer, B2B SaaS, 5 years” — so both a parser and a hiring manager place you quickly.
Lead and manager structure
Leads still need personal outcomes, not only “managed a team.” Show decisions: what you stopped, what you scaled, how you hired or mentored. Managers should separate people leadership from individual contribution so the ATS does not hide the IC work.
Keep the file to two pages unless a public-sector form demands more. Upload once in JobBucket; apply to roles that match the level you wrote, not every vacancy on the board.