Writing a career description for an experienced hire
A career description sits next to your resume and shows, project by project, what you actually did at each company and what came of it.
How it differs from a resume
A resume summarizes your whole background: contact details, employers, education and skills, usually one line per role. A career description goes one level deeper and explains the projects behind each role, with your responsibilities and results. In Korea, employers hiring experienced candidates often ask for it as a separate document, either in the job posting or in their own application form. If a posting asks for one, submit it even when your resume already has detailed bullets, because reviewers expect to find the project detail there.
Structure by company, then by project
List companies with the most recent first, and under each company list the projects you worked on, also most recent first. Start each company with a short header: department, position, period and one or two sentences on what the job covered. Aim for one to two A4 pages, and do not go beyond three even with a long career. If you are running over, keep the projects closest to the role you are applying for and merge smaller work into a single summary line.
What to write for each project
Give every project a name and a period that falls inside the company's dates. Then state your role, the team size and your contribution, either as a share such as 40% or as Lead when you owned it. Add the main technologies or tools, two to five of them, rather than your full stack. Finish with two to four result lines that each describe one action and its outcome.
Writing results with numbers
A simple way to write each result line is STAR (situation, task, action, result) or PAR (problem, action, result), compressed into a single sentence. Put a number in most lines: a before-and-after value, a percentage change, a count or a time frame. When the real figure is confidential, express it as a ratio or a relative change, and refer to clients as Company A or by industry. Only use numbers you can explain and defend in an interview.
Common mistakes
Writing 'we did' throughout hides your own part, so describe your actions and state the team size separately. Listing duties or technologies without results leaves the reviewer guessing what changed because of your work. Vague words such as improved, various or actively add length without information; replace them with the specific change and its size. Also check that internal code names, acronyms and confidential numbers have been removed or explained.
Final check before sending
Save the document as a PDF so the layout stays the same on any device. Use a clear file name such as '[Role_Name] Career Description.pdf' so the reviewer can find it among many applications. Compare it with your resume line by line: company names, job titles and employment dates must match exactly. Finally, read it once as a stranger would, and fix any sentence that only makes sense to someone who worked with you.