<?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 Shailee Patel on Medium]]></title>
        <description><![CDATA[Stories by Shailee Patel on Medium]]></description>
        <link>https://medium.com/@shaileepatel?source=rss-f2d052bf3e35------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1CKtbBhkHj3aFeVi4RP8Iw.png</url>
            <title>Stories by Shailee Patel on Medium</title>
            <link>https://medium.com/@shaileepatel?source=rss-f2d052bf3e35------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:45:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shaileepatel/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[Here’s how I prepared for my interviews and landed a job at Google!]]></title>
            <link>https://medium.com/@shaileepatel/heres-how-i-prepared-for-my-interviews-and-landed-a-job-at-google-6b29d7434140?source=rss-f2d052bf3e35------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b29d7434140</guid>
            <category><![CDATA[coding-interviews]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leetcode]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Shailee Patel]]></dc:creator>
            <pubDate>Wed, 15 Sep 2021 09:48:19 GMT</pubDate>
            <atom:updated>2022-08-06T23:50:42.936Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A guide to the helpful resources I used to get offers from Google, other FAANGs and unicorn startups for .</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-0rQs4q2nAuwA4nZJxZXg.jpeg" /></figure><p>If you mention the tech interview process to a room of software engineers, many will speak out against common interviewing practices. A lot of the argument comes from the reasoning that solving algorithms on a whiteboard doesn’t actually represent, or translate to the day to day tasks of a software engineer. For the sake of this article, I won’t go into that conversation. Instead, I’ll explore these different types of interview practices from a candidate’s perspective, and what I learned along the way.</p><p>This article covers <a href="#5d09">interview process</a>, <a href="#bc77">different types of interview</a> (<a href="#3a84">algorithms</a>, <a href="#92db">system design</a> and <a href="#8fcb">behavioral</a>), <a href="#0738">how to prepare</a>, <a href="#d648">when to start</a> and <a href="#607b">useful resources</a> to help you better navigate your tech interviews.</p><h3>Interview process</h3><p>Here are the six high level stages of a typical interview process for a tech company:</p><ol><li>Application:<br>There are several ways to submit your application:<br>​ ​ ​​•​ ​ ​​Company website<br>​ ​ ​​•​ ​ ​​LinkedIn, AngelList, Indeed (or similar) job portals<br>​ ​ ​​• ​ ​Reach out on LinkedIn<br>​ ​ ​​•​ ​ ​​Career fair<br>​ ​ ​​•​ ​ ​​University job portal<br><em>Pro Tip: Try to get a referral when submitting an application</em></li><li>Recruiter call: Typically a 30 min call with the recruiter to go over your background and skill set. Recruiter determines if you move to the next round based on how well you match the job role.<br><em>Pro tip: Have your intro pitch ready and review the job listing you applied for, to bring up relevant skills at appropriate times during the conversation.⁣</em></li><li>Coding challenges: Online assessments typically between 1–2 hrs where you solve a coding challenge that tests your data structure and algorithm (DS&amp;A) skills. You write code to pass test cases (some hidden, some not) for those questions.⁣<br><em>Pro tip: Get familiar with at least one programming language and practice solving problems on Leetcode. I highly recommend getting the premium subscription. This is the link I used to get a </em><strong><em>15% discount on Leetcode</em></strong><em>: </em><a href="https://leetcode.com/subscribe/?ref=db2QbVLj"><strong><em>https://leetcode.com/subscribe/?ref=db2QbVLj</em></strong></a></li><li>Phone screen: Typically 1–2, 1hr technical rounds focusing on DS&amp;A and communication skills. Don’t jump right away into solving the problem and take your time to understand it first. Ask clarifying questions to scope the problem well and identify edge cases.<br><em>Pro tip: Explaining your thought process throughout the interview is as important as solving the problem.</em></li><li>Onsite:A full day of interviews for which the company might fly you out to their headquarters (during covid they are virtual).⁣ This will typically be more intense than the previous technical interviews, and you probably will get harder questions. Depending upon the company and level you are interviewing for, difficulty of the questions might range anywhere from medium to hard. For preparation, study company specific questions on Leetcode, get a good night’s rest. (Make sure you use the $$ the company gives you for food, travel, tourism etc too :P )<br><em>Pro Tip: Prep your behavioral answers (think of many different activities/situations you can talk about, and practice using the STAR — situation, task, action, result — method). Brush up on algorithms and think of edge cases.</em></li><li>Offer: Congrats, you’ve received the offer! What next? Negotiate if you can (competing offers help, especially if they’re lucrative). Also, be sure to ask iIf you need an extension on the offer deadline.</li></ol><h3>The different types of interview I encountered</h3><p>Typically, an on-site will cover three main subjects: algorithm, architecture design, and behavioral, which is what I had studied and prepared for. I’ll briefly go over each of the topics I encountered.</p><h3>Algorithm Interviews</h3><p>The most common type of interview you will encounter. The interviewer will ask you to solve a problem on a whiteboard.This will assess your knowledge of data structures, sorting algorithms, recursion, time/space complexity analysis as well as pattern and edge-case recognition. In this interview, you will most typically come up with a brute-force solution, and then try to improve upon that solution and discuss the tradeoffs, if there are any, with the different solutions you propose.</p><p>This was the bread and butter of my preparation. Every day, I solved algorithms on a hang-up whiteboard, analyzed their time/space complexity as well as trying to understand what happens at each line of code.</p><p>Personally, I really enjoy whiteboard algorithms because I don’t necessarily have to worry about writing compilable syntax (most of the time), and that lets me focus solely on the problem at hand. Other people may dislike whiteboarding, but to them I’d say to practice it consistently and it may change their mind.</p><h3>System Design Interviews</h3><p>This is an interesting interview that I always looked forward to. The interviewer will ask you to design a system (on a whiteboard of course) similar to Google calendar, tiktok feed, facebook messenger, amongst other common systems.</p><p>You are being assessed on how you take a broad concept and design a system that meets all the requirements and constraints. It’s up to you as the candidate to ask the right questions. These will define the requirements and constraints. This interview is more of a conversation mixed in with some drawing diagrams. Everything is quite high-level, so you won’t be writing any actual compilable code.</p><p>Naturally, you should steer the conversation to cover your knowledge of how systems work. I am a full stack engineer, so I talked about architecture patterns, client server interaction, modularization of functionality, how to scale the API endpoints, design database and such.</p><h3>Behavioral Interviews</h3><p>The interviewer will ask you questions about yourself and how you deal with certain types of situations. The preparation for this one isn’t as difficult as the others but does require a lot of introspection on your behalf.</p><p>The questions are typically along the lines of:<br>​ ​ ​​•​ ​ ​​How do you deal with failure?<br>​ ​ ​​•​ ​ ​​What is your biggest weakness?<br>​ ​ ​​•​ ​ ​​How do you resolve conflicts?<br>​ ​ ​​•​ ​ ​​What would you do differently?</p><p>Just be genuine, show passion for your work, own your flaws, show initiative for improvement and you’ll do fine. I recommend practicing using the STAR (situation, task, action, result) method.</p><h3>How you should prepare</h3><p>During my preparation, I always knew that interviewing would be challenging. But I had no idea how hard it actually would be until I was knee-deep into my first interview.</p><p>In the lead-up to the interviews, I had used both <a href="https://leetcode.com/subscribe/?ref=db2QbVLj">paid</a> and free services, which simulated coding and whiteboarding interviews over the phone with people who had experience interviewing candidates in the industry. Those practice interviews were essential for priming me for the pressure I’d feel. But as I later realized, they only amounted to a fraction of what a real interview consists of.</p><p>I’d advise against interviewing at your dream job without having a few mock or real interviews under your belt. The nervousness can be incredibly overwhelming, and it can only be dulled through practice.</p><blockquote>As with many other things in life, practice will improve your confidence.</blockquote><p>Even if you’re already a great programmer in your day job or getting great grades, those skills don’t exactly transfer 1:1 when you’re in a tiny interview room. Persistence, repetition, and consistency with interview preparation and practice will be the key determining factors for your outcome.</p><p>If anyone were to ask me what would be areas to focus on, I’d suggest the following:</p><ul><li>Learn to write code by hand on paper and a whiteboard first and then throw it into an IDE for syntax highlighting, this should become second nature to you.</li><li>Develop deep knowledge of data structures, their strengths, and weaknesses in comparison to each other. I discovered that implementing data structures and their behaviors from scratch taught me so much more than what I knew from their abstract concepts.</li><li>Completely understand Big O notation for both time and space complexities, this will pair perfectly with your algorithm and sorting questions.</li><li>Grasp all major sorting algorithms because the difference in time/space complexities have the potential to derail your optimum solution for an algorithm you’re trying to solve.</li></ul><h3>When to start</h3><p>Depending on your timeline, you may want to start sooner than later. A lot of the companies I interviewed with had a 12 month cooling period before a failed candidate could reapply. On the flip side, if you know you won’t be ready within a year, you may as well start the process now and get a small taste of what it’s like to go through the interview process so when you are ready, it won’t be nearly as scary. Typically, I have seen people take 3–6 months to move into a new role.</p><blockquote><strong>Don’t worry, you’ve got this!!</strong></blockquote><p>Thank you for reading! You can connect with me on <a href="https://www.linkedin.com/in/shailee26/">LinkedIn</a>, <a href="https://www.instagram.com/storiesbyshailee/">Instagram</a>. Happy to answer any queries that you may have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BsviSz3s7bSwN3j6VIMhhA.jpeg" /></figure><h3>Resources</h3><p>Algorithms<br>​ ​ ​​•​ ​ ​​<a href="https://leetcode.com/subscribe/?ref=db2QbVLj">LeetCode</a><br>​ ​ ​​•​ ​ ​​Cracking the Code Interview<br>​ ​ ​​•​ ​ ​​Interview Cake<br>​ ​ ​​•​ ​ ​​HackerRank<br>​ ​ ​​•​ ​ ​​AlgoExpert</p><p>Mock Interviews<br>​ ​ ​​•​ ​ ​​Interviewing.io<br>​ ​ ​​•​ ​ ​​Pramp</p><p>System Design<br>​ ​ ​​•​ ​ ​​<a href="https://github.com/donnemartin/system-design-primer">System design primer</a><br>​ ​ ​​•​ ​ ​​<a href="https://www.educative.io/courses/grokking-the-system-design-interview">Grokking the System Design Interview</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b29d7434140" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to become a Software Engineer without a CS degree?]]></title>
            <link>https://medium.com/@shaileepatel/how-to-become-a-software-engineer-without-a-cs-degree-d5fb637f640f?source=rss-f2d052bf3e35------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5fb637f640f</guid>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Shailee Patel]]></dc:creator>
            <pubDate>Tue, 24 Aug 2021 15:07:45 GMT</pubDate>
            <atom:updated>2022-08-06T23:51:02.189Z</atom:updated>
            <content:encoded><![CDATA[<p><em>My journey of learning to code and landing a job at Google as a Software Engineer</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VUBqGjo_1f1uOtVi1O9Xzg.jpeg" /></figure><p>So you want to learn to code. Fantastic! You’ve heard the chatter about bootcamps, read about how much developers earn, and seen tech startups valued at billions of dollars. It’s the talk of the town, and you’re thinking about checking it out for yourself — maybe even considering a career change.</p><p>Now what?</p><p>In this article, I am hoping I can convey some of the lessons I have learned in this regard with some specific advice for aspiring software engineers. I’ll cover thinking about <a href="#41fd">where to start from</a>, <a href="#f620">how to pick a programming language</a>, <a href="#af36">what is full stack development</a>, <a href="#a49e">how to learn Javascript</a>, <a href="#b0cf">how to acquire an advanced skill set</a>, <a href="#f232">how to choose a bootcamp</a>, <a href="#5d41">process of getting into a bootcamp</a>, <a href="#8480">what I learned at the bootcamp</a> and <a href="#9715">how to continue improving your skill set</a> to help you find your footing in the tech space.</p><h3>Where to start from?</h3><p>In my case I googled the most widely used programming languages and the ones which have a good amount of resources available to learn from. At the beginning, my goal was to learn a language that was easy to pick up. After researching online and talking to friends, it came down to three options: Javascript, Python and Java (sounds similar to Javascript but is entirely different :P)</p><h3>How to pick a programming language?</h3><p>There’s probably a reason you’re thinking about learning to code. Maybe you want to change careers, boost your skill set, or start a personal project. What do you want to be able to do? What do you want to build? For me, it was changing careers and breaking into software engineering. I wanted to learn a language that would help me achieve my goal in the best possible way. As with any field, Software engineering also has a lot of branches you can work in and full stack development is one of the most promising areas to pursue and Javascript is the go-to language for full stack development.</p><h3>What is full stack development?</h3><p>In simple terms, it is a combination of front end development (what users see) and backend development (where the data lives). Javascript is versatile and can be used to develop both the pieces.</p><h3>How to learn Javascript?</h3><p>There are a lot of resources out there to learn javascript and that can be overwhelming. I wanted to learn in a way where I could actually see what I can build using it and so I chose to do an online <a href="https://www.udemy.com/share/101W9C3@f65wEaeC49-XKFMi-t8PbuA76w0S8BpyQ9qBeV5rJF1YadhU2UQVgfuSAN_w_X8U/">web development course</a> from Udemy. I learnt HTML5, CSS3, Javascript, built and deployed web applications. I would say, if you want to learn something quickly, you can’t have your attention scattered everywhere except where you need it. Whatever you pick, focus on it until you have a sufficient mastery of it and only then move on to something else. While it’s still true that learning more than one language or doing more than one course can teach you different ways of seeing things, and even deepen your understanding of your primary language, it is a good idea to start small and build on it.</p><p>Once I finished the course, I felt I had a good understanding of programming in Javascript and building web applications. But, coming from a non-traditional background, I knew I had to improve on my CS fundamentals, more specifically <a href="https://www.udemy.com/share/101X5s3@cbdpX465WqvWkwhMCy4hieWMkbzsVUV5shvgCzeJ2trCKGB4HYF1fZtmU6fAYi-C/">Data structures and algorithms</a> that I learned by enrolling in another course on Udemy.</p><h3>How to acquire an advanced skill set?</h3><p>I got the foundation after doing these courses but there was still a long way to go to acquire the advanced skills required to work as a Software Engineer in the industry. Going forward I had two options, getting a formal degree or doing a coding bootcamp. After a lot of evaluation, I went with the option of doing a bootcamp since it felt more hands-on and accelerated at the same time.</p><h3>How to choose a Bootcamp?</h3><p>There are a lot of coding bootcamps out there but these are some of the things I kept in mind while choosing one:</p><ol><li>Reputation in industry</li><li>Placement of alumni in FAANG companies</li><li>Course Curriculum</li><li>Learning Structure</li></ol><p>Since I am based in the San Francisco Bay Area, I chose Hack Reactor. It is one of the most reputed and the oldest bootcamps in the Bay area. Some other good bootcamp options are Full stack academy, App academy, General Assembly and HackBright.</p><h3>Process of getting into Hack Reactor?</h3><p>It was about a 2 month long process from the application to starting the bootcamp. The process was as follows:</p><ol><li>Submit an application and finish a coding challenge as part of it</li><li>Give a Technical Admissions Assessment</li><li>If admitted, you are enrolled in a month long pre-course</li><li>Successfully complete pre-course to become eligible to start the Software Engineering bootcamp</li></ol><h3>What I learned at Hack Reactor?</h3><p>As part of the program, we developed production grade web applications using cutting edge tech (React, ES6, AWS, Node to name a few) in a project based learning environment, did pair programming sessions and learned to think like a software engineer.</p><p>I worked on developing three full stack projects as part of an agile team, using Trello as ticket management system where I learned how to develop features that keep the end users in mind, designed systems from scratch that handle web traffic at scale, did horizontal scaling, deployment on cloud, load balancing, API development and database optimization.</p><h3>How to continue improving your skill set?</h3><p>If you have the time, creating personal projects is an excellent way to practice/learn coding and get acquainted with frameworks &amp; languages that you might want to use in the future. In addition, having personal projects on your resume can help you stand out, especially if you are just starting out and don’t have much work experience yet.⁣⁣</p><p>Here are some ideas for potential starter projects:</p><ul><li>Personal portfolio website: I’d recommend this as the first project you definitely should do! This is a static website that you can create and deploy where you showcase your accomplishments, projects, work experience, and academics.</li><li>Chrome extensions: These are light-weight Javascript files injected into chrome. Extensions are quite easy to publish and can change your browser/site views in all sorts of cool ways.⁣</li><li>Video games: Even though there are specific languages and game engines most suitable for mainstream game development, you can write a game in almost any language. Coding a game in a new language forces you to learn the basics and functionality of a language better than a lot of other projects.⁣</li><li>Reddit bot: Reddit has a really easy API to work with. If you like browsing reddit, this could be a great choice for you.⁣</li><li>Contribute to open-source: This is often a fantastic indicator that the candidate is willing to go the extra mile, and can do teamwork in a large project. Find a decent-size open-source project for this (maybe not Linux or Python codebases, but something bigger than a toy project).</li><li>Native apps, like iPhone or Android apps</li><li>Blockchain apps</li><li>If you have a problem (however small it may be) in your life that you’d like to mitigate, think of how you could create an app, script, website, extension etc. to make it go away! Chances are that you aren’t the only one with this problem, and others would benefit from your project too.⁣</li></ul><blockquote><strong><em>It takes time to build all the skills needed: Be a marathon runner</em>.</strong></blockquote><p>There’s so much you can do with code. It takes a lot of time and effort to get up the learning curve, and you’ll likely have a lot of late nights bashing your head on the keyboard. But it’s more than worth it for the sense of accomplishment when you look at what you’ve built, and the magic of making something work. Choosing a career in software development is choosing a path of lifelong learning.</p><p>Thank you for reading! You can connect with me on <a href="https://www.linkedin.com/in/shailee26/">LinkedIn</a>, <a href="https://www.instagram.com/storiesbyshailee/">Instagram</a>. Happy to answer any queries that you may have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*QZ237Yqx5B4sOL9G.jpg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5fb637f640f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>