What Is A Technical Interview? (Coding Rubric)

A technical interview is a job interview that tests skills needed for a technical role. For software roles, it may include a coding problem, questions about your approach, and tests of your code. There is no universal format or scoring system. This sample coding rubric shows what interviewers may assess and how you can prepare with a clear plan.

Technical interviews: format, expectations, and preparation

A technical interview checks how you apply job-related skills, not only what facts you can recall. For a software role, that can mean solving a coding problem while explaining your choices. Employers set their own interview formats, so ask what to expect and review the role’s stated skills before you practice.

Coding interviews are common in software hiring, but not every technical interview is a coding test. Some include a discussion of past projects, debugging, system design, or questions about tools used in the role. A recruiter or hiring team can tell you which parts apply.

In a live coding interview, you may use a shared editor and talk through a problem as you work. In an online assessment, you may solve tasks on your own within a set time. A take-home task gives you more time but may require a written explanation or discussion afterward.

These are examples, not promises about what a specific employer will use. Ask about the format, language, tools, and expected level. Also ask whether accommodations are available if you need them. Knowing the format can help you prepare without guessing.

Coding rubric: skills assessed, scoring, and practice

A coding rubric is a set of criteria used to judge a solution and the way you reached it. Employers may not share their scoring rules, and their priorities can differ. The weights below form a sample coaching rubric, not an industry standard or a prediction of any employer’s decision.

Coding accuracy means that the solution does what the prompt asks. A candidate can earn credit for a sound approach even if time runs out before the code is complete. Still, explain what remains unfinished and why.

Problem-solving approach includes how you understand the task, choose a strategy, and respond when a test reveals a flaw. Interviewers may want to see your reasoning, not just a final answer.

Complexity describes how the time or memory used by an algorithm changes as the input grows. For example, O(n) means work tends to grow in step with the input size n. You do not need to optimize every solution at once. First make it correct, then discuss whether a faster or smaller approach is needed.

Code quality and testing cover whether another person can follow your code and whether you check how it behaves. Test a normal case, a boundary case such as an empty input, and a failure case if the prompt allows one. The right tests depend on the task.

Communication does not mean talking without pause. It means sharing the key choices behind your solution, asking focused questions, and listening to feedback. If you are unsure, say what you are assuming and ask whether that matches the prompt.

Use this rubric to spot practice gaps, not to guess an employer’s exact score. If a company publishes assessment criteria, follow those instead.

How to solve a coding problem during the interview

A repeatable process gives you a way to work through an unfamiliar problem without relying on memorized answers. It also helps an interviewer understand your decisions. The steps below are a practice guide; adjust them to the task, the interview format, and any instructions you receive.

Clarify the prompt and plan a solution

Start by restating the task in your own words. Ask about input limits, expected output, duplicates, and how to handle unusual inputs if the prompt leaves these details open. Then describe a simple plan before you code, so you and the interviewer can check that you are solving the same problem.

For example, a prompt may ask you to find a value in a list. Ask whether the list is sorted and whether it can be empty. Those details can change the best approach. Do not assume a rule that the prompt has not given you.

Write code, then test important cases

Choose data structures that fit your plan, and use names that make the code easy to read. As you write, explain decisions that affect the solution. Once it runs, test a typical input, a boundary case, and any case that might break your logic.

If you find an error, describe what the test showed and revise the code. A bug found during testing is useful evidence about your approach. It is better to show a clear correction than to ignore a failing case.

Explain complexity and trade-offs

After checking correctness, state the time and space complexity if you can. Explain what part of the code drives that cost. If there is a more efficient method, compare it with your current solution and say whether the change is worth making for the stated input size.

For instance, a method that checks each item against every other item may take O(n²) time. A hash set may help reduce lookup time for some tasks, but it also uses memory. Discuss the trade-off rather than claiming that one method is always best.

Academic preparation, practice strategy, and student experience

Coursework can build useful foundations, but a degree does not guarantee readiness for a particular interview format. Students, career changers, and working candidates can all practice the same core skills: data structures, algorithms, debugging, testing, and clear explanations. Let the role description guide which skills deserve your time.

Use a four-step plan:

1. Review the role. Note the programming language, tools, and skills named in the job description. Start with those instead of trying to study every topic.
2. Practice deliberately. Solve problems at a level that fits the role. Explain your thinking aloud, test edge cases, and record the mistakes you repeat.
3. Run mock interviews. Ask a classmate, mentor, or career adviser to use the same rubric each time. Seek feedback on correctness, reasoning, communication, and pacing, not only speed.
4. Check the interview details. Ask what format to expect, which tools are allowed, and how to request accommodations. Use your project work as evidence of skills, but be ready to explain your own contribution.

When I help students make sense of hiring steps, I encourage them to separate what a role requires from what a course or practice program promises. A coding bootcamp or interview-prep course may help you build skills, but a certificate is not automatically a degree or transferable academic credit.

Before paying for a program, check the total cost, refund terms, and any claims about job placement. If you need formal academic credit, ask the college that may accept the credit how it evaluates transfer work. For U.S. institutions, verify accreditation through a U.S. Department of Education-recognized accreditor. ABET’s Computing Accreditation Commission accredits eligible computing degree programs, not interview-preparation courses in general.

Practice case: using the rubric on a sample problem

This practice case shows how the rubric can guide feedback on a coding problem. It is an example, not a report of a specific employer’s test or a real candidate’s score. Its purpose is to show what you can observe and improve during a mock interview.

Imagine the prompt asks you to return the first repeated number in a list, or report that none exists. Before coding, ask what “first” means: the first value whose second occurrence appears, or the first value in the list that appears again later? The answer changes the logic, so clarification matters.

A workable approach is to scan the list from left to right and store values already seen in a set. When a value is already in the set, return it. If the scan ends, report that there is no repeat. This approach takes O(n) expected time and O(n) extra space for a list of n values.

A useful mock-interview review might note:

• Accuracy: Did the code return the expected value for repeated and non-repeated inputs?
• Approach: Did the candidate clarify what “first” meant?
• Complexity: Did the candidate explain the time and space costs?
• Testing: Did they check an empty list, a single value, and a repeated value?
• Communication: Did they explain assumptions and respond to a hint?

If the candidate missed a case, the next step is specific: revise the test set, correct the logic, and try a similar problem later. That is more useful than recording only whether the answer was completed.

Career pathways: using feedback to improve readiness

Interview feedback is most useful when it points to a skill you can practice. A missed test case may call for more testing practice; unclear explanations may call for mock interviews. One interview is only one assessment, and its result does not define your overall ability or future prospects.

After a mock interview or hiring round, write down:

• Which requirement or edge case you missed
• Where your plan became unclear
• Whether your complexity analysis was accurate
• What feedback or hints helped
• One action to practice before the next interview

Then connect practice to evidence. If you improve at testing, show that habit in a class or portfolio project. If you need stronger data-structure knowledge, review the relevant course material and solve focused problems. The aim is steady improvement, not memorizing a fixed set of answers.

Frequently asked questions

What happens in a technical interview?
It depends on the employer and role. A software interview may include coding, project questions, debugging, or system design. Ask the hiring team which parts to expect.

Is a technical interview always a coding test?
No. Some technical interviews focus on projects, tools, design, or role-specific knowledge. Check the interview instructions or ask the recruiter.

What does a coding interview rubric measure?
A rubric may assess correctness, problem-solving, complexity, code quality, testing, and communication. Employers choose their own criteria and weights.

Do I need to finish the coding problem to pass?
Not always. Some interviewers may give credit for a sound approach, clear reasoning, and useful tests even if time runs out. The employer decides how it scores the interview.

Should I memorize coding solutions?
Focus on understanding patterns and explaining your choices. Memorized answers may not fit the details of a new problem.

What does O(n) mean in an interview?
O(n) describes a growth pattern where the work tends to increase in step with the input size n. It is a way to discuss an algorithm’s time or space use.

What should I test in a coding interview?
Test a normal case, a boundary case, and a case that could expose a logic error. Choose tests that match the prompt and its stated requirements.

Can a bootcamp certificate replace a computer science degree?
Not automatically. A certificate and a degree are different credentials. Check the employer’s requirements and confirm with a college whether any course credit may transfer.

How can I ask for an interview accommodation?
Contact the employer or recruiter and ask about its process for requesting accommodations. The steps and available options depend on the employer and your needs.

How should I use a sample coding rubric?
Use it to guide practice and identify skills to improve. Treat its weights as coaching suggestions, and follow any assessment criteria the employer provides.

(This article was written by one of our staff writers, Nathan Sterling. Visit our Meet the Team page.)