<?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 Vivian Kaun on Medium]]></title>
        <description><![CDATA[Stories by Vivian Kaun on Medium]]></description>
        <link>https://medium.com/@viviankaun?source=rss-73ed91157a7d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wQkLTCcMH75CJ4p7.</url>
            <title>Stories by Vivian Kaun on Medium</title>
            <link>https://medium.com/@viviankaun?source=rss-73ed91157a7d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:17:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@viviankaun/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[Preparing for your Software Engineering Interview at Linkedin]]></title>
            <link>https://medium.com/@viviankaun/preparing-for-your-software-engineering-interview-at-linkedin-5fc11d8b7d7a?source=rss-73ed91157a7d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fc11d8b7d7a</guid>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Vivian Kaun]]></dc:creator>
            <pubDate>Mon, 30 Sep 2019 20:58:09 GMT</pubDate>
            <atom:updated>2019-09-30T20:58:09.330Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.facebook.com/careers/life/preparing-for-your-software-engineering-interview-at-facebook">Preparing for your Software Engineering Interview at L</a>inkedin</p><p>HR 給的準備方向</p><p>The phone interview will be an hour-long that will consist of two coding scenarios that you can solve in the programming/scripting language you are most confident it.</p><p>To breakdown that hour for you in more depth, the first 5–10 minutes will focus on <strong>resume-related questions</strong> and <strong>introductions</strong>. Most of the time will focus on working through at least two coding problems. These questions will be heavier on your <strong>computer science fundamental/academic topics</strong>, touching on things like data structures and algorithms, hash tables and maps, big O notation, binary searches, recursion, etc.</p><p><strong><em>*Our interviews are not congruent to what engineers are doing on a day-to-day basis, so preparing for our interviews is highly encouraged!</em></strong></p><p>Our engineers will be looking for your ability to not only code solutions for these problems, but also looking at your ability to work towards clean code and generate optimal solutions (i.e. are you looking out for <em>edge cases, corner cases, bugs,</em> are you able to <em>generate test cases if asked</em>), as well as your problem solving abilities and communication skills. From a problem-solving standpoint, are you able to demonstrate a strong logic process, can you think your way through to a solution, etc. In terms of communication, can you verbalize or discuss your methodologies and approach with our engineers, can you <em>ask questions to clarify</em> the problem at hand, etc.</p><p><strong>Major components of our assessment involve:</strong></p><p>1. Applying algorithm, data structures and Computer Science fundamentals</p><p>2. Explanation and implementation of the solution in code without any of the aids engineers typically have access to (e.g. IDE, online docs).</p><p>3. Pace — you will be under the time gun.</p><p>4. There may also be an assessment on failure modes and larger-system considerations.</p><p><strong>Algorithms hints:</strong></p><p>1. Think about the trade-offs of different approaches.</p><p>2. Knowing the run-time complexity of your solution may indicate whether you can do better.</p><p>3. Don’t over-complicate your algorithm to fit in specific concepts — we are looking for answers to the question, not looking for certain techniques.</p><p><strong>Coding sites to use:</strong></p><p>1. <a href="https://leetcode.com/">Leet Code</a></p><p>2. <a href="http://www.wired.com/2014/08/how-to-solve-crazy-open-ended-google-interview-questions">How to solve open ended interview questions</a></p><p>3. <a href="http://courses.csail.mit.edu/iap/interview/materials.php">Hacking the Google Interview</a></p><p>4. <a href="http://www.topcoder.com/tc?d1=tutorials&amp;d2=alg_index&amp;module=Static">Top Coder</a></p><p>5. <a href="http://www.developersbook.com/corejava/interview-questions/corejava-interview-questions-faqs.php">Developers book (Core Java)</a></p><p>6. <a href="http://stackoverflow.com/questions/58354/algorithm-data-structure-design-interview-questions">Stack Overflow</a></p><p><strong>Tips:</strong></p><p>· Tip #1: <strong><em>Ask</em> clarifying questions</strong> instead of making assumptions. Before starting on your implementation, be clear on requirements. Describe your high-level approach first before implementing.</p><p>· Tip #2: <strong><em>Verbalize</em> your thoughts out loud while you’re solving a problem</strong>. Our interviewer wants to understand your thought process and how you go about solving a problem. So by thinking out loud, you’ll give them an idea and they’ll be able to give you hints to steer you in the right direction. Clear technical communication is key. <em>Give an idea</em> of what the engineer is going to expect before jumping into the solution and take notice of suggested hints.</p><p>· Tip #3:<strong> You will be assessed on both <em>speed</em> as well as the <em>quality</em> of the solution.</strong> So, don’t take too much time to think through the problem, but take enough time so you can provide a clean and elegant solution. For some questions, the expectation is that someone should be able to work through the problem in “X” minutes, so there could be multiple questions in the hour slot; others may take the entire hour to solve.</p><p>· Tip #4:<strong> If asked about an interesting project, make sure to choose a project that you are actually interested in rather than just picking your most current project.</strong> Show <strong><em>enthusiasm and details</em></strong> about the project by expressing who was your audience, why the project/product was being built, and dig into your contributions and specific responsibilities.</p><p>· Tip #5: <strong><em>Find and fix</em> your bugs using edge cases, tests,</strong> or other means.</p><p>· Tip #6: <strong><em>Visit</em></strong> our engineering blog to find out a bit more about the different technologies and projects we are working on as well as get a feel for our engineering and company culture.</p><p>o <strong>Here are some helpful links to learning more about LinkedIn Engineering:</strong></p><p>§ <a href="http://engineering.linkedin.com/"><strong>Engineering Blog</strong></a></p><p>§ <a href="http://blog.linkedin.com/2015/03/11/linkedins-culture-of-transformation/"><strong>LinkedIn’s Culture</strong></a></p><p>§ <a href="http://data.linkedin.com/opensource"><strong>Open Source @ LinkedIn</strong></a></p><p>§ <a href="http://www.slideshare.net/linkedin/tagged/LinkedIn%20Engineering%20Insights"><strong>Engineering Insights (Video interviews with engineers at LinkedIn)</strong></a></p><p>· Tip #7: <strong><em>Practice</em> </strong>algorithmic problems &amp; look up types of questions asked in a LinkedIn interview (but don’t focus too narrowly on what you find online)</p><p>· Tip #8: Ask relevant and appropriate questions about LinkedIn to show your interest. This is your chance to <strong><em>interview us</em></strong> to make sure that LinkedIn is the right fit for you.</p><p><strong>Lastly, below are links to posts written by our Software Engineers. They give a lot of info and provide different perspectives on how to prepare for this type of interview.</strong></p><p><strong>Articles geared towards Preparation:</strong></p><p><a href="https://www.linkedin.com/pulse/20140425202654-10752460-what-to-do-and-not-do-if-i-interview-you?trk=mp-reader-card">What to do (and not do) if I interview you</a></p><p><a href="https://www.linkedin.com/pulse/interviews-exams-jacob-kessler">Interviews are not Exams</a></p><p><a href="https://www.linkedin.com/pulse/20140205163949-28614372-getting-that-job-at-linkedin?goback=%2Enmp_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1&amp;trk=object-title">Getting That Job At LinkedIn</a></p><p><a href="https://www.linkedin.com/pulse/design-interview-from-interviewers-perspective-joey-addona">The Design Interview From the Interviewer’s Perspective -primarily for onsite interviews</a></p><p><a href="https://www.linkedin.com/pulse/success-coding-interview-joey-addona">Success in the Coding Interview</a></p><p><strong>Book to refer:</strong> Cracking the Coding Interview: 189 Programming Questions and Solutions</p><p><strong>Coding Reference</strong>: <a href="https://www.quora.com/profile/Gayle-Laakmann-McDowell">Quora</a></p><p>…And some more additional information about LinkedIn!</p><p><strong>LinkedIn’s Vision/Culture/InDay</strong></p><p>1. <a href="http://blog.linkedin.com/2015/03/11/linkedins-culture-of-transformation/"><em>Linkedin’s Culture</em></a></p><p>2. <a href="https://www.linkedin.com/company/linkedin-economic-graph"><em>Linkedin’s Vision</em></a></p><p>3. <a href="http://blog.linkedin.com/2015/07/29/inday-investing-in-our-employees-so-they-can-invest-in-themselves/"><em>Linkedin’s inDay</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fc11d8b7d7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Preparing for your Software Engineering Interview at Facebook]]></title>
            <link>https://medium.com/@viviankaun/preparing-for-your-software-engineering-interview-at-facebook-27eb0fbdb0d2?source=rss-73ed91157a7d------2</link>
            <guid isPermaLink="false">https://medium.com/p/27eb0fbdb0d2</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Vivian Kaun]]></dc:creator>
            <pubDate>Mon, 30 Sep 2019 19:15:24 GMT</pubDate>
            <atom:updated>2019-09-30T19:15:24.188Z</atom:updated>
            <content:encoded><![CDATA[<p>HR 給了有用的資源</p><p><strong>System Design: </strong><a href="https://www.hiredintech.com/app?fbclid=IwAR2YqP2LLekdxk0mavoP69PVfJse_z2cN40XmdS0pdV5lGcd1i2ODrzmMSo#system-design"><strong>link</strong></a></p><p><strong>Article: </strong><a href="https://www.facebook.com/careers/life/preparing-for-your-software-engineering-interview-at-facebook"><strong>Preparing for your Software Engineering Interview at Facebook</strong></a></p><p><strong>Practice: We recommend </strong><a href="http://www.leetcode.com/"><strong>Leet Code</strong></a><strong> (medium and hard questions)</strong></p><p>Engineering at Facebook Info</p><p><a href="https://www.facebook.com/Engineering/videos/10150411360573109/">Bootcamp Video — something very unique to Facebook’s culture</a></p><p><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.businessinsider.com_inside-2Dfacebook-2Dengineer-2Dbootcamp-2D2016-2D3&amp;d=DwMFaQ&amp;c=5VD0RTtNlTh3ycd41b3MUw&amp;r=OejG2qLiVRQqNb1crIqYinG0_RiW-jMlO8auCduQ8t4&amp;m=tmc21FOotg8zUH8_PrNnkFR8dyhgBMbA39hY-PAyY8E&amp;s=A3ohht2PxTnzbc6WsHdbbN-zimqyCAqj0cMvp-84KBM&amp;e=">Bootcamp Description</a></p><p><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__hbr.org_2015_06_an-2Dinside-2Dlook-2Dat-2Dfacebooks-2Dapproach-2Dto-2Dautomation-2Dand-2Dhuman-2Dwork&amp;d=DwMFaQ&amp;c=5VD0RTtNlTh3ycd41b3MUw&amp;r=OejG2qLiVRQqNb1crIqYinG0_RiW-jMlO8auCduQ8t4&amp;m=tmc21FOotg8zUH8_PrNnkFR8dyhgBMbA39hY-PAyY8E&amp;s=A_exfpfoQ7bBMBaQ2-2bNb008k5T6eM5McJM5j8TTfs&amp;e=">Facebook Approach to Automation</a></p><p><a href="https://code.facebook.com/projects/">Facebook Open Source</a></p><p><a href="https://code.facebook.com/videos/">Engineering Videos</a></p><p><a href="https://code.facebook.com/posts">Engineering Blog</a></p><p><a href="http://newsroom.fb.com/">Facebook Newsroom</a></p><p><a href="http://www.facebook.com/Engineering">Facebook Engineering Page</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27eb0fbdb0d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>