Welcome to TechKareer’s technical blog, where we bring you valuable insights from industry experts to help you on your career journey. Today’s feature highlights a powerful tech talk with Devang Sharma, an incoming Software Development Engineer (SDE) at Google. Devang has previously worked at Mobile Premier League (MPL) and Groww, and in this session, he shared his personal experiences, preparation strategies, and industry insights on cracking FAANG interviews, particularly at Google.

The Power of a Job-Specific Resume

Devang emphasized the importance of tailoring your resume for the role you’re applying to. He pointed out that most HR professionals might not be experts in all technical stacks, so it becomes your responsibility to align your resume precisely with the job description. This involves using relevant keywords from the job post and highlighting projects or experience that resonate with that role. For example, if you're aiming for a backend position, make sure your backend-related experiences and technologies are front and center.

Interestingly, Devang stressed that even a referral won't save your application if your resume is misaligned. He noted that he would be sharing his resume template, which played a key role in his own success. His takeaway: customize every application, and don’t rely on a generic resume.

Inside the Google Hiring Process

Devang gave a detailed breakdown of the hiring journey at Google:

Initial HR Outreach: Usually initiated via LinkedIn or email, where the HR checks your availability and briefly discusses your skills and preferences.
HR Screening Call: This conversation explores your experience, coding profiles, and familiarity with Data Structures and Algorithms (DSA). If there's a match, your profile is then aligned with a role and a team.
Technical Screening Round: This round is significant as it only happens once in your lifetime at Google. If you pass it once, you won’t have to repeat it in future applications. Failing this round, however, results in a six-month cool-off period.
Onsite DSA Rounds (Virtual): There are three virtual technical rounds focused on solving DSA problems.
Googliness and Leadership Round: This behavioral round evaluates how well you align with Google’s work culture, your leadership potential, and your problem-solving approach in hypothetical scenarios.
Team Matching: If all rounds go well, your profile enters the team matching stage. Hiring managers from within Google review your resume, and if there's mutual interest, you’ll have a short conversation with the manager.
Hiring Committee Review: If you pass the team match stage, your entire profile and performance in previous rounds go to a hiring committee. Upon approval, you receive an offer, which is followed by background checks and onboarding.

Devang's entire journey took approximately six months—from the HR call in October to receiving the offer in February. Notably, the first technical round was not an online assessment but a proper interview, thanks to a referral. Google also provided one or two mock interviews with actual Google employees to help him prepare.

Mastering DSA for FAANG Interviews: The Striver Way

For aspiring candidates, Devang strongly recommends focusing on DSA, especially for SDE-1 and SDE-2 roles where system design questions are rare. He discouraged investing in expensive “guaranteed internship” courses and instead advocated for free, high-quality resources available online.

His go-to resource was the Take U Forward platform by Striver:

A to Z Sheet: Ideal for beginners, this sheet contains over 450 problems covering everything from basic data types to advanced topics like tries. Each question comes with YouTube tutorials, articles, and practice links. Devang suggests a 3–4 month timeframe for completing this.
Striver’s SDE Sheet: With around 150 questions, this is ideal for those preparing for interviews within 1–2 months. It targets problems frequently asked by top product-based companies.
S79 Sheet: A last-minute brush-up resource with 79 top interview questions. Useful for revising within 15 days of your interview.

Devang stressed not just solving problems but understanding the intuition behind them. He advised taking handwritten notes and identifying patterns, such as using binary search for “minimum of maximum” problems. He also mentioned LeetCode’s Blind 75 as another essential list for FAANG aspirants.

He solved around 250 selected problems and emphasized quality over quantity. Clear communication during interviews is equally important—think out loud, ask clarifying questions, and start with brute-force before optimizing.

DSA Difficulty Across Companies

Devang gave a comparative view of DSA problem difficulty at different companies:

Amazon: Easy to medium level
Google, LinkedIn, Indeed: Easy to hard level
Uber, Rippling, Rubrik: Tend to ask harder, competitive-programming-level questions

Competitive programming can help for some companies but isn’t necessary for Google or most others, where DSA fundamentals matter more.

Navigating Job Opportunities and the Application Process

Devang’s strategies for navigating job openings differ based on company size:

For MNCs: Focus on official career pages. Avoid relying heavily on third-party job portals, which often contain outdated listings.
For Startups: Referrals are key. Startups like Groww and MPL don’t always post public listings. Devang suggests reaching out directly to engineering managers, SD3s, and HRs through LinkedIn or cold emails. He acknowledged the low response rate and advised persistence, follow-ups, and crafting strong messages—possibly using tools like ChatGPT for better outreach.

He mentioned internship programs like Google STEP, Flipkart Runway, and Walmart Spark, which are available from the second year of college and can pave the way to full-time roles.

Job openings are more frequent between January and March, post-appraisal cycles. However, those with less than 1 year of experience might find fewer opportunities compared to those with more.

Comparing Company Cultures: Startups vs MNCs

Devang also shared his observations on work culture:

Early-Stage Startups (~100 employees): Fast-paced, high ownership, extreme learning, low stability, and often lower pay.
Unicorns/Established Startups (500–5000 employees): Blend of startup speed and MNC structure. Good pay, focused ownership, and audacity to pitch ideas.
Big MNCs (Google, Amazon, etc.): Relaxed work culture, strong processes, and excellent work-life balance. You might own a smaller piece of a large product but enjoy perks like food allowances, gym, and a settled lifestyle.

Devang personally prefers MNCs for their chill lifestyle and time for personal projects.

Q&A Session Highlights

Question: I’m struggling to find job opportunities. What’s the best way to approach it?
Answer: For MNCs, always apply through their official careers page rather than relying on job portals, which often list outdated openings. For startups, job openings might not be publicly posted. In that case, directly reach out to engineering managers, senior developers, or HRs through LinkedIn or cold emails. Keep your messages personalized and don’t hesitate to follow up if you don’t get a response initially.

Question: I’m not very strong in DSA but I love building things. What kind of companies should I target?
Answer: Startups are your best bet. They usually care more about what you’ve built and your ability to learn and deliver quickly, rather than your DSA skills. MNCs generally use DSA as a standardized screening method, especially for SDE-1 and SDE-2 roles.

Question: What’s the difference in work culture between big tech companies and startups?
Answer: Big tech companies like Google or Amazon have a relaxed, process-driven work culture with better work-life balance. Startups, especially early-stage ones, are fast-paced with high ownership and faster learning curves, but can be unstable. Devang personally prefers the relaxed lifestyle of MNCs.

Question: How long does it take to complete the A to Z DSA Sheet by Striver?
Answer: Around 3 to 4 months if you’re consistent. It covers over 450 problems and is very detailed, so time and dedication are needed.

Question: I’m from a non-engineering background like B.Com. Can I still get into tech roles at MNCs?
Answer: Yes, absolutely. Focus on building strong development projects and mastering DSA. Having a good grasp of the basics, some solid personal projects, and decent DSA knowledge can get you noticed.

Question: I forget the logic of DSA problems after a day or two. How do I retain better?
Answer: Handwritten notes help a lot. Write down key takeaways, patterns, and edge cases. Also, don’t rush through problems—focus on understanding the logic and intuition behind each solution.

Question: How long did your Google interview process take?
Answer: The entire process took around 6 months. The first tech round was not an online assessment (OA) but a proper interview. This was likely due to having a referral, which helped skip the OA stage.

Question: How did you prepare while working full-time?
Answer: Devang dedicated 3–4 hours each day after work. He solved 10–12 problems daily and made consistent efforts, including sacrificing weekends and holidays. Consistency was key.

Question: Do competitive programming platforms like Codeforces or CodeChef help?
Answer: Yes, they do. Recruiters often check your profile on these platforms. Having a decent rating can add credibility, especially for companies that prefer candidates with strong problem-solving skills. However, they’re not mandatory for every company.

Question: What makes a good project?
Answer: A good project solves a real-world problem, has a well-thought-out design, and showcases your ability to work end-to-end on a solution. Avoid making clones or just following tutorials. Add your own ideas and try to build something original or useful.

Question: How can I improve my communication skills for interviews?
Answer: Practice mock interviews, either with peers or on platforms. Also, watch interview prep videos and understand what kind of communication is expected like thinking out loud, breaking down problems verbally, and clearly stating your approach. This is especially important at companies like Google.

Conclusion

Devang Sharma’s journey to Google reflects a mix of strategic planning, dedicated preparation, and a deep understanding of what top tech companies look for. His actionable advice—from tailoring your resume and mastering DSA using free resources to understanding the nuances of the hiring process—offers a roadmap for any aspiring SDE. Whether you're just beginning or in the middle of your interview prep, these insights are sure to keep you on track and motivated.

Don't forget to visit the TechKareer’s YouTube channel to stay updated with more insightful talks and expert discussions to supercharge your tech journey.

Google’s Devang Sharma: Expert Insights on Cracking FAANG

Table of contents