Texas Instruments Interview Experience | Software | 2025 | On-campus
- Result
- Offer
- Location
- On-campus, Top IIT
- Posted
- 11 Dec 2025
Summary
Selected for Embedded Software Role at Texas Instruments after a detailed interview covering problem-solving, algorithm design, and project discussions. The interview included coding challenges, system design, and technical deep dives into open-source projects.
How it went
I walked into the interview room feeling confident, having prepared extensively for the technical aspects. The interview started with a review of my resume, followed by a detailed discussion about my projects and internship. I explained how my ML and SDE projects addressed specific problem statements using established algorithms. The interviewers then asked about my most impactful project, which was a Python package I published with 18,000 users. We discussed licensing choices and the technical pipeline for handling PDF tables. The interview concluded with a coding challenge for the N-Queens problem, where I wrote clean, well-structured C++ code. Despite the initial uncertainty about the final selection, I was thrilled to learn I had been selected directly from Round 1.
Questions asked (2)
- 01
Find the k-th smallest element in an unsorted array
Algorithms · Medium
Implement an algorithm to find the k-th smallest element in an unsorted array of size N. Discuss the time complexity and compare it with sorting the entire array.
- 02
N-Queens Problem
Algorithms · Hard
Write a function to solve the N-Queens problem using backtracking. Explain the constraints used to track column, diagonal, and anti-diagonal positions.
How they prepared
I focused on strengthening my problem-solving skills through LeetCode practice, especially algorithms related to data structures and optimization. I also reviewed my projects and internship work to ensure I could clearly articulate their technical details and relevance to embedded systems. Additionally, I practiced coding in C++ and prepared to explain complex systems like open-source pipelines and licensing decisions.