HackWithInfy: The Route to Infosys's Higher Pay Bands

HackWithInfy is Infosys's annual coding contest for engineering students, and the reason it is worth eight weeks of your time is not the prize money. It is the offer letter on the other side. A student who enters Infosys through the ordinary campus process usually joins as a Systems Engineer. A student who performs well in HackWithInfy is usually considered for the Specialist Programmer or Power Programmer bands instead — same college, same degree, same graduating year, a package widely reported at two to three times the standard one. That gap is the whole argument, and most write-ups about the contest never state it plainly.

Everything below describes the pattern of the contest as it has run in recent seasons, not a calendar. Infosys restates eligibility years, registration windows and round dates each cycle, and every season a set of blogs publishes confident dates for a cycle Infosys has not announced. Confirm the current ones on the official Infosys careers page.

What HackWithInfy actually is

It is a competitive programming contest, run by Infosys and hosted in recent seasons on HackerEarth, open to pre-final and final year engineering students across India. Lakhs register; a few thousand clear the first round; a small set of finalists reach a Grand Finale. Prize money exists and is respectable, but for almost everyone entering, the contest functions as a hiring funnel rather than a tournament.

The logic from Infosys's side is straightforward. Aptitude-led volume hiring is good at establishing a floor — this person can reason, can write basic code, can be trained — and bad at finding the top few per cent, because a short coding section cannot separate the competent from the genuinely strong. A three-hour contest with hidden test cases and a time limit can. The bands it feeds are the reason it exists.

The three doors into Infosys, and what each one pays

The routes below lead to the same company, often the same campuses, sometimes the same office in Bengaluru or Hyderabad — and to very different numbers. The figures are widely reported ranges, not published policy; they move with hiring conditions and are not guaranteed to anyone.

Route	Reported CTC (fresher)	How you get in	What is expected of you
Systems Engineer / Operations Executive	Around ₹3.6 LPA	Standard campus drive or off-campus hiring test — aptitude, verbal, basic coding, then an interview	Trainable generalist. Foundation training, then allocation to whatever project needs headcount — development, support, testing
Digital Specialist Engineer / Specialist Programmer	Roughly ₹6.5–9 LPA	Strong HackWithInfy performance, the InfyTQ certification route, or a separate specialist hiring test	Real depth in one language, solid data structures and algorithms, ability to build rather than only maintain
Power Programmer	Roughly ₹9–12 LPA	Top-tier HackWithInfy performance — finalists and near-finalists — followed by a technical interview	Strong competitive programming, full-stack or systems capability, expected to work as an individual contributor on complex builds

Now make the difference concrete. Take ₹3.6 LPA against a mid-range Power Programmer offer of, say, ₹9.5 LPA. In year one that is a gap of roughly ₹5.9 lakh. But the gap does not stay flat, because hikes are percentages of a base — a 10% increment on ₹9.5 LPA adds nearly ₹1 lakh, the same 10% on ₹3.6 LPA adds ₹36,000. Assume modest, similar increments on both and the three-year total difference lands somewhere near ₹19–20 lakh. The compounding continues after that: your next employer anchors on your last CTC, so a higher entry band raises the base for every switch you make for the next decade.

Two qualifications. CTC is not money in your account — employer EPF, gratuity provision and variable pay sit inside that number, and the difference between CTC and in-hand salary is larger than most students expect; run your figures through the in-hand salary calculator rather than dividing by twelve. And tax is not the variable here: under the new regime for FY2025-26, the ₹75,000 standard deduction and the Section 87A rebate together make income tax nil up to ₹12,00,000 of taxable income, so at every one of these packages a fresher pays nil or close to it. What moves your monthly credit is EPF and CTC structure, not the slab.

The format, as it has historically run

The shape has been consistent even when details moved. Registration opens on the Infosys careers site and the contest runs on HackerEarth. Round 1 is an online qualifier of a few hours with a handful of algorithmic problems of mixed difficulty, scored on hidden test cases, typically with partial credit. Those above a cut-off — which is not published in advance — move to a harder second online round. A small set of top scorers reach the Grand Finale, historically on the order of a hundred finalists, held as a live event with prize money at the top.

The structural point most students miss is that the funnel does not end at the Finale. Performance in the earlier rounds has itself been used to shortlist candidates for higher-band interviews, so a strong Round 1 and Round 2 showing has value even if you never reach the Finale. Treat the Finale as the stretch outcome and a strong qualifier score as the realistic one — and register the day registration opens, not the week it closes.

What the problems look like, and what to practise

These are conventional competitive programming problems: a clean statement, constraints, sample input and output, a time limit, hidden tests. If you have used Codeforces, CodeChef or LeetCode the format will feel familiar. That is a real difference from TCS CodeVita, where statements are wrapped in long narratives and half the difficulty is extracting the actual problem from three paragraphs of story. HackWithInfy rounds sit closer to a standard contest — the difficulty is the algorithm, not the comprehension.

That makes the preparation surface easy to name. Arrays and strings first, because everything else assumes them. Then hashing, sorting and the standard library of whichever language you use. Then two pointers and sliding window, binary search including binary search on the answer, recursion and backtracking. Then the structural topics: stacks, queues, heaps, linked lists, trees, and graphs with BFS, DFS, topological sort and shortest paths. Then greedy, and finally dynamic programming, which is where most candidates quietly stop and where the separation between clearing Round 1 and clearing Round 2 usually happens.

If you are starting from a weak base, work through a structured DSA plan for placements before attempting timed contests, because contest practice on top of no foundation only teaches you to panic faster.

The InfyTQ route, for students who are not contest-strong

Contests reward a single three-hour peak. Some genuinely capable engineers do not have that peak — they are careful, slow under a countdown, and solve things properly given an evening. For them the certification route is the honest alternative, and it is worth saying so rather than pretending everyone should grind competitive programming.

InfyTQ is Infosys's own learning platform for engineering students, covering programming fundamentals, Python or Java, and databases. The Infosys Certified Software Programmer examination on it has historically been a path to a higher-band offer for students who clear it, and it tests something different from a contest: sustained coverage of fundamentals, applied coding and database work rather than one sitting. Specifics change by cycle, so verify the current structure on InfyTQ itself. There is no reason to choose between the two — the syllabus overlap is large and they fail independently, so a bad contest day costs you nothing on the certification.

An eight-week preparation plan

This assumes roughly 90 minutes on weekdays and a longer weekend block, which is realistic alongside coursework. The counts are targets, not ceilings, and the discipline that matters most is upsolving: after every timed session, solve what you could not solve, without a deadline, until you can write it from memory. People who skip that step plateau in about three weeks.

Week	Focus	What to practise	Target
1	Foundations	Arrays, strings, complexity analysis, your language's standard library and fast input/output	25 easy problems; be able to state the complexity of everything you write
2	Hashing and sorting	Hash maps and sets, frequency counting, custom comparators, prefix sums	25 problems, roughly a third of them medium
3	Search patterns	Two pointers, sliding window, binary search on arrays and on the answer	25 problems; binary search on the answer is the highest-yield single pattern here
4	Recursion and first contest	Recursion, backtracking, subsets and permutations; one timed virtual contest	20 problems plus 1 contest, fully upsolved afterwards
5	Linear structures	Stacks, queues, monotonic stack, heaps and priority queues, linked lists	25 problems; write a heap-based solution without looking anything up
6	Trees and graphs	Binary trees, BST, traversals; graph representation, BFS, DFS, cycle detection, topological sort, Dijkstra	25 problems; be able to write BFS and DFS from a blank file in under five minutes
7	Greedy and DP	Exchange-argument greedy; DP on 1D and 2D states, knapsack, LIS, grid paths, DP on strings	25 problems, DP-heavy; this week decides Round 2
8	Contest simulation	Full-length timed contests under real conditions, then revision of your weakest two topics	3 contests, every problem upsolved; no new topics this week

Two rules make it work. Give a problem a genuine 40 minutes before opening an editorial, and after reading one, close it and write the solution yourself. And keep a plain text file of every problem you failed with one line on why — wrong data structure, missed edge case, ran out of time. After a month that file, not the problem count, tells you what to fix.

The interview that follows a good result

Clearing a round gets you an interview, not an offer — the point students most often misread — and it is not the same interview the standard fresher process runs.

The ordinary Infosys fresher interview after an aptitude-led drive is largely a confirmation exercise: basic questions on your language and DBMS, a look at your final year project, an HR conversation about relocation and the training bond. The higher-band interview is a technical conversation. Expect one or two data structures and algorithms problems solved live while you explain your approach, where the panel cares how you arrive at the solution and whether you can state its time and space complexity, not only whether it compiles. Expect your projects interrogated properly — why this database, what happens under load, what you would change — plus follow-ups on operating systems, DBMS and networks. An HR round still closes it, and the usual HR interview questions still apply.

So rehearse a four-minute account of one project you can defend in depth, and read through commonly asked Infosys interview questions so the fundamentals portion costs you nothing. Make sure the resume reaching the panel lists the contest performance and project stack in a form a parser can read; a free ATS resume checker catches the formatting that silently drops content.

How it compares with CodeVita and Elite NLTH

These three get grouped together and they are not the same kind of thing. TCS CodeVita is a global contest with long, story-wrapped problem statements, and the comprehension load is a real part of the difficulty; strong performers have historically been considered for TCS's Prime and Digital offers, which sit well above the base package. It is separate from the mainline hiring test, and if TCS is on your list you will still want to prepare the TCS NQT route in parallel.

Wipro Elite NLTH is not a contest at all. It is a national hiring test — aptitude, written communication and coding — that functions as the main door into Wipro's fresher bands, with higher tracks layered on top. HackWithInfy sits between them: contest-format problems like CodeVita, but with the band outcome stated more directly and a shorter path from score to interview. All three are the same manoeuvre — a large services firm building a side channel to find the candidates its volume process cannot distinguish. Before spending a chunk of your final year on any of them, it is worth being clear about what you are buying; the trade-offs in service-based versus product-based companies matter as much as the entry band does.

The honest caveat

A coding contest is a lottery with a skill floor. The floor is real — nobody clears Round 2 by luck. Above it, outcomes are noisy: which problems appear, whether the one topic you skipped shows up, how a slow start eats a three-hour window, how many strong candidates happen to compete that season. Finalists have missed higher-band offers, and band allocation moves with hiring conditions in a given year. A Power Programmer offer is not guaranteed to every finalist, and nobody at Infosys promises otherwise.

So enter it and run the normal process. Sit the campus drives, prepare aptitude properly, apply through off-campus drives, keep the referral conversations going. The students who get hurt are the ones who treat a good Round 1 score as a job in hand and stop attending placement sessions in October. Fold this into your overall campus placement preparation as one track among several and the downside disappears — the worst case is eight weeks spent getting substantially better at data structures and algorithms, the most portable thing you can carry into any interview.