Interview Guides · Aaron Ong

Interview guides

5 quick reads. Practice with the coach.

Guide

How to Answer “Tell Me About Yourself”

This is usually the first question, and most people answer it by reading their resume out loud. They already have your resume. What they don’t have is you.

Resumes don’t hire people. People hire people. Use this question to show how you think, what you care about, and who the team gets if they hire you.

The shape: present, past, future (60 to 90 seconds)

  • Present: what you do now, and what you enjoy about it.
  • Past: one or two experiences that explain how you got here, and what they taught you.
  • Future: why this role is the natural next step.

Make it yours

A list of titles sounds like everyone else. Add one or two of these:

  • Your philosophy of work. For example: “I don’t think a process is done until it runs without me.”
  • How you learn. Do you take things apart, read everything, ask a lot of questions?
  • What life outside work teaches you. Chess can teach strategy. Team sports teach communication. Music teaches patience.

A good test: what would you say if you couldn’t mention your title or your company? Whatever comes out is closer to the real answer.

Template

“Right now I’m a ___ at ___, where I spend most of my time on ___. The part I enjoy most is ___.
I got here through ___. That taught me ___, and it’s still how I approach my work.
Outside of work I ___, which has taught me ___.
I’m excited about this role because ___, and I think my experience with ___ could help your team with ___.”

Example

“Right now I’m a customer support lead at a small software company. Most of my day is solving problems nobody has a playbook for yet, and that’s the part I love.
I started on the phones. I noticed we answered the same ten questions every day, so I built a library of reply templates the whole team ended up using. That taught me to fix the system, not just the ticket.
Outside of work I coach my niece’s soccer team, which has taught me a lot about patience and explaining things simply.
I’m excited about this role because you’re growing fast, and I’d love to help build a support process that grows with you.”

Notice it doesn’t list every job. It tells a short story with a point.

Common mistakes

  • Going too long. Aim for 60 to 90 seconds, then stop. They’ll ask follow-ups.
  • Starting from the beginning. Start with now.
  • Memorizing it word for word. Know your three beats, then say it a little differently each time. It should sound like you talking, not reciting.
  • Being someone else. Don’t play the version of you that you think they want. Show up as yourself. The right team will be drawn to the real you.
Practice it

“Help me write my ’Tell me about yourself’ answer, then let me practice saying it.”

Practice now →
↑ Back to top
Guide

How to Answer Behavioral Questions

“Tell me about a time you...” These questions are about your past, because how you handled things before is the best window an interviewer has into how you’ll handle things on their team. Every role gets them, from engineering to nursing to retail.

The good news: a handful of stories can prepare you for almost all of them.

Use STAR

  • Situation: where you were and what was going on. One or two sentences.
  • Task: what you were responsible for.
  • Action: what you did. This is the biggest part. Say “I,” not just “we.”
  • Result: what changed. Use a real number if you have one: time saved, money, people, units.

Then add one more line: what you learned. People often skip it, and it’s often what interviewers remember.

Build your story bank

Write down 5 stories before your interview. Most questions will fit one of them:

  1. A hard problem you solved
  2. A conflict or disagreement with a teammate or manager
  3. A failure or missed deadline, and what you learned
  4. A time you led something or went beyond your role
  5. A time you had to learn something fast

One story can answer many questions. A conflict story can also be a leadership story or a communication story.

Example

Question: “Tell me about a time you disagreed with your manager.”

Situation: “My manager wanted to roll out a new process on Monday, and I’d found a step that kept failing in testing.”
Task: “I owned testing, so it was my job to flag it.”
Action: “I asked for 15 minutes, showed him the failures, and offered two options: launch with a workaround, or wait two days for a real fix.”
Result: “We chose the two-day fix, and it launched smoothly.”
Learned: “Disagreeing goes better when you bring data and options, not just a no.”

About a minute. Clear, specific, honest.

Tips

  • Use real stories only. Don’t make one up or stretch the numbers. Follow-up questions find the cracks, and honesty is part of what they’re hiring.
  • Your failure story can be a strength. Pick a real failure, own it without blaming anyone, and spend most of the time on what you changed afterward.
  • Keep it short. Aim for one to two minutes. If they want more, they’ll ask.
  • It’s okay to pause. “Let me think of a good example” is a perfectly good sentence.
  • Match the story to the job. Reread the posting. If it says “fast-paced and cross-functional,” have a story ready that shows exactly that.
Practice it

“Run a behavioral interview with me. Ask one question at a time and coach my answers using STAR.”

Practice now →
↑ Back to top
Guide

How to Answer Technical Questions

A technical interview isn’t a trivia test. It’s a window into how you think when you don’t have all the answers yet. The candidates who stand out aren’t always the ones who know the most. They’re the ones who make their thinking easy to follow.

The 5-step pattern

  1. Repeat the question in your own words. “So you want me to design a bracket that holds 50 pounds and fits in this space. Is that right?” It buys you a few seconds and catches misunderstandings early.
  2. Ask clarifying questions. What are the constraints? What matters most: cost, speed, safety, simplicity? Asking good questions is part of the job.
  3. Think out loud. Say what you’re considering and why. “My first idea is X. The risk is Y, so I’d check Z.” A quiet minute followed by a perfect answer tells them less than a messy thought process they can actually see.
  4. Check in along the way. “Is this along the lines of what you’re looking for?” It keeps you from going down a rabbit hole built on a wrong assumption.
  5. Land it. Sum up your answer, name one trade-off, and say what you’d do next if you had more time.

When you don’t know

Never guess or bluff. It costs you trust. Try this instead:

“I’m not sure, but here’s how I’d approach it. I’d start by ___, and I’d want to talk to someone on the team who knows ___. My best reasoning right now is ___.”

Then actually reason it out. “I don’t know” on its own is a dead end. “I don’t know, and here’s how I’d find out” shows them how you’d act on day one.

If you freeze

Pause. Breathe. It’s okay to say, “Give me a moment to think.” Silence feels long to you and normal to them. If your mind goes blank, name it: “I’m a little nervous, let me back up.” Once you say it out loud, your brain can switch back into problem-solving.

Example

Question: “This part keeps failing in the field. How would you find out why?”

  • Clarify: “How often is it failing, and does it fail the same way each time?”
  • Think out loud: “I’d gather the failed parts and look for a pattern: same batch, same supplier, same conditions.”
  • Trade-off: “I could patch the symptom fast, but I’d want the root cause so it doesn’t come back.”
  • Next step: “I’d test my top theory with a small experiment before changing the whole process.”

Swap in your own field. A nurse, a software engineer, and a sales rep all get “how would you solve this?” questions. The pattern is the same.

Remember

They want you to succeed. Most interviewers are hoping you’re the person who can help their team. Treat them like a teammate working the problem with you, not a judge.

Practice it

“Ask me a technical interview question for my role, then coach me on how clearly I explained my thinking.”

Practice now →
↑ Back to top
Guide

Why Cramming the Night Before Doesn’t Help (and What to Do Instead)

It’s the night before your interview, and you’re tempted to stay up reviewing every topic that might come up. I get it. It feels productive, and it quiets the worry for a moment.

But an interview isn’t a final exam. You can’t learn a field in one night, and they aren’t testing whether you memorized a textbook. They want to see how you think, how you communicate, and whether you’d be good to work with. All of that gets harder when you’re tired and anxious.

Why cramming backfires

  • It feeds the nerves. Every topic you review reminds you of another one you haven’t. You go to bed feeling less ready, not more.
  • It costs you sleep. Your clearest thinking comes from a rested mind. Tired, it’s harder to pause, listen, and reason out loud.
  • It pulls you toward reciting. Trying to remember facts word for word makes you sound like you’re reading. Interviews reward conversation.
  • It’s the wrong prep. Most of what they’ll ask is about you: your experience, your stories, your choices. You already know that material. It just needs a light review.

The night-before plan (about an hour, then stop)

  1. Reread the job posting. Underline the 3 things they seem to need most.
  2. Look over your stories. Match one real example to each of those 3 needs. Don’t memorize them. Just remind yourself they exist.
  3. Say your “Tell me about yourself” out loud once. Present, past, future. Then let it go.
  4. Write down 3 questions to ask them. For example: “What are the biggest challenges your team is facing right now?”
  5. Get the logistics ready. Outfit, directions or video link, charged phone, water, a copy of your resume.

Then close the laptop. Do something that reminds you it’s okay if you don’t get this job: dessert with a friend, a walk outside, planning your weekend. You are more than one interview.

If there’s a topic you really don’t know

Don’t spend the night on it. Prepare one honest sentence instead:

“I haven’t worked with that much yet, but here’s how I’d get up to speed quickly...”

Said calmly, that often lands better than a shaky, half-memorized answer.

The real prep happened earlier

Your experience, your projects, the problems you’ve solved: that’s what you’re bringing into the room. One night won’t change it much. A rested, calm version of you will show it best.

Tonight’s checklist

  • Posting reread, 3 needs underlined
  • 3 stories matched to those needs
  • Intro said out loud once
  • 3 questions written down
  • Logistics ready
  • Something kind for yourself
  • In bed on time
Practice it

“My interview is tomorrow. Help me make a short, calm prep plan for tonight instead of cramming.”

Practice now →
↑ Back to top
Guide

How to Mentally Prepare and Calm Nerves Before an Interview

Almost everyone gets nervous before interviews, including people who’ve done a lot of them. Nerves usually mean you care. The goal isn’t to make them disappear. It’s to keep them from running the show.

Start with “Why am I nervous?”

Ask yourself that, and answer honestly. Usually it’s something like:

  • “I really need this job.”
  • “I’m afraid I’ll freeze or look dumb.”
  • “I don’t feel good enough for this role.”

Naming the fear takes away some of its power. Fear is information, not an enemy. Once it’s named, you can answer it: “If this one doesn’t work out, I’ll keep going.” “If I freeze, I’ll pause and ask for a moment.” “They invited me because something in my background stood out.”

Change the frame

  • It’s a conversation, not an interrogation. The interviewer is a person, maybe overworked, hoping you’re the one who can help their team. Treat them like a future teammate.
  • You’re interviewing them too. You’re both finding out if there’s a fit. When it’s real, everyone wins.
  • Attract, don’t chase. Don’t play the person you think they want. Show up as yourself. Confidence comes from being honest, not from being perfect.
  • It’s practice either way. However it goes, you’ll learn something about interviewing and about what you want.

Fill your cup before you walk in

An hour or so before:

  • Move. Take a short walk or stretch.
  • Breathe. A few slow breaths, letting each exhale run a little longer than the inhale.
  • Connect. Text or call someone who cares about you.
  • Reflect. Write down three things you’ve done that you’re proud of. Look how far you’ve come.
  • Be grateful. Name one thing you’re thankful for today, job or no job.

You want to walk in feeling safe, connected, and ready to create, not running on empty.

During the interview

  • Pause. Silence feels long to you and normal to them. “Let me think about that for a second” is a great sentence.
  • Name it if it spikes. “Sorry, I’m a little nervous. I really want to get this right.” Saying it out loud lets your mind move on to the problem, and most interviewers will relax with you.
  • Ask a question. “What are the biggest challenges your team is facing right now?” Turning the focus to them calms you and shows you care.

A simple pre-interview script

Say this to yourself before you start:

“I’m prepared enough. I’m here to have a real conversation and see if this is a fit. If I don’t know something, I’ll say so and reason it out. However it goes, I’ll learn from it.”

After

Plan something kind for yourself afterward, whatever happens. Then jot down what went well and what you’d change. That turns every interview into progress.

Practice it

“I have an interview coming up and I’m nervous. Help me figure out why, and help me get calm and ready.”

Practice now →
↑ Back to top