Interview questions by type
Civil Service Changing and Improving: interview questions and examples
Changing and Improving is the Success Profiles behaviour about looking for better ways of doing things and making them happen: suggesting ideas, reviewing how work is done, taking sensible, managed risks and helping people adapt to change.
A strong example shows you noticed a real problem, proposed or tried a practical change, involved the people it affected, and can show what improved. Small, real improvements usually score better than vague stories about transformation.
How it is assessed, and how it changes by grade
Applications often ask for a behaviour statement for Changing and Improving, commonly around 250 words; the advert says how many words. At interview, a panel asks one or two questions on it and scores your answer against a scale for the grade.
The Success Profiles framework describes each behaviour at levels: Level 1 broadly AA/AO, Level 2 EO, Level 3 HEO/SEO, Level 4 Grade 7/6 and Level 5 the Senior Civil Service. At AA/AO, panels look for openness to change and ideas for improving your own work. At EO, they expect you to review a process, suggest and test practical improvements, and consider simpler or digital options. At HEO/SEO, you should be encouraging ideas from others, leading changes, managing the risks and helping colleagues through them. At Grade 7/6, the focus is on creating a culture where improvement happens and leading change across teams or organisations.
Interview questions on Changing and Improving, and what the panel is looking for
Tell me about a time you suggested or made an improvement to how things were done.
What the panel is looking for: A specific problem, your idea, how you tested or introduced it, and evidence that it worked.
Describe a time you had to adapt to a change you did not agree with at first.
What the panel is looking for: That you raised concerns constructively, then made the change work, rather than resisting or simply complying.
Give an example of when you asked for feedback and changed something because of it.
What the panel is looking for: That you sought feedback actively, from users or colleagues, and acted on it.
Tell me about a time you took a risk to try something new.
What the panel is looking for: A managed risk: you thought about what could go wrong, got agreement where needed and had a way to check or reverse it.
Describe a time a change you introduced did not work as planned.
What the panel is looking for: Honesty and learning: how you noticed, what you adjusted and what you would do differently.
For EO posts: how have you used technology or a simpler process to save time or reduce errors?
What the panel is looking for: A practical change, even a small one such as a template or tracker, with a measurable effect.
For HEO/SEO posts: tell me about a time you helped a team through a significant change.
What the panel is looking for: That you explained the reasons, listened to concerns, adjusted the plan where sensible and kept people involved.
For Grade 7 posts: how have you encouraged innovation in your team?
What the panel is looking for: That you created conditions for others' ideas, such as time, permission to test or recognition, not just that you had good ideas yourself.
How to build a Changing and Improving example with STAR
Pick a change you drove or shaped, not one that simply happened to you. The strongest examples have a clear before and after. At EO, one process you improved is enough; at HEO and above, show how you brought others with you and managed the risks.
- Situation: what was not working, and how you knew.
- Task: what you set out to change, and your role in it.
- Action: how you worked out the fix, tested it, involved others and handled resistance.
- Result: the before and after, ideally with a number, and whether the change lasted.
Example answer
Tell me about a time you suggested or made an improvement to how things were done.
Situation: I was a shift supervisor in a supermarket, and our click-and-collect orders were often not ready at the promised time. Customers were waiting at the desk, and complaints were building up.
Task: nobody had asked me to fix it, but I was responsible for the evening shift, which had the most late orders, so I wanted to find out why.
Action: for two weeks I noted every late order and the reason. Most were not about staffing: pickers were walking the store in the order items were listed, so they crossed the shop several times. I suggested to the store manager that we print pick lists sorted by aisle, which our system could do but no one had switched on. She agreed to a trial on my shift. I showed the pickers the new lists and asked them to tell me what was not working. One pointed out that chilled items were then sitting out too long, so we moved chilled and frozen to the end of the list.
Result: after a month, late orders on my shift had dropped from around one in five to about one in twenty, and complaints fell. The manager rolled the sorted lists out to every shift, and I wrote a one-page guide for new pickers. I learned to measure a problem before guessing at the fix.
Example 250-word statement
Written for an EO application
In my role as an administrator in a university's student records office, I handled requests for official letters confirming students' enrolment. Requests arrived by email in many formats, and we often had to write back for missing details, which meant students waited up to two weeks.
I reviewed a month of requests and found that most delays came from the same three missing details. I suggested replacing the email route with a short online form that required those details, built with the university's standard form tool. My manager was cautious, because some students had complained about online forms before, so I proposed a four-week trial while keeping the email route open.
I built the form, wrote clear guidance, and asked six students to test it before launch. Their feedback led me to add a field for the address the letter should go to, which had not been in my original design. During the trial I tracked how long each request took and shared weekly figures with the team.
By the end of the trial, most requests came through the form, the average wait had dropped from about ten working days to three, and we had almost stopped writing back for missing details. The team adopted the form permanently, and I now trial changes on a small scale and measure them before asking for a wider rollout.
Mistakes to avoid
- Describing a change that management introduced, where your only part was going along with it.
- Giving an idea with no evidence it worked. Panels want the before and after.
- Presenting change as easy. Leaving out the resistance, risk or setback makes the story less credible and removes your best evidence.
- Choosing a huge organisational transformation where your own contribution is unclear.
- Criticising colleagues who resisted the change instead of showing how you brought them with you.
Frequently asked questions
What is a good Changing and Improving example for the Civil Service?
One where you noticed a specific problem, suggested or made a practical change, involved the people affected and can show a before and after. It can come from any job: a shop, an office, a school or volunteering.
What does Changing and Improving look like at HEO or SEO?
At HEO and SEO, panels expect more than a personal idea. They look for you leading a change, encouraging ideas from others, managing the risks and helping colleagues adapt.
How do I write a 250-word Changing and Improving statement?
Use one STAR example. Keep the situation short, spend most of the words on how you developed, tested and introduced the change, and end with a measurable result and what you learned. Check the advert for the word limit.
Can I use a change that did not work?
Yes, if you show what you learned and how you adjusted. Panels value honest reflection, but make sure there is still a clear action and outcome from you.