MyInternships.in
13 QUESTIONS · JUNIOR TO SENIOR · WITH ANSWERS

Online Assessments (HackerRank, CodeSignal, Karat) Interview Questions and Answers

How the online assessment stage actually works — HackerRank and CodeSignal scoring, the Karat interview format, SQL assessments, take-home assignments and the debugging environments that catch candidates out.

11 junior2 mid-level0 senior

How to use this set

Every question below is written the way an interviewer actually phrases it, followed by a model answer you could say out loud in 30–60 seconds, and — where it helps — the reason the question is asked and the trap most candidates fall into. Questions are tagged Junior, Mid or Senior so you can skip to your level.

This is one of 9 topic sets in the complete Internship Prep interview questions guide. Work through the fundamentals first, then the services your target role actually uses.

1
Junior level

What is a CodeSignal score and what counts as good for an internship?

Answer: CodeSignal reports a General Coding Assessment score from 300 to 850, derived from how many of four tasks you complete correctly and how quickly. Most companies that screen on it set their bar between 600 and 700; 750+ clears essentially every internship threshold.

Why interviewers ask this: The four tasks rise in difficulty, and the last is often not solvable in the time left. Banking tasks 1 to 3 cleanly usually beats gambling the clock on task 4 — partial credit exists for passing test cases, so submit something that runs rather than leaving an elegant half-finished attempt.

2
Junior level

How do I raise a CodeSignal score from around 600 to 750+?

Answer: Almost always by going faster on tasks 1 and 2, not by getting stronger at task 4. Practise implementation-heavy string and array simulation problems until they take five minutes rather than fifteen, and keep a snippet file of your language's parsing idioms.

Why interviewers ask this: The GCA rewards speed on the easy half. Candidates plateau because they train hard algorithms while losing ten minutes to fiddly index handling in task 2. Time yourself; if task 1 takes more than eight minutes, that is the thing to fix.

3
Junior level

How is a HackerRank OA usually structured for internships?

Answer: Typically two to four problems in 60 to 90 minutes, sometimes with multiple-choice CS-fundamentals questions and occasionally a SQL section. Scoring is by hidden test cases, so partial passes give partial marks.

Why interviewers ask this: Read the constraints before choosing an approach: HackerRank states n explicitly, and n ≤ 10⁵ rules out O(n²) immediately. Many failures are timeouts on a correct algorithm, not wrong answers.

4
Mid level

What SQL shows up in a HackerRank SQL assessment?

Answer: Joins across two or three tables, GROUP BY with HAVING, window functions such as ROW_NUMBER and RANK, subqueries and CTEs, and date filtering. The classic questions are nth-highest salary, duplicates, and per-group top-N.

Why interviewers ask this: Window functions are the differentiator — per-group top-N is clean with ROW_NUMBER() OVER (PARTITION BY ...) and painful without it. Also know that WHERE filters rows before aggregation and HAVING after; mixing them up is the most common wrong answer.

SQL
-- Top 2 earners per department
SELECT department, name, salary FROM (
  SELECT department, name, salary,
         ROW_NUMBER() OVER (PARTITION BY department
                            ORDER BY salary DESC) AS rn
  FROM employees
) t
WHERE rn <= 2;
5
Junior level

What is a Karat interview and how is it different?

Answer: Karat conducts outsourced technical screens on behalf of companies. It is a live 45 to 60 minute call with an engineer, usually split into rapid-fire technical questions on your stated experience, then one or two coding problems, recorded for the hiring company to review.

Why interviewers ask this: The rapid-fire section is the part candidates under-prepare. Be ready to answer crisply on anything in your resume — the language you claimed, how HTTP works, what a database index does. "I put it on my resume but have not used it much" is a genuine red flag in that format.

6
Junior level

How do I handle a take-home assignment for a software internship?

Answer: Scope it to the stated time limit, make it run with one documented command, write a short README explaining your decisions and trade-offs, and add a few meaningful tests. Do not gold-plate — a clean, complete small solution beats an unfinished ambitious one.

Why interviewers ask this: The README is what gets read first. State what you would do with more time; that converts a missing feature from an omission into a considered decision. Committing in logical steps rather than one giant commit also signals real working habits.

7
Mid level

What is tested in a live debugging round?

Answer: You are given a small codebase with failing tests or a reported bug and asked to find and fix it while talking through your reasoning. It tests whether you read code, form a hypothesis and verify it, rather than changing lines until the error disappears.

Why interviewers ask this: Reproduce first, then narrow with prints or a debugger, then fix, then re-run the whole suite. Say your hypothesis out loud before each change — "if the off-by-one is in the loop bound, this input should fail too". Random edits are visible and are scored badly.

8
Junior level

Can I use my own IDE and look things up during an OA?

Answer: It depends on the platform and the stated rules. Many OAs allow documentation lookup but run proctoring or tab-focus detection and forbid other people or AI tools. Read the instructions on the first screen — they are the binding rules, not the general norm.

Why interviewers ask this: Violations are usually detected and cost you the pipeline for that company, sometimes for a year. If a rule is unclear, ask the recruiter before you start rather than deciding on your own interpretation mid-test.

9
Junior level

What CS-fundamentals MCQs appear alongside coding tasks?

Answer: Time and space complexity of standard algorithms, OS basics (process versus thread, deadlock, paging), DBMS basics (normalisation, ACID, indexing), networking (TCP versus UDP, HTTP status codes) and OOP concepts.

Why interviewers ask this: These are quick marks and cheap to prepare. A single revision pass over complexity tables, ACID properties and the TCP handshake usually converts most of this section.

10
Junior level

I passed sample cases but failed hidden ones. What usually went wrong?

Answer: Nearly always an unhandled edge case or a timeout. Check empty input, a single element, all-equal elements, negative numbers, integer overflow in fixed-width languages, and whether your complexity fits the stated constraints.

Why interviewers ask this: Before submitting, spend one minute deliberately running the empty and single-element cases. That habit converts more hidden-test failures than any additional algorithm study.

11
Junior level

How long should I spend on an OA problem before moving on?

Answer: If you have no working approach after roughly a quarter of the total time on one problem, write the brute force, submit it for partial credit and move to the next. Come back only if time remains.

Why interviewers ask this: Scoring is per test case across all problems, so an unattempted easy problem costs more than a suboptimal solution to a hard one. Sequential perfectionism is the most common way strong candidates fail an OA.

12
Junior level

Do OA results carry over between companies or roles?

Answer: Generally no. Some assessment vendors let you share a score with multiple participating companies, but most companies run their own and results expire, typically after six to twelve months.

Why interviewers ask this: If you are offered the option to share a CodeSignal score, only share a score you are happy with — a shared weak score can pre-empt a stronger later attempt at some companies.

Preparing for a Internship Prep role?

Browse live Internship Prep cloud internships and fresher jobs hiring across India right now.

Browse Internships
13
Junior level

How should I prepare in the week before an OA?

Answer: Do two timed full-length practice assessments under real conditions rather than untimed problem sets. Fix the specific failure mode each one exposes — usually speed on easy problems, or edge-case discipline.

Why interviewers ask this: Practising untimed trains a different skill from the one being measured. The timer, not the difficulty, is what most candidates actually fail on.

Continue your Internship Prep interview prep

See all 9 Internship Prep topics →

Ready to apply for Internship Prep roles?

Cloud internships and fresher jobs across India — filtered to roles that actually name Internship Prep in the requirements.

Browse Internships

Canonical: https://myinternships.in/tech-internship-prep/online-assessments-oa