Autocoder

Info Edge (Naukri) Interview Questions with Answers

Last updated 2026-11-19

Info Edge is the company behind Naukri, 99acres, Jeevansathi and Shiksha. Its products are search-heavy classifieds: job and property search, resume databases, alerts and recommendations. Engineering interviews for such companies tend to mix core Java or another backend language, SQL, data structures and a practical feel for search and caching.

The twelve questions below are practice in the style of those topics, with worked answers. They are not a record of any specific interview. For algorithm problems see Info Edge coding round questions, and for general SQL drill how to crack the SQL interview.

Rounds (commonly reported)Written or online test, technical interviews, HR
TopicsJava/OOP, SQL, DSA, search and caching basics
ProductsNaukri, 99acres, Jeevansathi, Shiksha

Rounds as commonly reported

There is no official Info Edge description in our sources, so treat this as general guidance. Prep communities usually describe a screening test with aptitude and programming questions, one or two technical interviews that go deep on your language, database and a project, and an HR conversation about role fit and expectations. Depth in one stack is valued more than shallow coverage of many.

What search-driven products add

A job portal lives on relevance and freshness. Know what an inverted index is, why a SQL LIKE query does not scale for text search, and how you would keep search results fresh while the database changes. Those three ideas appear in most good answers.

Hiring status

Our company facts file holds no sourced hiring announcements or process description for Info Edge, so no drive dates, openings or package figures appear here. Info Edge has no page in our hiring section; check the company's own careers site for current roles and eligibility.

Info Edge (Naukri) Interview Questions with Answers: questions with worked answers

  1. 1

    Introduce yourself and explain why Info Edge.

    easy

    Cover education, one project with an outcome you can measure, and the stack you are strongest in. For "why Info Edge", mention something real: you have used Naukri for job alerts, you are interested in how a search over millions of resumes stays fast, or you want to work on products with a large Indian user base. Keep the answer under two minutes and end on what you want to build next.

  2. 2

    What is the difference between an abstract class and an interface in Java?

    easy

    An abstract class can hold state, constructors and concrete methods, and a class can extend only one. An interface defines a contract; since Java 8 it can have default and static methods, and since Java 9 private methods, but no instance state, and a class can implement many. Use an interface for a capability several unrelated classes share, such as Comparable, and an abstract class when subclasses share fields and behaviour. Abstract classes cannot be instantiated directly.

  3. 3

    Explain equals() and hashCode() and what breaks if you override only one.

    easy

    equals defines logical equality; hashCode must return the same value for equal objects. If you override equals alone, two equal objects can land in different HashMap buckets, so get and contains fail. If you override hashCode alone, equal-hash objects are never treated as equal. The contract: equal objects have equal hash codes, but equal hashes do not imply equality. Use the same fields in both and avoid mutable fields in keys.

  4. 4

    Find the second highest salary in an employees table, including the case where it does not exist.

    medium

    DENSE_RANK handles ties and is easy to read; a subquery with MAX is the portable alternative. Wrap the result so a missing second salary returns NULL rather than no row.

    sql
    SELECT MAX(salary) AS second_highest
    FROM employees
    WHERE salary < (SELECT MAX(salary) FROM employees);
    
    -- ranking version, n-th highest generalises by changing 2
    SELECT DISTINCT salary
    FROM (SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) AS r
          FROM employees) t
    WHERE r = 2;
  5. 5

    Why is searching resumes with LIKE '%java%' slow, and what do you use instead?

    medium

    A leading wildcard cannot use a B-tree index, so the database scans every row. Text search engines build an inverted index: a map from each term to the list of documents containing it, built after tokenising, lowercasing and stemming. A query looks up each term and intersects or scores the posting lists, which is fast regardless of table size. Databases offer this as full-text indexes; large systems use Elasticsearch or Solr. Ranking uses a score such as BM25, boosting title matches and recent postings.

  6. 6

    How would you implement job-alert matching: a new job arrives and users who saved matching searches should be notified?

    medium

    Flip the problem. Instead of running every saved search against each new job, index the saved searches by their key attributes (skills, location, experience band) and look up candidates from the job's attributes, then verify the full predicate. Batch notifications through a queue, de-duplicate per user and apply frequency caps so users get a digest rather than a flood. Process asynchronously so posting a job is not slowed by alert fan-out, and make the consumer idempotent in case of retries.

  7. 7

    What is the difference between an inner join, left join and the cases where each is correct? Give a job-portal example.

    medium

    An inner join returns only rows with matches on both sides: jobs that have at least one application. A left join keeps every row from the left table and fills the right side with NULL: all jobs, with application counts of zero for jobs nobody applied to. Use the left join with COUNT(a.id), not COUNT(*), so unmatched jobs count zero. Filtering the right table in WHERE turns a left join into an inner join; put such conditions in the ON clause instead.

    sql
    SELECT j.id, j.title, COUNT(a.id) AS applications
    FROM jobs j
    LEFT JOIN applications a ON a.job_id = j.id AND a.status <> 'withdrawn'
    GROUP BY j.id, j.title;
  8. 8

    How does Java garbage collection decide what to free, and how do you diagnose a memory leak?

    medium

    The collector frees objects that are unreachable from GC roots such as thread stacks and static fields. Generational collectors keep a young generation for short-lived objects and promote survivors to an old generation. A Java memory leak is usually an unintended reference: a static map or cache that only grows, listeners never removed, or ThreadLocals in pooled threads. Diagnose with a heap dump (jmap or a flag on OutOfMemoryError) opened in a tool such as Eclipse MAT, and look at what retains the largest object sets.

  9. 9

    Design a cache in front of the job-details page.

    medium

    Use cache-aside: read from the cache, on a miss load from the database and store with a TTL. Job pages are read far more than written, so a TTL of minutes with explicit invalidation when the employer edits or closes the job works. Handle a stampede on a viral job with a lock or request coalescing on the key. Close or expired jobs must not be served stale, so keep the TTL short for them or purge on status change. Monitor hit ratio and eviction counts.

  10. 10

    Explain how an index speeds up a query and when it hurts.

    hard

    A B-tree index keeps keys sorted, so equality and range lookups take O(log n) page reads instead of a full scan. A composite index on (city, experience) serves queries filtering on city, or city and experience, but not experience alone (leftmost-prefix rule). Indexes cost write time and storage, since every insert and update maintains them, and low-selectivity columns such as a boolean gain little. Check the plan with EXPLAIN and prefer covering indexes for hot queries.

  11. 11

    Where do you see yourself in three years, and are you comfortable with the role's stack?

    medium

    Be honest and concrete. Say you want to own a feature end to end and be trusted with on-call or design reviews, and name the skills you will have built. If the stack is new to you, point to a time you learnt one quickly and shipped something with it. Interviewers dislike both "CEO in three years" and "I have no plans"; a grounded growth path with learning habits reads best.

  12. 12

    Describe a time you had to meet a deadline with an incomplete requirement.

    medium

    Describe the situation briefly, then show the decision: you confirmed the single most important outcome with the stakeholder, shipped that first behind a flag, and wrote down assumptions so changes were visible. Close with the result and one lesson, such as asking clarifying questions earlier. Evidence of communication matters more than the specific project.

Frequently asked questions

What should I study for an Info Edge technical interview?

Core Java or your main backend language, OOP, SQL (joins, grouping, ranking, indexing), basic data structures and algorithms, and a clear explanation of your projects. Know how search and caching work.

Does Info Edge ask system design from freshers?

Small design questions such as a cache or a notification flow are plausible. Full distributed designs are more common at senior levels, but reasoning about indexes and caching helps at any level.

Is there a coding test?

Many companies of this type screen with an aptitude and coding test, but we hold no sourced description of Info Edge's current format. Confirm with the recruiter.

Where can I find current openings?

On the company's own careers site. We hold no sourced hiring dates for Info Edge.

How do I answer the HR round?

Prepare a short introduction, a project story, your reasons for the role and a realistic view of location and joining timeline. Be consistent with your resume.

Related guides

More in Company Interview Questions

See all in this section