Mock Interview

One-on-one meeting questions for junior engineers at a startup

A one on one meeting (1:1) is time for a junior engineer and their manager to clarify expectations, discuss problems, and plan development. It is not a hiring interview or an oral exam. When startup priorities change, use the meeting to agree on what matters, where support is needed, and who will act next rather than reciting every ticket.

Prepare a shared agenda before the meeting

Bring one useful example, one uncertainty, and one request. Link the relevant ticket or pull request so you can discuss the work without reconstructing it from memory. Managers should read those notes and add context or feedback, not take over the whole agenda.

GitLab's 1:1 guidance recommends contributions from both participants and private access to meeting notes. Agree on access and expectations at your company. Put ordinary delivery updates in the team tracker; keep sensitive feedback in an appropriately restricted space.

Do not hold an outage, security concern, or urgent delivery blocker until the next 1:1. Use your team's escalation process when action cannot wait.

Copy this suggested 30-minute agenda

Adjust the timing to the issue, and choose a few questions below rather than trying to cover all twenty-four.

Date / engineer / manager: [names and date]

0–3 minutes — Check-in: workload, energy, and anything affecting the week.

3–10 minutes — Priorities: desired outcome, trade-offs, and decisions needed.

10–20 minutes — Review and blockers: [ticket or PR], what I tried, and the help requested.

20–27 minutes — Feedback and growth: one concrete example and one learning step.

27–30 minutes — Commitments: decision / owner / due date / evidence of completion.

End with a recap even if one important topic takes most of the meeting. Move unfinished items forward deliberately.

Process questions: how work is planned, reviewed, and shipped at your company

  1. How does the company turn a customer problem into a planned engineering task, and who sets its acceptance criteria?
  2. Before I start implementation, which design or product decisions need review and who can approve them?
  3. Which checks, reviews, and release approvals must a change pass before it is shipped to users?
  4. After a release, how do we monitor the change, decide whether it worked, and handle rollback if needed?

Questions about priorities and decision-making

  1. Which of my current tasks matters most for the release, and what should I pause if urgent work arrives?
  2. What does “done” mean for this ticket beyond code being merged?
  3. When a customer request conflicts with planned work, who should decide which takes priority?
  4. Which implementation decisions can I make independently, and which need a design discussion first?

Questions about code review and quality

  1. What should my pull request include so a reviewer can understand the change and its risks?
  2. How long should I wait for a review before asking another reviewer or raising the delay?
  3. How should I distinguish blocking review comments from optional suggestions on this team?
  4. Could we walk through one recent review comment so I understand the reasoning, not just the requested edit?

Questions about blockers and asking for help

  1. When should I stop investigating alone and ask for help on an unfamiliar service?
  2. Who is my backup contact when my usual mentor is unavailable?
  3. What context should I include in a help request: expected behavior, logs, attempts, and a specific question?
  4. If missing access or an external dependency blocks me, who can escalate it and what should I do meanwhile?

Questions about feedback and growth

  1. In my recent change, which decision showed good judgment, and which would you approach differently?
  2. What one habit would most improve the clarity or maintainability of my next pull request?
  3. Which small project would help me learn a relevant part of the system without taking on unsupported responsibility?
  4. What evidence should we review next month to tell whether I am making progress?

Questions managers can ask the junior engineer

  1. What felt unclear this week that you thought you were expected to understand already?
  2. Where did waiting for a decision, review, or access interrupt your work?
  3. What support would help you try the next step yourself rather than have someone take over?
  4. What should I change about how I explain priorities or give feedback?

Listen before solving. Agree on the problem and the kind of support needed; more supervision is not automatically the right response.

Leave with owners, not vague intentions

GitLab's suggested agenda format distinguishes requests for help and actions for each participant. You can use a simpler follow-up record:

Decision: [what we agreed and what is deferred].

Engineer: [next step], by [date], recorded in [ticket or PR].

Manager: [support or decision], by [date].

Next check: [when we will review the result].

For example, the engineer writes a PR risk summary while the manager arranges a reviewer. At the next meeting, check what happened before adding more commitments. Move shared work actions to the tracker without copying private feedback into public tickets.

Keep interview practice separate from your manager 1:1

If you are separately preparing for a hiring interview, choose a role or paste a valid job description on the homepage. Answer by voice or text, complete an evaluation, then review the feedback.

That is job-interview practice, not a dedicated manager 1:1 simulator. It cannot replace your actual manager conversation, agree on company priorities, or resolve a workplace blocker. Use the agenda and questions here directly with your manager.

Preparing for a job interview as well?

For separate job-interview practice, choose a role or paste a valid job description on the homepage. Answer by voice or text and review feedback after completing an evaluation.

Start interview on the homepage