## My Preparation Journey I had been practicing DSA on LeetCode for around two years and solved the Striver SDE Sheet twice, which helped strengthen my problem-solving approach. Along the way, I explored multiple programming languages including Python, Java, C/C++, and Solidity, and worked with different technologies such as the MERN stack, blockchain, machine learning, and deep learning. This broad exposure made it easier to adapt when Accenture’s requirements were announced. ## Recruitment Process Overview Accenture’s hiring process consisted of four rounds: Online Assessment, Technical Interview, Communication Round, and HR Interview. The role primarily focused on Java. ## Online Assessment (OA) The OA had multiple sections, including aptitude-based questions, a path-finding game, and fast calculation tasks. Strong logical thinking and time management were key to clearing this round. ## Technical Round The technical round was divided into three parts: * **Frontend:** HTML, CSS, and JavaScript basics * **Backend:** Java fundamentals * **Database:** SQL queries and concepts Having clarity in fundamentals helped me navigate this round confidently. ## Communication Round This round tested overall communication skills through multiple sections such as reading comprehension, storytelling, scene explanation, grammar correction, repetition exercises, and a writing section. The writing task included email writing and short story writing, all within a limited time. ## HR Round The HR interview was conversational and focused on understanding me as a person. I was asked to introduce myself, share my favorite college memory, talk about events I hosted, discuss my experience there, mention my most liked and disliked subjects, and finally ask questions of my own. ## Key Takeaways This experience taught me that long-term consistency, strong fundamentals, and clear communication matter a lot. Preparing broadly helped me adapt quickly to role-specific requirements. ## Advice Start early, stay consistent, and don’t limit yourself to just one skill. Your first offer is a result of patience, learning, and belief in your preparation.

## 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.

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 Process 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. mutiple question were asked based on class, Object,and overal OOPs concept. ## 2. Database Management Systems (DBMS) Though not the primary focus, the interview did assess my understanding of database fundamentals and real-world data design. # 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.