Infosys Data Engineer Interview Questions (2026)

1. 1Infosys Online Assessment60 minMedium

   Timed test with logical reasoning, verbal ability, quantitative aptitude, and the well-known pseudocode section that decides interview shortlisting and track.

2. 2Power Programmer (SP) Coding Round50 minHard

   For HackWithInfy/InfyTQ-routed candidates, a competitive-programming style interview with 2-3 DSA problems requiring working code and complexity analysis.

3. 3Technical Interview40 minMedium

   Panel covers OOP, DBMS and SQL queries, one or two programs or pseudocode on paper/screen, and a walkthrough of academic or work projects.

4. 4Techno-Managerial Round40 minMedium

   For laterals, a delivery manager probes system-level decisions on past projects, estimation, client communication, and how the candidate handles production issues.

5. 5HR Round25 minEasy

   Values-and-stability conversation covering why Infosys, C-LIFE values awareness, relocation, training agreement, and salary/joining logistics.

1. Q1

   Design the incremental pull for Infosys's retail client's daily sales fact load. Which watermark column do you trust, and what happens when the source clock drifts?

   HardSQL roundincremental extractionInfosys-specific

   Context:

   Infosys retail client's daily sales fact load

   How to answer:

   Pick an audit column the source actually maintains, overlap the window, and dedupe on a business key rather than assuming exactly-once. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

2. Q2

   Rows in Infosys's telecom client's call-detail-record pipeline arrive more than once after a retry. Write the SQL that lands exactly one row per business key and say which one survives.

   MediumSQL rounddeduplication on loadInfosys-specific

   Context:

   Infosys telecom client's call-detail-record pipeline

   How to answer:

   ROW_NUMBER over the business key ordered by load or update time, with an explicit survivorship rule you can defend to the client. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

3. Q3

   The client wants history preserved on the customer dimension behind Infosys's insurance client's claims data lake. Write the SCD Type 2 merge and name what it costs.

   HardSQL roundslowly changing dimensionsInfosys-specific

   Context:

   Infosys insurance client's claims data lake

   How to answer:

   Effective-from/to plus a current flag, hash-diff on tracked columns, and the row growth and query complexity you accept in return. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

4. Q4

   After a new join, the fact row count in Infosys's e-commerce client's clickstream ingestion tripled. Debug it and prove the fix.

   HardSQL roundjoin fan-out debuggingInfosys-specific

   Context:

   Infosys e-commerce client's clickstream ingestion

   How to answer:

   Find the one-to-many side, check key uniqueness first, pre-aggregate or dedupe, then verify with counts before and after. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

5. Q5

   A dimension key is missing when the fact for Infosys's healthcare client's patient-records batch feed loads. What do you write instead of dropping the row?

   MediumSQL roundNULL and late-arriving keysInfosys-specific

   Context:

   Infosys healthcare client's patient-records batch feed

   How to answer:

   Route to an unknown-member key, keep the fact, and reprocess when the dimension lands — never silently lose revenue rows. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

6. Q6

   The reconciliation query over Infosys's logistics client's shipment-tracking pipeline scans the whole table every night. How do you make it cheap?

   MediumSQL roundquery performanceInfosys-specific

   Context:

   Infosys logistics client's shipment-tracking pipeline

   How to answer:

   Partition pruning, predicate pushdown, and clustering on the filter column; read the plan before changing anything. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

7. Q7

   One Spark task in Infosys's manufacturing client's sensor telemetry feed runs for an hour while the rest finish in a minute. Diagnose and fix it.

   HardPython and Spark rounddata skewInfosys-specific

   Context:

   Infosys manufacturing client's sensor telemetry feed

   How to answer:

   Inspect partition sizes for a hot key, then salt, broadcast the small side, or repartition — and say which one you would try first and why. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

8. Q8

   Walk through what actually happens when Infosys's media client's subscriber-events pipeline does a groupBy on a billion rows. Where does the time go?

   HardPython and Spark roundshuffle and partitioningInfosys-specific

   Context:

   Infosys media client's subscriber-events pipeline

   How to answer:

   Wide vs narrow transformations, shuffle write and read, partition count, and spill to disk. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

9. Q9

   When would you broadcast the dimension in Infosys's utilities client's smart-meter reading feed, and when does that blow up?

   MediumPython and Spark roundbroadcast joinsInfosys-specific

   Context:

   Infosys utilities client's smart-meter reading feed

   How to answer:

   Small-side size against executor memory, the auto-broadcast threshold, and the driver OOM you get when you force it on a large table. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

10. Q10

    The landing zone for Infosys's travel client's booking and cancellation mart has hundreds of thousands of tiny files. What is the damage, and what is the fix?

    HardPython and Spark roundsmall files problemInfosys-specific

    Context:

    Infosys travel client's booking and cancellation mart

    How to answer:

    Listing and task overhead, then compaction, target file sizes, and fixing the writer rather than compacting forever. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

11. Q11

    A teammate solved a transformation in Infosys's banking client's nightly core-banking ingestion with a Python UDF. When is that the wrong call?

    MediumPython and Spark roundUDFs vs built-insInfosys-specific

    Context:

    Infosys banking client's nightly core-banking ingestion

    How to answer:

    Serialization cost and the lost optimizer pushdown; reach for built-in functions first, then pandas UDFs if you must. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

12. Q12

    The same intermediate DataFrame in Infosys's retail client's daily sales fact load is used four times. Do you cache it? Defend the answer.

    MediumPython and Spark roundcaching and reuseInfosys-specific

    Context:

    Infosys retail client's daily sales fact load

    How to answer:

    Recompute cost against memory pressure and eviction; measure with the DAG rather than caching by reflex. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

13. Q13

    State the grain of the fact table behind Infosys's telecom client's call-detail-record pipeline in one sentence, and show what breaks when the grain is wrong.

    MediumData modelling roundgrain definitionInfosys-specific

    Context:

    Infosys telecom client's call-detail-record pipeline

    How to answer:

    One row equals one what; a mixed grain gives double counting no downstream fix can rescue. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

14. Q14

    Model Infosys's insurance client's claims data lake as a star schema. Which tables are facts, which are dimensions, and why not one wide table?

    MediumData modelling roundstar schema designInfosys-specific

    Context:

    Infosys insurance client's claims data lake

    How to answer:

    Conformed dimensions, additive measures, and the update and consistency cost of a single flattened table. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

15. Q15

    Explain the bronze, silver and gold layers for Infosys's e-commerce client's clickstream ingestion, and what is not allowed to happen in each.

    MediumData modelling roundlayered architectureInfosys-specific

    Context:

    Infosys e-commerce client's clickstream ingestion

    How to answer:

    Raw fidelity in bronze, conformed and deduplicated in silver, business-shaped aggregates in gold; no business logic hidden in ingestion. State the requirement, the data you would move, and the checks that make the output trustworthy. Walk the design concretely: sources, storage layout, transformations, schedule, and the failure cases. Close with how you would validate the result and hand it over to whoever runs it next.

Practice these with instant AI feedback in a live mock interview → Start a Infosys Data Engineer mock

Clear the online test; revise coding fundamentals and projects; prepare HR/behavioral

Other roles at Infosys

Data Engineer interviews at other companies