Free resource

The interview questions pack

The questions that come up again and again, grouped by type, each with a short note on what the interviewer is really after. Save this page and skim it the night before.


How to use this: don't memorize scripts. For each question, know the one point you want to land and one real example. Read our full guides on the blog, and let Poisely back you up live.

The opener

  • Tell me about yourself. Present, past, future: who you are now with one achievement, the experience that built you, why you want this role. 60 to 90 seconds.
  • Walk me through your resume. A narrative, not a readout. Connect each step to where you're headed.
  • Why are you looking to leave / why now? Stay positive about the past, frame it as moving toward something, not running away.
  • Why this company? Show you did the homework. Name something specific about their product, team, or mission.
  • Why this role? Connect the role's core need to what you genuinely want to do more of.

The classics

  • Why should we hire you? Mirror the role: name its two or three needs, prove each with evidence, tie it back to them.
  • What's your greatest strength? Pick one relevant to the role and back it with a concrete result, not an adjective.
  • What's your greatest weakness? A real one that isn't core to the job, plus the concrete work you're doing on it.
  • Where do you see yourself in five years? Show ambition that fits the role's path; you want to grow, not job-hop.
  • What are your salary expectations? Give a researched range, or deflect to learning more about the role first if it's early.
  • Why is there a gap in your resume? Be honest and brief, then redirect to what you bring now.

Behavioral (use STAR)

Situation, Task, Action, Result. Spend most of your time on the action and end with a measurable result.

  • Tell me about a time you disagreed with a coworker. Show you resolve with evidence and stay professional.
  • Tell me about a time you failed. A real failure, owned, with the durable lesson it taught you.
  • Tell me about a project you're proud of. Your specific contribution and the impact, with a number.
  • Tell me about a time you led without authority. Taking ownership of an outcome that wasn't strictly your job.
  • Tell me about a time you had to learn something fast. Your method for getting up to speed, and the result.
  • Tell me about handling competing priorities or a tight deadline. How you triaged and communicated, not just that you worked hard.
  • Tell me about receiving difficult feedback. That you took it well and changed something concrete.
  • Tell me about a time you went above and beyond. Initiative that created real value.

Remote and working-style

  • How do you structure your day? Give your actual system, not "I'm disciplined."
  • How do you communicate across time zones? Lead with async defaults: written updates with full context, recordings for complex topics.
  • How do you stay motivated working alone? Point to a system: weekly goals, progress tracking, check-ins you initiate.
  • What's your backup if your internet fails? A concrete plan, hotspot, nearby wifi, early warning to the team.
  • How do you build trust with remote teammates? Camera on, responsiveness, reliability, a little non-work connection.

Situational

  • How would you handle a conflict with your manager? Seek to understand first, raise it directly and privately, focus on the work.
  • What would you do in your first 90 days? Listen and learn, build relationships, find an early win.
  • How do you handle tight deadlines with limited resources? Prioritize ruthlessly, communicate trade-offs early.
  • How do you prioritize when everything is urgent? Impact versus effort, and confirm priorities with stakeholders.
  • A customer or stakeholder is unhappy. What do you do? Listen, acknowledge, own the next step, follow through.

Technical and screening

  • Walk me through how you'd approach [problem]. Clarify first, state your approach and its trade-offs before diving in.
  • What's a technical decision you're proud of, and why? Show you reason in trade-offs, not absolutes.
  • How do you keep your skills current? Specifics: what you read, build, or follow.
  • Describe a bug or problem you debugged. Your systematic process, not just the fix.
  • How do you handle code review or feedback on your work? Collaborative, ego-free, focused on the outcome.
  • For data and annotation roles: how do you handle an ambiguous guideline? Follow the rule, flag genuine ambiguity rather than guess, value accuracy over confidence.

Your turn to ask

Never say "no questions." Have two or three ready:

  • What does success look like in this role in the first 6 to 12 months?
  • What's the hardest problem the team is working on right now?
  • How does the team balance shipping speed with quality?
  • What do you enjoy most about working here?

Walk in with backup

Knowing the questions is half of it. Poisely listens during the real interview and quietly shows and speaks the perfect answer in your earbud, so you stay sharp even when one catches you off guard.

Try Poisely free No card needed. Works on any remote interview.