Finance and data analyst interview prep
Finance exports, reconciliations, currencies and month-end processes.
Free questions
technical
An export writes amounts like 1.234,56. How do you load them correctly?
A strong answer covers
- Convert with the source culture, e.g. Change Type with locale de-DE.
- Don't replace commas and dots by hand; thousands separators break that.
- Check a sample of large values after conversion.
Avoid
- Find-and-replace on separators
- Using the machine's default locale
data quality
How would you reconcile bank transactions against the ledger in Power Query?
A strong answer covers
- Standardise keys first: dates, amounts rounded to cents, references trimmed.
- Use a full outer join, or left and right anti joins, to list unmatched items on each side.
- Match on a composite key (date + amount + reference) and review partial matches separately.
- Produce a reconciliation table with status columns for review.
Avoid
- Matching on amount alone
- Not handling duplicates on either side
technical
How do you calculate each cost centre's share of total spend?
A strong answer covers
- Group by cost centre with the sum of spend.
- Compute the grand total in its own step: List.Sum of the grouped column.
- Add a share column dividing each total by the grand total.
- Decide whether shares are fractions or percentages and format accordingly.
Avoid
- Typing the total in
- Multiplying by 100 and then formatting as a percentage too
requirements
Month-end deadlines are tight. How do you make your Power Query process dependable?
A strong answer covers
- Build checks that run on every refresh: totals vs source, row counts, unmatched keys.
- Keep a documented, ordered step list with clear names.
- Test the query on last month's data and on a deliberately messy sample before close.
- Agree cut-off times and what happens if a source arrives late.
Avoid
- Manual tweaks each month
- No validation before publishing numbers
technical
Explain banker's rounding and when it matters.
A strong answer covers
- Number.Round rounds halves to even by default: 2.5 becomes 2, 3.5 becomes 4.
- Accounting rules may require away-from-zero rounding; specify RoundingMode.AwayFromZero.
- Round at the agreed point (line or total) to avoid reconciliation differences.
Avoid
- Assuming 2.5 always rounds to 3
Loading more questions…