Restaurant general manager: job description, interview questions, and screening workflow

The safe-sounding hire is someone with ten years of restaurant management experience at a well-known chain. That resume line often hides the exact gap that sinks this hire. A chain GM operates inside a system someone else built: a corporate playbook for staffing ratios, a fixed vendor list, a district manager one call away when a decision gets hard. An independent restaurant has none of that. The person you're hiring has to build the system, not execute one, and defend a decision when the floor and the numbers disagree with no one above them to escalate to. A resume full of chain experience can't tell you whether someone has ever actually done that. This guide is built to screen for ground-up ownership and judgment under real ambiguity, not for years of title alone.

What a restaurant general manager actually does at a small, independent restaurant

At a chain, a general manager works from a corporate operating manual: fixed staffing ratios, an approved vendor list, a district manager who reviews major decisions and absorbs a real share of the risk. At an independent restaurant or a small local group, none of that exists unless the GM builds it themselves. They own the P&L, they choose (and negotiate with) every vendor, and when a decision gets hard, the next person up the chain is the owner, who hired this person specifically so they'd stop being the one making every call.

That's also what separates this role from the two it sits above. A restaurant shift manager runs the floor for a block of hours and hands off to the next one. A kitchen manager owns the back of house across every shift: food cost, the BOH schedule, and compliance. A general manager owns the whole operation across both, plus everything neither of them touches: the full P&L, hiring and holding accountable the shift and kitchen managers themselves, vendor and landlord relationships, and the restaurant's standing in the community it depends on. At a very small restaurant, one person sometimes holds all three jobs while the business gets off the ground. If you're hiring a dedicated GM, the posting should say so clearly, because a real GM candidate expects real ownership, not a bigger title on the same shift-lead job.

The core responsibilities, in practice:

• Owning the restaurant's full P&L: revenue, labor cost, food cost, and margin, not just one shift's numbers or one week's food order
• Hiring, developing, and when necessary removing shift managers, kitchen managers, and key staff, since there's usually no separate HR function to lean on
• Negotiating with vendors and landlords, and managing the relationships that determine your cost structure and your lease terms over time
• Setting and adjusting pricing, hours, and menu strategy in partnership with the owner, based on real performance data, not gut feel alone
• Building the operating systems (scheduling logic, opening and closing procedures, a training program) that a chain would hand you and an independent restaurant has to invent
• Representing the restaurant in the community: local partnerships, handling a public reputation issue, being the face of the business when the owner isn't there
• Reporting directly to the owner, and being the last line of defense before a problem reaches them

At a single-location independent, this is the hire that determines whether the business is a sustainable operation or a collection of good shifts held together by the owner's constant attention. That's worth naming clearly when you post the role, because it's a fundamentally different pitch than "manager wanted, restaurant experience required."

Job description you can post today

Copy this, then adjust the specifics (your concept, your team size, your ownership structure) to match your restaurant.

Restaurant general manager
[Restaurant name] is looking for a general manager to own the full operation: the P&L, the team, and our standing in the community. This is a fit for someone who's built systems from scratch before, not just executed someone else's.

What you'll do
Own the restaurant's P&L, including labor and food cost against margin targets. Hire, develop, and manage our shift managers, kitchen manager, and key staff. Negotiate with vendors and manage our landlord relationship. Set pricing, hours, and menu decisions in partnership with ownership, backed by real performance data. Build and maintain the operating systems (scheduling, training, opening and closing procedures) that keep the restaurant running without you standing over every shift. Represent the restaurant in the community and handle reputation issues directly.

What we're looking for
Real experience owning a P&L and building operational systems, ideally at an independent restaurant or small group rather than only inside a corporate chain's playbook. A track record of hiring, developing, and when necessary letting go of managers, not just crew. Comfort negotiating with vendors and landlords. Someone who makes a defensible call when there's no one above them to ask, and who communicates that decision clearly to the owner after the fact, not just when it goes well.

Schedule
[Insert expected hours and on-call expectations, e.g. a mix of floor presence during peak shifts and dedicated time for ownership-level work]

[Insert pay and any bonus or profit-share structure, per your company's policy and any applicable state salary transparency requirements]

10 interview questions, and what a good answer sounds like

1. Tell me about a system, process, or policy you built from scratch, not one you inherited or executed from a corporate manual.

This is your ground-up ownership check. A strong answer names something specific they actually built: a training program, a scheduling logic, a vendor negotiation process, and describes the reasoning behind it. A weak answer describes executing an existing system well, which is a real skill but not this one, or can't produce an example that wasn't handed to them.

2. Walk me through the last time your food cost or labor cost came in worse than expected for a period. What did you find and what did you change?

You're checking for real P&L ownership, not just awareness that these numbers exist. A strong answer names a specific diagnosis (a supplier price shift, a scheduling inefficiency, a menu item underperforming) and a specific structural fix. A weak answer stays vague ("we tightened up") or can't produce a real example, suggesting they've reported on these numbers without truly owning them.

3. Two of your key managers, your kitchen manager and a shift manager, disagree on a decision that affects both of their areas. How do you handle it?

This tests how they manage across peers who report to them, not just how they manage a single team. A strong answer describes getting both perspectives directly, making a clear call with reasoning both can understand, and following up to confirm it actually got implemented. A weak answer avoids picking a side, defers the decision back to both of them, or lets the tension sit unresolved.

4. Tell me about a negotiation with a vendor or your landlord that didn't go the way you initially wanted. What did you do?

Listen for a real story with actual leverage and tradeoffs, not a generic "we found a compromise." A strong answer names what they asked for, what they got, and what they gave up or accepted instead. A candidate who's never had to negotiate anything meaningful with an outside party may not be ready for the vendor and lease relationships this role actually owns.

5. If I asked you to improve this restaurant's margin by a specific amount over the next 90 days, where would you actually start?

This is a strategic thinking question, and it should produce a short list of high-leverage moves with real reasoning, not ten ideas at once. A strong answer picks two or three drivers (labor scheduling, a specific menu item's cost, a vendor renegotiation) and names the tradeoffs and risks of each. A weak answer lists everything they can think of with no prioritization, or defaults to "cut costs" with no specifics.

6. Describe how you keep visibility into what's actually happening across shifts you're not personally working.

This tests execution discipline at a scale beyond one shift. A strong answer names an actual operating cadence: specific reports they review, a regular check-in structure with their managers, a way of spotting a problem before it becomes a crisis. A weak answer relies on "I just know my restaurant," with no real system behind it.

7. Tell me about a time you had to get something done through someone you had no direct authority over, a vendor, a landlord, a city inspector, a neighboring business.

This is your influence question. A strong answer names a specific ask, understands what mattered to the other side, and secures a concrete commitment. A weak answer escalated immediately to a legal threat or a higher authority as the first move, without attempting to work the relationship directly.

8. Tell me about a time you had to hire, develop, or let go of a manager who reported to you, not a line-level hire.

Managing managers is a different skill than managing a shift, and this checks whether they've actually done it. A strong answer shows real judgment: what they saw, how they coached first if applicable, and a clean, respectful handling of the actual decision. A candidate with years of GM-adjacent titles who's never actually managed another manager is a real flag worth probing further.

9. How do you find out you're wrong about something before it gets expensive, when you're the last person to check your own decisions?

This surfaces whether they actively invite dissent or run the restaurant purely on their own instincts. A strong answer names a real habit: soliciting pushback from their managers, tracking a specific leading indicator, a story where they changed course because someone below them was right. A weak answer can't name a time they changed their mind, or treats disagreement from staff as something to manage rather than learn from.

10. Why an independent restaurant or a small group, instead of a bigger role at a corporate chain?

This surfaces whether they understand what they're actually signing up for: less structure, less safety net, and full ownership of decisions no one else will make for them. A strong answer names something real: the appeal of building something themselves, direct ownership over outcomes, more say over the concept. A candidate who describes wanting more resources and more corporate support may be a harder fit for the ambiguity this role actually requires.

A scorecard you can score candidates against

Ten questions only help if everyone interviewing is listening for the same thing. Score every candidate on the same six signals instead of comparing gut feelings about who sounded most in command.

How to screen restaurant general manager candidates without losing a week to it

This is also the one restaurant hire where the interview room itself works against you. A candidate who's spent years managing a room, calming customers, and presenting numbers with confidence is demonstrating a real GM skill, not proving they have the judgment to run your restaurant when you've stopped watching. Our general manager interview questions post goes deeper on why a smooth live interview can't tell the difference on its own, and why pairing it with a verified track record or a structured assessment matters more for this hire than almost any other. Restaurant hiring also runs on some of the highest turnover of any industry, which is exactly why a rushed GM hire made under pressure tends to cost more than the vacancy it was meant to solve. See our piece on the real cost of restaurant turnover for the data behind that pattern.

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, so you can build a process around what this role actually rewards: independent judgment and P&L ownership, not restaurant vocabulary or a well-known chain's name on a resume.

A workflow that fits a single-location or small-group independent restaurant:

• Resume screening weighted toward independent ownership, not just tenure. A long resume at a well-known chain looks reassuring, but it can hide someone who's never built a system from scratch. Look for evidence of independent operational ownership specifically, and flag it for a closer look regardless of the brand names involved.
• A one-way video interview built around the ownership and judgment questions. Ask 2-3 of the scenario questions above, especially the system-building question and the vendor negotiation question, on video before you commit an in-depth, in-person conversation. You'll hear how someone actually reasons through ambiguity, not just how confidently they talk about restaurants in general.
• A leadership assessment for your finalists. Have finalists work through Truffle's leadership skills questionnaire. It rates observable behaviors across competencies like strategic thinking, execution discipline, and influence, which map directly onto the margin-planning, cross-team, and vendor-facing parts of this job that a standard interview struggles to surface.
• A working session with your real numbers before an offer. Bring your finalist in to review an actual week of your P&L or a real vendor situation and talk through what they'd do. This is where you see whether their judgment holds up against your restaurant specifically, not a hypothetical one.

Our resume screening and one-way video interview tools handle the first two steps in one place, with AI surfacing your strongest matches against the criteria you set. You review the evidence and make the call on the hire that runs your entire operation.

What the leadership skills questionnaire surfaces for this role

The leadership skills questionnaire rates observable leadership behaviors rather than scoring a single right-or-wrong exam, which fits a role this broad. Three competencies matter most for a GM specifically, distinct from the delegation and conflict signals that matter most for a shift or kitchen manager.

Strategic thinking. A strong signal is someone who picks a few high-leverage drivers when asked to move a number, names their assumptions, and anticipates the side effects on staffing or the guest experience. A weak signal is a scattershot list of ideas with no real prioritization, which predicts a GM who reacts to everything and improves nothing.

Execution discipline. A strong signal is a lightweight but real operating cadence: specific reports reviewed, a regular structure for checking in with their managers, visibility into shifts they're not personally working. A weak signal is relying on instinct alone, with no actual system for catching a problem before it becomes a crisis.

Influence. A strong signal is getting a vendor, landlord, or outside party to commit to something specific by understanding what mattered to them, not by escalating to authority as a first move. A weak signal is an inability to produce a real example of moving someone they didn't directly manage.

The questionnaire surfaces these tendencies as structured signal against the expectations you set for the role. You still make the call, and pairing it with the system-building and negotiation questions above gives you more than one read on the same person.

Common hiring mistakes for this role

Over-weighting a well-known chain's name on the resume. Chain experience can mean someone executed a corporate playbook well, which is a real skill but not the one this role needs most. Screen directly for evidence they've built a system from scratch, not just run one someone else designed.

Confusing shift-lead or kitchen-manager readiness with GM readiness. Being excellent at running a floor or a kitchen doesn't predict whether someone can own a full P&L, negotiate with a vendor, or manage the managers they used to work beside. If you're promoting internally, test those specific, higher-altitude skills directly instead of assuming the title comes with the capability.

Skipping a real working session with your own numbers. A candidate can talk fluently about margins and vendor negotiation in the abstract. Watching them reason through your actual P&L or a real vendor situation is the closest thing to the real job you can test before an offer, and it's worth the extra step.

Moving too slowly and losing a strong candidate to the next offer. GMs who can actually own a P&L and build systems from scratch are hard to find and don't sit available for long. A process that drags across several weeks reads as disorganized to exactly the kind of decisive operator you're trying to hire.

Writing a posting that blurs GM with a bigger shift-lead role. A vague "manager wanted, must be a leader" posting undersells the P&L and vendor-facing ownership this role actually carries and pulls in candidates expecting a shift-management job. Be specific about the scope in the first few lines so the person who applies understands what they're actually signing up for.

Filling the roles this GM will manage directly? See our restaurant shift manager and kitchen manager hiring guides for job descriptions, role-specific interview questions, and screening workflows for the layer of leadership below this one.