Skip to content
Interview Questions

Adani Interview Experience 2026

How Adani fresher interviews usually run, campus and off-campus. We synthesized GET and technology-track reports into a round table, outcome notes, and prep takeaways - patterns shift by business unit and year, so treat this as a prep map, not a script.

Adani placement process includes: 1. Online Assessment (90 minutes) - Coding/aptitude questions. 2. Technical Interview Round 1 (60 minutes) - Technical concepts. 3. Technical Interview Round 2 (60 minutes) - Advanced concepts and projects. 4. HR Interview (30 minutes) - Motivation and company fit. Total duration: 2-3 weeks from application to offer.

Eligibility (from student reports): 7.0+ CGPA or 70%.

Fresher package ballpark (from student reports): Analyst: ₹8-15 LPA. Confirm on your offer letter.

Round-wise process

Round Duration What they test
Online / Written Test 90-160 min Aptitude + branch domain (+ basic coding on some tech drives)
Async video (some GET drives) ~30 min total Values, intro, communication under timer
Technical Interview 30-60 min Core subjects, resume, project depth
HR (often same panel) 20-30 min Location, shifts, motivation, unit fit

Real interview experiences

Adani hires most freshers through the Graduate Engineer Trainee (GET) route across engineering disciplines, not through a CSE-only coding drive. The public write-ups reflect that: the screening is an aptitude test with a branch-specific domain section, and the interview is a short panel conversation on your branch subjects and your resume. There is very little DSA in the reported accounts.

A documented on-campus GET drive (ECE candidate)

The most detailed public write-up is from a final-year ECE student who went through Adani’s on-campus GET drive and was selected. Four stages:

Resume screening - the shortlist was drawn before any test.

Online aptitude assessment (L&T EduTech platform)

  • Four sections of 40 questions each, 160 minutes total: Analytical Ability, Quantitative Ability, Verbal Ability, and a branch-specific domain section (ECE in this case).
  • The candidate rated verbal as the easiest and the analytical and domain sections as the tougher ones.
  • Roughly 40 candidates advanced out of 150+.

Asynchronous video interview (Talocity)

  • A one-way recorded assessment: 5 questions, about 30 seconds of prep and 2 minutes to answer each, with roughly 36 hours to complete it.
  • Content was a self-introduction plus questions on personal values and experiences - not technical.

Technical interview (MS Teams, ~40 minutes)

  • Panel of two technical interviewers plus one HR interviewer.
  • Questions spanned control systems, data science applications, networking (OSI and TCP/IP models, protocols, subnetting), cybersecurity, logic gates, and communication systems - i.e. branch fundamentals, not algorithms.
  • Behavioural portion covered what the candidate knew about the company, career interests, and willingness to relocate.

Outcome: selected. 17 offers were made across four engineering disciplines from that drive.

Takeaways

  • What decided it: Branch fundamentals (control, networking, communication) plus calm async-video and relocation answers in a mixed tech+HR panel
  • Common fail: Treating the Talocity one-way video as optional, or listing skills you cannot defend when the panel walks the resume
  • How to practise: One full 160-minute aptitude mock; record five 2-minute video answers on a phone timer

What pooled candidate reports add

Individual Adani write-ups are sparse, so the rest is best read as pooled reporting rather than one person’s story:

  • Difficulty is rated low-to-moderate. Glassdoor’s aggregate for the GET role sits near 3/5 on difficulty with about 86% of candidates calling the experience positive; across all Adani Group roles the figures are roughly 2.92/5 and 61.5% positive. GET and Software Engineer are reported as the easier Adani interviews; SDE and Assistant Manager roles are rated the hardest.
  • The interview is resume-driven. The recurring advice is that interviewers ask about everything written on your resume, so do not list a skill or project you cannot defend. Reported questions include a self-introduction, why they should hire you, what you like about the group’s businesses, what you are passionate about, and why Adani - plus, in some panels, logical puzzles and questions on Python libraries.
  • HR is short. Multiple reports describe only two or three HR questions, sometimes folded into the same panel as the technical round. General interviews are commonly around 25 minutes, and can end in 15 if the panel is satisfied early.
  • The cycle is fast. Glassdoor’s self-reported average time from interview to outcome is about 6 days for GET and roughly 12 days across all Adani Group titles.

Takeaway: for Adani, branch fundamentals plus a defensible resume matter more than contest-grade DSA. Budget real prep time for the aptitude test - it is where the 150-to-40 cut happens - and rehearse the one-way video round, which catches candidates off guard because there is no interviewer to read.

GET (Technology), off-campus Ahmedabad (2026 cycle - candidate reports)

Profile: B.Tech CS/IT, eligible for GET Technology; applied via careers.adani.com when the Ahmedabad technology intake opened.

Reported stages

  1. Resume screen against CGPA and stack keywords (Java/.NET/Node mentioned in prep guides).
  2. Online aptitude (~60 questions / ~60 minutes) - quantitative, logical, verbal, plus role-specific MCQs (OOP, DBMS/SQL, basic APIs).
  3. Async video interview - short prep window per question (~30–60 seconds), ~2 minutes to record; prompts on introduction, values, and past teamwork (not coding).
  4. Panel (technical + HR) - project walkthrough, REST/SQL follow-ups for technology track, relocation and business-unit interest.

Outcome pattern: rolling intake; timelines vary by vertical. Takeaway: technology GET rewards timed aptitude + crisp video answers + one backend project you can whiteboard - not LeetCode hard sets.

Takeaways

  • What decided it: Timed aptitude accuracy plus a whiteboard-ready backend/API project and clear business-unit interest
  • Common fail: Preparing FAANG DSA lists while under-practising the 60-in-60 aptitude and short async-video window
  • How to practise: Drill OOP/DBMS MCQs under a timer; rehearse a 2-minute REST/SQL project walkthrough

Mechanical GET, campus to Mundra greenfield (alumni report)

Profile: Metallurgical/mechanical engineer (NIT Raipur cohort cited on GeeksforGeeks work-experience forums), selected as GET ~₹7 LPA (candidate-reported starting CTC).

Onboarding: ~1 month Mundra induction with batch of GETs; plant tours across Adani businesses in the region; probation 8 months before promotion stories to assistant-manager band (₹9 LPA in the same report - treat as one data point).

Work themes: P&ID and mechanical drawing reviews, vendor coordination, package tracking, budgeting support for a greenfield metals/plant project.

Candid pros/cons from the report: steep learning and responsibility early; ~10-hour site days and remote industrial township lifestyle - HR screens for this honestly.

Takeaway: core-branch GET interviews are about drawings, discipline, and site readiness, not DSA.

GET (IT/ECE), pooled campus report (2025)

Profile: B.Tech IT/ECE, ~7.2 CGPA, strong projects, moderate contest rating.

Online assessment: tighter time pressure than practice; at least one section needed an optimized pass to stay competitive with the shortlist.

Technical + HR (combined panel): resume-led - APIs, data store choices, failure modes at fresher depth; warm-up “explain your project end-to-end.”

HR slice: why Adani, location flexibility, long-term fit in infra/energy (not generic IT services).

Result: selected after HR/managerial close. Takeaway: coherent domain + aptitude narrative beat a higher CGPA with weak explanation in this report.

Sources:

Patterns differ by campus, business unit, and year. If your college placement email says something different, follow that.

Questions that come up often

Coding / technical

  1. Basic array / string coding. Usually expects clear logic
  2. OOPs or domain follow-ups. Usually expects fundamentals
  3. Explain a project end-to-end. Usually expects clarity and ownership
  4. Discussion on domain + aptitude and basic coding, bottlenecks, failure modes, simple APIs
  5. Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioural

  1. Why this company / business unit?
  2. Location flexibility
  3. How your project or internship maps to the role
  4. Long-term plans

Pre-interview checklist (Adani GET)

  • Confirm business unit (Ports, Power, Green, Transmission, Enterprises, GET Technology) from the invite - prep differs.
  • Run one full timed aptitude matching your platform (4×40 vs 60-in-60 reports).
  • Rehearse async video answers (intro, values, teamwork) with a phone timer - 60–120 seconds each.
  • Resume audit: every skill and project must survive “why did you choose X?” follow-ups.
  • Prepare relocation / site posting answer before HR; it is a common filter for industrial locations.
  • Pack branch fundamentals flashcards (power/mechanical/civil/ECE) - not FAANG DSA lists unless the role is technology GET.
  • Bring 2 questions about induction, site rotation, and KPIs for your discipline.

Practical tips for Adani

  • Clear the screening round first. Timed practice beats last-minute topic hopping.
  • For domain questions, explain domain + aptitude in plain language, inputs, outputs, what breaks at scale.
  • OOPs and SQL still open a lot of Adani panels. Do not skip fundamentals.
  • HR answers should be concrete. One story with a result beats five slogans.
  • If you do not know something, say so and outline how you would find out.

HR interview

After technical rounds, Adani usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

Sample answers for high-frequency questions

Use these as frames, not scripts - interviewers probe follow-ups.

Q. Explain the Rankine cycle and where losses occur in a thermal power plant.
A. The Rankine cycle has four ideal processes: isentropic compression of feedwater in the pump, constant-pressure heat addition in the boiler and superheater, isentropic expansion through the turbine, and constant-pressure heat rejection in the condenser. Thermal efficiency is the net work divided by heat added, and it improves by raising the boiler pressure and superheat temperature or lowering the condenser pressure. Practical plants add reheat, which sends steam back to the boiler after the high-pressure turbine to reduce blade erosion from wet steam, and regenerative feedwater heating using extracted steam. Real losses come from turbine and pump isentropic inefficiency, boiler flue-gas and radiation losses, condenser terminal temperature difference, and auxiliary power consumed by fans, mills, and pumps, which is why a subcritical unit lands near 33 to 38 percent efficiency while a supercritical unit reaches the low 40s.

Q. Why does power factor matter in an industrial plant, and how is it corrected?
A. Power factor is the ratio of real power in kW to apparent power in kVA, and it equals cosine of the phase angle between voltage and current for sinusoidal supplies. Inductive loads such as induction motors and transformers draw lagging reactive power, so for the same real power the current rises, which increases I-squared-R losses in cables and transformers, causes voltage drop, and eats into transformer capacity. Utilities also levy penalties below a threshold, commonly 0.95. Correction is normally done with shunt capacitor banks sized in kVAr and switched by an automatic power factor controller, or with synchronous condensers and static VAR compensators at larger scale. Correcting from 0.75 to 0.95 cuts the current drawn by roughly 20 percent for the same load.

Q. How does a transformer work, and why can it not operate on DC?
A. A transformer works on Faraday’s law of electromagnetic induction: alternating current in the primary produces a time-varying flux in the laminated core, and that changing flux induces an EMF in the secondary proportional to its turn count, so the voltage ratio equals the turns ratio and, ignoring losses, the current ratio is its inverse. DC produces a constant flux, so the rate of change of flux is zero and no EMF is induced in the secondary; worse, the primary then presents only its small winding resistance, so the current is limited only by that resistance and the winding burns out. Transformer losses split into core losses, comprising hysteresis and eddy current losses that are roughly constant with load, and copper losses that vary with the square of load current, with maximum efficiency occurring where the two are equal.

Q. What is MPPT in a solar PV plant, and why is it needed?
A. A photovoltaic array’s power-versus-voltage curve has a single peak, and the voltage at that maximum power point shifts continuously with irradiance and, more strongly, with cell temperature, since open-circuit voltage falls by roughly 0.3 to 0.4 percent per degree Celsius. Maximum Power Point Tracking is a control algorithm inside the inverter or DC-DC converter that continuously adjusts operating voltage to sit at that peak. The common algorithms are Perturb and Observe, which nudges the voltage and keeps the direction that increased power, and Incremental Conductance, which compares incremental conductance against the negative of instantaneous conductance and handles rapid irradiance changes better. Without MPPT the array would sit wherever the load fixes its operating point and typically give up 10 to 25 percent of available energy.

Q. What is the difference between Plant Load Factor and Capacity Utilisation Factor?
A. Plant Load Factor is the actual energy generated over a period divided by the energy the plant could have generated running at rated capacity for the hours it was actually available, so it measures how hard an available plant was run. Capacity Utilisation Factor divides actual generation by rated capacity times all the hours in the period, whether the plant was available or not, so it also absorbs outages. For thermal plants the two differ mainly by planned and forced outage time. For renewables the distinction matters less because output is resource-limited: a solar plant in Gujarat or Rajasthan typically reports a CUF around 19 to 22 percent and a wind site perhaps 25 to 35 percent, and those numbers are the standard yardstick for comparing sites rather than plant health.

Tips from successful candidates

Assessment tips

  • Confirm the current Adani pattern from the drive mail before practising old papers
  • Finish one problem or section fully before starting the next
  • Revise the fundamentals listed in the round table on this page

Interview tips

  • Narrate trade-offs; expect “why” after every answer
  • Only list projects you can defend under follow-ups
  • Prepare 3-4 STAR stories for behavioural prompts

HR tips

  • Know why Adani, not just why the industry
  • Be clear on location / notice period / higher studies
  • Practise answers on the dedicated HR page

Sources

These links are research inputs we used to map GET round structure and recurring questions - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for Adani.

Outbound candidate write-ups and references:

Cross-check the current drive mail for timings. For OA practice, see Adani placement papers.

Adani hub

HR interview questions

Placement papers

Preparation guide

Similar companies

Reliance · L&T · Mahindra · Google · Amazon · Microsoft