<?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 David Lee on Medium]]></title>
        <description><![CDATA[Stories by David Lee on Medium]]></description>
        <link>https://medium.com/@david.lee?source=rss-25cf8e6a164c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*eXuvqmYwrdCGrKC2.jpg</url>
            <title>Stories by David Lee on Medium</title>
            <link>https://medium.com/@david.lee?source=rss-25cf8e6a164c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 01:44:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@david.lee/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[Square Interview Experience (Part 2)]]></title>
            <link>https://medium.com/@david.lee/square-interview-experience-part-2-b0c7525b9d48?source=rss-25cf8e6a164c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0c7525b9d48</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[square]]></category>
            <category><![CDATA[internships]]></category>
            <dc:creator><![CDATA[David Lee]]></dc:creator>
            <pubDate>Fri, 06 Nov 2015 05:04:56 GMT</pubDate>
            <atom:updated>2015-11-06T05:04:56.218Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Onsite Interview</h4><p><em>If you missed it, here’s “</em><a href="https://medium.com/@david.lee/my-square-interview-experience-part-1-957bf6c01e08"><em>Square Interview Experience (Part 1)</em></a><em>”</em></p><p>On October 16th, four days after the on-campus interview, I received an email from my original recruiter (names have been redacted):</p><blockquote>David,</blockquote><blockquote>Congratulations! We’re excited to be moving forward with your application and are writing to invite you to a full day of onsite interviews at our <a href="http://www.wired.com/business/2013/10/square-new-office/">new office</a> in San Francisco!</blockquote><blockquote>I want to introduce you to a couple VERY important people who will take you through the remainder of the process: [redacted] (cc’d) will now be your primary recruiter, and [redacted] (also cc’d) will coordinate any logistics with your travel/application, etc.</blockquote><blockquote>At this time, <strong>please email [redacted] and cc [redacted] with the following information:</strong></blockquote><blockquote>1.<strong> Preferred onsite dates</strong> (Fridays preferred, Tuesdays as secondary option)</blockquote><blockquote>2. Will you need need <strong>travel accommodations </strong>(hotel, flight, etc.)?</blockquote><blockquote>3. Any <strong>updates</strong> on your job search (offer deadlines, etc.)?</blockquote><blockquote>4. Type of <strong>work</strong> (Android, iOS, Web, Risk, etc.) you’re most interested in</blockquote><blockquote>Thanks again, and we look forward to seeing you again soon!</blockquote><p>Thrilled, I emailed the recruiters with the necessary information and waited for confirmation for next steps. On October 19th, I confirmed my interview date (November 3rd) and waited for more information.</p><p>Both my recruiters were amazing. They were very prompt with replies to all the questions that I had about logistics. I requested a flight a few days in before my interview to explore San Francisco, which they were more than willing to provide. They did make it clear that I was responsible for my own hotel accommodations besides the night before the interview, which is very fair.</p><p>Before my flight out to San Francisco, I was sent three emails. One contained a link to the Square Orbitz account, which enabled me to book my flight. The next was the hotel reservation, which was booked by Square, with my reservation number. The last email had information about reimbursements, what to expect, and general information about the interview, including a schedule of the day’s events:</p><blockquote>During each interview, you will write code with one of our engineers. The engineer will present a question and you’ll have approximately 45 minutes to come to a workable solution. All questions are rooted in algorithms and real world production. You’ll have about 10–15 minutes at the end of each to ask specific questions about our work, teams and culture.</blockquote><blockquote>9:15 Arrival</blockquote><blockquote>9:30 Breakfast with the Campus Team</blockquote><blockquote>10:00 Interview 1</blockquote><blockquote>11:00 Interview 2</blockquote><blockquote>12:00 Tour</blockquote><blockquote>12:15 Recruiter Close</blockquote><blockquote>12:30 Departure</blockquote><h3>The Night Before</h3><p>Square booked me at Hotel Abri, located very close to the Powell Street BART station.</p><p><a href="http://www.yelp.com/biz/hotel-abri-san-francisco">Hotel Abri - Union Square - San Francisco, CA</a></p><p>The day before, I did some more practice problems from HackerRank and LeetCode. Having gone through the on-campus interviews, I felt a little more prepared to tackle pair-programming- as such, I solved the practice problems in the exact same way that the on-campus interviews went. If you’re looking to prepare for the Square onsite interview, I highly suggest solving questions by writing them in your own development environment and your own test cases. For me, this was the preferable method of practicing over online environments like the ones provided by HackerRank and LeetCode because it was the exact same environment as the environment in my interview, and it gave me the chance to think of and write my own test cases, including edge cases. Writing my own test cases forced me to think of other implementations, which benefitted me when describing multiple approaches to the interviewer.</p><p>However, the biggest piece of advice I can give the day before the interview is this:</p><p><strong>Just. Relax.</strong></p><p>I can’t stress this enough. I had trouble with this for interviews before the Square onsite one- I would attempt to try all the practice problems and read through Cracking the Coding Interview for the n-th time. However, I realized that there aren’t many things that I could improve that would make a noticeable difference in my coding style, so it’s better to get a good night’s sleep and wake up the next morning feeling rested and ready rather than sleepy and stressed out.</p><p>The next morning, I woke up fairly early. I took an UberPool to Philz Coffee, bought some coffee to bring back to New York, and headed to Square’s office.</p><h3>The Interview</h3><p>Square’s office is located on 1455 Market Street, in the same building as Uber. The building receptionist gave me a key to access the elevators, which brought me to the Square lobby.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*72i4Kb48_xGUQKCV6BXfwg.jpeg" /><figcaption>Courtesy of Officelovin’ (Note: I forgot to take pictures of the office, which I sorely regret)</figcaption></figure><p>The receptionist had me sign in, sign an NDA, and take a picture, after which she handed me a name tag and showed me a place to leave my backpack and luggage (my flight was at 4:30 in the afternoon, so I planned on leaving immediately). I chatted with the fellow candidates until the recruiters who were had been in contact with arrived.</p><p>After a quick rundown of the schedule, we went for breakfast at the restaurant located a few floors above the lobby. There were a bunch of different options- breakfast tacos, an omelette bar, bagels and toast, cereals, etc. (Note: the plates are square-shaped. I pointed this out and one of the recruiters started laughing).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EjGCsvp8B45W8aiEKb_ZQA.jpeg" /><figcaption>Courtesy of Officelovin’</figcaption></figure><p>We sat down in a cafeteria with gigantic windows that gave us a great view of the city and chatted with the recruiters to get to know them better as well as to learn more about what it what it was like to work at Square and their favorite things about working in San Francisco. After breakfast, we went back into the lobby, were given the opportunity to pick up snacks or coffee and use the restroom, and went into the interview area.</p><p>The interview area was basically two rows of tables with iMacs and two seats, two keyboards, two keyboard mice, and a pad of paper at each iMac. Just as before, the interviewers introduced themselves and then immediately gave me a question to implement. After about 45 minutes, I was given a chance to ask the interviewers about their work and other questions about Square that I had.</p><p>The onsite interview questions were no different in terms of difficulty or structure from the questions during the on-campus interviews, but interview nerves had me stumbling over some bugs and implementation details. Again, it’s important to stay calm; it’s easy to make a single mistake that could make you think “OMG I screwed up” and make you even more stressed out. Remember, the interviewers are there to help you, so there’s no shame in asking for help when you need it either. The interviewers will be more than willing to give you advice and actually code themselves as well.</p><p>The same pieces of advice that I wrote about in my previous article about on-campus interviews applies to the onsite interviews. Know how to actually use data structures and algorithms and discuss other possibilities. In fact, it’s best to keep on talking throughout the entire interview; it might be hard to think while you talk, but it shows the interviewer your thought process, which is the most important part of their evaluation.</p><p>I found that the pad of paper was also a very nice addition to the interview environment. I find it very helpful to draw out my thoughts, especially when dealing with certain data structures that are easier to explain with the aid of a drawing than with just words.</p><p>There were two interviews back to back. After the second one, we were given a tour of the office, including a gallery of the first few iterations of the Square credit card reader and sketches of the first app, the new staircase that linked the top floors to the bottom ones, a robot that could move around the office for meetings from remote locations, and the different conference rooms named after various world currencies or places in San Francisco (my favorite ones are the ones that are named after different squares in San Francisco- Union Square, for example, is the main conference room for important meetings). The office is amazing. Employees were scattered about in different areas in the office to work. It almost has an Apple-esque feel because of how modern and minimalist it is.</p><p>After the tour, we wrapped up the day with a free shirt, messenger bag, and water bottle as well as details about what to expect next in this process. I headed for burritos in the Mission at El Farolito with a couple other candidates and took an Uber to the airport for my flight back after lunch.</p><h3>Final Thoughts</h3><p>I was thoroughly pleased with my interview experience with Square. The recruiters were very helpful, the interviewers were passionate and genuinely excited to work for Square, and I am a huge fan of their pair-programming methodology for interviews because it allowed me to show off how I think while I code. As a recap of the advice that I have for future candidates:</p><ol><li>Know <em>how </em>to implement and use data structures</li><li>Explore different possible solutions</li><li>RELAX</li><li>Keep on talking</li></ol><p>Overall, I would say that the interview experience was a success. Even if I don’t receive an offer, I am grateful to have participated in this process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0c7525b9d48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Square Interview Experience (Part 1)]]></title>
            <link>https://medium.com/@david.lee/my-square-interview-experience-part-1-957bf6c01e08?source=rss-25cf8e6a164c------2</link>
            <guid isPermaLink="false">https://medium.com/p/957bf6c01e08</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[square]]></category>
            <dc:creator><![CDATA[David Lee]]></dc:creator>
            <pubDate>Wed, 04 Nov 2015 23:10:08 GMT</pubDate>
            <atom:updated>2015-11-06T05:05:28.771Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Resume Screen and the On-Campus Interview</h4><p>For the past few months, I have been applying to and interviewing for software engineering summer internships. During my internship search, I noticed a lack of recent internship interview experiences outside of Glassdoor about newer companies (think companies other than Google, Microsoft, Facebook, Amazon, Apple, etc.). As a result, I am writing about my experiences with companies that I haven’t found as many resources for online as I did for bigger or older companies with the hope that others applying to these companies could benefit. I won’t go into what the interviewers asked me (I believe that violates the NDA), but I will go over what the interviews were like as well as share some things that I learned during the process.</p><p>The following is the first installment of my interview experience with Square, a payments company most known for enabling vendors to accept credit or debit card payments by attaching a small device to your phone or tablet like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TTvdvRy4II_Djh9Ck1XHnw.png" /></figure><p>Created by Jack Dorsey, the founder of Twitter, Square’s other products help business owners operate and expand their businesses by providing analytics and organizational services (like Square Payroll, Square Dashboard, Square Customer Engagement, etc.), enabling consumers to purchase gift cards, financing companies with small amounts of capital and many other features. Aside from my interest in their products as well as their impact on small businesses, Square recently filed to go public sometime in the near future. The prospect of working at a company that would be in the early post-IPO stages was another reason that I was interested in working for Square.</p><h3>The Resume Screen</h3><p>I applied to Square for a software engineering intern position on September 23rd of this year on their website and indicated that I was interested in working in the San Francisco or New York offices. I was pleasantly surprised when a recruiter reached out to me about a week later with the following email:</p><blockquote>Hope all is well! I found your resume through the Sequoia / Start @ Startup resume database. As next steps we’d like to invite you to interview with us on 10.12 (day after the conference ends) when we’re on campus. Please sign up here for 2 interview slots and I will send you full preparation info prior to then. Thanks!</blockquote><p>What was interesting about this email was that the following day, I received another email from the Square recruiting team informing me that “the team decided to move forward with other candidates they felt were a better fit at this time.” I guess my resume was screened by two different recruiters, which goes to show that passing the resume screen is subjective and depends heavily on who reads your resume. I signed up on the Google Sheet to interview on October 12th on-campus with two different engineers.</p><h3>The On-Campus Interview</h3><p>I had started to prepare for internship interviews early- during the summer, I solved the problems in Cracking the Coding Interview by <a href="https://medium.com/u/e21bc4f4525e">Gayle Laakmann McDowell</a> and reviewed my data structures and common algorithms. I was expecting a traditional whiteboard coding environment where an engineer would give me a question that I was expected to solve on the whiteboard while explaining my thinking throughout the entire process.</p><p>I was intrigued when I received another message from Square telling me to bring my laptop to the interview. I had never actually written code on a computer in an interview before (granted I hadn’t had many technical interviews before this). In the email, the recruiter said that I would have 45 minutes to come up to a workable solution to a problem that the interviewer gave as well as 10–15 minutes in the end for me to ask the interviewer questions. There were several technical interview tips that they also included as well as some suggested questions to prepare for.</p><p>My interviewers were fantastic- they seemed passionate about their projects and enthusiastic about working with me. Both interviews were conducted pair-programming style, which means that the interviewer seemed like a fellow engineer who I was working with, offering me suggestions along the way to improve solutions. Another interesting part of the interview was that I was allowed to Google things like syntax or API calls that I had forgotten. Furthermore, one of my interviewers allowed me to include some code that I had already written to make the process easier. In short, instead of this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*JKNthFd7YyLH735gfblqlQ.jpeg" /><figcaption>Whiteboard programming</figcaption></figure><p>the interview looked more like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*YEABg21WHjc6WScMENAOrg.jpeg" /><figcaption>Excuse the stock photo watermark</figcaption></figure><p>If I were to give any advice (at least for the Square interview) regarding the questions themselves, it would be to know how to apply the data structures and algorithms that you learn in school to real world situations instead of simply committing them to memory. Rather than memorizing <em>how</em> to implement quicksort, for example, know why you would want to use quicksort over mergesort, the time and space tradeoffs, etc. At the end of the day, the interviewer isn’t looking to see if you could memorize things; in fact, it would be pointless because there are implementations of data structures and algorithms for most common programming languages out on the internet. The interviewer wants to observe how you approach a problem and understand the thought process behind the implementation decisions that you make.</p><p>Speaking of implementation decisions, you should always talk about various approaches and their tradeoffs if multiple different approaches come to mind before beginning to code. What I mean by this is that you should talk about other possible implementations for the future without necessarily implementing it during the interview, especially if the other implementations are complicated. As a concrete example, suppose you have two ideas on how to implement a solution, with one being a more intricate approach that requires an extra data structure and the other being a simpler solution that does not. It would help to talk about the benefits of the first implementation and how it might be better for future implementations of the problem. This shows that you are constantly thinking about other approaches to the solution as well as the tradeoffs associated with other approaches. The interviewer would also be more than happy to work with you while discussing the different approaches.</p><p>After wrapping up the coding portion of the interview, the interviewers answered any questions that I had about Square, from the culture to what they did. They also asked me to send in the code that I had written, which I believe will be used when it comes to the final hiring decision (more on that later). I walked out of both interviews feeling fairly confident, and waited four days to receive another email from the recruiter.</p><p><em>To be continuted in </em><a href="https://medium.com/@david.lee/square-interview-experience-part-2-b0c7525b9d48"><em>Part 2: The On-Site</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=957bf6c01e08" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>