"Tell Us About a Process You Improved": A Finance Interview Answer Guide
“Tell us about a process you improved.”
This question comes up in almost every finance interview, from Senior Accountant to Financial Controller. It is one of the best opportunities you will have to show initiative, analysis and results in one story.
Yet many candidates give weak answers. They describe the new process in detail but forget the result. Or they talk about what “we” did so much that the panel cannot see their contribution. Or they choose a tiny example that does not show much.
This article explains how to answer the process improvement question well, with a simple structure and an example answer.
What the panel is looking for
You notice problems rather than accepting them
You analyse the cause, not just the symptom
You can design a practical solution
You can bring other people with you
You deliver a measurable result
You learn from the experience
Choosing the right example
Pick an improvement that is relevant to the role, that you led or significantly contributed to, and that has a clear result. Good examples include:
Shortening the month end close
Automating reconciliations or reporting
Reducing errors in payroll or payables
Improving budget or forecast processes
Strengthening a control after a problem
Redesigning a management report
Choose something with a number attached if you can.
A simple structure
The problem. What was wrong and why it mattered.
What you did. How you analysed it, what you designed and how you implemented it.
Who you worked with. How you brought others along.
The result. What changed, with numbers.
What you learned. One sentence.
This is a version of the STAR method. For more, see using STAR in interviews.
An example answer
"When I joined as Finance Manager, month end took 11 working days, which meant managers got their results almost halfway through the next month. Decisions were being made on old information.
I mapped the close and found three main delays. Accruals were done at the end rather than during the month, bank reconciliations were manual, and we were waiting on site data that arrived late.
I introduced a close calendar that moved accruals into the last week of the month, set up automated bank rules in Xero that matched about 80 per cent of transactions, and agreed firm deadlines with site managers, with a simple template for their data.
It took three months to settle. By the fourth month, we were closing on day five, and managers were getting results in the first week. Errors also dropped, because we were not rushing.
What I learned was that the biggest delays were outside finance. Getting the site managers on board mattered as much as the technical changes."
That answer takes about 90 seconds. It shows problem, analysis, action, collaboration, result and learning.
Using “I” and “we”
Improvements often involve teams. That is fine. But make your contribution clear. Use “I” for what you did personally, and “we” for what the team did together. If the panel cannot tell what you did, they cannot credit you for it.
Be ready for follow-up questions
Panels often dig deeper. How did you know it was the accruals causing delays? What resistance did you face? What would you do differently? How did you measure the result?
Prepare for these. The detail behind your story is what makes it credible.
Have more than one example
Prepare two or three improvement stories, so you can choose the best one for each panel. One might focus on speed, another on accuracy and another on controls or reporting. For more on quantifying these, see process improvement on a finance resume.
More example topics
Here are some other process improvements that make strong interview stories.
Introducing automated invoice capture that cut processing time by 60 per cent
Redesigning the budget process to cut the cycle from 12 weeks to 6
Fixing a payroll accrual error that had caused post-close adjustments every month
Replacing a 40-tab Excel pack with a Power BI dashboard
Introducing a delegation of authority after a duplicate payment
Standardising reporting packs across several entities
Choose the one closest to the role you are interviewing for.
When the improvement did not fully work
Sometimes the best stories include setbacks. Perhaps the first version failed, or people resisted the change. Including this makes your story more credible and shows resilience.
“The first automation rules matched only 40 per cent of transactions, so I reviewed the exceptions for a month and rebuilt the rules. After that, we reached 80 per cent.” That detail shows persistence and learning.
Linking it to the new role
Finish your answer by connecting it to the role you are applying for. “I noticed in the ad that you are looking to speed up month end. I would take a similar approach here.” That shows you are already thinking about how to add value.
Using numbers you can defend
Make sure every number in your story is accurate and explainable. If you say you saved 500 hours a year, be ready to explain how you calculated it. Credibility is everything in finance interviews.
Two more example answers
A control improvement
"As Financial Controller at a $75 million health services provider in Melbourne, I found that we had paid the same supplier invoice twice, for $48,000. It was recovered, but it showed a gap. Invoices could be entered from email and from the supplier portal, and the system did not flag duplicates across both.
I ran a test over two years of payments and found four more duplicates worth $31,000 in total, which we also recovered. I then set up a duplicate check on supplier, amount and date, and made a weekly exceptions report part of the payment run. I also trained the accounts payable team on why it mattered, not just how to run it.
In the 18 months since, we have caught 22 potential duplicates before payment. The auditors removed the finding from their management letter. What I learned is that a control only works if the people using it understand the risk."
A reporting improvement
"As a Finance Business Partner in a retail group in Auckland, I supported 14 store managers who each received a 20-page monthly pack. When I asked them, most said they only looked at sales and wages.
I worked with three store managers to design a one-page report with six measures, including wages as a percentage of sales against target. I built it in Power BI so it refreshed automatically. It took five weeks from first draft to launch.
Wage overspend across the stores fell from 2.1 per cent over budget to 0.4 per cent within two quarters, because managers could see the problem each week. My own reporting time also dropped by about two days a month."
Adjusting the story by level
The same question means different things at different levels.
Senior Accountant: the panel wants to see that you fixed something in your own area, and that it stuck.
Finance Manager: they want to see you led a change across the team and managed the people side.
Financial Controller or Head of Finance: they want to see you chose the right problem, set priorities and made a change that affected the whole business.
Finance Business Partner: they want to see an improvement in how the business made decisions, not just in how finance worked.
Choose your example to match the level of the role, not your current title.
Turn the story into resume bullets
Your best interview story should also appear on your resume, so the panel is primed to ask about it.
Before: “Improved month end processes.”
After: “Cut the month end close from 11 to 5 working days by moving accruals into the month, automating bank matching and setting firm site data deadlines.”
Before: “Implemented new controls in accounts payable.”
After: “Introduced a duplicate payment check that recovered $79,000 and stopped 22 duplicate invoices before payment.”
Likely follow-up questions
“How did you get the team or the business to accept the change?”
“What did it cost, in time or money?”
“Is it still working now?”
“What was the next improvement you would have made?”
Have a one or two sentence answer ready for each. Short, confident follow-up answers make the main story more believable.
A quick checklist before the interview
Is the problem clear in two sentences?
Can the panel tell what I did, not just what the team did?
Does the result include at least one number I can explain?
Have I included one thing that went wrong or surprised me?
Can I tell it in under two minutes?
If any answer is no, rework that part of the story before you practise it again.
Common mistakes
Describing the process without a result
Choosing a trivial example
Hiding your contribution behind “we”
Talking too long about the background
No numbers
Not preparing for follow-up questions
Your next step
Write your best process improvement story using the five-part structure. Time yourself telling it. Aim for 90 seconds to two minutes.
If you want your resume and LinkedIn to show your improvement results, my Gold package covers your resume, cover letter, LinkedIn and positioning strategy.
If you want to test your interview stories, book a complimentary Clarity Session.
