
Nike is hiring for a Software Engineer I, ITC role in Bangalore, and it’s genuinely worth a look even if you’re right at the edge of the experience bar — the listing asks for 1+ years of professional experience, which realistically includes candidates who’ve just crossed that mark, completed a substantial internship plus a few months of full-time work, or graduated with genuinely strong, demonstrable full-stack project experience. If you’re sitting between 0 and 1 year — say, a recent graduate with a solid internship behind you — this is worth applying to rather than ruling yourself out preemptively; let Nike’s recruiters make that call rather than assuming you’re not a fit.
What “ITC” actually means, and why it matters
ITC stands for Nike’s IT/HR Technology organization specifically — this role sits within the team that builds and maintains Nike’s internal HR and Talent Acquisition systems, including platforms like Workday Recruiting. That’s a genuinely different context than working on Nike’s consumer-facing apps or e-commerce platform — you’d be building internal enterprise tooling that supports how Nike itself hires and manages talent globally, not the shopping experience Nike customers interact with directly.
What the role actually involves
- Designing, building, testing, and maintaining scalable web applications and services, spanning both front-end and back-end work
- Implementing dynamic, responsive user interfaces using modern JavaScript frameworks, specifically React
- Designing and implementing RESTful APIs, microservices, and backend services using Node.js, Python, or similar technologies
- Working with NoSQL databases for efficient data storage and retrieval
- Writing unit and integration tests, maintaining high code quality using tools like Jest or Mocha
- Identifying and fixing performance bottlenecks across the full stack
- Integrating with and maintaining CI/CD pipelines for smooth software delivery
- Participating fully in Agile processes — sprint planning, daily stand-ups, code reviews, and retrospectives
Required qualifications
- A Bachelor’s degree in Computer Science, Engineering, or a related field — or equivalent experience
- 1+ years of professional experience as a Full Stack Software Engineer or in a similar role
- Hands-on experience with React (or similar front-end frameworks) and server-side languages like Node.js or Python
- Genuine experience with NoSQL databases
- Hands-on exposure designing and consuming RESTful APIs and web services
- Familiarity with cloud platforms, preferably AWS, including serverless architectures
- Proficiency with Git, GitHub, or similar version control tools
- Experience with unit testing, integration testing, and test-driven development (TDD)
- Strong debugging, troubleshooting, and performance optimization skills
- Genuine comfort thriving in a fast-paced, ambiguous environment
What strengthens a competitive application
- Familiarity with CI/CD tools — Jenkins, CircleCI, or GitLab
- Experience with containerization technologies like Docker
- Familiarity with microservices architecture
Understanding the realistic salary picture
This is genuinely worth clarifying since Nike salary data online varies enormously by seniority level: broader “Software Engineer at Nike” averages you’ll find quoted elsewhere (sometimes ₹30–35 LPA+) typically blend senior and lead-level compensation into the average. For the specific SWE I level this posting targets, Levels.fyi data puts compensation at approximately ₹14.5 LPA — a meaningfully more accurate reference point for this particular role than broader company-wide averages.
Who genuinely thrives on a team like this
Nike’s broader engineering culture messaging (drawn from closely related ITC postings) emphasizes a collaborative, intellectually curious environment where engineers actively mentor each other and contribute back to both internal and external engineering communities — worth knowing if you’re weighing this against a more purely execution-focused role elsewhere, since genuine curiosity and knowledge-sharing appear to be real, valued traits here, not just resume language.
Questions Candidates Commonly Have
1. Is this role open to freshers with strong personal projects? Based on the explicit requirement of 1+ years of professional Full Stack Software Engineering experience, this doesn’t appear to be an open fresher role — candidates without professional experience should treat this as a role to work toward.
2. Does this role involve Nike’s consumer-facing apps or e-commerce platform? No — this role sits within Nike’s ITC (HR Technology) organization, supporting internal systems like Workday Recruiting, not Nike’s consumer-facing shopping or app experiences.
3. Is remote work an option for this role? No — the listing specifies an on-site location at WeWork, Embassy GolfLinks, Bangalore, without indicating remote or hybrid flexibility.
4. Why do salary figures for “Software Engineer at Nike” vary so dramatically across sources? Broader averages quoted online often blend all seniority levels — from SWE I through Tech Lead — into one number. For the specific SWE I level this posting targets, Levels.fyi data suggests approximately ₹14.5 LPA is a more accurate reference point than company-wide averages.
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
I'd define clear, resource-based endpoints — GET /applications, POST /applications, GET /applications/:id — following REST conventions consistently, use appropriate HTTP status codes for different outcomes, and consider pagination and filtering for list endpoints early rather than retrofitting them later.
NoSQL databases (document, key-value, or graph-based) offer flexible schemas and horizontal scalability, better suited for rapidly evolving data models or very high write throughput. Relational databases excel with structured, relationship-heavy data requiring strong consistency — the right choice depends on the actual data shape and access patterns, not just team preference.
I'd write failing tests first that define the expected behavior, implement just enough code to pass those tests, then refactor with the safety net of passing tests in place — this keeps the codebase genuinely test-covered by design, rather than tests being added as an afterthought once the feature already "works."
Use a real, specific example — even from a personal or academic project — walking through how you isolated whether the bottleneck was in rendering, network requests, or backend processing before optimizing, since "full stack" performance debugging genuinely requires ruling out layers systematically rather than guessing.
A genuine answer should reflect real interest in enterprise/internal tooling — the scale and reliability expectations for systems supporting a company's own hiring and operations are genuinely different from consumer apps, and that's worth acknowledging honestly rather than pretending it doesn't matter.
