Details below were current as of October 2025. Roles like this move fast — confirm directly on NTT DATA’s careers page or IBM’s careers page before applying.
Bangalore’s IT hiring market has two names that show up constantly in fresher job searches: NTT DATA and IBM. Both have run active recruitment for entry-to-mid-level tech roles in the 5–10 LPA range, and both attract the same pool of candidates — B.Tech/B.E. graduates and early-career professionals with 0–3 years of experience. Here’s what’s actually worth knowing before you apply to either.
Why these two companies keep showing up together
NTT DATA and IBM aren’t competitors in the way two startups might be — they’re both large, India-heavy IT services and consulting operations that hire in volume, especially out of Bangalore and Hyderabad. NTT DATA runs global delivery centers supporting clients across banking, healthcare, and manufacturing. IBM’s India operations span everything from cloud consulting to hardware R&D. For a fresher, the practical difference is less about brand prestige and more about which specific team and technology stack you land in — that varies far more within each company than between them.
Quick comparison
| Factor | NTT DATA | IBM |
|---|---|---|
| Typical fresher salary (Bangalore) | 5–8 LPA | 6–10 LPA |
| Common entry roles | Business Analyst, Data Analyst, Support Engineer | Associate Software Engineer, Cloud Consultant |
| Core skills screened for | SQL, Excel, communication, basic domain knowledge | Java/Python, cloud fundamentals, problem-solving |
| Interview rounds (typical) | Aptitude test → technical → HR | Online assessment → 2 technical rounds → HR |
| Work model | Hybrid, mostly office-based | Hybrid, varies by team |
What the NTT DATA roles actually involve
Most fresher-level NTT DATA openings in this salary band are Business Analyst or Data Analyst positions supporting a specific client account. Day to day, that usually means pulling and cleaning data in SQL or Excel, building reports (often in Power BI), and communicating findings to a client-facing team lead. It’s less “build a product from scratch” and more “make sense of a client’s data and present it clearly” — a genuinely useful skill to build early, even if it’s less flashy than pure software development.
What the IBM roles actually involve
IBM’s entry-level tech roles in this bracket tend to be more hands-on-code — associate software engineer positions where you’re writing and testing code (commonly Java or Python), often on cloud infrastructure projects. IBM’s scale means you’re more likely to be one of many engineers on a large, established codebase rather than owning a feature end-to-end from day one, which is normal for a first job at a company this size.
How to prepare for either interview process
- For NTT DATA-style analyst roles: practice writing SQL joins and aggregate queries — this comes up in nearly every analyst screening. Be ready to walk through a dashboard or report you’ve built, even if it was for a college project.
- For IBM-style engineering roles: revise data structures and basic algorithm questions (arrays, strings, sorting). Have a GitHub repo, even a small one, that you can talk through confidently.
- For both: the HR round usually covers notice period, relocation willingness, and shift flexibility — have honest, decided answers ready rather than figuring it out on the spot.
A note on salary expectations
The “5–10 LPA” range you’ll see in listings is wide for a reason — it usually reflects a spread across different sub-roles and experience bands within the same job title, not a negotiable range for every single candidate. A genuine fresher with no prior internship is more realistically looking at the lower half of that range; the upper end tends to go to candidates with a relevant internship, certification (like an AWS or Azure associate cert), or a strong academic project portfolio.
Before you apply
- Check both companies’ official career portals directly — listings on aggregator sites (including this one) can be delayed or already closed.
- Match your resume’s keywords to the specific job description rather than sending one generic resume to both.
- If given a choice between the two, think about which day-to-day work suits you more — analyst-style data/communication work, or engineer-style coding — rather than picking purely by brand name.
Written by Babu Addakula, Job Visit.
