General & Operations Manager Interview Questions

I run the North America business at Ridgeline Industrial, a $180M distributor of MRO supplies to the food and beverage sector. Full P&L, 340 people across four DCs, and I report to the CEO. Over the last three years I've moved on-time delivery from 87% to 96%, EBITDA margin from 9.2% to 13.1%, and I've released $14M of working capital by consolidating from four suppliers to two on our top SKU family.

Before Ridgeline I spent six years at Sylvan Manufacturing, first as director of operations at the Cincinnati plant and then as VP of ops for the two-plant Midwest region. I ran two plant turnarounds — one greenfield ramp, one distressed asset we bought out of bankruptcy — and I installed the operating rhythm that survived both.

My pattern is scale operator. I'm here because your PE thesis calls for doubling throughput on the same footprint in three years, and that is the exact problem I've now solved twice.

I read your last two investor deck excerpts that Riverstone made public, and the pattern is clear: you have a distribution asset that has scaled ahead of its operating rhythm, and the near-term unlock is the same one I lived at Ridgeline — moving the business from a founder-led sales-forward operating model to a systems-forward one without losing the customer relationships that got you here.

Two former colleagues from Sylvan now work for your parent company — one in ops at your Georgia site, one in FP&A at the fund. Both told me the same thing: the CEO backs operating decisions, the board runs a real monthly business review rather than a rubber-stamp deck, and the current management team wants a GM to lead them, not manage around them.

That combination is rare, and it matches how I want to work. I want the next ten years of my career to be inside one operating team I can build. Everything I've read tells me that team is here.

I'll go chronological and stay tight. Started as a Six Sigma black belt at Emerson right out of Georgia Tech, three years in the Chicago motors plant driving a $6.2M cost-out program on the machining line. Moved to plant engineer, then production manager, span of 42 people running the second shift.

Left for Sylvan in 2016 as director of ops at the Cincinnati plant — a distressed asset the company had just acquired. Ran the turnaround: replaced two of three superintendents, installed a daily tiered accountability meeting, moved on-time from 71% to 94% and EBITDA from negative to 11% over eighteen months. Got promoted to VP ops for the two-plant Midwest region in 2019, ran the greenfield ramp of the Indianapolis plant to steady-state in nine months against a plan of twelve.

Moved to Ridgeline in 2022 as SVP and GM for North America, full P&L, the role I hold today. Every move has been toward broader scope on the same operating problem — turning capable-but-uneven businesses into predictable ones.

Cincinnati plant, 2016. Sylvan had bought it out of a distressed sale for the specialty-alloy customer book. I inherited a facility running 71% on-time, 4.8% quality escape rate, negative EBITDA on $62M of revenue, and a senior operations team that had turned over twice in three years.

First thirty days I did no reorganization. I stood on the floor across every shift, did the customer-quality complaint teardowns with the plant engineer, and built a one-page diagnostic that named eight specific loss buckets — machining downtime, changeover time on the two flagship lines, supplier quality on incoming stock, and a scheduling handoff between the ops manager and the shipping lead that was costing us four hours a day.

Next ninety days I installed a daily tiered accountability meeting, replaced two of three superintendents with internal promotions I'd identified during the diagnostic, and moved the scheduling handoff into a single 6 a.m. gemba walk.

Twelve months in: on-time 94%, escapes 0.9%, EBITDA 11%, and I had a leadership bench I could promote from.

Sylvan Midwest, 2020. The VP of quality had been in the seat six years, was well-liked by the plant floor, and was the person most senior operators had learned from. He was also, measurably, no longer at the level the business needed — quality escape rate had drifted from 1.1% to 3.4% over eighteen months and he was resisting the SPC and PLM investments the CFO had already funded.

I did not replace him quickly. I spent thirty days on the ground running the escape data with him line by line, gave him a specific set of expectations and a ninety-day plan, offered coaching support through an outside quality director I trusted, and made the CEO and CHRO aware from day one.

At day sixty it was clear the plan was not landing. I told him directly, offered a transition into a technical fellow role that let him keep dignity and equity, and ran the search for his replacement in parallel. He accepted the fellow role and stayed two more years mentoring the plant leads.

Escape rate was back to 1.0% within eight months of the new VP starting. I still send him a Christmas card.

Ridgeline, Q3 2024. Our largest customer — a national bottler — asked for a 6% price concession across the top eighteen SKUs in exchange for a three-year commitment. Sales wanted to say yes. The CFO wanted to say no. The customer was 22% of North America revenue and 31% of gross-margin dollars.

I ran the analysis with the head of pricing and the CFO's team in one week. The 6% ask would have taken the customer's gross margin from 34% to 28%, still profitable, but the same terms cascading to our next three customers would have taken North America GM from 31% to 26% and blown the EBITDA plan by 220 basis points.

I met the head of sales one-on-one before the pricing committee, walked him through the cascade math, and offered him a package he could sell the customer: a 3% price concession, a two-year commitment, a service SLA on emergency deliveries, and a joint 2027 innovation roadmap. He carried it, the customer signed, and margin held.

The head of sales and I still run a weekly one-on-one. That's the standoff pattern I use: run the numbers first, then negotiate.

Early in my career as a plant director I stayed on the shop floor too long. I made the classic new-GM mistake of solving the day's fires personally because I trusted my own diagnostic more than I trusted my superintendents' — which was a self-fulfilling loop, because they never built the muscle to diagnose without me.

I fixed it deliberately when I moved into the Midwest VP role. I built a written weekly cadence with each plant manager that let me stay out of daily operations except for a 6 a.m. Monday call and a monthly business review. I resisted answering their operational questions in real time and instead pushed the decision back with a coaching question. The first six months were slower than I liked, and I had to sit on my hands more than once.

The tradeoff was worth it. By month twelve, both plant managers had built accountability meetings I would not have designed, and one of them is now running a $400M business elsewhere. But I had to relearn what my job actually was, which was building the operating rhythm, not running it.

Sylvan Midwest, FY2021 Q1. I had committed a 12% throughput lift on the Indianapolis line by end of Q1 in the annual plan. We came in at 7%. The CFO ran the variance to EBITDA at $1.8M for the quarter.

The miss traced to two structural calls I owned. First, I under-scoped the ramp curve on a new automated packaging cell — I'd planned six-week ramp when the OEM history said ten. Second, I lost two senior operators in the same month to a competitor and did not have a written succession bench that could absorb the loss without a productivity drag.

I put the miss in writing to the CEO and the board on the Monday after the quarter closed rather than waiting for the review. Fix was two parts: I rewrote the ramp assumption in the FY22 plan against OEM data, and I built a documented succession bench for every seat two levels down.

Q2 came in at 14%, and we finished FY21 at 9% throughput lift against a 12% target — still a miss, but the underlying rhythm was fixed. The board respected the transparency more than the miss cost us.

The Cincinnati turnaround. Not because of the numbers — 71% to 94% on-time and negative EBITDA to 11% is real, but I've had bigger deltas. Because the plant survived, three-hundred people kept their jobs, and the leadership team I built is still running that plant six years later after two GMs above me have come and gone.

Specifically I am proud of two internal promotions I made during the diagnostic — a first-shift lead who is now the plant manager, and a scheduling clerk who is now the ops planning director. Both were invisible to the prior GM. I saw them because I stood on the floor before I made org changes, and I bet on them because the diagnostic data said their line-level performance was already a standard deviation above the mean.

That is the outcome I'm proudest of because it compounds. Every business I've run since has benefited from that lesson — the bench is already in the building, and the first GM move is to see it, not import it.

Inside operations, one scope wider. In the next two years I want to prove out the value-creation plan for this business — the throughput doubling and margin expansion in the deal thesis — and build a leadership team that outlasts my tenure in the seat.

In three to five years I would like to be the COO of a multi-BU platform, either at this company if the platform scales, or at a comparable PE-backed asset if the board's build-versus-buy math takes us in a different direction. Long-term I am probably a CEO — a small-cap public company or a founder-led business at the point of professionalization. That is a seven-to-ten-year arc, and the intervening years are what determines whether I get there.

None of that requires me to leave operations to advance. If anything, the roles I want next require me to spend more time closer to the floor, not less. That is why I keep choosing operating seats over staff seats.

Two reasons, both structural. First, Ridgeline is now three years into the plan I signed up for and the value-creation levers I was hired to pull are largely pulled — the working capital release is done, the on-time and margin lifts are through the initial curve, and the next twenty-four months of that business are steady-state execution against a maturing plan. That is a good problem, but it is not the problem I do best.

Second, my CEO announced last quarter that the business is being prepared for a sale in mid-2027 rather than a bolt-on-growth thesis. That is the right call for the shareholders, and I have told him I will hand the business to the buyer in strong shape, but the multi-year build-out I want to run next needs a fresh mandate on a business at the start of its curve, not the middle.

Your business is at the start of its curve. That is the reason I applied, and it is the reason I want the offer — I want to spend the next five years building, not preparing for exit.

Days one to thirty: no reorganization, no new initiatives. I run a written diagnostic across three lenses — commercial (top ten customers, top ten SKUs, pricing waterfalls, sales pipeline conversion), operational (asset utilization, quality escape rate, on-time, safety incident rate, working capital cycle), and people (org chart two levels down, top-performer census, open-seat map, engagement pulse). I meet every direct report one-on-one for ninety minutes, and I do a listening tour with the top ten customers, the top five suppliers, and the CFO.

Days thirty-one to sixty: a written diagnostic memo to the CEO and the board sponsor with the three or four value-creation levers I see and the sequencing of the moves I would make. I install the operating cadence I want — daily tiered meeting on the floor, weekly S&OP, monthly business review with a standard deck, quarterly board review — even before I make org changes.

Days sixty-one to a hundred: the first senior-seat call, the first cost-out or margin-lift initiative kicked off, and a clear FY plan handoff with the CFO. By day 100 the CEO should be able to describe the operating rhythm without me being in the room.

Daily, three metrics: safety incident count from the prior twenty-four hours, on-time-in-full at the customer-order level, and cash — daily cash balance and the AR aging bucket that moved. Those three run the tiered accountability meeting at 8 a.m. across every site.

Weekly, three metrics: gross margin by product family or SKU cluster (updated against plan), sales pipeline conversion by stage (compressing quote-to-cash), and headcount plan-versus-actual with open-seat status. Those three run the operating team meeting on Monday.

Monthly, the full P&L walk with the CFO plus a customer-health scorecard (top-twenty customers, NPS or churn signal, service level), plus a talent scorecard (top-performer retention, backfill rate, engagement pulse). The monthly business review sequences these three so the board sees the same view we see internally.

The reason to over-invest in cadence early: every predictable business runs on cadence, and every unpredictable business runs on heroics. My job is to move the business from the second to the first.

Top-down. I start with revenue growth versus plan and versus prior year, and I split it into price, volume, and mix contributions — because those three have completely different operational implications. Then gross margin at the same three levels, and specifically the delta between reported GM and standard-cost GM, because that variance is where operational leakage hides.

SG&A next, split between fixed and variable and between people cost and third-party spend. Ratio checks: SG&A as a percent of revenue against the same-year peer set, headcount productivity as revenue per employee against a two-year trend, and any single vendor category that is more than 5% of SG&A.

Then EBITDA and free cash flow, with a specific look at the working-capital cycle — days sales outstanding, days inventory, days payable — because those three lines are the biggest short-term operating lever available to a new GM. I close with a one-line hypothesis about the two or three moves I would make in the next quarter and what they would deliver.

I run three lenses in sequence. Strategic: does the capability sit on the critical path of the business's value-creation plan for the next five years, or is it commodity infrastructure that will be table stakes across the industry inside three years? If it is critical-path, build bias; if it is commodity, buy bias.

Financial: unlevered IRR, payback in years, and NPV against the company's cost of capital. I model three scenarios — base, downside, upside — and I stress the downside against the current EBITDA base to see whether a missed ramp would blow the covenant. I insist on a third-party sanity check on the build cost from either an OEM or a competing internal team.

Operational: capacity, uptime, and integration into the operating rhythm. A build gives control but costs three years of leadership attention; a buy gives speed but introduces vendor risk and often locks in a data model I regret in year four.

The decision usually resolves on strategic first, financial second, operational third. Reversing that order is where GMs get in trouble.

I decompose it into three buckets. Core capabilities — the work that touches customers or that carries our differentiating IP — is permanent, full stop. Retention risk on this bucket is my biggest single lever, and the compensation and coaching investment goes here.

Cyclical demand — the work that flexes with volume — is a mix of permanent and temporary, sized to the demand floor plus 10%, with temp labor absorbing anything above that. The right ratio is usually 65/35 or 70/30 permanent-to-temp on cyclical work; below 60% permanent, quality drops and safety incidents rise; above 80%, the P&L can't absorb a 15% volume drop without a layoff.

Non-core, non-strategic — janitorial, security, some IT operations, some indirect procurement — is outsourced to specialists with SLAs, on the theory that a vendor whose core business is the work will outperform an internal team where it is a distraction.

I revisit the mix quarterly against the demand signal and the labor market. Fixed answers age poorly.

I walk in five layers. Safety first — I look for pinch points, blocked emergency exits, missing PPE, and the visible near-miss board if there is one. If there isn't one, that is the first data point.

Then flow — I trace the raw material from receiving to shipping and count how many touches, how many staging areas, and how often the material changes hands. Excessive staging is inventory hiding operational problems.

Then people — I look at the daily-management board at each work center and read what is on it. I stop and ask two operators what their top issue is today; the answer tells me whether the tiered accountability meeting is real or theater.

Then quality — I look at the visible SPC charts, the last three shift-turnover notes, and the customer-complaint teardown board. I want to see the process for capturing an escape, not just the number.

Then leadership — I ask the plant manager what he would do if I gave him $200K unrestricted this quarter. The answer tells me what he cares about and how well he knows the business.

Same shape at every scope I've run: a small, tight leadership team — five to seven direct reports, no more — organized by the two or three operating levers that carry the plan. In a distribution business that is ops, commercial, and finance. In a manufacturing business it is plant ops, supply chain, commercial, and quality. I resist adding "chief of staff" or general roles that dilute accountability.

Composition: I want a balance of internal promotes and outside hires. Two-thirds internal keeps continuity with the operating rhythm and the customer relationships; one-third outside brings new operating standards. Anything more than half outside in the first two years and I've usually created a culture shock the business can't absorb.

Cadence: I meet each direct report one-on-one weekly for forty-five minutes with a written agenda, and the leadership team meets Monday for ninety minutes on the operating scorecard. Individual development happens off-cycle, not inside the operating meeting. That separation matters.

I resist the answer "when the current system is broken," because the current system is always broken. The right question is whether the business is at a scale, complexity, or integration inflection where the current system is the binding constraint on the next twenty-four months of the plan, and whether the leadership team has the bandwidth to run the implementation without the business drifting.

I insist on three artifacts before I approve. A written business case with quantified benefits, phased over eighteen to thirty-six months, that survives a downside scenario. A written change-management plan with an executive sponsor, a full-time internal PM, and a training investment sized at 20% of the systems budget. A written go/no-go criterion for each phase gate.

Timing: I never run a major systems implementation and a senior-seat turnover in the same twelve-month window. The business absorbs one big change per year; two is where you find yourself explaining a missed quarter to the board.

Same protocol every time. Notification cascade first: shift lead notifies plant manager, plant manager notifies me within thirty minutes if it is a lost-time or recordable incident, I notify the CEO and the CHRO the same day. If it is a serious injury or fatality, the CEO and general counsel are on the call within the hour and the response follows the crisis plan.

Root-cause investigation second: within seventy-two hours a written five-why or fishbone analysis led by the plant safety manager, with the operating team and a member of my leadership team present. I attend serious-injury investigations personally.

Systemic response third: any corrective action from the RCA is put into the operating standard, communicated across sites within the week, and audited at the next monthly business review. I include the safety leading indicators — near-miss reports, safety observations closed, training hours — in the daily and weekly cadence.

The reason to be disciplined: safety leading indicators predict every other operating metric. A plant that is losing on safety is losing everywhere else within two quarters.

I listen first and take notes. Board pushback usually contains information I don't have — a customer signal, a competitive dynamic, a prior operating regime's history — and my first job is to extract it before I defend the plan.

Then I decompose. If the pushback is on sequencing, I usually adjust; the board sees the calendar in a way an incoming GM can't. If the pushback is on a specific move — say, the senior-seat call I've scoped in day sixty — I ask for the specific concern and offer either data I can bring back within a week or a compromise on timing. If the pushback is on the plan's economic thesis, I don't compromise; I ask for a working session with the deal partner and the CFO to reconcile the model.

The reason to differentiate: sequencing is negotiable, moves are usually adjustable, and economics are load-bearing. Blurring those three categories is where new GMs cave to a board on the wrong axis and then can't deliver.