Financial Controller
Structured interview questions for Financial Controller, with what a strong answer surfaces for each one.
BehavioralBusiness partnering Describe a situation where your analysis changed a business decision made by management. What was your role concretely?
What a strong answer surfacesBusiness-partnering ability: the candidate describes the data analysis, the translation into a recommendation and the effect on the decision (an investment stopped, pricing changed, sales focus shifted). Bonus: the candidate names how they then convinced management of the recommendation. Candidates who describe only I produce reports without an impact example act as a data supplier, not as a business partner.
BehavioralAnalytical rigor Tell me about a particularly intense budget or forecast phase. What happened, and what did you learn from it?
What a strong answer surfacesCalm under pressure and method: the ability to prioritize under deadline (the headline figures first, granularity later), to gather inputs from several functions and to uncover inconsistencies. Bonus: the candidate afterward built a template, checklist or schedule for the following cycles. Anyone who describes a budget phase where everything ran smoothly has never budgeted autonomously or downplays the reality of the process.
BehavioralBusiness partnering Describe a situation where you had to explain a complex financial message (e.g. a margin erosion or a forecast miss) to management or an operational team.
What a strong answer surfacesThe ability to translate: turning a technical concept (a contribution-margin shift, working-capital tie-up, an EBITDA bridge) into operational vocabulary, without condescension or unnecessary jargon. Bonus: a concrete example with a visual representation (a waterfall chart, a bridge chart) and a clear action derivation. At an SMB the controller is often the financial translation layer between accounting and management; pedagogy is therefore critical.
SituationalAnalytical rigor In the month-end close you find that the margin in one business unit is 4 percentage points below plan. How do you analyze the cause, and how do you communicate the result?
What a strong answer surfacesA structured plan: (1) build a bridge (volume, price, mix, unit costs, special effects), (2) quantify the respective contributions, (3) cross-check the cause with the operational function (sales for pricing, operations for unit costs), (4) a clear recommendation to management. Anyone who voices a guess straight away without a bridge analysis (it's the competition) or pushes the difference into the next month with further detailed analysis needed lacks analytical rigor.
SituationalBusiness acumen Management asks you to build a business case for a planned investment (machine, software, a new branch) of €800,000. Which steps do you take, and which metrics do you deliver?
What a strong answer surfacesMethod: (1) align the assumptions with the operational stakeholders (sales for the revenue effect, operations for the productivity effect), (2) build a cash-flow series over 5 to 7 years with investment, operating and tax effects, (3) deliver metrics: NPV, IRR, payback period, sensitized scenarios (best, base, worst), (4) a clear recommendation with risk notes. Anyone who presents only an ROI without a cash-flow series and without sensitivity stays superficial; anyone who delivers 80 Excel tabs without a clear recommendation lacks business partnering.
SituationalBusiness acumen Liquidity will fall below a critical threshold in 90 days if nothing happens. How do you structure your recommendation to management?
What a strong answer surfacesA structured plan: (1) build a working-capital bridge (receivables, payables, inventory), (2) identify and quantify levers (accelerate dunning, extend payment terms, reduce inventory, defer investment), (3) scenarios with a clear time profile, (4) a recommendation with the 2 to 3 most effective levers and an owner per lever. Anyone who jumps straight to expand the credit line without quantifying the levers overlooks the operational steering potential; anyone who names purely operational levers without addressing the escalation path on failure is not mature enough.
TechnicalExcel and BI competence Which tools do you use for reporting and analysis? Describe the tool you are most confident in, and one that has given you the most difficulty.
What a strong answer surfacesConcrete familiarity with at least one modern reporting and BI solution (SAP CO, Lucanet, Power BI, Tableau, Jedox, IDL Konsis, Cognos) and with advanced Excel (Power Query, Power Pivot, dynamic arrays). The ability to talk in detail about one module (e.g. consolidating a forecast in Lucanet, building a Power BI dashboard with DAX measures, parameterizing a SAP CO profit-center report). Admitting a difficulty shows honesty; anyone who masters all tools is suspect.
TechnicalP&L and balance-sheet reading Explain the EBITDA bridge between two consecutive fiscal years at an industrial SMB with the following structure: revenue minus material costs, personnel costs, other operating expenses. Which drivers do you break out, and in which order do you present them?
What a strong answer surfacesExpected answer: (1) volume effect on revenue, (2) price effect on revenue, (3) mix effect on revenue, (4) material-cost effect (volume plus price plus supplier mix), (5) personnel-cost effect (FTE change plus tariff increase plus bonus), (6) other effects (energy, rent, special effects). Presentation order: from the largest to the smallest driver, with the respective sign. Anyone who cannot break down the EBITDA bridge or mixes effects (e.g. volume and mix in one driver) does not command P&L analysis at mid level.
TechnicalP&L and balance-sheet reading The difference between HGB and IFRS in the recognition of development costs and lease agreements? In which cases must a German SMB worry about it?
What a strong answer surfacesAnswer: under HGB, development costs are generally expensed immediately (an option to capitalize self-created intangible assets under § 248(2) HGB, rarely used in practice); under IAS 38, development costs are to be capitalized under six criteria. Leasing under HGB distinguishes operating and finance leasing (capitalization only for finance leasing); under IFRS 16 virtually all leases are capitalized. A German SMB is affected when it has a parent or subsidiary in IFRS consolidation (a listed group or group-wide IFRS reporting). Candidates who know the HGB-IFRS logic without having applied IFRS are a fit for a mid role at a pure SMB; anyone who has never heard of it is a warning signal at a group subsidiary.
CaseBusiness acumen Forecast build: your company has reached 24 M€ in revenue over 8 months this year (a run rate of 3 M€ per month). Sales reports 30 % growth for next year based on the pipeline. Which steps do you take before you confirm a forecast number?
What a strong answer surfacesExpected steps: (1) adjust the run rate for seasonality (Q4 is stronger or weaker than average in many sectors), (2) decompose the pipeline assumption (historical vs. assumed win rate, the ramp time for new customers, the churn assumption for existing customers), (3) cross-check top-down market growth (a sector analysis, competitive moves), (4) build sensitivity bands (best, base, worst) and validate the base scenario with sales. Anyone who simply takes 30 % into the forecast acts as a data supplier; anyone who rejects 30 % without discussion is not capable of business partnering.
CaseAnalytical rigor Working-capital analysis: receivable days (DSO) have risen from 45 to 62 days, payable days (DPO) have stayed constant at 38 days, inventory turnover has worsened from 6 to 4.5. Which levers do you propose to management, in which order?
What a strong answer surfacesMethod: (1) decompose the DSO rise (which customer segments, new payment terms, dunning discipline), (2) decompose inventory turnover (which item groups, ordering behavior, seasonal stocking), (3) quantify the levers (each day of DSO at 30 M€ revenue equals about €82k of tied-up liquidity), (4) order by impact and implementation speed (dunning in 30 days, inventory reduction in 90 days, supplier payment-term negotiation in parallel). Anyone who makes proposals without quantification or names the levers with equal priority lacks analytical steering ability.
CaseExcel and BI competence You take over a role where the monthly management reporting is produced in 14 manual Excel sheets with a 3 to 5-day lag after month-end. What 90-day plan restores it?
What a strong answer surfacesA systematic method: (1) an audit of the existing sheets and identification of the 3 to 5 most important metrics, (2) identify the source systems (ERP, CRM, payroll) and evaluate the data connection (direct vs. CSV export), (3) choose Power Query or Power BI as the platform depending on company maturity, (4) an iterative approach: first automate the top-3 reports, then expand, (5) target: bring the reporting lag to 2 days after the close. Anyone who answers a full BI implementation in 6 months without naming iteration lacks operational pragmatism; anyone who answers it stays manual but faster lacks tool maturity.
ValuesBusiness partnering How do you take critical feedback from a business partner (e.g. the head of sales, the head of operations) who calls your analysis detached from reality?
What a strong answer surfacesA learning posture: the candidate describes taking the feedback seriously (not just hearing it), reviewing the assumptions jointly with the business partner and either adjusting the analysis or communicating the assumptions more clearly. Bonus: the candidate translated the learning into a recurring practice (e.g. a monthly assumptions review with the operational functions). Anyone who describes having justified their own logic instead of taking the remark on board shows a coachability weakness that is critical in business partnering.
ValuesBusiness partnering Describe your relationship with accounting, the tax adviser and the auditor. Where do you see the interface between controlling and accounting?
What a strong answer surfacesA partnership posture: the controller uses accounting as a data source but checks the analytical consistency themselves (e.g. cost-center allocation, accruals with a plan-actual effect). Bonus: a concrete example where the candidate reworked an account structure with accounting in order to break things down better analytically. Anyone who describes accounting as a subordinate function or a mere data supplier shows a defensive posture that complicates audits and the month-end close; anyone who has no view of their own on the interface does not operate at mid level.
ValuesBusiness partnering An analysis shows an unpleasant effect (e.g. a margin erosion in a strategically important product, a performance shortfall in a newly hired sales unit). Management asks you to soften the message before it goes to the advisory board. How do you react?
What a strong answer surfacesThe ability to say no without confrontation while preserving analytical integrity: the candidate proposes to add context to the message (a root-cause analysis, an action plan) rather than altering it, and names the risks of a softened presentation to the advisory board. Bonus: the candidate cites the responsibility of the CFO function toward supervisory bodies and personal professional liability. Anyone who answers I adjust it without questioning does not protect management in a supervisory case; anyone who refuses dryly without offering an alternative lacks business partnering.
Evaluation playbook
The Financial Controller role reveals itself across three to four evaluation stages. Stage 3 (a budget or month-end case study) is the central filter: without demonstrated analytical confidence and business-partnering ability, tool skills and an academic profile have no foundation.
Stage 1: CV review
Look for: sectoral coherence (a controller from industry works differently than someone from services or SaaS), tenure (at least 24 months on previous controlling roles), concrete tool mentions (SAP CO, Lucanet, Power BI, Tableau, IDL Konsis, Jedox) and explicit responsibility perimeters. A candidate who names only reporting or analysis without detailing the tools and granularity is conspicuous. Check the academic profile: a business-administration degree with a focus on controlling, finance or accounting is standard; CIMA, CMA or the IHK certified accountant (Bilanzbuchhalter:in) is a plus for profiles with corporate experience.
Stage 2: Phone interview (30 min)
Three questions only: (1) Describe your current responsibility perimeter (forecasting, budgeting, month-end analysis, business partnering with which functions?), (2) Which tools do you use most intensively, and in which module do you feel most confident? (3) Why are you looking for a change now? (clear narrative vs. scattered). Outcome: go/no-go in a 5-minute debrief.
Stage 3: Structured interview plus case study (120 min)
Work through the 15 questions below, alternating behavioral, situational, technical, case and values (60 min). Add a case study: either building a budget from a provided data set (a revenue forecast, an OPEX breakdown, an investment cash flow) or analyzing a month-end close with unusual variances (60 min, at the whiteboard or with an Excel file). At least 2 interviewers, ideally the commercial lead or CFO plus an experienced controller. Independent scoring before the debrief.
Stage 4: References (structured check)
Call two references: a former manager (commercial lead, CFO, management) and a business partner from an operational function (sales, operations, product) who worked with the candidate. Ask both the same four questions: What is she/he strongest at? Where would you hire someone complementary? Would you hire them again tomorrow? A concrete example where they influenced a business decision with numbers? The fourth question delivers the real signal: effectiveness as a business partner, not pure number production.
How to recognize a great hire
| Trait | Below bar | On bar | Above bar |
|---|---|---|---|
| Analytical rigor | Delivers reports with no recognizable bridge analysis (volume, price, mix, special effects). Plan-actual variances are commented on without a cause breakdown. Recurring inconsistencies between data sources are not uncovered. | A structured bridge analysis on the most important metrics (P&L, margin, working capital). Quantifies drivers and checks assumptions with the operational functions. Spots and reports data inconsistencies in their own perimeter. | The analytical reference on the team: breaks down complex effects (an EBITDA bridge across multiple business units, consolidation effects) without help. Anticipates risk areas before they become a problem. Trains juniors in the bridge methodology. |
| Excel and BI competence | Uses Excel at a basic level (VLOOKUP, simple pivots). Reporting stays manual with many copy-paste steps. No own BI experience; dependent on IT for data extraction. | Advanced Excel (Power Query, Power Pivot, dynamic arrays, DAX basics). Commands at least one BI or consolidation tool (Power BI, Tableau, Lucanet, Jedox) in full autonomy. Can read SQL queries and write simple joins. | Builds complete BI dashboards with DAX measures, drill-down and self-service logic. Automates month-end reporting (Power Automate, scripts) to a 2-day lag. Structures data models for self-service and consolidation across several subsidiaries. |
| P&L and balance-sheet reading | Reads the P&L and balance sheet at a surface level (revenue, EBITDA, equity). Accruals, working-capital mechanics, the cash-flow reconciliation are not confidently commanded. HGB-IFRS differences are unknown or unclear. | Commands the P&L, balance sheet and cash-flow statement confidently; can break down an EBITDA bridge and perform a working-capital analysis. Understands the HGB-IFRS logic (leasing, development costs, revenue recognition), even if not all topics have been applied personally. | A deep understanding of accounting mechanics including consolidation (elimination of intercompany revenue, capital consolidation, currency effects). Recognizes analytical distortions from accounting options (e.g. capitalizing development costs, operating vs. finance leasing) and adjusts the analysis accordingly. |
| Business partnering | Delivers reports on request without active recommendations. Little contact with operational functions outside the reporting occasion. A defensive posture on questions about the method or the assumptions. | Active recommendations on business decisions with a clear data basis. Maintains an accessible relationship with sales, operations and management. Can explain and visualize technical topics in operational vocabulary. | A recognized financial point of reference in the company: other functions consult spontaneously to anticipate the financial impact of their decisions. Structures assumptions reviews with operational functions and trains other teams in the key concepts (contribution margin, cash-flow effect, investment ROI). |
| Business acumen | Analyses stay in financial logic (accounts, postings, balances) without a link to operational reality. Sector specifics (business model, value creation, cost structure) are not built into the analysis. | Understands the business model and the central operational drivers (customer acquisition cost, order throughput, material-cost mechanics). Links financial and operational metrics in analyses and forecasts. | Brings a genuine strategic view of the business model: recognizes levers that operational functions themselves do not see and proposes pricing, investment or structural adjustments. A concrete example: a recommendation that led to a measurable margin or cash-flow improvement. |
30 / 60 / 90 day success plan
By day 30
- An understanding of the complete reporting perimeter (month-end close, KPI reporting, the forecast cycle, the budget process) and the most important data sources (ERP, CRM, payroll, treasury)
- An audit of the existing reporting: identifying the three to five most important weak points (manual bottlenecks, inconsistencies, missing driver analyses)
- First documented 1:1s with management, the commercial lead and at least two operational business partners (sales, operations) on expectations and priorities
- Taking over the running reporting routines (month-end analysis, the KPI dashboard, the forecast update) without external help
By day 60
- First independent bridge analysis on the month-end close produced and presented to management (a plan-actual variance with broken-down drivers)
- At least two manual reporting steps automated (Power Query, Power BI or comparable); the reporting lag reduced
- The forecast cycle taken over: inputs gathered from the operational functions, assumptions documented, sensitivity bands built
- First structured recommendation to management on an analytical finding (a margin shift, a working-capital effect, an investment topic)
By day 90
- A stable month-end cadence with a max. 5-working-day lag (or an agreed target) held consistently
- The budget process prepared or already kicked off (depending on the annual calendar): timeline, templates, stakeholder mapping
- Documentation of the central reporting and forecast procedures (sources, assumptions, validation steps) completed
- A formal review with management or the commercial lead: development areas set for the following 90 days (e.g. a BI roadmap, assumptions reviews, expanding business partnering)