Production Manager Interview Questions

The interviewer wants to see that you can run a whole growing operation, not just one part of it. Build your answer around one operation: its size and crops, who bought from you, and how you organized a season from propagation to sale. Then name one or two things you changed and what they improved.

Sample answer: "At my last job I managed a wholesale container nursery growing shrubs and perennials for garden centers, with a small crew. I planned the crop list each fall from the previous year's orders, scheduled propagation and potting so plants were ready to sell in spring, and checked inventory every week so our sales staff only promised what we had. When I saw we were losing too many plants to overwatering in one block, I split it into irrigation zones by pot size. Losses in that block dropped the next season, and we shipped more of what we grew."

Pitfalls to avoid: listing duties without saying how you did them; claiming results you can't explain; leaving out the people side, such as how you led the crew.

The interviewer wants to know that you can identify plants and work out what is affecting them before recommending treatment. Walk through the plant features and references you use, then your checks for disease, weeds and insect pests. Explain when you seek confirmation rather than guess.

Sample answer: "I check the plant's leaves, stems and growth habit against its label and a plant reference. Once I know the plant, I can compare the damage with problems that affect it. When a bench of hydrangeas started yellowing, I checked the leaves and roots for symptoms and insect signs. I also identified plants growing in the pots to see whether they were weeds. The affected hydrangeas had brown, soft roots, and the media was staying wet near a leaking drip line. I sent a sample to an extension lab for confirmation before choosing a response."

Avoid treating before confirming the plant and problem, assuming every symptom comes from pests, or presenting a guess as a firm identification.

The interviewer wants to learn how you match the coming season's crop plan to demand and growing capacity.

Explain your process in order. Start with sales records, unsold stock and customer orders. Show how you estimate the plant mix and quantities, then check growing time, available space and budget. Explain how you allow for expected losses without committing more space or money than the nursery has.

For example: "I start with confirmed orders and compare them with last season's sales and leftover stock. I use that to plan quantities by plant type, then check when each crop will need space and be ready to sell. If several crops need the same greenhouse area at once, I adjust quantities or timing before committing to them. I also check material costs against the budget and include a loss allowance based on our records. I revisit the plan when orders change."

Avoid choosing crops only because you like them, treating last year's sales as a guarantee, or overlooking space needed while crops overlap.

The interviewer wants to see how you match a crop's needs to the space and resources you have. Explain what the crop needs in light, temperature, humidity and water, the settings available to you, and the cost and timing of each. Then say how you set its care schedule.

Sample answer: "We wanted to add ferns for summer sales. They need shade, steady moisture and protection from hot afternoons. Our greenhouse space was booked with bedding plants through spring, and the open field was too sunny. I chose the shade house, since it gave the right light at a lower cost. I set up overhead mist on a timer for the hottest hours, put the ferns on a light feeding schedule, and checked moisture daily for the first few weeks before adjusting. The crop was ready on time with few losses."

Pitfalls to avoid: using one setting for every crop; ignoring cost and space; not explaining how you adjusted the schedule once plants were in.

The interviewer wants to learn how you use irrigation adjustments to solve a real watering problem in a nursery or greenhouse.

Organize your example with Situation, Task, Action, Result. Name the system, the plants and the problem you were responsible for fixing. Explain how your observations led to a change, then describe the checks that showed whether it worked. End with what you learned.

For example: "After we moved a batch of nursery pots, some stayed dry even though the drip system was running. I was responsible for checking the setup. I found emitters delivering water beside several pots instead of into them. I repositioned the lines and emitters, ran the system and checked delivery across the batch. I checked root ball moisture again after the next watering. Water was reaching the affected pots, so I left the schedule alone. I learned to check delivery after moving stock before changing run times."

Avoid assuming longer watering solves every dry spot, changing settings without checking delivery, or calling the problem fixed without checking the plants.

The interviewer wants to know you protect workers, customers, plants and the environment, and that you follow the rules. Explain how you decide to treat, how you apply, and what records you keep. Applicator licensing and record rules vary by state, so say you follow your state's requirements.

Sample answer: "I start with scouting, so we only treat when a pest or deficiency is confirmed and at a level that needs action. Before any pesticide goes out, I check the label for the crop, the rate, the protective gear and the re-entry interval. Only licensed staff apply restricted products, and I make sure sprayers are calibrated. We post the treated area and keep it closed until the re-entry time is up. For fertilizer, I base rates on soil or media tests rather than guessing. Every application is recorded with the product, rate, area, date and who applied it."

Pitfalls to avoid: treating the label as a suggestion; spraying on a fixed schedule without scouting; leaving out worker safety or records.

The interviewer wants to learn how you turn a pruning goal into sound choices for nursery plants.

Use Situation, Task, Action, Result to describe the stock, the goal, your decisions and the outcome. Spend most of the answer on your choices about timing and cuts. If you supervised a crew, distinguish your directions from the work others did. Finish with a lesson from checking the plants.

For example: "We had a batch of spring-flowering shrubs that needed shaping before sale. I was responsible for planning the pruning. I checked their growth habit and chose selective cuts after flowering rather than cutting the whole batch back hard. I demonstrated the cuts on one plant and checked the crew's first plants before they continued. The batch kept a natural shape without losing the healthy framework we wanted. Checking those first plants taught me that a demonstration was more useful than a general instruction to tidy the stock."

Avoid describing every species as needing the same cuts, taking credit for decisions someone else made, or leaving out the result.

The interviewer wants evidence that you inspect carefully and that your checks catch problems before they grow.

Use Situation, Task, Action, Result. Say what you were inspecting and why, what you noticed, how you traced the cause, and what happened after you reported or fixed it.

Sample answer: "During a routine walk-through, I noticed a small puddle of fluid under one of our machines. It wasn't on the checklist, but I wiped it up and checked again an hour later, and it was back. I followed the line and found a fitting that had worked loose. I tagged the machine, reported it to my supervisor, and maintenance replaced the fitting before the end of the shift. If it had failed during a full run, we would likely have lost most of a day."

Pitfalls: Don't claim you never miss anything. Avoid stories where you found a problem but didn't report it. Don't skip how you confirmed the cause.

The interviewer wants to learn how you make plant care advice clear enough for a customer to use at home.

Build your answer with Situation, Task, Action, Result: identify the plant and the customer's uncertainty, explain your role, describe your advice and check for understanding, then give the outcome. Include what you learned about explaining care without jargon.

For example: "A customer buying a potted shrub was unsure about watering after planting. I needed to explain how to check the root ball rather than give a fixed daily schedule. I showed them where to feel for moisture and used the plant's care label to explain its light needs. I asked them to talk me through their plan. Their answer showed they had misunderstood where to check, so I demonstrated again. They then explained it correctly. That taught me to check understanding instead of just asking whether my advice made sense."

Avoid assuming a nod means understanding, giving care advice that ignores the plant's needs, or claiming a later growing result you never saw.

The interviewer wants evidence that you test things carefully and use what you find to make them better.

Use Situation, Task, Action, Result. Explain what you tested and why, how you set up the test, what the results showed, and what you changed. End with how you measured the improvement.

Sample answer: "Customers kept saying our online order form was confusing, so I was asked to look into it. I had five coworkers who had never used the form place a test order while I watched and took notes. Four of them got stuck on the same shipping step. I suggested moving that step and rewording two labels, then ran the same test again. All five finished without help, and complaints about the form dropped over the next month."

Pitfalls: Don't describe a change made on a hunch with no test. Avoid skipping how you checked the result. Don't use jargon without explaining it.

The interviewer wants to know how you track whether work is on target and what you do when it isn't.

Answer both parts. First, describe your method for checking work: what you measure, how often, and how you get feedback. Then give one example of a time you found a problem and corrected it, using Situation, Task, Action, Result.

Sample answer: "I set a few clear checkpoints for any task, such as a draft date and a final review, and compare progress against them each week. On one project, a teammate's section was behind at the draft checkpoint. I asked what was getting in the way and learned they were waiting on data from another team. I followed up with that team, got the data the next day, and we moved the review back two days. The project still finished on time."

Pitfalls: Don't describe constant checking that sounds like micromanagement. Avoid blaming the person who fell behind. Don't skip the corrective action.

The interviewer wants to see that you keep an eye on your work area or data, notice problems early, and act on them.

Use Situation, Task, Action, Result. Describe what you were checking and how often, what signaled the problem, and the steps you took right away. Include who you told and what you did to stop it happening again.

Sample answer: "I review our inventory report every Monday. One week I saw that one item's stock had dropped far faster than usual. I checked the order records and found a duplicate order that had shipped twice to the same customer. I told my supervisor, contacted the customer to arrange a return, and asked our systems team to block duplicate orders. The return came back the following week, and we haven't seen the problem since."

Pitfalls: Don't pick a problem someone else found and you only fixed. Avoid stopping at the fix without saying how you prevented a repeat. Don't stay vague; name what you were monitoring.

The interviewer wants to see how you guide other people's work: setting direction, keeping them motivated, and helping them grow.

Use Situation, Task, Action, Result. Name who you oversaw and on what work, then give one concrete thing you did for each part: direction, motivation, and development. Finish with how the work turned out.

Sample answer: "Last year I led two newer coworkers on a project to clean up our customer records. I split the work by region and gave each person a clear weekly target. When one of them got discouraged by the slow pace, I showed them a faster way to find duplicates and pointed out how much they had already finished. I also had the other person run our weekly check-in to build their confidence. We finished a week early, and both later took on similar projects on their own."

Pitfalls: Don't describe only giving orders. Avoid vague claims like being a natural leader. Don't leave out what the workers achieved.

The interviewer wants to see that you can find the right person for a role in a fair, organized way.

Use Situation, Task, Action, Result. Describe the role you were filling, how you defined what the job needed, the techniques you used to screen and interview, and how the hire worked out. Say which technique helped most.

Sample answer: "I helped my manager hire a new team member last spring. Before posting the job, we listed the three skills that mattered most and wrote interview questions for each one. Every candidate got the same questions, and we scored the answers separately before comparing notes. We also asked the top two candidates to do a short work sample. The structured questions helped us compare people fairly, and the person we hired was working on their own within a few weeks."

Pitfalls: Don't describe hiring on gut feeling alone. Avoid any mention of personal traits that have nothing to do with the job. Don't skip how the hire turned out.

The interviewer wants to see that you think beyond today's tasks and can plan the steps to reach a bigger goal.

Name one or two objectives you set, why they mattered, and the time frame. Then explain the plan you made to reach them, how you tracked progress, and where things stand now. The Situation, Task, Action, Result structure works well here.

Sample answer: "One objective I set was to shorten the time it took new team members to work on their own, from about two months to one. I broke it into steps: write a training checklist, record short how-to videos, and pair each new hire with a buddy. I finished the checklist in the first quarter and the videos over the next six months. By the end of the year, new hires were working on their own in about five weeks."

Pitfalls: Don't list goals without a plan. Avoid objectives that were really your manager's, unless you explain your part. Don't claim the goal was fully met if it wasn't; partial progress is fine.

The interviewer wants to see that you think through the trade-offs of a decision before acting.

Use Situation, Task, Action, Result. Describe the decision, the options, and the costs and benefits you weighed, including money, time, risk, and the effect on people. Explain which you chose and how it turned out.

Sample answer: "Our team's printer broke for the third time in a year. One option was another repair, which was cheap. Another was a new printer, which cost more up front. I looked at the past year's repair bills and the downtime each breakdown caused. The repairs plus lost time were likely to cost more than a new machine over two years. I shared that with my manager, we bought a new printer, and we haven't had a breakdown since."

Pitfalls: Don't focus only on money; include time and people. Avoid a decision you made without checking the facts. Don't skip how it turned out.

The interviewer wants to see that you weigh options carefully instead of going with the first idea, and that your reasoning leads to better results.

Use Situation, Task, Action, Result. Describe the problem, list two or three options you considered, and give the main strength and weakness of each. Explain which you chose and why, then describe the impact.

Sample answer: "Our team needed a faster way to answer common customer questions. I compared three options: hiring a part-time assistant, writing a help page, or creating email templates. Hiring was quick but costly. A help page would take longer but reduce calls over time. Templates were cheap but only sped up our replies. I recommended the help page, with templates as a short-term fix. Within a few months, repeat questions fell noticeably."

Pitfalls: Don't list options without saying what you compared them on. Avoid choosing an option without explaining the trade-off. Don't leave out the impact.

The interviewer wants to see how you handle problems with many parts: how you break them down, choose a path, and follow through.

Use Situation, Task, Action, Result. Explain why the problem was complex, such as several causes or many people affected. Walk through how you found the root cause, the options you weighed, and how you put the solution in place. End with the benefit to your employer.

Sample answer: "Our monthly billing kept going out late. The cause wasn't one thing: data arrived late from two departments, and the billing software needed manual fixes. I mapped each step, timed them, and found the manual fixes took the most time. I compared hiring temporary help with automating the fixes, and we chose automation with help from our technology team. Billing went out on time for the next three months, and customers paid faster."

Pitfalls: Don't pick a simple problem and call it complex. Avoid skipping the options you considered. Don't take credit for others' work; name who helped.