Preparing for a job interview is a journey, especially after 16 years in the IT industry. I can confidently say that finding a new job is not a simple task. Life teaches us that nothing worth achieving comes easy; the satisfaction gained from overcoming challenges is both profound and lasting.

Whether you are a recent college graduate or an experienced professional seeking new opportunities, I hope this blog provides valuable insights to assist you in your job search. When I first embarked on this journey, I felt overwhelmed by the multitude of resources available. It took time, but I eventually identified several key resources that were truly beneficial.

Two Paths to Job Searching

In my experience, I’ve observed two primary paths to securing a job: the Self-Determined Journey and the Reference Journey. While there are certainly other avenues, I will focus on these two for the sake of clarity.

1. The Self-Determined Journey

This is akin to the experience of a fresh graduate entering the job market without any support. Many warned me that securing interviews would be challenging; however, I discovered that a solid profile—backed by effective resume writing—can indeed attract attention.

Being a passionate, continuous learner is crucial. It’s not enough to merely stay updated on the latest technologies; you must also be thoroughly prepared for interviews. This journey is about self-discovery and resilience, and every effort you invest can enhance your chances of success.

2. The Reference Journey

The Reference Journey, on the other hand, begins by leveraging your network. While this approach can lead to quicker interview calls, it still requires a strong foundation of preparation. Once you receive a call, your skills and readiness will determine the outcome. Thus, a preparation mindset is essential.

Essential Resources for Job Seekers

There is a wealth of resources available online, including YouTube channels and books, that can guide you through the interview preparation process. Here, I’ve compiled some quick references for job seekers that may serve as a helpful starting point.

While waiting for the right opportunity to come your way, embrace continuous learning and maintain a positive attitude. This mindset is often more important than securing an immediate job offer.

Remember, failures are stepping stones to success!

The Interview Process

Most companies will require you to navigate through approximately six interview rounds, typically structured as follows:

DSA/Technical Round

Demonstrate proficiency in your chosen programming language and showcase your coding fluency by solving problem statements. Ensure you cover edge cases and clarify the problem before diving in.
Topics to Cover:

Arrays, Strings, Two Pointers, Sliding Window, Stack, Queue
Linked Lists (Single, Double, Circular)
Sorting (Bubble, Insertion, Selection, Quick, Merge)
Binary Search, Trees, Tries, Heaps/Priority Queues
Recursion, Backtracking, Graphs, Greedy Algorithms, Dynamic Programming

Resource: Top LeetCode playlists and questions can be found under https://github.com/AnithaRajamuthu/InterviewExperience
Few of Good Reads (PDF Soft copy Books) can be located https://github.com/AnithaRajamuthu/Interview.git

Coding Platforms : Hacker Rank, Codelity widely used in most of companies

High-Level Design

Understand the fundamental building blocks of system design. Research company blogs to learn how complex problems are solved in enterprises. Design your solutions for the top 20 problems you encounter, being specific about the data structures you would use.

Low-Level Design

Refresh your knowledge of SOLID principles and design patterns, and engage in coding practice.

Hiring Manager Round
This round focuses on behavioural questions and your past project experiences. Prepare examples that showcase your skills and achievements.
Leadership Round (Optional)
- This round is primarily for professionals at the P5 level and above, focusing on architectural design questions.
HR Round
- The final stage involves discussing the offer and negotiating terms.

This is a general overview based on my experiences with various companies, and the order and number of interview rounds may vary by organization.

Adding some tips around common pitfalls and solutions here (Might help for experienced interviews)

1. Inadequate Problem-Solving Approach

Pitfall: Jumping straight into a solution without fully understanding the problem.

Explanation: Often, candidates rush to provide a solution before fully understanding the scope of the issue or its business context. This can lead to proposing solutions that miss the mark or overlook key requirements.

Solution: Take the time to clarify the problem. Ask thoughtful questions to gather details about the business context, scope, and impact. This ensures your solution is aligned with the actual needs of the organization.

2. Overcomplicating Solutions

Pitfall: Proposing overly complex or over-engineered solutions.

Explanation: While it’s tempting to showcase advanced technologies or elaborate designs, simplicity is key. Overcomplicating a solution can lead to unnecessary costs, complexity, and long-term maintenance headaches.

Solution: Tailor your solutions to the scale and needs of the organization. Avoid proposing bleeding-edge technologies unless they are truly necessary. A simple, scalable, and maintainable solution is often the most effective.

3. Not Understanding the Company’s Tech Stack

Pitfall: Failing to align your solutions with the company’s existing technology.

Explanation: Architects are expected to work within the company’s established tech stack. Suggesting new technologies that don’t integrate well with existing systems can cause unnecessary disruption or require steep learning curves.

Solution: Research the company’s current tools and frameworks before the interview. Design solutions that complement and enhance the existing infrastructure, ensuring your suggestions are both feasible and scalable within the current ecosystem.

4. Inability to Handle Trade-offs

Pitfall: Failing to address the trade-offs between different architectural decisions.

Explanation: Every design decision comes with trade-offs—whether it’s cost, performance, security, or time-to-market. Ignoring these trade-offs can make you seem inexperienced or unprepared.

Solution: Discuss the pros and cons of each solution you propose. Highlight how your design balances competing factors and how you would adjust based on business priorities, security needs, or budget constraints.

5. Not Considering Non-Functional Requirements

Pitfall: Focusing only on functional requirements and neglecting non-functional aspects like scalability, security, and performance.

Explanation: IT Architects must design systems that not only meet functional requirements but also excel in non-functional areas. Ignoring these factors can result in solutions that perform poorly under real-world conditions.

Solution: Always consider non-functional requirements such as security, scalability, and maintainability in your designs. Ensure that your architecture can handle growth, secure sensitive data, and perform under stress.

6. Not Demonstrating Leadership and Stakeholder Management Skills

Pitfall: Focusing solely on technical details and not showing how you lead and manage stakeholders.

Explanation: IT Architects often lead teams and collaborate with a variety of stakeholders, from developers to business executives. Failing to demonstrate your leadership and collaboration skills can make it harder for interviewers to gauge your fit within the organization.

Solution: Highlight your experience working with cross-functional teams. Emphasize how you communicate complex technical concepts to non-technical stakeholders and manage conflicting priorities within a team.

7. Not Practicing with Design Tools

Pitfall: Struggling with design tools or visual aids during the interview due to lack of familiarity.

Explanation: You may be asked to sketch an architecture or use tools like Lucidchart, Visio, or a whiteboard to present your design. If you’re not comfortable with these tools, you risk wasting time and presenting an unpolished solution.

Solution: Practice using common design tools and diagrams, such as UML or system flowcharts, before the interview. Focus on creating clear, simple diagrams that communicate your ideas effectively. Even if the diagram isn’t perfect, clarity is key.

Sometimes, even after clearing multiple rounds, you may get ghosted with no communication. As a fresher, you might end up doing 3 rounds of DSA for an experienced role due to HR oversights. Don’t let these setbacks distract or discourage you—expect the unexpected. Stay confident, positive, and calm, knowing the right opportunity will come. Treat every challenge as a stepping stone toward your next success.

Wishing you all the best in your job search ! Embrace the journey, stay strong, and

keep learning. Good luck!

Navigating the Job Search: Insights from few months experience