<?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 Joan Li on Medium]]></title>
        <description><![CDATA[Stories by Joan Li on Medium]]></description>
        <link>https://medium.com/@leechay1508?source=rss-fbfa4e3f4bf7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QPVI6WvVwVJW2szmtCxCgw.jpeg</url>
            <title>Stories by Joan Li on Medium</title>
            <link>https://medium.com/@leechay1508?source=rss-fbfa4e3f4bf7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:22:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leechay1508/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[Google UXD Intern Week 8 Reflection]]></title>
            <link>https://medium.com/@leechay1508/google-uxd-intern-week-8-reflection-87ba0cc921f2?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/87ba0cc921f2</guid>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 17:00:04 GMT</pubDate>
            <atom:updated>2025-07-21T17:00:04.466Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uLsF55Q5ENnBwnyl" /><figcaption>Photo by <a href="https://unsplash.com/@laurenedvalson?utm_source=medium&amp;utm_medium=referral">Lauren Edvalson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>If you are not a Medium member, please click this <a href="https://medium.com/@leechay1508/87ba0cc921f2?source=friends_link&amp;sk=467bb5573ee1548e9ae19bc16340933b">Link</a> for free reading access</blockquote><p>With the project fine-tuned, this week I focused on turning it into a slide deck with a compelling narrative. Storytelling is one of the key skills I want to strengthen during this internship, so I’ve been asking for advice from people around me. One key takeaway I’ve learned is that a good story needs a clear user. Once the user is defined, we can walk through where they’re coming from, what problem they face, and why the solution matters to them. With this structure in mind, I used Gemini to help me craft a narrative around my design project.</p><p>Besides the story itself, the design process is also crucial to share. Since my process involved lots of back and forth, I organized the iterations into alternative explorations. This helped make my final solution feel more grounded. I found that showing alternatives really helped — some audience members even mentioned that my slides answered all their questions before they had to ask.</p><p>Once the slides were ready, it became all about seeking feedback and practicing. One thing I noticed at Google is that many people write scripts before presenting. That inspired me to do the same. Writing a script helped me relax and made me feel more confident during my presentation.</p><p>Another important lesson this week was about handling feedback. During the presentation, I received some feedback that I didn’t know how to respond to on the spot. Later, I had a one-on-one with my host, and he shared advice that really stuck with me. He reminded me that I’m the one most familiar with the product. Other stakeholders might be focused on different areas and may not have the same depth of understanding about the user I’m designing for. So I shouldn’t be intimidated by seniority. Also, not all feedback needs to be acted on. Sometimes, it’s okay to acknowledge it by saying, “I’ll keep that in mind,” and then keep the meeting moving. His support really boosted my confidence.</p><p>With my first project wrapped up, I had a bit more time to explore something fun. I joined two cooking classes and had a great time connecting with other interns and Googlers. After putting in so much effort over the past few weeks, it feels nice to slow down just a bit and reflect on what I want to learn in the second half of the internship.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87ba0cc921f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google UXD Intern Week 7 Reflection]]></title>
            <link>https://medium.com/@leechay1508/google-uxd-intern-week-7-reflection-d9a51c7d6cd0?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9a51c7d6cd0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[hci]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 06:04:13 GMT</pubDate>
            <atom:updated>2025-07-14T06:04:13.299Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B-h7hkHxHV0cU4o2" /><figcaption>Photo by <a href="https://unsplash.com/@laurenedvalson?utm_source=medium&amp;utm_medium=referral">Lauren Edvalson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>If you are not a Medium member, please click this <a href="https://medium.com/@leechay1508/d9a51c7d6cd0?source=friends_link&amp;sk=b26547894fffe4448e496adf853ba2f4">Link</a> for free reading access</blockquote><p>This week was the midpoint of my internship. I took a full day to reflect on my achievements so far and the areas I still want to grow. I also received detailed and thoughtful feedback from my host. One thing I hadn’t noticed until reading the feedback was how much I’ve improved in being user-centered. Google’s strong user experience culture has really influenced me. I regularly ask UX researchers about user needs, and when working with cross-functional stakeholders, I always advocate for the users. I truly believe I was able to grow in this area because of the environment I’m in, and I’m deeply grateful for it. It motivates me to continue delivering thoughtful, user-focused design.</p><p>On the project side, I spent most of the week fine-tuning the details with cross-functional stakeholders, including the PM, engineer, UX designer, and UX writer. I worked with engineers to understand feasibility and make sure my mockups reflect what can actually be implemented. I discussed metrics with the PM, iterated copy with the UX writer, and adjusted based on insights from the UXR team. At one point, I got stuck. There were so many perspectives to consider that it felt overwhelming. But through those discussions, I realized there’s rarely one right answer. In the end, I had to make a call based on what I believe is best for users. Next week, I’ll present my final design to my host, and I feel ready to back it up with all the iterations and reasoning behind it.</p><p>Outside the project, I had a few coffee chats with UX designers across the company. I want to make the most of my time here and learn from different teams. This week, I spoke with designers from DeepMind, Google Meet, and Google Cloud. I really appreciated their openness and insights. It helped me see how different products take shape behind the scenes. I plan to keep meeting more people before the internship ends.</p><p>Time flies. I can’t believe the internship is already halfway through. I genuinely love the job, the team, the food, the city, and most importantly, the people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9a51c7d6cd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google UXD Intern Week 6 Reflection]]></title>
            <link>https://medium.com/@leechay1508/google-uxd-intern-week-6-reflection-3fc059b78a96?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fc059b78a96</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Sat, 05 Jul 2025 22:22:18 GMT</pubDate>
            <atom:updated>2025-07-05T22:22:18.130Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TSfS6v7YrIUHOOe-" /><figcaption>Photo by <a href="https://unsplash.com/@laurenedvalson?utm_source=medium&amp;utm_medium=referral">Lauren Edvalson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>If you are not a Medium member, please click this </em><a href="https://medium.com/@leechay1508/3fc059b78a96?source=friends_link&amp;sk=0c7b8060028663789f36af9e8bceb1dc"><em>Link</em></a><em> for free reading access</em></p><p>After aligning on the design direction last week, I started exploring the details of the proposal. The direction involved many technical considerations, so I collaborated closely with engineers to gain a deeper understanding of the product. The more I explored, the more I understood why this idea hadn’t been a favorite among stakeholders before — there were real challenges to tackle. Despite the technical challenges, I iterated quickly and had frequent discussions with the engineer to come up with viable solutions.</p><p>In our meeting with the PM and engineering team, we had an in-depth discussion about both usability and feasibility. Our goal was to make sure the project was scoped realistically, considering the time and resources we have. We agreed that while my proposal addressed the user’s pain points effectively, it would take more time to implement. But we didn’t stop there. Instead, we discussed what it would take to build this feature in the future, outlining possible scope and phases. At the same time, we explored what we could deliver now given our current resources. In the end, we struck a well-balanced plan that considers both short- and long-term goals.</p><p>Looking back, even though my initial proposal didn’t move forward as-is, I found the process valuable. Sharing my thinking with stakeholders helped me practice critical thinking, clear communication, and healthy compromise. I’m especially grateful for the respect and support I received from my manager, PM, and engineers which reminded me that the work I’m doing brings value. Next week, I wil fine-tune the design and hand it off to development process.</p><p>Fun fact: Because of the July 4th holiday, this was a short week and many colleagues took time off. I decided to try a cooking class for the first time! We learned to make fresh pasta and watched the chef prepare an amazing pesto. I’ll definitely join the next one, it was such a fun way to learn and connect with others!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pPdPKja_0zPXGSGc" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fc059b78a96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google UXD Intern Week 5 Reflection]]></title>
            <link>https://medium.com/@leechay1508/google-uxd-intern-week-5-reflection-18f4f74345d2?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/18f4f74345d2</guid>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Tue, 01 Jul 2025 03:53:58 GMT</pubDate>
            <atom:updated>2025-07-01T03:53:58.068Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8hTauN7hGrUwFwkz" /><figcaption>Photo by <a href="https://unsplash.com/@laurenedvalson?utm_source=medium&amp;utm_medium=referral">Lauren Edvalson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>If you are not a Medium member, please click this </em><a href="https://medium.com/@leechay1508/18f4f74345d2?source=friends_link&amp;sk=f4789f085f9c113ec5a4d139f76ffe7f"><em>Link</em></a><em> for free reading access</em></p><p>This week marked a meaningful milestone in my internship journey. Wanting to take a more proactive role in leading the design direction, I made a conscious effort to seek feedback more frequently. I’ve learned that keeping the ball rolling in design often means being open to iteration, even when it’s messy.</p><p>During the early exploration phase, I encountered a lot of pros and cons to every path. The biggest challenge was pushing for a design direction that I truly believe could solve a real user problem. To back it up, I collaborated closely with our UX researcher to dive into user needs and pain points. I also reached out to the broader UX team for feedback and alignment. My co-host suggested I put together a presentation deck to clarify my thinking and communicate more effectively. As someone who doesn’t consider themselves naturally strong at verbal communication, this tip really helped. Building the deck gave me a structure to organize my thoughts and made it easier to guide discussions with clarity and confidence.</p><p>By the end of the week, I hosted my second cross-functional workshop with PM and Engineering. I had a comprehensive deck that clearly laid out my thinking, rationale, and vision. It helped me gain buy-in from both PMs and engineers. That moment felt like a turning point, not just because the idea moved forward, but because I felt myself growing into someone who can advocate for users with both conviction and respect. I’m learning how to communicate better, tell a compelling story, and express strong opinions while remaining open and collaborative. After the presentation, I felt a stronger sense of trust from stakeholders, which motivates me to keep pushing forward.</p><p>Next week, I’ll continue iterating on the design. My goal is to deliver a solution that not only solves problems but resonates deeply with our users and stakeholders.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18f4f74345d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google UXD Intern Week 4 Reflection]]></title>
            <link>https://medium.com/@leechay1508/google-uxd-intern-week-4-reflection-a4fc3110a964?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4fc3110a964</guid>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Tue, 01 Jul 2025 03:52:27 GMT</pubDate>
            <atom:updated>2025-07-01T03:52:27.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3-lZ-wUXRnI-76NF" /><figcaption>Photo by <a href="https://unsplash.com/@laurenedvalson?utm_source=medium&amp;utm_medium=referral">Lauren Edvalson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>If you are not a Medium member, please click this </em><a href="https://medium.com/@leechay1508/a4fc3110a964?source=friends_link&amp;sk=50a529bd8ae6993c1192cd0907f32817"><em>Link</em></a><em> for free reading access</em></p><p>This week, I led a design workshop with PMs and engineers to align on the product direction — a first for me. As someone still building confidence in stakeholder-facing situations, I was nervous going in. Leading a meeting like this felt like stepping into unfamiliar territory.</p><p>During the discussion, there were moments when I got stuck. Some topics went deep into product logic I wasn’t yet familiar with. I hesitated to ask for clarification in the moment, partly because I didn’t want to slow things down, and partly because nerves got the best of me. That hesitation left me a little lost and unable to fully contribute at times.</p><p>Reflecting on this, I realize this is an important area for me to grow. Next week, I want to work on asking questions more openly — especially when I don’t understand something. Being honest and curious will help me connect the dots faster and show that I’m here to learn and lead, not just follow.</p><p>Despite the bumps, hosting the workshop was still a big step forward. I put myself in the driver’s seat, and now I know more clearly where I need to steer next.</p><p>*I am quite busy this week, thanks to ChatGPT’s help for this post!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4fc3110a964" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google UXD Intern Week 3 Reflection]]></title>
            <link>https://medium.com/@leechay1508/google-uxd-intern-week-3-reflection-2b18d2922e5e?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b18d2922e5e</guid>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Mon, 16 Jun 2025 05:28:10 GMT</pubDate>
            <atom:updated>2025-06-16T05:30:09.857Z</atom:updated>
            <content:encoded><![CDATA[<h3>Google UXD Intern: Week 3 Reflection</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ImR_xK6r85bJCFOn" /><figcaption>Photo by <a href="https://unsplash.com/@laurenedvalson?utm_source=medium&amp;utm_medium=referral">Lauren Edvalson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>If you are not a Medium member, please click this <a href="https://medium.com/@leechay1508/2b18d2922e5e?source=friends_link&amp;sk=747f46df2093dc03ede79014de56fd3e">Link</a> for free reading access</blockquote><p>This past week was quite dynamic, marked by several significant learning experiences. I had my initial design draft review with the Product Manager, and also participated in my first design critique session, both receiving and providing valuable feedback.</p><p>On the critique date, I wasn’t aware the meeting was going to be a critique, so I went in without extensive preparation. However, it turned out to be incredibly productive. Since most participants were unfamiliar with my project, their “fresh eyes” offered a wealth of new ideas that I had overlooked. After this first critique, my host provided crucial feedback on my presentation style: I need to assume no one knows anything about what I’m working on. Before presenting, it’s essential to clearly set the scene by crafting a strong narrative that articulates the user’s goals and needs.</p><p>The insightful feedback from the critique session made me realize <strong>I could, and should, explore more broadly during my early ideation process</strong>. At the project’s outset, my manager emphasized our product’s very strict UI constraints. Consequently, I initially focused heavily on technical limitations, perhaps even more than on exploring the optimal user experience. This led me to miss opportunities for out-of-the-box thinking and proposing designs that truly prioritize the user.</p><p>Recognizing this, I spoke with two experienced designers about how they balance feasibility and usability in the early stages. A common piece of advice I received was to <strong>initially “forget” all limitations and think widely</strong>. To address feasibility, I can then develop a separate version of the design that adheres to the constraints. Later, during proposals, I can present both versions and collaborate with the PM and Engineers to find the right balance.</p><p>As I’ve started collaborating more closely with the PM and Engineers, I’m also actively learning how to communicate my ideas strongly yet respectfully. I posed this question to several designers within the company, and the key takeaway is consistent: <strong>always come prepared with clear reasons for your design decisions, and people will respect your perspective</strong>. Furthermore, it’s vital to think more critically rather than simply agreeing to everything.</p><p>Next week, I’m looking forward to even closer collaboration with my PM and Engineer to advance the project. Having immersed myself further in the company culture and gotten to know more colleagues, I feel more confident in proposing ideas and, when necessary, respectfully declining with solid justifications. With more project work on the horizon, I’m excited to contribute and craft a design that effectively solves a user’s problem.</p><p><strong>Fun things</strong>: I tried the free fitness class and massage appointment for the first time this week! It is so cool to explore different perks and activities within the company. I can’t wait to explore more!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b18d2922e5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google UXD Intern Week 2 Reflection]]></title>
            <link>https://medium.com/@leechay1508/google-uxd-intern-week2-reflection-c199bdb9fa55?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c199bdb9fa55</guid>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Mon, 09 Jun 2025 00:36:01 GMT</pubDate>
            <atom:updated>2025-07-14T06:05:02.312Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LKgXM01CjFYiAyHG" /><figcaption>Photo by <a href="https://unsplash.com/@laurenedvalson?utm_source=medium&amp;utm_medium=referral">Lauren Edvalson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>If you are not a Medium member, please click this <a href="https://medium.com/@leechay1508/c199bdb9fa55?source=friends_link&amp;sk=2d9c1e5e34fb9df7733532418b36eb6c">Link</a> to free reading access</blockquote><p><strong>TLDR</strong>: In Week 2, I focused on improving 1:1 efficiency by asking immediate questions. My main goal for next week is to be more proactive and take ownership of my design project, plan to sketch more, take notes, and schedule weekly PM meetings to build trust. I’m still learning the complex product details, aiming for critical thinking and better note-taking. I also learned a valuable Google lesson: “Always assume good intent,” which helps reduce overthinking and hesitation.</p><p>Last week, I aimed to improve the efficiency of my 1:1 meetings and reduce overthinking. I’m pleased to report significant progress this week. A key takeaway from my numerous conversations is the importance of <strong>asking questions as soon as I don’t fully understand something</strong>. It’s much easier to clarify details in a live conversation than through follow-up messages.</p><p>Moving forward, my primary area for improvement next week is to become more <strong>proactive</strong>. Historically, I’ve tended to follow my manager’s direction rather than taking full ownership. However, now I have the exciting opportunity to own a design that will involve close collaboration with Product Managers (PMs) and Engineers to launch a new feature. This demands a higher level of proactivity and professionalism.</p><p>To achieve this, I plan to:</p><ul><li><strong>Ask more frequent questions</strong> of my host and co-host.</li><li><strong>Act faster</strong> in my responses.</li><li><strong>Reduce passive thinking time</strong> by immediately translating thoughts into action. This means sketching in Figma, taking detailed notes, and sending questions as they arise.</li><li><strong>Schedule weekly 1:1s with my PM</strong> to kickstart design exploration and ask detailed questions to maintain momentum.</li></ul><p>My goal is to demonstrate my professionalism as quickly as possible to build trust with stakeholders.</p><p>This week, I began delving into the intricate details of the product. It’s complex and quite new to me, requiring extra time to digest, and I’m still in the learning phase. To collect my questions more efficiently, I’m focusing on <strong>taking more notes as I process information</strong>. Additionally, when listening to explanations, I want to cultivate a more <strong>critical thinking</strong> approach rather than simply accepting everything. If I don’t fully understand, I’ll make sure to ask for concrete examples.</p><p>Beyond project work, I’m actively balancing networking in the office with focused work at home to maximize efficiency. I’m grateful to Google for providing a monitor, and I’ve invested my first salary in a new pair of headphones, both of which I believe will significantly boost my productivity.</p><p>This week also included more onboarding sessions, which provided a great opportunity to meet other interns in the San Francisco office. A powerful lesson I learned from one of these sessions was to “<strong>always assume good intent, and things will be easier</strong>.” This concept was entirely new to me. I’ve often overthought and worried, leading to hesitation even in small decisions. However, embracing the “Googley” spirit means assuming people have good intentions, which will undoubtedly help me make decisions more confidently.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c199bdb9fa55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google UXD Intern Week 1 Reflection]]></title>
            <link>https://medium.com/design-bootcamp/google-uxd-intern-week1-reflection-bc53f1ff59cc?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc53f1ff59cc</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Mon, 09 Jun 2025 00:33:26 GMT</pubDate>
            <atom:updated>2025-07-14T06:07:20.927Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HSB8cMy3c8Abs8NQ" /><figcaption>Photo by <a href="https://unsplash.com/@laurenedvalson?utm_source=medium&amp;utm_medium=referral">Lauren Edvalson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>If you are not a Medium member, please click this <a href="https://medium.com/@leechay1508/bc53f1ff59cc?source=friends_link&amp;sk=e88f38c6ea2c4aa35a2590ffdb2ab871">Link</a> to free reading access</blockquote><p><strong>TLDR</strong>: My first week as a UXD intern at Google was finally here! Before starting, I set clear goals: to be ready for a full-time job post-graduation, become a confident designer, master organizational networking, and make a strategic impact. The first week mainly involved onboarding and getting comfortable. I proactively embraced networking, having six 1:1 meetings with colleagues which helped me understand the team structure and get resources. Looking ahead, I’ll start my project with a UX audit, deepen my understanding of the product, and continue networking more efficiently, all while adapting to Google’s culture.</p><p>It’s not a dream, I really landed a UXD internship at Google, and this day has finally come!</p><p>Before my internship even started, I spent a lot of time thinking about my goals and what skills I wanted to learn. My main goal is straightforward but big: <strong>I want to be ready to find a full-time job when I graduate.</strong> To break that down, I listed three key skills:</p><ul><li><strong>Becoming a confident designer and storyteller</strong>, which includes selling ideas and getting buy-in.</li><li><strong>Learning how to network in a big organization</strong> so I can get help and work more efficiently.</li><li><strong>Going beyond design</strong> to make strategy and impact across teams through design.</li></ul><p>My first week was mostly about onboarding courses and waiting for system access. I only got to talk to my host and co-host once, on my second day. Our first 1:1 was more about getting me familiar with the company, office, and systems, and just getting to know each other. We haven’t had a chance to discuss my goals in depth yet. My managers told me not to expect to do any project-related work in my first week; they just wanted me to get comfortable.</p><h3>Building Confidence and Networking</h3><p>I was pretty nervous in my first week and wasn’t sure if I was prepared to work at Google. During our first lunch, my managers complimented my interviews, saying I prepared very well and performed impressively. These kind words really helped build my confidence and made me relax a bit. Just like the onboarding sessions said, I’m here for a reason, so I shouldn’t worry.</p><p>Regarding the second skill I want to learn, <strong>networking</strong>, I had limited 1:1 experience in previous jobs, so I was a bit hesitant to send out invitations. However, when I checked my manager’s calendar, I saw many colleagues had 1:1s with others. I appreciate the transparency at Google, which made me realize that sending 1:1 invitations to other Googlers is likely encouraged. So, I spent some time understanding the team structures and started sending out invitations. I also asked my manager for names of people I’d work with in the future, and after each conversation, I’d ask the person to recommend other Googlers they thought would be great to talk to.</p><p>I had six 1:1s in my first week. For example, during my 1:1 with my skip manager, I asked him what important skills he looks for when hiring a junior UX designer since my ultimate goal is to prepare for my next career step. He emphasized the importance of networking to build my identity within the team and encouraged me to have at least one coffee chat with everyone in my office. I really appreciated this conversation because it helped confirm my goals are on the right track. Another impressive 1:1 was with a Lead UX Researcher. I was initially a bit nervous to send an invitation to other functional members, but I found talking to a UXR surprisingly helpful. She gave me a lot of great resources about the product I’m going to work on. These materials helped me learn more about our product through their research, understand how UXD and UXR collaborate and know who I can reach out to for help in the future. Other conversations also helped me understand what other designers are working on, which not only helped me get to know each person but also understand the team’s structure.</p><h3>Looking Ahead</h3><p>I think I had a good start on practicing networking and building relationships with colleagues in my first week. I plan to keep meeting more people next week, including product managers and engineers. What I want to improve is being more confident when sending invitations. I was still a bit hesitant to schedule a time, which ended up taking me a lot of time to set up the conversations. Ultimately, I hope to do this more efficiently. I’ll chat with my hosts to get their feedback and any tips to improve.</p><p>I also had a chance to look at a UXR report and a UI review request deck. The content was so comprehensive and professional; I really enjoyed reading it. I wish I could contribute something of a similar level by the end of my internship.</p><p>Next week, I’m going to start working on my project. I’ll begin by doing a UX audit of the product, where I hope to bring fresh ideas to the team. Also, I aim to understand the business value of my project more deeply by chatting with my PM and hosts. At this stage, meeting other people is still my priority since I’m not very familiar with the product yet. By the end of next week, I hope to have a draft of my plan.</p><p>Overall, this first job experience in the U.S. has been incredibly impactful. I’m actively learning about the new culture, and I deeply appreciate Google’s commitment to creating a friendly and inclusive environment. Many aspects are new to me, including working in a hybrid model. I’m learning to strike a balance and discover the most efficient ways to work within this new dynamic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc53f1ff59cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/google-uxd-intern-week1-reflection-bc53f1ff59cc">Google UXD Intern Week 1 Reflection</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launchfolio: a Homepage Generator Built With AI, GSAP, and Me]]></title>
            <link>https://medium.com/@leechay1508/launchfolio-a-homepage-generator-built-with-ai-gsap-and-me-62d93f8b58a2?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/62d93f8b58a2</guid>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Sat, 17 May 2025 21:02:25 GMT</pubDate>
            <atom:updated>2025-05-17T21:02:25.081Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gh4OZaFi7z7iWAmC" /></figure><p>Hi, I am Joan, currently an HCIM graduate student at the University of Maryland. <strong><em>Launchfolio</em></strong> is the final project for <em>INST630: Programming Human-Centered Interfaces</em> at UMD HCIM, focusing on practicing front-end programming. In this project, I leveraged my design skills and programming skills, showcasing the synergy between creativity, web development, and AI usage.</p><h3>Idea</h3><p>As a designer grounded in UX design, I’m no stranger to design, logic, HTML, or CSS. My front-end programming skills thrive in basic layout and communication with developers. But when it came to JavaScript or advanced interaction, that was uncharted territory. Therefore, when beginning this project, I wanted to explore and learn JavaScript, interaction, and animation, and create something useful. <em>Launchfolio</em> was born: a customized homepage generator that can inspire individuals. I envisioned a tool where users could input their name, title, skills, etc., and then see their personal homepage bloom from one of several animated templates, powered by GSAP. You can try it yourself<a href="https://launchfolio-630.web.app/"> here</a>.</p><h3>Began From Figma</h3><p>I started by drafting low-fidelity wireframes on Figma, mapping out user flow and key screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2HF3rwps0iOXNURB" /><figcaption>Low-fidelity wireframes</figcaption></figure><p>After defining key screens, I crafted high-fidelity wireframes by imagining how each template could express a different mood. For example, I use sans-serif and serif fonts in different templates to create a unique look and feel. I sought inspiration and explored various interactions — hover effects, animated cursors, horizontal scrolls, text, etc from <a href="https://gsap.com/">GSAP demos</a> and <a href="https://www.awwwards.com/">Awwwards</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PIzQfHWubsw6Qb4J" /><figcaption>High-fidelity wireframes</figcaption></figure><h3>Co-Develop with AI</h3><p>After designing, the coding process came next. HTML and CSS were familiar friends. JavaScript, however, was a steep climb. I collaborated closely with AI tools for support, including <strong>Cursor Pro, ChatGPT 4o, and Chrome AI Assistant</strong>.</p><h4>Start with Cursor to make it work</h4><p>Cursor Pro helped me a lot when I was initially building the core functions. <strong>The process of asking AI questions in a chat panel, comparing code changes in the code canvas, and accepting or rejecting changes is highly streamlined in the Cursor</strong>. I really enjoyed the collaboration process with Cursor at the early stage, for it allowed me to develop functions with JavaScript even if I am not professional at all. Since I am familiar with HTML and CSS, I only asked Cursor to build the basic functions and flow, and then I followed my Figma file, leveraging Figma dev mode to polish the interface by myself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HbjZiKwKcw0j3NWi" /><figcaption>Cursor</figcaption></figure><p>While Cursor had several strengths, I also ran into a few limitations. <strong>Firstly</strong>, I found Cursor struggled as the codebase became heavier. It kept failing to generate code in the later development phase. <strong>Secondly</strong>, I felt like Cursor preferred to write all the code in a single file, which ended up making it difficult to manage tons of code. I tried to separate files into their functions manually, such as form.css, and style.css. It is much easier for me to review, but it turned out too hard for Cursor to check codes across different files. <strong>Lastly</strong>, during my collaboration with Cursor, I found that Cursor always wanted to make code changes no matter what my initial input was. When I wanted to ask follow-up questions, I had to reject code changes every time, which interrupted my workflow. With these apparent disadvantages, I turned to ChatGPT for help in the later fine-tuning process.</p><h4>Learn with ChatGPT</h4><p><strong>ChatGPT Plus</strong> became my partner and mentor. The biggest strength of ChatGPT is that it provides clear explanations, creates multiple solutions, and allows asking follow-up questions. This conservative process not only helped me to build functional code, but most importantly, <strong>it helped me to learn</strong>. I really like the feature in which I can quote specific terms or sentences in ChatGPT’s output and ask for clarification. I still remember debugging that GSAP plugin warning and reconfiguring file structures for Firebase Hosting multiple times. ChatGPT wasn’t just a chatbot but a powerful collaborator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*vM9eTMALVwSZG0BX" /><figcaption>ChatGPT</figcaption></figure><p>On the other hand, one downside of ChatGPT is that it isn’t integrated into my coding environment Therefore, I had to upload my files and copy-paste changes to my files every time, which took a lot of time. Even with this minor inconvenience, I appreciate the process of working with ChatGPT, for it allowed me to learn along the process.</p><h4>Last debugging with Chrome AI Assistant</h4><p>Aside from Cursor and ChatGPT, <strong>Chrome’s AI Assistant</strong> inside the inspector is a cool tool I found and tried for the first time during this project. Since the code is already live and rendered in the browser, Chrome AI Assistant can directly inspect the actual DOM and behaviors, making it helpful for catching bugs quickly. I remember there were two times when both Cursor and ChatGPT failed to solve my issue, and then Chrome AI Assistant solved it. While Chrome AI Assistant didn’t give me clear explanations like ChatGPT, it helped me realize <strong>the issue was solvable</strong>, which gave me the push to keep digging, and eventually, I found the solution with ChatGPT’s help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A_MNeWII_B-rb8Ol" /><figcaption>Chrome AI Assistant</figcaption></figure><h4>Me, along the process</h4><p>While AI tools supported me throughout the project, I was never just passively following instructions. Instead, <strong>I played the key role of the decision-maker, integrator, and quality controller</strong>. For example, AI often gave me a partial answer. I had to piece different responses together and adapt code to make it actually work. Moreover, AI usually provides solutions from a single perspective. I had to rename variables and integrate codes into my existing functions, making adjustments to ensure everything worked cohesively within the full context in mind. Most importantly, I made the final calls. When multiple solutions showed up, I had to choose what felt most aligned with my vision, directing AI to my goal.</p><p>Through dozens of iterations, I learned not only how to make things work, but how to continuously seek solutions when things did not work. AI was like a powerful assistant, but the creative direction, problem framing, and quality checks were still my job. This co-creation process with AI made me feel invaluable as a human, who keeps vision in mind and has the power to create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Z7jz50nPnK1vNzgBipceA.gif" /><figcaption>Full demo</figcaption></figure><h3>What went wrong (and What went right)</h3><p>Reflecting on the whole process, not everything went smoothly. To start, I didn’t organize my code structure well in order to collaborate with Cursor. For example, I only have one JavaScript file, which turned out extremely hard to scroll through and find codes. If I have a chance to do it again, I’d like to separate and manage files more wisely. Secondly, I didn’t realize the complexity of scroll-triggered animation until this project. To control a scroll trigger, I had to set the proper section height (vh) to make the screen scrollable, which required a lot of manual adjustment. Therefore, I ended up only implementing some easy scroll trigger animations.</p><p>On the other side, most of the process went well. I am proud to design three homepage templates with distinct styles and delightful animations. My favorite animation is the pulse light in style 1. I was inspired by Apple’s mood recording function, and I successfully built it with CSS. I also successfully integrated the Gemini API to generate a personalized slogan in the templates to reflect the user’s skills. This is my first time integrating API and it turned out easier than I expected. With generative AI, the user experience is leveled up. Moreover, this is my first time learning GSAP for animation. The ScrumbleText, SplitText, and ScrollTrigger are like magic, making pages more vivid but in a simple code structure. Seeing it all come to life on a live site felt like magic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*S6H_WsR9Wt5p2NY40BJM9A.gif" /><figcaption>Style 1</figcaption></figure><h3>Final Thoughts</h3><p>Before this project, I had vibe coding experiences using GitHub Copilot and Cursor to build small projects including <a href="https://timeproject-8e822.web.app/timeConverter.html">Time Zone Converter</a> and <a href="https://timeproject-8e822.web.app/">Time List</a>. In these two projects, I relied 100% on AI for the programming process to see the AI’s code capability.</p><p>In this homepage generator project, instead, <strong>I learn how to code while collaborating with AI</strong>. I believe AI can facilitate the learning procedure, as long as I keep learning as a goal in mind. During the developing process, I saw AI’s strengths in streamlining processes, explaining concepts, and suggesting fixes. However, they couldn’t replace intuition. I think that’s the most important insight: AI is a tool, not a crutch. When paired with a clear vision and a persistent and curious human mind, it becomes a creative amplifier.</p><p>I didn’t become a JavaScript expert overnight. But I became a designer unafraid of JavaScript (LOL), curious about interaction, and confident in building useful tools from scratch. <em>Launchfolio</em> isn’t just a homepage generator but an experiment and reflection of what happens when design meets code and when human meets artificial intelligence.</p><p>I am really proud of this fun project, and I learned much more than I expected. Thank you Prof. Alex for the meaningful project and the amazing semester. Hope you have fun with my project: <a href="https://launchfolio-630.web.app/">Launchfolio</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GMm5149s14ivwpLPVfIPWg.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62d93f8b58a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I got into Google! 美國設計實習求職反思 2025 Summer UX Design Internship Hunting Reflection]]></title>
            <link>https://medium.com/@leechay1508/i-got-into-google-2025-summer-ux-design-intern-hunting-reflection-b5d7f396a9ec?source=rss-fbfa4e3f4bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5d7f396a9ec</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Joan Li]]></dc:creator>
            <pubDate>Fri, 28 Feb 2025 00:47:36 GMT</pubDate>
            <atom:updated>2026-02-11T15:19:25.519Z</atom:updated>
            <content:encoded><![CDATA[<p>第一次在美國求職，感受到市場的競爭，也在壓力下不斷的學習與迭代，過去半年真是精實的一段時間。很幸運的拿到北美 Google UX Design Summer Intern 的 Offer，回顧過去半年遇到的種種挑戰，希望能幫助大家少走一點冤枉路。</p><blockquote>If you are not a Medium member, please click this <a href="https://medium.com/@leechay1508/i-got-into-google-2025-summer-ux-design-intern-hunting-reflection-b5d7f396a9ec?sk=d3b37ca7c956d8e4f1fbe33c3daab664\">Link</a> to free reading access</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uC9QjbAM1qQ-VTCQ" /><figcaption>Photo by <a href="https://unsplash.com/@kai_wenzel?utm_source=medium&amp;utm_medium=referral">Kai Wenzel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>前言</h3><p>Hi 我是 Joan，2022 年畢業於台科工設，2024 Fall 到美國 University of Maryland 就讀 MS in HCI。這次求職是針對 2025 Summer internship，目標是 UX Design / Product Design 的職位。過去有約兩年的實習經驗及一年的正職經驗，都是和 UX Design 相關的工作內容。這篇文章會分享找工作所有環節的技巧和反思，最後也會分享我拿到 Google Offer 的過程與心得。</p><p>我從八月底開始申請，截至二月中共投了 166 個職缺，收到六個面試，最後拿到一個 Offer。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5wFP5KcLJDvqB2Qo" /></figure><h3>如何準備能拿到面試</h3><h4>內推 Referral</h4><p>內推的重要性在北美市場已經逐漸下降，除非能在 Career Fair 或 Conference 直接和 Recruiter or Hiring Manager 聊天拿到內推，不然一般在 LinkedIn 上和陌生人要內推的價值不太高，所以建議<strong>職缺出來立刻投遞的效益比尋找內推還大</strong>。我一開始大概有找了十個內推，但這十個職缺最後都在履歷關就被刷掉，所以我後來就沒有再花時間尋找內推了，包含最後拿到 Offer 的 Google 也是直接投遞官網沒有內推。</p><h4>投遞 Apply</h4><ul><li>職缺發出來後越早投越好，記得打開 LinkedIn 職缺的通知。</li><li>建議要來美國留學的大家<strong>儘早準備作品集</strong>，以 Google UXD Intern 來說，職缺在十月八號就刊出來了，開學才準備一定來不及。我在出國前就完成作品集初版，到美國後<strong>持續透過 ADPList 尋求專業建議並快速迭代</strong>。</li><li>投遞後建議記錄一下自己投了哪些，並把職缺內容複製下來，避免未來要面試時找不到當時的 JD。</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*JjIoP9AjD0ZJeSpx" /><figcaption>我用 Notion 紀錄投遞的職缺</figcaption></figure><h4>履歷 CV</h4><ul><li>一句話包含：<strong>用了什麼方法、解決什麼問題、創造什麼價</strong>值。內容就盡可能把 JD (Job Description）裡的關鍵字塞進去</li><li><strong>客製化</strong>：履歷出版完成後，可以根據每個 JD 抽換關鍵字</li><li><strong>留白</strong>：項目跟項目之間留點空間，讓人一眼就能看出分隔</li><li><strong>資訊層級抱持一致性</strong>：畢竟是做設計，字體字級的使用要簡單且統一就能讓排版乾淨易讀</li><li><strong>迭代</strong>：找個不熟悉你的履歷的人幫忙看，確認是否真的寫得清楚明白</li></ul><h4>作品集 Portfolio</h4><ul><li><strong>多看：</strong>多觀摩其他人的作品集和履歷，絕對比自己關著門硬幹有效。可以在 LinkedIn 上搜各個大公司 + design intern 去找歷年的實習生，然後去看他們的作品集；另外 Reddit 上很多討論，如果有看到心儀公司的實習生可以主動私訊問能不能看他們的作品集，基本上大家都很願意分享。</li><li><strong>首頁視覺</strong>：以前我都逃避首頁設計，想說我有好的內容比較重要（暈）。後來在 LinkedIn 上搜了各個大廠實習生的作品集，每一份都是我一打開就感到震憾，被大洗禮之後我也痛定思痛的改了首頁的 Hero Section Design。每個作品集被點開以後大概不到一分鐘的時間就會被關掉，如果你只有一個和大家長的差不多的 Hero，那很難被記住。</li><li><strong>視覺化、視覺化、視覺化</strong>！！沒有人有空去閱讀你費心寫下的文字，若整篇 case study 下來只有文字，那閱讀者整頁滑下來應該什麼也記不得。簡單的視覺化可以用一些 icon 或區塊來達成；另外像是訪談，比起寫出繁冗的訪談問題，一張訪談紀錄的截圖或照片更能讓人了解：「哦！你做了訪談！」，其他細節內容若有興趣面試都有機會再解釋。</li><li><strong>留白</strong>：上下區塊之間的空隙留大一點，仔細回想通常專業的網站都長這樣；除了空間上可以呼吸，也可以幫助閱讀者更仔細的專注在每個區塊，不被上下內容影響。</li><li><strong>邏輯通順</strong>：Case study 就是一篇故事，試著像講故事一樣講給別人聽，檢查看看內容邏輯是否順暢，有沒有哪個區塊根本不需要放，有沒有哪個東西順序怪怪的。</li><li><strong>美感</strong>：美感不一定是浮誇的平面設計或插圖，以 UX Design 來說，美感講求的是資訊層級是否清楚、字體、字級、顏色、陰影、圓角、間距等細節的使用是否一致，就像在設計專案中常做的 Design System，你的作品集也需要 Design System。</li><li><strong>常見錯誤</strong>：在 Youtube 上搜尋 Reaction to design portfolio 之類的關鍵字，看別人怎麼評價作品集。例如這個影片：<a href="https://www.youtube.com/watch?v=mIT93Pqp0PA&amp;t=1s">Reacting to 14 portfolios super-fast</a>，可以檢查看看自己有沒有犯了一些常見錯誤。</li><li>我的作品集：<a href="https://jiayunli-design.com/">https://jiayunli-design.com/</a></li></ul><h3>如何準備面試</h3><h4>Design Challenge</h4><p>我拿到的六個面試只有其中一個碰到 Design Challenge，有點像是 Take-home Assignment 的概念，要在限定的時間內完成。建議在開始做之前先去了解該公司的產品，觀察他們習慣<strong>用什麼策略解決問題</strong>。比如說當時我面試的公司著重在數據分析與數據應用，我在解題時就更專注於思考題目中哪些數據的應用可以減輕使用者體驗，最後也有通過該挑戰。</p><h4>HR Call</h4><p>HR 通常就是問你<strong>求職的目標、為什麼想加入該公司、你對該公司的了解有哪些</strong>。這時候要細讀 Job Description 以及公司官網，也可以試著搜尋 “公司名稱 + Design” 看看有沒有設計團隊的文章或影片可以參考，可以更清楚該設計團隊在尋找怎樣的角色。</p><p>通常電話的最後 HR 也會讓你問問題，除了可以問基本的面試流程、我建議詢問<strong>設計團隊最重視的能力</strong>、設計團隊的架構等等，因為之後大機率是要和設計師面試，若能掌握對方團隊自己也可以更有自信地面試，而了解對方重視的價值也能讓準備更對症下藥。舉例來說我曾問過 HR 設計團隊希望實習生有行銷經驗還是產品經驗，HR 回答他們對實習生的期望比起行銷或產品，他們更希望看到強烈的學習慾望。</p><h4>Portfolio Presentation</h4><p>Youtube 上有很多很好的影片可以看，可以觀察別人簡報怎麼做、<strong>怎麼把故事描述得生動、如何解釋每個設計決策、如何表現自己在過程中不斷反思等</strong>，推薦 Christy Hu 的影片 <a href="https://www.youtube.com/watch?v=LeN-Kl22C1Q">The UX Design Portfolio Presentation that Got Me Hired at Google</a> ，當初邊看邊記下滿滿筆記。</p><p>簡報做好以後就是多練習、多討論、多迭代，作品集簡報算是唯一可以百分之百掌握的面試內容了，試著把內容講給不熟習你專案的人聽，看他們是否能聽懂你的故事，充分的練習也可以讓你在面試的時候更放鬆。我的作品集簡報在前幾場面試幾乎每次結束後都有修改，因為每次都會發現有些別人聽不懂的地方，我會試著調整並找到更簡單易懂的呈現方式。</p><h4>白板題 Whiteboard Challenge</h4><p>我在六個面試只有遇到一次 Whiteboard challenge ，也因為經驗不足，那家公司在白板題後被拒絕了。後來覆盤我覺得最大的心得是<strong> Whiteboard challenge 沒有正確答案，被 Challenge 的時候千萬不要慌</strong>！只要有條有理的說明自己為什麼做了這個設計決策、對使用者帶來什麼正向影響，只要你說得通就好。千萬不要像我一樣，一被 Challenge 就被牽著鼻子走。</p><h4>行為面試 Behavioral Interview</h4><p>多練習，<strong>準備五到八個故事，基本上他們可以套進所有的問題裡</strong>。準備時也要去了解每個問題的意義是什麼，比如說「你的同事沒做到承諾的事你會怎麼辦？」這個問題其實是想知道「你會如何幫助別人？」，了解常見的問題會讓你更得心應手地面對各式各樣的題目。</p><h4>如何拿到 Google UX Design Intern Offer</h4><p>我沒有拿到內推，是在職缺公布的第二天直接在官網投遞。完整的時間線如下：</p><ul><li>2024/10/9 官網投遞</li><li>2024/12/16 收到問卷（履歷有通過的人才會收到，問一些能力以及感興趣的組別）</li><li>2024/12/18 回覆問卷</li><li>2025/1/17 收到面試邀請</li><li>2024/1/27 兩個 45 分鐘的線上面試</li><li>2025/2/7 Recruiter 來信說有 Update</li><li>2025/2/11 收到 Offer</li></ul><p>我在面試前找了兩位 Google 員工 Coffee Chat，了解公司內部的合作方式、對設計實習生的期望、以及面試的技巧，我覺得這兩場 Coffee Chat 對我幫助很大，讓我可以更精準的展現我的能力。以下幾個是我總結 Google 對 UX Design Intern 的期望：</p><ul><li><strong>溝通技巧</strong>，尤其是跨職能的合作：多用過去的經驗展現自己和他人溝通的方式，比如說你會主動做會議紀錄並 Follow up</li><li><strong>Be User-Centered</strong>：設計師最主要的工作內容就是提供好的用戶體驗，可以用過去的經驗說明自己如何解決用戶痛點、為用戶創造價值</li><li><strong>熱情</strong>：除了 Google 我也聽到其他公司對實習生的期望是有熱情。為什麼想加入 Google、為什麼想成為設計師。我有在面試中特別提到自己對 Google 產品的熱愛，以及對 B2B 產品的熱忱（我面試的是 B2B 的組別）</li><li><strong>主動</strong>：包含幫助他人、學習新知識、問問題，都是主動的表現</li></ul><p>最後就是多練習了，網路上有很多 Googleyness interview 的題目，那時候我把每一題都練過一遍，也盡量讓我的回答符合上面幾個要點。</p><h4>沒有相關經驗怎麼辦</h4><ol><li><strong>想辦法創造經驗：</strong>做 side project、加入學校社團、參加黑客松等，甚至創業，這些都有機會做專案。最好做一些有機會和人合作的專案，尤其是工程師、PM等角色，因為<strong>合作能力</strong>對設計師很重要。</li><li>所有東西都是可以包裝的：作品集就是在講故事，一個故事有很多種講法，可以針對你的求職目標去包裝。</li></ol><h4>如何 Build Connection / Networking</h4><p>北美職場很重要的另一點是 Networking，最簡單的方式就是用 ADPList，上面有很多很願意幫忙的前輩。另外也很鼓勵大家主動在 LinkedIn 上 Reach out，老實說我也很害怕發訊息給陌生人，聊天室至今也還留著一堆沒有被回覆的 Cold messages，但在這之中還是很幸運的遇到不少人願意回覆的前輩，也和素昧平生的設計師練習面試，這些對我的幫助都很大。</p><p>另外就是我和朋友一起建立了設計指北針這個社群，回想當初自己的初衷就是透過社群遇到更多的人，也真的因為這個平台讓我有機會和前輩聊天，更讓我在面試中分享這個社群的營運而得到讚賞。</p><h3>Key takeaways</h3><ul><li>儘早準備作品集和履歷，最好是八九月就完成，後續才有時間尋求建議並優化</li><li>多觀摩其他人的作品集和履歷，可以在 LinkedIn 上搜各個大公司 + design intern 去找到歷年的實習生，然後去看他們的作品集；另外 Reddit 上也有很多討論，如果有看到心儀公司的實習生可以主動私訊問能不能看他們的作品集</li><li>多尋求幫助，ADPList 很好用</li><li>快速迭代，作品集是一個大工程，但如果一直不改就用遠改不完</li><li>主動 Reach out，面試前最好跟該公司內的設計師聊聊，了解他們重視哪些能力</li><li>如果想成為最優秀的那群人，那就先去找到那群人，看看他們平時都在幹嘛</li><li><strong>保持紀律的持續投履歷，同時放寬心的看向下一個職缺和面試</strong></li></ul><h3>總結</h3><p>這一路走來一點也不容易，在將近半年的求職路後終於拿到 Offer，還是夢寐以求的公司，簽下 Offer 後的幾天都開心到睡不著覺，覺得這一切好不真實。在美國找工作是一件很困難的事，但過程也學到很多，我覺得這一路走來最重要的就是要多看、多問、多反思，<strong>看到別人厲害的地方、看見自己的亮點、承認自己的不夠好的地方，才有優化的方向</strong>。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o1Fm-4mdthBoerr0" /><figcaption>Google Offer Letter</figcaption></figure><p>很感謝一路走來所有願意給予幫助的前輩，找工作的過程曾經歷過無數次的迷茫，但每次和前輩的聊天都讓我能重拾熱忱，繼續往前走。也謝謝讀到最後的你，祝福你能早日上岸。</p><p>如果對設計實習的申請有任何問題，歡迎在 <a href="https://www.linkedin.com/in/jiayunli223/">LinkedIn</a> 上與我聯繫，若有作品集與面試等求職相關的諮詢需求，歡迎透過<a href="https://www.instagram.com/designcompass.tw/">設計指北針</a>與我預約。</p><blockquote><strong>感謝你閱讀這篇文章，如果你覺得這篇文章對你有幫助，歡迎給我 50 下拍手鼓勵，也歡迎在下方留言讓我知道你的想法！拍手小秘訣： 只要將滑鼠按著不放，就能夠連續拍手囉，試試看吧 👏</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5d7f396a9ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>