A Nike Software Engineer I role in Bengaluru under the ITC banner is one of the few Nike India tech postings this year that explicitly opens its door to 0-year candidates rather than quietly requiring a year or two of prior work despite the “entry” title. “ITC” stands for Nike’s India Technology Center — a Bengaluru-based engineering hub Nike set up in 2021 to build the internal platforms and tools that power Nike’s global product, design, and commerce operations.
| Job Title | Software Engineer I, ITC |
|---|---|
| Company | Nike (India Technology Center) |
| Location | Karnataka, India (Bengaluru) |
| Job Type | Full-Time |
| Work Mode | Not specified in listing — confirm with recruiter |
| Experience Required | 0–2 years of software development experience (fresher-friendly) |
| Education | Bachelor’s degree in CS, Engineering, Information Systems, or equivalent experience |
| Estimated Salary/CTC | ₹15L (Levels.fyi median, Nike SWE I entry level, Greater Bengaluru) |
Who You’d Work With and What You’d Build
You’d report to a Software Engineering Manager based in Bengaluru and sit inside a team of engineers who partner closely with a Product Manager to hit specific software objectives — so this isn’t a role where you’re handed disconnected tickets; there’s a defined team, a defined manager, and a defined mission around tooling for Nike’s design and creation community.
The actual day-to-day spans a genuinely broad stack for an entry-level posting: building and operating scalable software across web, front-end, and cloud-native platforms; shipping responsive and accessible web experiences using modern front-end tooling and design systems; working with cloud-native APIs and services through an API-first approach; and participating in Agile sprint ceremonies rather than working solo.
You’d also be expected to own your work across the full lifecycle — development, testing, deployment, monitoring, and what Nike’s listing calls “operational excellence,” which is corporate phrasing for actually keeping what you ship stable after it goes live, not just handing it off and moving on.
The Skill Bar — What’s Actually Required vs. Nice-to-Have
- The hard requirements are a Bachelor’s degree in Computer Science, Engineering, Information Systems (or equivalent experience)
- 0–2 years of software development experience, and hands-on experience with either React or Vue.js — Nike lists both as acceptable, not both as mandatory.
- Beyond that, the listing gets noticeably technical for an entry-level role: experience with cloud architecture, DevOps, infrastructure-as-code, and CI/CD tooling; direct AWS exposure specifically to Lambda, Step Functions, DynamoDB, Elasticsearch, and S3; testing frameworks like Mocha, Jasmine, and Jest; and a solid grip on design patterns and core computer science fundamentals.
- AI/ML and data solutions experience is listed as preferred rather than required, as is familiarity with REST, domain-driven design, and microservices architecture. Realistically, very few candidates at the 0–2 year mark will check every one of these boxes — treat the AWS-specific services and testing frameworks as the differentiators worth highlighting if you have them, and the broader cloud/DevOps and architecture concepts as things worth being conversational about even without deep production experience.
Interview Prep — What’s Actually Being Evaluated
Candidates who’ve interviewed for Software Engineer I/SDE-1-level roles at Nike (including at the Bengaluru ITC) describe onsite processes with 2–3 back-to-back rounds, often held on a single day with direct elimination between rounds: a backend/technical-depth round, a design-oriented technical round, and a hiring-manager/behavioral round. Below, five practice questions are organized by the underlying skill Nike appears to test for at this level — not confirmed real Nike questions.
About NIKE
Nike is the world's largest athletic footwear and apparel company, founded in 1964 as Blue Ribbon Sports by Phil Knight and Bill Bowerman before being renamed Nike, Inc. in 1971. It designs, develops, markets, and sells athletic footwear, apparel, equipment, and accessories globally, alongside owning subsidiary brands like Converse and Jordan Brand. Headquarters: Beaverton, Oregon, US Founded: 1964 Industry: Apparel...
View Company Profile →Top Interview Questions
Prepare with commonly asked questions for this role
Without await, the async function returns a pending Promise immediately instead of the resolved value, so any code depending on that result runs before the operation actually finishes. In practice, I'd either await it directly, chain a .then(), or make the calling function async too — and I'd always wrap it in error handling since unhandled promise rejections can silently fail.
I'd start with an S3-backed storage layer for the actual files, a metadata database tracking versions and ownership, and a simple API layer in front for upload/retrieve/version operations. For the front end, I'd focus on clear version history and rollback since that's the core value for a design team, and I'd keep the first version intentionally narrow rather than over-engineering permissions and workflow on day one.
I'd solve it recursively — iterate through the array, and whenever I hit a nested array, recurse into it and compare its max against the running maximum, otherwise compare the number directly. It's a clean fit for recursion since the nesting depth isn't fixed, and I'd add a base case for empty arrays to avoid edge-case bugs.
I'd start with the happy path — valid input returning the expected response — then layer in edge cases like missing fields, invalid data types, and unauthorized access. I'd also mock external dependencies like database calls so the tests stay fast and isolated, rather than depending on a live environment.
In my current work, I focus on writing code that's readable for the next person, not just functional — clear naming, small functions, and comments where logic isn't obvious. In my personal project, I intentionally picked a stack I hadn't used before to push my learning, which taught me a lot about debugging unfamiliar tooling under time pressure.