Operations Analyst

You'll sit inside engagement teams of three or four, reporting to a senior consultant but talking to clients from week one. Nobody here builds a model in isolation and hands it over — you'll be in the room when your analysis gets challenged, which is the fastest way to get good at it. Fair warning: we argue about chart axes, and we lose entire afternoons to it.

Make sure every claim Bailey Hart puts in front of a client is one we can defend under questioning. You'll build the models, clean the messy client data, and find the pattern that explains the symptom — then say so plainly, even when it's inconvenient for the story the team had already started telling.

• You'll build the financial and operational models that sit under every diagnosis.
• You'll wrangle client data that arrives as fourteen spreadsheets with three different definitions of “revenue.”
• You'll design the charts and tables that go into final findings — clarity over decoration, always.
• You'll benchmark client performance against sector data and flag where the comparison is genuinely unfair.
• You'll sit in client interviews and take the notes that later turn out to matter.
• You'll tell a senior consultant when their hypothesis isn't supported by the numbers. This is the job, not a side quest.
• You'll maintain the internal benchmark library so nobody rebuilds the same analysis twice.

• 1–3 years in analytics, finance, consulting, or a data-heavy operating role.
• Real spreadsheet fluency — not “I know VLOOKUP,” but comfort restructuring a bad dataset without complaining much.
• Curiosity about why a business works, not just how its numbers move.
• Precision in writing. A caveat placed badly is worse than no caveat at all.
• Polish and English, both solid.
• Bonus: SQL, Python, or a genuine opinion about how a table should be formatted. We have those opinions here — the site itself came from a 108™ Supply template, so the bar for “that's close enough” was set uncomfortably high before you arrived.