There were 2 in person interview. First was DSA with 2 medium-hard questions one was one graph traversal but confusing with DP 2nd one was on 1-D DP. The ML Breadth and Depth round was on mostly self-attention, transformer, encoder, decoder architecture, deep learning training and some classical ML algorithms.The deep learning concepts of overfit and underfitting conditional question was asked at the end of the interview. I would rate this medium-hard level.

✨ Excited to Share! Selected by Versa Network ✨ I’m happy to announce that I have been selected after successfully clearing my interview at Versa Network. The interview process covered a wide range of topics and tested both fundamentals and practical understanding. The key areas included: 🔹 Resume & Project Discussion – Walkthrough of my work, responsibilities, and the project I developed. 🔹 OOPS Concepts – Four pillars of OOPS, virtual functions, and memory layout. 🔹 DBMS – Core concepts and real-world application. 🔹 DSA – Two coding questions (one from LeetCode arrays and one based on linked list basics and implementation). 🔹 Computer Networks – Difference between TCP and HTTP, and related networking principles. I’m grateful for this opportunity and excited for the journey ahead. Looking forward to contributing, learning, and growing with the team! 🚀

There were 2 in-person interview rounds. The first round was pretty straightforward - it had an easy coding questions, a simple puzzle and few logical reasoning and critical thinking questions. The coding question was not too complex, and the puzzle was more about logical thinking. The second round was a bit more challenging. It was a mix of technical questions from my resume, and some tricky SQL questions. The interviewer dug deep into my projects and asked questions about the technologies I had used. The SQL questions were a bit tough, but I managed to answer most of them. Overall, I'd say the interview process was pretty standard, and the interviewers were nice and practicing coding questions, puzzles, and brushing up on your technical skills, especially SQL and data structures will come in handy.

## My Nvidia Technical Test Experience I recently completed a technical test with Nvidia for an Internship + FTE role. The difficulty was medium, and my application is currently in process. Here's a breakdown of my experience. ## The Process The test contained aptitude questions that resembled the logic, problem-solving, and analytical skills needed for JEE mathematics. The questions were designed to assess fundamental abilities crucial for the role. ## Topics Covered & Difficulty The test included questions from Digital Systems, with a focus on Static Timing Analysis, Johnson and Ring Counters, and FSMs (Finite State Machines). There was also a significant portion dedicated to Computer Architecture, covering memory depth and other memory-related concepts. One question involved CMOS regions of operation. The C programming section had three questions where I had to analyze code and determine the output, which were relatively simple.

I recently had the opportunity to interview with Texas Instruments for an internship, and I'm happy to share my experience. Overall, the interview process was quite straightforward and I'm thrilled to say that I was selected! Here's a breakdown of how it went: ## The Process The interviewers were friendly and created a comfortable environment. They started by asking about the projects I've worked on, which allowed me to highlight my skills and experiences. They also inquired about my interested courses and plans for the next semester, showing their interest in my academic background and future goals. The interview lasted around 30-45 minutes, and the conversation flowed very naturally, leaving me feeling at ease throughout. ## Topics Covered & Difficulty The technical questions focused on Digital Design and Verilog, which aligned well with my coursework. The questions were relatively easy, focusing on testing fundamental knowledge. The interviewers built upon some questions to understand my thought process and problem-solving approach. Based on my experience, I'd recommend brushing up on Digital System concepts. ## My Thoughts on the Culture From my interactions, I got a sense that Texas Instruments fosters a collaborative and supportive environment. I would say talk to a lot of people, not just the mentor they assign you. Seek help from the manager as well. Don't get your emotion mingled up cuz i got that spot off on those areas. ## Advice for Others My advice to other candidates would be to thoroughly review the fundamentals of digital systems and be prepared to discuss your projects in detail. It's also important to showcase your problem-solving skills and demonstrate your ability to think critically. Remember to relax, be yourself, and engage in a friendly conversation with the interviewers. Also, don't get your emotion mingled up. This is a place where people are ready to help you out.

Very friendly interviewers. They focus a lot on your projects. Be thorough with low level details of how you have implemented things in your projects. Since I am from a Computer Science background, they asked question about Computer Organization and Architecture, Memory Models and basic C programming (DSA was also covered in this part). One question was on the difference between pass by value and pass by reference functions. Some more questions were asked about memory safe languages (like Rust) since I had written about them in my Resume. Other than that, they also ask about your interests in related domains, (for example they asked me about Linux Driver Development which I was just getting into).

## My Texas Instruments Interview Experience (Internship) Last year, I had the opportunity to interview with Texas Instruments for an internship role. I was selected for technical interviews in both analog and digital domains after passing the initial technical test. The interview process consisted of two rounds. ## Technical Rounds: Digital In the digital technical interview, the questions were mostly direct and focused on fundamental concepts. I was asked about flip-flops, muxes, static timing analysis, and binary-to-hex code conversion. The interviewer also inquired about a startup project I had worked on, wanting to understand my contributions and the technologies I used. The questions were mostly from digital design, including logic gates, muxes, and other digital-related logic. ## Technical Rounds: Analog The analog interview was quite different, featuring tricky questions about op-amps and analog circuits. These questions required a strong understanding of the subject's basics. The interviewer started with RC circuits and progressively added complexity, such as adding an extra capacitor or providing an initial charge, then asking for analysis after each modification. ## Topics Covered & Difficulty The technical interview questions were of medium difficulty and covered a range of topics: * **Digital Design Fundamentals:** Questions on flip-flops, muxes, and logic gates tested my understanding of basic digital building blocks. * **Static Timing Analysis:** This involved understanding timing constraints and how they affect circuit performance. * **Analog Circuit Analysis:** The questions on op-amps and RC circuits required a solid grasp of analog fundamentals. You can find the exact wording of the questions I was asked in the dedicated section below. ## Company Culture Overall, the company culture at Texas Instruments seems very positive and supportive. ## Advice for Others My advice to others is to focus on the basics of digital systems and have a strong foundation in analog circuits if applying for an analog role. Understanding the fundamentals is key to tackling the more complex problems they might present.

Okay, here's my interview experience with Amazon for an internship position. Unfortunately, I was rejected after the technical round, which I found to be of medium difficulty. Let me walk you through it. ## The Process The interview was technical and started with brief introductions. We then jumped straight into two Data Structures and Algorithms (DSA) questions. The first was based on binary search, specifically searching on answers. I managed to solve it partially but struggled with the edge cases. The second question was about finding the Lowest Common Ancestor (LCA) in a binary tree. I solved it, but my solution was a bit complex. ## Topics Covered & Difficulty The interview focused on Data Structures and Algorithms. One question involved a medium-difficulty binary search problem where I had to efficiently search for an optimal solution within a range, but I struggled with some edge cases. The second question was a standard tree problem, specifically finding the Lowest Common Ancestor in a Binary Tree. While I solved it, I made it a bit more complex than necessary. You can find the exact wording of the questions I was asked in the dedicated section below. ## My Thoughts on the Culture Amazon is one of the best companies in the world, and it definitely has a great company culture. The environment seemed very focused and driven, with a strong emphasis on problem-solving and innovation. ## Advice for Others My main advice would be to write clean, well-documented code and explain your thought process clearly. The interviewer specifically told me to improve my code writing and explanation skills. Even if you solve the problem, poor code quality or a lack of clear communication can be a reason for rejection. Focus on making your code easy to understand and articulate your reasoning behind each step. Good luck!

Interviewing with Hummingwave Technologies for a Software Development Engineer (SDE) position was one of the most enriching technical discussions I’ve had so far. The interview lasted around 50–55 minutes and covered a spectrum of topics — from fundamental OOP concepts and database management to a deep, detailed discussion around the projects on my resume. I’m happy to share that the experience went well, and I ultimately secured the offer. Here’s a detailed walkthrough of the interview. The interview began with a short personal introduction from both sides. I was asked to walk the interviewer through my background, technical interests, and key projects. This quickly set the tone for a conversation that was both technical and exploratory. 1. Object-Oriented Programming (OOP) A significant portion of the early interview revolved around OOP. The interviewer focused more on conceptual clarity and practical usage than theoretical memorization. Questions : What are the four pillars of OOP? Explain the difference between a class and an object. How does polymorphism differ at compile time vs runtime? What is abstraction, and how do you implement it in a real application? How do interfaces differ from abstract classes? If you were designing your Plant Recognition System using OOP, how would you structure the classes? How would you use inheritance or composition to reduce redundancy in your ML pipeline components. 2. Database Management Systems (DBMS) Though not the primary focus, the interview did assess my understanding of database fundamentals and real-world data design. Questions : What is normalization, and why is it important? Difference between primary key and unique key. Explain the different types of JOINs with examples. Design a table schema for storing movies and user ratings (related to my movie recommendation project). 3. Deep Dive into My Projects This was the longest and most detailed segment of the interview. The interviewer wanted to understand the depth of my involvement, my problem-solving approach, and the reasoning behind my technical decisions. A. Plant Recognition System Questions What dataset did you use and how did you prepare it? Why did you choose your specific model architecture? How did you handle class imbalance? If accuracy drops under low-light conditions, how would you improve robustness? How would you reduce inference time without significantly affecting accuracy? B. Movie Recommendation System Did you use collaborative filtering, content-based filtering, or a hybrid approach? What features did you extract? How did you compute similarity between users or movies? How do you measure the performance of a recommender system? How would you solve the cold-start problem for new users? How would you scale the recommendation pipeline as data volume grows? C. Camouflaged Object Detection This project attracted special attention due to its complexity and uniqueness. Questions : What makes camouflaged object detection a challenging task? Which model architecture did you use? How did you evaluate model performance? If objects blend almost perfectly with their surroundings, how can the model be improved? How would you adapt your model for real-time video detection? I think they were evaluating my understanding of model optimization, domain challenges, data processing, and deployment considerations. This is the end of questions. The interview concluded with a short discussion about: My preferred tech stack How I usually debug issues My willingness to learn new tools and adapt They also allowed me to ask questions about the role, team structure, and company culture. Final Result After some days, I received the confirmation that I had been selected for the SDE role at Hummingwave Technologies. The interview was well-structured, conversational, and intellectually engaging. What stood out most was the company’s emphasis on understanding thought process over memorized answers. This experience circulated around the importance of strong fundamentals combined with practical, hands-on project knowledge.

There was a test before the interview that consisted of aptitude and English grammar sections, followed by a technical interview. The technical interview mostly revolved around my projects and some CS fundamentals. Questions were asked from topics such as computer networks, OS, and DBMS. Most of the aptitude questions were of easy to medium difficulty, but the English grammar section was quite difficult. The interview is easy to clear if you can explain your projects clearly and confidently.