Ask every candidate the same first round questions.
These prompts are written for a recorded interview. Ask one thing at a time so answers stay comparable. See all resources.
Write questions candidates can answer in one take.
Keep each prompt short. Avoid live-coding puzzles that need a shared editor. Ask for a walkthrough, a decision, or a past example so you can review the same signal across the pipeline.
Starter questions you can add to a Hirekal interview.
Technical interview questions are in the React, Node.js, Next.js, and senior engineer sets. These are prompts to send, not answers to study. Each role has six questions. See interview workflows.
Customer service interview questions
Difficult conversations, when to escalate, and how a reply stays clear for the customer and the next teammate.
Read the questionsCall center interview questions
Angry callers, when to transfer, hold, and how a call ends with a next step the next agent can follow.
Read the questionsRemote React engineer interview questions
Component structure, state, rendering bugs, and how a remote React team reviews work across time zones.
Read the questionsNode.js engineer interview questions
API reliability, production incidents, slow dependencies, and how a Node.js service stays understandable.
Read the questionsNext.js developer interview questions
Server versus client rendering, caching surprises, and how a Next.js app stays fast as it grows.
Read the questionsSenior software engineer interview questions
System trade-offs, production incidents, what to ship now, and how senior engineers lead design and mentoring.
Read the questionsSales representative interview questions
Discovery calls, lost deals, follow-up after a quiet buyer, and how a deal moves when more than one person decides.
Read the questionsMarketing expert interview questions
A first 30 days with a new audience, channel choice, failed campaigns, and how results get explained.
Read the questionsQuestions about these prompts.
How to use role specific questions in a Hirekal interview.
What questions should you ask in a one-way video interview?
Keep each prompt short enough for one take, and ask one thing at a time. A walkthrough, a decision, or a past example works better than a live-coding puzzle. Each role has its own page: customer service, call center, remote React engineer, Node.js engineer, Next.js developer, senior software engineer, sales representative, and marketing expert.
Should every candidate answer the same video interview questions?
Yes, for that interview. You do not have to use every prompt. Pick the ones that fit the role, then keep that set consistent.
Do these interview questions produce an automatic score?
No. The prompts are not a score. Your team watches or reads the responses and decides who moves forward.
Should a one-way question need a shared editor?
No. Avoid live-coding puzzles that need a shared editor. Ask for a walkthrough, a decision, or a past example the candidate can answer in one take.
Which roles have starter questions?
Customer service, call center, remote React engineer, Node.js engineer, Next.js developer, senior software engineer, sales representative, and marketing expert. Open the role page and use the prompts that fit.
Send the questions. Review the recordings later.
Candidates record on their own time. Your team watches the same answers before scheduling the next conversation.