Success Profiles CV Guide for Civil Service Jobs

Experience is about what you have done and achieved, not how long you have occupied a job title. A Success Profiles CV should therefore avoid vague duties such as "responsible for administration" and replace them with specific evidence: the caseload you handled, the service you improved, the report you produced, the system you used, the decision you supported, or the problem you solved.

Experience can come from work, volunteering, study, projects or responsibilities outside paid employment if it clearly matches the requirement. This matters if you are moving from the private sector, local government, the NHS, education, a charity, a regulator or a career break. A charity treasurer can show budget monitoring and governance. A retail supervisor can show customer service, conflict handling and team coordination. A course representative can show consultation and influencing.

Behaviours are the actions and activities linked to effective performance in a job. A vacancy may name behaviours such as Making Effective Decisions, Communicating and Influencing, Managing a Quality Service, Delivering at Pace, Working Together, or Seeing the Big Picture. You do not need to cover all Civil Service behaviours unless the advert asks for them. You need strong evidence for the selected ones.

On a CV, behavioural evidence usually appears in your bullet points. You can show a behaviour without writing a full interview answer. For example: "Reprioritised a 120-case backlog after policy changes, agreeing risk-based triage rules with two team leaders and reducing overdue cases by 38% in six weeks." That gives context, action and outcome in one line.

Technical evidence covers specialist skills, qualifications, professional standards or knowledge needed for the role. A finance post may need accountancy study or budgeting knowledge. A digital role may need agile delivery, SQL, content design, cyber controls, service design or product management evidence. A policy role may need consultation, drafting, ministerial submissions or evaluation.

Put technical evidence where recruiters can find it quickly. If the advert lists essential technical criteria, use a short skills section near the top and reinforce each skill in your employment history. A skill list says you have the capability; a bullet point shows how you used it.

Strengths are usually assessed through interview questions, situational judgement or other selection methods, not through a long CV section. Ability is often tested through online assessments such as verbal or numerical reasoning. Your CV cannot take those tests for you, but it can show the same qualities in context: analytical thinking, judgement, resilience, problem solving, learning quickly and making balanced decisions.

Use strengths and ability as editing checks rather than headings. Ask whether the CV shows the way you work, not just the tasks you completed. A caseworker CV might show empathy, discipline and judgement. A project support CV might show organisation, pace and collaboration. A policy CV might show analysis, curiosity and clear written communication.

Look for wording such as "we will assess experience", "technical skills will be assessed", "behaviours assessed at sift", or "you will be asked to provide a CV and personal statement". If the advert says the CV is assessed against experience and technical skills, make those the strongest sections. If it says behaviours are assessed in the application, prepare short behaviour-led evidence too.

Do not assume the same CV will work for every department. A project delivery role, a casework role and a policy role may all use Success Profiles, but the evidence they value will be different. Match the context, not just the framework.

Civil Service behaviours change by grade. An EO role may need clear delivery, customer focus and accurate case handling. An HEO or SEO role may expect more judgement, stakeholder work and improvement. Grade 7 or Grade 6 evidence often needs strategic thinking, leadership through others and stronger accountability.

This is where many CVs feel underpowered. A senior applicant may list tasks but not scale, risk, budgets, policy impact or people leadership. A junior applicant may try to sound strategic when the advert really wants accurate service delivery and learning agility. Pitch your evidence to the grade named in the vacancy.

Once you understand the advert, adjust your headings and bullets. If the role is asking for project support, do not hide project evidence under a vague "administration" heading. If it asks for data analysis, make analysis visible in your profile, skills and experience. If it asks for stakeholder communication, show who you communicated with and what changed because of it.

This does not mean copying the advert word for word. It means using the same vocabulary where it is truthful. A recruiter should be able to move from the essential criteria to your CV and find matching evidence within seconds.

Some adverts ask for an anonymised CV. If that happens, remove personal identifiers the instructions name, such as your name, age, gender, photo, full address or other identifying details. Keep professional information that is needed to assess the role, such as relevant qualifications, employment history and skills.

If the advert does not ask for anonymisation, include your name, phone number, professional email, town or region, and LinkedIn or portfolio link if relevant. Do not include a photo, date of birth, marital status, National Insurance number or full street address.

Your CV profile should be short, factual and tailored to the vacancy. Aim for three to five lines. Name the type of work you do, the level of responsibility you have held, and two or three evidence areas that match the advert. Avoid broad claims such as "hard-working professional" or "passionate about public service" unless the rest of the sentence proves them.

For example:

"HEO project support officer with experience coordinating cross-team delivery plans, tracking risks and preparing briefing updates for senior stakeholders. Strong evidence in Managing a Quality Service, stakeholder engagement and improving reporting routines, including a recent dashboard change that reduced weekly status-update time by 30%."

That profile works because it names level, role fit, skills and evidence. It also creates a bridge into the employment section. The reader knows what to look for next.

A skills section is useful when the advert lists technical or professional requirements. Keep it targeted. Six to ten skills are enough for most applications. Choose skills that are named or strongly implied in the advert, such as casework, policy analysis, procurement support, risk management, stakeholder engagement, data reporting, ministerial briefing, finance processing or service improvement.

Do not make the skills section a detached keyword list. If you include "risk management", the employment section should show a risk register, mitigation plan, escalation process or decision you supported. If you include "written communication", show briefings, reports, correspondence or guidance you produced.

Your employment history should carry most of the proof. For each role, include your job title, organisation, location if helpful, and dates. Add one short line of context when the organisation or team is not obvious. Then use bullet points that show achievements, responsibilities and outcomes.

For recent relevant roles, use four to six bullets. For older or less relevant roles, use two or three. A CV for Success Profiles should be selective. The question is not "What have I ever done?" It is "What evidence helps this panel score me against this vacancy?"

Include education that helps the application. For technical roles, professional qualifications can be important and should not be buried. Accountancy study, APM, Agile, CIPD, CIPS, PRINCE2, ITIL, data qualifications, security certifications or specialist degrees may all be relevant depending on the post.

If education is your strongest evidence, such as for an entry-level policy, apprenticeship or graduate application, include modules, projects or research that match the role. If you have substantial work experience, keep education shorter and prioritise current evidence.

Use STAR to plan, then compress it for the CV. Situation and task should be short. Action and result should be clearer. A useful pattern is: action verb + context + method + outcome.

For example:

• Built a weekly risk tracker for a delayed supplier project, giving senior stakeholders a single view of blockers and helping the team recover two missed milestones.
• Analysed 800 survey responses for a policy consultation, grouping themes into five evidence categories and producing a briefing note used in the final recommendation.
• Coached three new team members on casework quality checks, reducing returned files and improving consistency against internal guidance.

These examples are not full interview answers. They are short enough for a CV but detailed enough to show behaviour, experience and technical evidence.

A panel needs to understand the size and complexity of your work. Include numbers where they help: caseload, budget, response time, stakeholders, team size, error rate, deadlines, service users, reports, savings or quality scores. Do not invent numbers, but do use honest scale.

Judgement is often more important than volume. If you made a decision, explain the basis. If you escalated a risk, explain why. If you improved a process, explain the problem it solved. A bullet that says "processed 300 applications" shows workload. A bullet that says "prioritised 300 applications by risk and deadline after a policy change" shows judgement.

Private-sector and wider public-sector applicants often have strong evidence but hide it in unfamiliar language. Translate the value. Sales account management may become stakeholder engagement, negotiation and service improvement. Retail supervision may become operational delivery, customer handling and staff coaching. University projects may become research, analysis and written briefing.

Do not pretend your experience is identical to the role. Show why it is relevant. Use phrases such as "transferable evidence includes" in your planning notes, then turn the best examples into normal CV bullets.

An ATS-friendly CV is not about hiding keywords. It is about making your evidence easy for both software and people to read. Use standard headings, avoid tables where possible and save the document in the requested format. If no format is specified, PDF is usually safe for design stability, while Word can be better for some application portals. Follow the advert.

Use keywords naturally. If the advert says "stakeholder engagement", use that phrase where your experience genuinely includes it. If it says "risk management", name the risk work you have done. Do not scatter keywords without evidence.

Before submitting, imagine a panel member reading quickly with the criteria beside them. Can they find your strongest evidence for each requirement? Can they see the level, scale and outcome? Are your most relevant examples on page one? Is anything important hidden under a weak heading?

Remove content that does not help the sift. Hobbies, long school histories, unrelated short courses and old responsibilities can all take space from stronger evidence. Keep the CV focused on the role.

Many applications ask for a CV and a personal statement. Use the CV to present your experience and achievements clearly. Use the statement to explain how your evidence meets the essential criteria in more depth.

A good pairing avoids duplication. If the CV bullet says you reduced a backlog by introducing a triage process, the statement can explain the situation, stakeholders, decision-making and result in a fuller STAR example. The two documents should reinforce each other, not compete for space.