AI interview copilot
An AI interview copilot is software that listens to interview questions and suggests how to answer them on your screen, or that runs practice interviews beforehand. Some products do only one of these and others do both. Whether live assistance is allowed during a real interview depends entirely on the employer's rules.
A live copilot captures audio, turns the question into text, and drafts an answer outline from the question plus your resume and the job description. Whether you may use one during a real interview depends entirely on the employer's rules.
AI interviewer
An AI interviewer is software that asks interview questions, listens to or reads a candidate's answers, and sometimes asks follow-ups or scores the responses. Employers use it to screen candidates at scale, and candidates use it to practice with a mock interview built from their own resume and a job description.
Employer-run AI interviews are usually recorded, time-limited screening interviews that a recruiter reviews afterwards. Candidate-side AI interviewers are mock interviews you run on your own, built from your resume and a job description.
If an employer sends you an AI interview, read the instructions for timing, retries and rules on outside help, and practice answering aloud against a timer.
Applicant tracking system (ATS)
An applicant tracking system is software employers use to collect, organize and review job applications, including parsing resumes into structured fields. It stores candidate records and helps recruiters search and filter them, but recruiters, not the software, make the hiring decisions.
Use a simple single-column resume with standard headings, avoid text inside images, and mirror the job description's wording where it is true. An ATS organizes applications; recruiters still make the decisions.
Application autofill
Application autofill is software that fills repetitive fields on a job application form from a saved profile. Aissence's Chrome extension fills supported fields on supported applicant tracking systems for the candidate to review, and the candidate controls the final submission.
Autofill saves typing, not judgement. Check every filled field, answer the open-ended questions yourself, and confirm that your saved profile is current before you submit.
Bar raiser
A bar raiser is an Amazon interviewer from outside the hiring team who is trained to assess whether a candidate would raise the overall standard of the team they would join. The role exists to keep hiring standards consistent across teams, and bar raisers typically probe stories in more depth.
Expect behavioral questions tied to Amazon's leadership principles and deep follow-ups on your stories. Prepare examples with specific actions, trade-offs and results.
Behavioral interview
A behavioral interview asks about specific past situations ("tell me about a time you...") on the idea that how you acted before predicts how you will act in the job. Answers are judged on the situation you describe, what you personally did, and the result, so concrete examples matter more than general claims.
Prepare five or six real stories from your work and be ready to adapt each to different questions. Structure each with the STAR method and make your own actions the longest part.
Case interview
A case interview gives the candidate a business problem, common in consulting, and evaluates how they structure it, analyze data and reach a recommendation in conversation with the interviewer. The interviewer scores your reasoning and communication as much as the final answer.
Open by restating the problem and proposing a structure. Do the math out loud, keep a running hypothesis, and finish with a clear recommendation and next steps.
Competency-based interview
A competency-based interview asks questions designed to test specific skills and behaviors, such as leadership or problem solving, by asking for evidence from past experience. The competencies are usually listed in the job description, and each answer is scored against them.
Read the job description for the competencies it names, then prepare one strong story for each. Use STAR to keep stories focused.
Group interview
A group interview assesses several candidates at the same time, often through discussion or an exercise, to see how they communicate and collaborate. Interviewers watch how you contribute, listen and include others, and how you help the group reach a conclusion, not only how much you speak.
Contribute early and build on others' points rather than competing. Listen, name people, and help the group reach a conclusion.
Hiring committee
A hiring committee is a group that reviews interview feedback and makes or recommends the hiring decision, rather than leaving it to a single manager. Committee members usually read written feedback from several interviewers, so specific, well-evidenced answers carry further than a general impression.
Because the committee reads written feedback, clear, specific answers that an interviewer can quote accurately help you. Vague answers are hard to defend in the room.
HR screen
An HR screen is an early conversation with a recruiter or HR representative that checks your background, motivation, availability and compensation expectations. It decides whether you move to the next round, so clear, concise answers and a ready salary range matter more than technical depth.
Know why you want the role, your timeline and your salary range, and have two questions ready. Be concise; the aim is to move to the next round.
LeetCode-style question
A LeetCode-style question is an algorithm or data-structure problem with a defined input and output, like those on the LeetCode practice site, commonly used in technical interviews. Most reduce to a small set of patterns, such as two pointers, sliding window or graph traversal, which you can learn to recognise.
Most are variations on a small set of patterns. Learn the signal in the prompt that points to each pattern, then practice explaining your solution aloud.
Live coding interview
A live coding interview is one in which a candidate writes code in real time while the interviewer watches and discusses, usually in a shared editor such as CoderPad. The interviewer evaluates your problem solving, communication and how you respond to hints, not only whether the final code runs.
Talk through your thinking as you type. Interviewers score how you handle hints, test your code and recover from mistakes, not only whether the final answer is correct.
Mock interview
A mock interview is a practice interview that imitates a real one, run with a person, a recorded session or an AI interviewer, so you can rehearse answers and get feedback before the real interview. The most useful ones use your own resume and the actual job description, and let you repeat weak answers.
The useful ones use your real resume and the actual job description, ask follow-ups, and let you repeat weak answers. Mock interviews are standard preparation and break no employer rule.
One-way video interview
A one-way video interview is a recorded interview in which the candidate answers pre-set questions on camera on their own schedule, with no interviewer present. The employer reviews the recordings later, and the candidate usually gets a short preparation window and a fixed answer time for each question.
You usually get a short preparation window per question and a fixed answer time, often one to three minutes. Practice structured answers out loud against a timer, and test your camera and microphone before you begin.
Online assessment
An online assessment is a timed, usually automated test sent to candidates, often with coding problems, multiple-choice questions or situational judgement items, used to screen before interviews. Each platform sets its own rules on tools, notes and monitoring, so read the instructions before you start.
Read the platform rules carefully, since many online assessments are proctored and prohibit outside help. Practice under the same time limit and in the same environment.
Onsite interview
An onsite interview is the final round, a series of back-to-back interviews with several people, held at the employer's office or, more often now, as a virtual loop. Each conversation usually covers a different area, such as technical skills, collaboration and fit.
Pace your energy across the day, treat every conversation as a fresh start, and take a short break between sessions to reset. Send thank-you notes within a day.
Panel interview
A panel interview is one in which a candidate is interviewed by several people at the same time, often from different teams or levels. Panelists often have different areas of focus, such as technical depth, collaboration or fit, and they compare notes afterwards to reach one decision.
Address the person who asked the question, but make eye contact with the whole panel as you finish. Ask beforehand for the names and roles of the panel so you can tailor examples to each.
Phone screen
A phone screen is a short first-round call, usually with a recruiter, that checks basic fit, interest, salary expectations and logistics before further interviews. Its purpose is to decide whether to move you forward, not to assess you in depth, so concise, well-organized answers matter most.
Have a clear 60-second background, two reasons you want the role, and your salary range ready. Stand up if it helps your energy, and keep your resume in front of you.
Proctored assessment
A proctored assessment is a test monitored by a person or software, using the camera, microphone, screen or browser, to enforce the rules against outside help. What is monitored varies by employer and platform, and unapproved assistance can lead to disqualification.
Follow the stated rules exactly, including which tools and tabs are allowed. Unapproved assistance during a proctored assessment can disqualify you.
Reference check
A reference check is a conversation with people who have worked with a candidate, held late in the process, to confirm their experience and working style. Employers usually ask for a small number of references, so choose people who can speak to specific work and let them know to expect the call.
Ask people before listing them, brief them on the role, and send them your resume. Choose references who can speak to specific work.
Salary negotiation
Salary negotiation is the discussion, usually after a job offer, in which a candidate asks for a different salary or benefits than first offered. It can cover base pay, bonus, equity and start date, and it works best when you ground your ask in market data and a clear reason.
Research market data for the role and location, express enthusiasm, ask for what you want with a reason, and consider the whole package including equity, bonus and start date.
Sideline
Sideline is an Aissence beta feature that lets one trusted person follow your live interview session from their own browser. During the session the helper sees your shared screen and the live transcript text, and can send you short notes or code. No audio is relayed, and the helper cannot control your computer.
A helper counts as outside assistance. Many interviews forbid it, so read the interview instructions and ask the recruiter if they are unclear. You can switch the screen or the transcript off, or remove the helper, at any time.
Situational interview
A situational interview presents a hypothetical scenario ("what would you do if...") and asks how you would handle it. It tests judgement and reasoning rather than past experience, so the interviewer is listening for how you clarify the problem, weigh options and decide, not for one correct answer.
State your reasoning in order: what you would clarify, what you would do first and why, and what you would do if it did not work. If you have handled something similar, say so briefly.
STAR method
The STAR method is a way to structure a behavioral answer in four parts: Situation, Task, Action, Result. It keeps the answer focused on what happened and what you personally did, and it gives the interviewer a clear, complete story they can score and remember afterwards.
Spend little time on situation and task, most of it on your actions, and finish with a result you can name, ideally with a number. If your answer runs past two minutes, it usually contains a second story.
Stress interview
A stress interview deliberately uses pressure, such as rapid questions, interruptions or silence, to see how a candidate behaves under strain. It is used mainly for roles where composure matters, and the interviewer is observing your reaction as much as the content of your answers.
Slow down, take a breath before answering, and ask for a moment to think. Staying calm and honest scores better than an instant answer.
Structured interview
A structured interview asks every candidate the same questions in the same order and scores answers against a set rubric, to make comparisons fair and consistent. Because the scoring criteria are fixed in advance, answers that address the question directly and give specific evidence score best.
Answer the question asked, give specific evidence, and cover the competencies in the job description, because those are usually what the rubric measures.
System design interview
A system design interview asks the candidate to design a large software system, such as a URL shortener or news feed. It evaluates requirements gathering, architecture and trade-off reasoning rather than a single correct answer, and it is most common for mid-level and senior engineering roles.
Clarify requirements, estimate scale, sketch a high-level design, then go deep on the hardest part and discuss failure. Start simple and add components only when you can say why.
Take-home assignment
A take-home assignment is a work sample that a candidate completes on their own time and submits for review, such as a small coding project, analysis or written exercise. Employers use it to see real work product, so clear structure, a short explanation of trade-offs and respect for the stated time limit matter.
Confirm the time expected and the rules on outside help. Submit something small, working and well explained rather than something large and unfinished, and write a short note on your assumptions and trade-offs.
Technical screen
A technical screen is an early interview that tests the core skills of a technical role, typically through a short coding problem, technical questions or a discussion of past projects. It is usually run by an engineer, and it scores how you explain your reasoning as well as whether the code works.
Clarify the problem, say your approach before coding, and test with an example. Practice explaining your reasoning out loud, because the screen scores communication as well as code.
Whiteboard interview
A whiteboard interview is one in which a candidate solves a problem by writing or drawing on a whiteboard or digital equivalent, common for algorithms and system design. The format tests how you reason and communicate without an editor or compiler, so syntax errors matter far less than clear thinking.
Write legibly, narrate your thinking, and leave room to edit. The reasoning matters more than perfect syntax.