<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Minh Nguyen on Medium]]></title>
        <description><![CDATA[Stories by Minh Nguyen on Medium]]></description>
        <link>https://medium.com/@nameisminh1?source=rss-f0b1f6f67ef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Minh Nguyen on Medium</title>
            <link>https://medium.com/@nameisminh1?source=rss-f0b1f6f67ef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:23:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nameisminh1/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I utilised LeetCode to get multiple tech job offers]]></title>
            <link>https://medium.com/@nameisminh1/how-i-utilised-leetcode-to-get-multiple-tech-job-offers-5aa634c851ac?source=rss-f0b1f6f67ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/5aa634c851ac</guid>
            <category><![CDATA[leetcode]]></category>
            <category><![CDATA[data-structure-algorithm]]></category>
            <category><![CDATA[coding-interviews]]></category>
            <category><![CDATA[algorithms]]></category>
            <dc:creator><![CDATA[Minh Nguyen]]></dc:creator>
            <pubDate>Sun, 01 Jan 2023 22:56:10 GMT</pubDate>
            <atom:updated>2023-01-01T22:56:10.344Z</atom:updated>
            <content:encoded><![CDATA[<p>After sharing my journey of landing a job at Amazon, I’ve gained some interest in <a href="https://www.reddit.com/r/leetcode/comments/1005e3k/going_from_failure_to_faaang_my_journey/">this reddit post</a>, with questions into what went down into my preparation surrounding LeetCode going into my interviews.</p><p>Here are my answers to these questions.</p><blockquote>How long did it take?</blockquote><p>I prepared 2–3 months in advance of my interviews for big tech in 2022. During this time I spent around 2–3 hours a day preparing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*xIGxqiNs6QFg9MkxczBaww.png" /><figcaption>leetcode submission breakdown (2022)</figcaption></figure><p>On a longer term scale, here are my submissions across the years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8c2oA5BrR7dW5qO8w2CCFA.png" /><figcaption>2020 submissions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5DnVNKgftZsDx4-ttF76A.png" /><figcaption>2021 submissions</figcaption></figure><p><strong><em>Lessons learnt</em></strong></p><ul><li>On a year to year timeframe, I would have been better off leetcoding more consistently (30 minutes — hour everyday), rather than preparing in bursts a month or two prior to.</li></ul><blockquote><em>How much LeetCode? Easy medium hard ratio?</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_6-r4ITYVTGC4HlL-j2deQ.png" /></figure><p>This is my current breakdown, at the time I finished up my latest interviews in April, I had around ~450 questions completed.</p><p>Thoughts</p><ul><li>You’re not gaining any benefit by doing the types of questions your already comfortable with. If your crushing easy’s, increase the amount of mediums that you’re doing etc. Be deliberate about your practise, get the most value out of your time.</li></ul><p>Things I would have done differently</p><ul><li>Probably an ideal ratio would have been 1 : 3 : 1. Most questions asked in interviews are medium, so if you’re able to complete those comfortably your in a good spot to start interviewing.</li></ul><blockquote>Topic-wise or just random questions or Blind 75 etc?</blockquote><p><strong>Going into my Amazon/Atlassian/Canva/Google interviews this year</strong></p><p>I did the daily LeetCode questions, along with going through the top questions from amazon interview list provided by my LeetCode premium subscription.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/1*8OdRMHHinFvp4eZRTCsiNw.png" /></figure><p>This list was quite helpful in me preparing for amazon, as the questions I did end up getting were of similar difficulty / style. I would recommend going through company specific list if you have a strong preference for a specific company.</p><p>(You probably don’t need premium for doing something similar, theres a free company lists by using tags e.g. <a href="https://leetcode.com/company/amazon/">amazon list free</a>)</p><p><strong>Lessons learned</strong></p><p>When I started using leetcode, I was doing random questions. This goes against the grain of deliberate practise. The most effective way I could have started was about 20–40 easy’s, then mastering the <a href="https://leetcode.com/discuss/general-discussion/460599/blind-75-leetcode-questions">blind 75 list</a>. From that point you’d be well rounded enough to start interviewing, and I truly believe with around another 100 questions that consistently challenge and build up my skills, I would be just as effective with my ~450 questions.</p><p>So lesson is that quantity of questions doesn’t matter as quality of questions, and to get a level where you can comfortably go through common interview questions would be around ~200 questions.</p><blockquote>What resources did you use for prep / DSA?</blockquote><p>This has been a common question.</p><p>75% of my knowledge of Data Structure and Algorithms came from doing the DSA course at university, and grinding my butt off for that course specifically. The rest of my knowledge came from just googling things I didn’t understand when LeetCoding, and also utilised the answers / discussion section in LeetCode questions.</p><p>There may have been some miscommunication on my end, with many people asking me to DM them a specific resource (I was meant to imply I was going to answer the question in this post and link them the post).</p><p><strong>But what if I flunked that course in uni/college, or am self taught?</strong></p><p>The internet is your friend. Everything you know is online and free, for example here’s a <a href="https://www.youtube.com/watch?v=8hly31xKli0">popular course to learn DSA from scratch</a>.</p><p>The ideal process would be: learn a new data structure -&gt; do some easy LeetCode questions tagged with that data structure -&gt; repeat</p><p>And as obvious as it may sound just google things you don’t know / like ti know.</p><blockquote>If topic-wise, which topics did you realize were the most important?</blockquote><p>I just happened to do enough questions where I eventually got good coverage of all types of questions that would be asked.</p><p>If you can comfortably complete the leetcode blind 75, you’ve had enough coverage as well.</p><p>But to answer this question, and using <a href="https://leetcode.com/explore/interview/card/top-interview-questions-easy/">this list</a>, heres my breakdown of the most topics by importance:</p><p>TIER 1 (MUST)</p><ul><li>Arrays, Strings, Linked Lists, Trees, Sorting and Searching</li></ul><p>TIER 2 (Not asked as much as TIER1, but only move to this once you’ve done your fair share of TIER1 questions).</p><ul><li>Dynamic programming</li></ul><p>TIER 3 (semi-important, and involve a combination of tier 1 topics as well, but I wouldn’t categorise these as fundamental as TIER1)</p><ul><li>Design and Math questions</li></ul><blockquote>Would you say 450 questions is required to get into amazon?</blockquote><p>Definitely not. Entirely situational on your circumstances / capability / how you practise.</p><p>In hindsight, if I knew what I knew now in terms of effective practise, I could do it in 150–200 LeetCode questions.</p><p>But to answer another question — ‘when should I be able to start interviewing’ — I think once you are comfortable with most medium questions (for me probably around 150–200 questions), you should start interviewing.</p><h4>Reflections</h4><ul><li>Be deliberate about your practise, you should be doing questions that challenge you, but not to the point where it is too hard for you to complete the question. Focus on relevant topics that you struggle on, and if you’re preparing for a specific company, its useful to utilise LeetCode’s company specific question list.</li><li>Don’t hold interviewing back for too long. Once you’ve done 100–200 questions, you should start interviewing. Even if you don’t succeed, you’ve gained some practise / feedback to use going forward.</li></ul><h4><strong>Whats Next</strong></h4><p>After having achieved my goal of landing a job in Big Tech, I’m now focused on becoming a better Software Engineer / growing my career, and creating tech related content online.</p><p>You can <strong>f</strong><a href="https://twitter.com/minhdev_"><strong>ollow my twitter here</strong></a> as I continue to document my journey.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT5LMMhtMAD90mU8TK%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fseason-17-the-simpsons-17x6-xT5LMMhtMAD90mU8TK&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2FxT5LMMhtMAD90mU8TK%2Fgiphy.gif%3Fcid%3D790b7611d22c6b322d032139e5e9b003b12c5fea665466f0%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="328" frameborder="0" scrolling="no"><a href="https://medium.com/media/86ba49c4f213e1bc87de41e39b4720fe/href">https://medium.com/media/86ba49c4f213e1bc87de41e39b4720fe/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5aa634c851ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Going From Failure To Getting Offer at FAANG]]></title>
            <link>https://medium.com/@nameisminh1/going-from-failure-to-getting-offer-at-faang-36acf9e08fc6?source=rss-f0b1f6f67ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/36acf9e08fc6</guid>
            <category><![CDATA[faang]]></category>
            <category><![CDATA[big-tech]]></category>
            <category><![CDATA[looking-for-a-job]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Minh Nguyen]]></dc:creator>
            <pubDate>Sat, 31 Dec 2022 19:33:33 GMT</pubDate>
            <atom:updated>2022-12-31T19:33:33.935Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m Minh, currently a Software Engineer at AWS. I wanted to write this post to document my journey from near failure of finding any success in my career, to landing a job offer in big tech.</p><h3><strong>Struggles after High School</strong></h3><p>After grinding hard in my final year of high school to achieve a high academic score, I was feeling extremely burnt out in 2016. Choosing to study a degree in commerce/adv math, I struggled to even sit down to study for even 30 minutes, let alone finish a whole degree. I dropped after about a week.</p><p>For the rest of the year, I spent my days at internet cafes grinding League of Legends, to pass the time and figure out what I would do with the rest of my life. I thought this would be the end of my academic road, considering careers where I did not have to grow at all — jobs where I could pass time, go home and then play my video games.</p><h3>Starting my Computer Science degree</h3><p>In the latter half of 2017, I started studying computer science, however, by that time, I was so out long from doing any form of studying that getting into the introductory math and programming courses felt impossible for me to get through. I shortly dropped out, however these failures left some imprints on my academic transcript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-xQFI-7dAjyzMiqBNgnx-Q.png" /></figure><p>(AW means academic withdrawal).</p><h3>The slow grind to success</h3><p>I chose not to give up and decided continue my studies the following year in 2018. Taking on a part time load, and spending the holiday break to get into programming in my own time allowed me to achieve some successes in terms of making progress with my degree and finishing up a few courses.</p><h3>Finding an Internship</h3><p>In the year 2020, I wanted to find a Software Engineering internship. Thinking that this would be smooth sailing (I had about a 74 WAM with no previous experiences), I started shotgunning and applying for a tonne of places with a resume I created in about an hour.</p><p>My worst mistake is thinking this was purely going to be a numbers game. I had about 3 interviews, failed them all, and about 50 applications in I ended up with no offers. This was quite a big blow mentally, due to my expectation that if I applied for enough places I would end up with at least a few offers.</p><p>I made a last attempt to find any form of meaningful experiences that would help with my CV. I applied to a few unpaid student programs related to tech, and ended up getting an offer to join a student program with the label of an ‘internship’, which was better than nothing.</p><p>During this time, I luckily managed to pickup a tutoring position at my university, allowing me to get some more relevant things to put onto my CV.</p><h3>Final year of studying</h3><p>In my final year of studying, after racking up some things to put into my CV, I failed many Graduate Software Engineering position interviews despite leetcoding and spending a decent amount of time preparing. I settled with a Software Testing position I found, thinking it would be better than nothing.</p><p>After around 5 months, I took another shot to apply to graduate software engineering roles, and long behold, nearing the end of the year managed to get my first offer.</p><h3>Applying for Big Tech</h3><p>In 2022, I made the decision to take my shots at applying for big tech companies when the opportunities arose. These openings came earlier than expected, and I managed to get interviews for Google, Amazon, Atlassian and Canva.</p><p>Learning from my previous mistakes of shotgunning every role, I focused on these few companies, and prepared specifically for each position. I grinded leetcode more than I ever did, and did a bunch of mock interviews where I could really familiarise myself with an interview setting. I also prepared religiously for the behavioural portions of these interviews.</p><p>After religious preparation and execution, I managed to get an offer at Software Development Engineering (I) position and Amazon web services and accepted the offer.</p><h3>Lessons learnt</h3><p>Even if you are struggling in your degree / other areas, getting a job in tech/FAANG is still very possible, just don’t expect it to go as smoothly as you may think it would be. Take on opportunities that are available, and utilise the experiences as leverage to move onto the next role.</p><h3>Whats next</h3><p>Now, I’m learning to become an excellent Software Engineer, and would love to help others who are struggling / need advice getting into tech as well. I aim to create more content online.</p><p>You can <strong>f</strong><a href="https://twitter.com/minhdev_"><strong>ollow my twitter here</strong></a> as I continue to document my journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36acf9e08fc6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>