Non-Engineering Role Interview Questions (2026)

Marketing manager interview questions

Marketing manager interviews hinge on whether you can connect spending to outcomes. Interviewers have met plenty of candidates who can describe campaigns; they're hiring the one who can explain why this channel, what you'd cut when the budget shrinks, and how you knew something worked. That's commercial judgment, and it's what separates managers from coordinators.

The fastest way to stand out is to talk about what you chose not to do. Anyone can list channels. A manager explains trade-offs: why brand over performance here, why you killed a campaign early there, why you said no to a tactic the leadership team loved. Trade-off stories prove you think like an owner of the budget.

Here's how the evaluation typically works, the questions grouped by theme, and a framework for campaign answers that makes your judgment visible.

What hiring managers are scoring

• Strategy before tactics. Do you start from audience and positioning, or jump straight to "we should do TikTok"?
• Measurement honesty. Can you distinguish metrics that indicate revenue impact from numbers that merely look good in a deck?
• Budget reasoning. Given less money, what survives? Given more, where does it go and why?
• Cross-functional credibility. Marketing touches sales, product, and finance — can you describe negotiating with them?
• People management. For manager roles, expect questions about coaching specialists and handling underperformance.

The question bank, grouped

Strategy: "Walk me through how you'd build a go-to-market plan for a new product." "How do you decide between brand investment and demand generation?" Sketch a structure aloud: audience, message, channels, measurement — in that order.

Execution: "Tell me about a campaign you're proud of, end to end." "Describe a launch that went sideways and what you did mid-flight."

Measurement: "A channel is driving lots of leads but sales says they're junk. How do you investigate?" This tests whether you understand funnel quality, not just volume.

Management: "How do you set goals for a content person versus a performance marketer?" "Tell me about giving hard feedback to a direct report."

The campaign post-mortem framework

For any "tell me about a campaign" question, use this five-part shape. It forces you past storytelling into judgment:

1. Goal. The business outcome, stated plainly — pipeline, retention, awareness in a segment.
2. Audience and insight. Who you targeted and the specific belief about them that shaped the work.
3. Choices. The two or three decisions that mattered, including what you deliberately excluded.
4. Signals. What you watched while it ran, and what you adjusted in response.
5. Verdict. What worked, what didn't, and what you'd do differently. A real post-mortem always includes a regret.

Common mistakes

• Reciting channel lists when asked for strategy.
• Claiming success with engagement metrics and no line of sight to business impact.
• Taking sole credit for obviously cross-functional work — interviewers probe for this.
• No failure story. A marketer who claims nothing ever flopped hasn't been measured properly.

FAQ

How do I prepare for a case-style prompt like "plan a launch with a small budget"? Think out loud. State assumptions, pick one audience segment rather than spraying, and explain what you'd measure to decide whether to scale. The reasoning is the answer.

Should I bring a portfolio? For brand or content-leaning roles, yes — but frame each piece with goal and outcome, not just the creative. Beautiful work with no stated objective reads as decoration.

If your background is more commercial than creative, the sales interview guide pairs well with this one — the pipeline vocabulary overlaps more than people think. Rehearse your post-mortem stories with mock interview practice before the real panel.

Sales interview questions

Sales interviews are auditions. The interviewer is imagining you in front of their customers while you're still in front of them — which means how you handle the conversation matters as much as what you say. Expect to be evaluated on discovery instinct, objection handling, pipeline discipline, and whether you close the interview itself with a next step.

Strong sales candidates treat the interview like a discovery call. They ask about the team's sales motion, the ICP, where deals stall — before pitching themselves. If you spend the whole hour talking about yourself, you've just demonstrated the exact habit that loses deals.

Here's what gets scored, the questions grouped by stage of the sale, and a framework for the objection questions that trip up most candidates.

What hiring managers actually score

• Discovery skill. Do you ask layered questions and listen, or pitch features at the first opening?
• Pipeline hygiene. Can you describe how you build, qualify, and forecast — not just that you "hit target"?
• Objection handling. Do you get defensive, or do you get curious?
• Resilience with specifics. Loss stories with real lessons, not "everything works out in the end."
• Coachability. Especially for earlier-career roles, managers bet on people who take feedback fast.

Bring your real numbers — attainment, deal sizes, cycle length — because vague claims get probed. Never inflate them; sales leaders verify, and one embellished figure poisons everything else you said.

The question bank, grouped

Prospecting: "Walk me through how you'd build pipeline in a new territory with no inbound." "What does your first week look like here?"

Discovery and process: "How do you qualify a deal out?" "Tell me about a deal you chased too long." That second question is a trap for people who can't qualify — have an honest answer.

Objections: "The prospect says your competitor is cheaper. What do you say?" "They love the demo but won't move. Now what?"

Closing and resilience: "Tell me about the deal you're proudest of and the one that still stings." "Why did you lose your last big one?"

A framework for objection answers

Whether it's a live role-play or a "what would you say" question, use four moves:

1. Pause and validate. "That's a fair concern" buys you a second and lowers the temperature.
2. Diagnose before responding. Ask what sits behind the objection. "Cheaper" can mean budget trouble, a negotiation ritual, or a genuine value gap — and each needs a different reply.
3. Reframe around their stated priorities. Anchor on what they told you mattered, not on your feature list.
4. Advance or exit honestly. Suggest a concrete next step — or qualify the deal out and say why. Interviewers respect a candidate who knows when to walk away.

Notice the pattern: curiosity first, persuasion second. That order is what senior sellers do instinctively.

Common mistakes

• Talking for twenty minutes without asking the interviewer a single question about the role's reality.
• Claiming quota attainment you can't explain deal by deal.
• Bad-mouthing a previous employer's product or pricing — it signals how you'll talk about theirs someday.
• Ending the interview without confirming next steps. It's the easiest close you'll ever get, and skipping it is noticed.

FAQ

There's a mock cold call or pitch exercise. How do I prep? Practise opening with relevance rather than a script: one observation about their world, one question. If it's a pitch of their own product, spend more time on who buys it and why than on memorising features.

My numbers were middling. Do I hide them? No. Own them, then diagnose them — what you changed in your process, what the trend looked like after. Self-aware honesty beats evasive polish in every sales interview I've seen.

Moving up-market or into revenue leadership? The marketing manager guide covers the demand-generation side of the same pipeline conversation. Rehearse the role-play with mock interview practice — objection handling only feels natural once it's been said out loud a dozen times.

UX designer interview questions

UX interviews in 2026 are portfolio interviews. The conversation, the whiteboard exercise, the app critique — all of it orbits one question: can you explain the thinking behind your design decisions? Beautiful screens open the door; articulate reasoning about users, constraints, and trade-offs is what gets you hired.

Interviewers are hiring your judgment, not your deliverables. A polished case study with no visible reasoning reads as decoration. A messier project where you explain why you killed your favourite idea after usability testing — that's the candidate who gets the offer. Process honesty beats outcome polish every time.

Here's what gets evaluated, the questions grouped by interview format, a structure for case-study walkthroughs, and the mistakes that make strong designers look junior.

What interviewers are scoring

• Problem framing. Do you start from a user and business problem, or from a solution you fell in love with?
• Research instinct. How do you learn what users need — and how do you handle having no research budget?
• Iteration honesty. Did the design evolve? Can you show what changed and what evidence drove each change?
• Collaboration. How you negotiate with engineers on feasibility and with product on scope.
• Craft. Yes, visual quality still matters — but as the floor, not the ceiling.

The questions you'll face, by format

Portfolio walkthrough: "Take us through a project." Expect interruptions — the interruptions are the interview. "Why this layout?" "What did users struggle with?" "What would you do differently?"

Whiteboard / design exercise: "Design a way for users to do X." They're scoring how you scope, what assumptions you state, and whether you ask about constraints before drawing.

App critique: "Pick an app you admire and critique it." Have one ready — and critique something you genuinely use, with specific friction points, not generic praise.

Behavioural: "Tell me about a time an engineer said your design couldn't be built." "Describe a time research contradicted your instinct."

The case-study narrative structure

Structure each portfolio story in five beats, and rehearse a two-minute and a ten-minute version of each:

1. The problem. Who hurt, how you knew, and why the business cared.
2. The constraints. Timeline, tech limits, stakeholder landscape. Constraints make your decisions legible.
3. The turning points. The two or three moments where evidence changed your direction — a test, an insight, a constraint that forced invention.
4. The outcome. What shipped and how you knew it worked, stated honestly — qualitative feedback counts.
5. The reflection. What you'd do differently. Never skip this; it's where seniority shows.

Common mistakes

• Showing final screens with no visible process — no sketches, no failed directions, no reasoning.
• Claiming sole credit for team work. Interviewers probe "what was yours?" and inconsistency here is disqualifying.
• Presenting research as a ritual ("we did five interviews") without saying what it changed.
• No story about a design that failed or got cut. Immaculate portfolios read as curated, not candid.

FAQ

I have no commercial projects yet — can personal work carry a portfolio? Yes, if the thinking is real. Redesign something you actually use, do genuine usability tests with real people, and show the evidence honestly. Fabricated "client work" gets spotted fast.

How do I handle the design exercise if I get stuck? Narrate the stuck-ness: "I'm torn between two directions; here's the trade-off I'd test first." Thinking aloud under uncertainty is exactly the job.

If your work spans screens and platforms, the mobile app interview guide covers the platform constraints your interviewer may probe. Rehearse the walkthrough — especially surviving interruptions — with mock interview practice.

Teacher interview questions

Teacher interviews in 2026 come down to four things: can you keep children safe, can you run a calm classroom, can you show that students actually learned something, and do you reflect on your own practice. Everything else — subject knowledge, qualifications, enthusiasm — is assumed before you walk in. The panel is listening for judgment, not passion speeches.

The single biggest scoring dimension is safeguarding instinct. Panels ask scenario questions about disclosure, neglect concerns, and boundary situations to see whether you know when to act, who to tell, and why you'd never promise a child secrecy. Get this wrong and nothing else on your scorecard matters.

So prepare in that order: safeguarding first, classroom management second, evidence of learning third. Let's walk through each.

What the panel is really scoring

Most teaching interviews use a rubric, even if nobody shows it to you. The categories are remarkably consistent across schools:

• Safeguarding and professional boundaries — do you know reporting routes, and do you default to the child's welfare?
• Behaviour and classroom culture — do you have a system, or just a personality?
• Assessment and progress — can you describe how you know a class understood, not just what you delivered?
• Differentiation — what changes in your lesson for the student who's struggling, the one who's ahead, and the one learning English?
• Reflection — can you talk about a failure without defensiveness?

The questions you'll actually face

Safeguarding: "A student tells you something worrying and asks you not to tell anyone. What do you do?" "You notice a colleague being alone with a student behind a closed door. Walk me through your thinking." These have right answers: reassure without promising secrecy, record factually, report to the designated safeguarding lead the same day.

Classroom management: "A lesson is derailing ten minutes in. What do you do?" "How do you handle a student who refuses to work?" They're testing whether your response is consistent, proportionate, and focused on the learning rather than the power struggle.

Impact: "Tell us about a lesson that didn't land. What did you change?" "How do you know your students are progressing?" This is where vague answers die — you need a concrete example.

A framework for lesson-story answers

Use five moves, in this order, for any "tell us about a lesson" question:

1. Context. One sentence. Year group, topic, and what made this class particular.
2. Objective. What students were supposed to know or do by the end.
3. Action. The two or three decisions that mattered — not a minute-by-minute retelling.
4. Evidence. How you checked learning: exit tickets, questioning, the quality of written work.
5. Adjustment. What you did differently next time. This final step is where strong candidates separate themselves.

Rehearse three stories that fit this shape — one success, one failure you fixed, one behaviour challenge — and you can answer most of the interview.

Common mistakes

• Promising a hypothetical child confidentiality in a safeguarding scenario.
• Describing behaviour management as "building rapport" with no system underneath.
• Talking about what you taught instead of what students learned.
• Blaming the class, the timetable, or last year's teacher for a lesson that failed.

FAQ

How do I prepare for a demo lesson? Ask about the class in advance, plan one clear objective, and build in a mid-lesson check for understanding so you can visibly adapt. Panels score adaptation higher than polish.

I trained recently and lack stories. What do I do? Placement stories count. So does tutoring, coaching, or volunteering — as long as you frame them with the five moves above rather than apologising for your experience level.

If you're moving into education from another field, the edtech interview guide covers the product side of the same world. And if nerves are the problem, rehearse your three stories out loud with mock interview practice until the structure is automatic.

Internship interview questions

Internship interviews are not smaller versions of real job interviews — they're a different exam. Nobody expects you to have done the job. They're scoring trajectory: how fast you learn, how you respond to feedback, whether your curiosity is genuine, and whether you'd be a net positive on a team that's investing time in you. Potential, coachability, and preparation — that's the rubric.

The candidates who win internships turn coursework into evidence. "I don't have experience" is a losing frame; "here's a project where I taught myself something hard and shipped it" is the same biography told correctly. Every student has raw material — the skill is mining it.

Here's what interviewers actually score at this level, the questions you'll face, a framework for project stories, and the mistakes that make smart students look unprepared.

What interviewers are scoring

• Learning agility. Can you describe teaching yourself something nobody assigned you — and how you went about it?
• Coachability. How did you respond the last time someone told you your work wasn't good enough?
• Genuine interest. Do you know what this company actually does, and can you connect it to something you care about?
• Initiative. Clubs, side projects, part-time jobs, volunteering — anything where you chose to build rather than just attend.
• Communication. Can you explain a technical or complex thing plainly? Interns who can write and speak clearly get real work.

The questions you'll face

The openers: "Tell me about yourself." Have a sixty-second version: what you study, the thread of interest that runs through your choices, and why this role is the logical next step. "Why this company?" requires specifics — a product, a mission, a talk someone from the team gave.

Evidence questions: "Tell me about a project you're proud of." "Describe a time you had to learn something fast." "Tell me about working in a team where not everyone pulled their weight."

Coachability probes: "Tell me about harsh feedback you received." "What's the hardest thing you've failed at?" They want the aftermath — what you changed — not the wound.

Logistics disguised as questions: "What do you hope to get from this internship?" Have a real answer; "experience" is not one.

The project-story framework

For any project or coursework question, use five moves:

1. What it was. One sentence, plain language.
2. Your specific part. Not "we built" — what you did.
3. The hard part. Where you got stuck and how you got unstuck. This is the heart of the answer.
4. What you'd improve. Shows you evaluate your own work.
5. The bridge. One sentence connecting it to the role you're interviewing for.

Common mistakes

• Apologising for lacking experience. State what you have done; let them judge sufficiency.
• "I'm a hard worker" and "I'm a fast learner" with no story attached. Claims without evidence are noise.
• Team project stories where your contribution can't be identified.
• Knowing nothing about the company beyond its homepage headline.

FAQ

What if I genuinely have no projects to talk about? You have more than you think: a paper you went deep on, a job where you fixed a process, an event you organised. If truly nothing exists, build something small now — two weeks of self-directed work is a legitimate story.

Should I ask questions at the end? Always. Ask what past interns shipped, how mentorship works, and what distinguishes interns who get return offers. It signals you're evaluating the learning opportunity, not just collecting a line for your CV.

Many internships are remote now — the remote work interview guide covers the questions that come with those. Practise your stories out loud with mock interview practice, and track every application in the job tracker — internship seasons move fast and deadlines collide.