1 00:00:00,200 --> 00:00:03,300 Before we start our episode today, just a quick reminder 2 00:00:03,300 --> 00:00:05,800 that I'm giving away jetbrains. All products pack. 3 00:00:05,800 --> 00:00:09,500 Personal licenses for free. The all products, pack license, 4 00:00:09,500 --> 00:00:14,200 allows you to use all jetbrains IDs such as IntelliJ, pycharm 5 00:00:14,200 --> 00:00:18,300 goal and webstorm Etc. I'll choose three lucky winners 6 00:00:18,300 --> 00:00:20,700 and the contest will end in the next few days. 7 00:00:21,100 --> 00:00:24,400 Get more information on how to participate by going to this 8 00:00:24,400 --> 00:00:26,800 URL. Technology, you know, dot, f /. 9 00:00:26,800 --> 00:00:29,700 Jetbrains Dash. Give away his learning one more. 10 00:00:30,000 --> 00:00:34,400 I'm take the Juno, the dev slash jetbrains Dash giveaway, special 11 00:00:34,400 --> 00:00:37,000 thanks to jetbrains for sponsoring this giveaway. 12 00:00:37,500 --> 00:00:41,200 You think about becoming a tech influencer is content is Queen 13 00:00:41,200 --> 00:00:44,800 and consistency, quality and value matter. 14 00:00:44,800 --> 00:00:48,100 That's the trifecta of creating content that sticks. 15 00:00:52,600 --> 00:00:56,100 Hey everyone. My name is Henry sura, one. 16 00:00:57,300 --> 00:01:00,000 And you're listening to the tekhelet journal. 17 00:01:00,700 --> 00:01:03,800 The show will be bringing you the greatest technical leaders 18 00:01:04,099 --> 00:01:07,600 practitioners and thought leaders in the industry to 19 00:01:07,600 --> 00:01:11,900 discuss about their Journey ideas and practices that we all 20 00:01:11,900 --> 00:01:15,600 can learn and apply to build a highly performing technical team 21 00:01:15,900 --> 00:01:18,400 and to make an impact in your personal work. 22 00:01:19,100 --> 00:01:27,500 So let's dive into our Journal. Hey everyone, welcome to a new 23 00:01:27,500 --> 00:01:30,800 episode of the tekhelet journal with me Ojos Henry Surya with 24 00:01:30,800 --> 00:01:33,000 Robin. If you are new to the tekhelet 25 00:01:33,000 --> 00:01:36,400 journal, make sure to subscribe and follow the podcast on your 26 00:01:36,400 --> 00:01:40,000 favorite podcast app, in order to get notified for any new 27 00:01:40,000 --> 00:01:43,200 episode going forward. It is my mission to have the 28 00:01:43,200 --> 00:01:46,000 podcast Community. Grow even bigger, and to have 29 00:01:46,000 --> 00:01:49,200 more awesome and inspiring guests coming and sharing their 30 00:01:49,200 --> 00:01:52,200 wisdom with us. And if you are regular listener, 31 00:01:52,600 --> 00:01:55,000 do consider spending, During some time to leave me any 32 00:01:55,000 --> 00:01:58,200 feedback about the podcast. I would love to hear more from 33 00:01:58,200 --> 00:01:59,600 each of you. And let me know. 34 00:01:59,600 --> 00:02:03,200 If you have any great suggestion on how to improve the podcast 35 00:02:03,200 --> 00:02:06,600 for today's episode. I'm very excited to share my 36 00:02:06,600 --> 00:02:08,500 conversation with Stephanie Hwang. 37 00:02:08,500 --> 00:02:12,300 Stephanie is a Google Cloud developer Advocate and you might 38 00:02:12,300 --> 00:02:15,200 have seen her online on YouTube talking about Google Cloud 39 00:02:15,200 --> 00:02:18,900 related Technologies, see her in action presenting at conferences 40 00:02:18,900 --> 00:02:22,900 or even listen to her on the how I launched this a success story. 41 00:02:24,300 --> 00:02:27,700 Stephanie has a personal mission to blend storytelling and 42 00:02:27,700 --> 00:02:30,900 Technologies to create remarkable online developer 43 00:02:30,900 --> 00:02:33,800 contents. Stephanie also holds her own 44 00:02:33,800 --> 00:02:36,700 YouTube channel called staff. You should know where you can 45 00:02:36,700 --> 00:02:40,200 find Korea, tag and productivity tips and advice. 46 00:02:40,600 --> 00:02:43,200 There are a lot of great things that we discussed about in this 47 00:02:43,200 --> 00:02:46,900 episode, ranging from personal brand being attack influencer 48 00:02:47,000 --> 00:02:51,200 public speaking career advice. And also how women can thrive in 49 00:02:51,200 --> 00:02:53,300 technology. I really enjoyed this 50 00:02:53,300 --> 00:02:54,900 conversation. Sensation and I hope you all 51 00:02:54,900 --> 00:02:57,300 enjoy it as well. So let's get started. 52 00:02:58,500 --> 00:03:01,400 Are you a start-up in software development Which is less than 53 00:03:01,400 --> 00:03:04,800 five years old. If yes our sponsor at jetbrains 54 00:03:04,800 --> 00:03:08,800 have a 50% startup discount offer, which allows startups to 55 00:03:08,800 --> 00:03:12,300 purchase multiple products and subscriptions for up to 10 56 00:03:12,300 --> 00:03:16,500 unique licenses over a period of months to find out more search 57 00:03:16,500 --> 00:03:20,000 for jetbrains startup discount offer, or you can check out the 58 00:03:20,000 --> 00:03:25,600 link mention in the show notes. Hey, Stephanie, welcome to the 59 00:03:25,600 --> 00:03:27,900 technique, you know, very excited to have you here in this 60 00:03:27,900 --> 00:03:29,900 year. Hey, thank you so much for 61 00:03:29,900 --> 00:03:31,600 having me today. I'm so excited to be here. 62 00:03:31,800 --> 00:03:35,000 So Stephanie, maybe you can tell the audience here about 63 00:03:35,000 --> 00:03:36,300 yourself. What's your role? 64 00:03:36,300 --> 00:03:38,600 And what are you up to now? Sure. 65 00:03:38,600 --> 00:03:43,800 So I am a developer Advocate at Google cloud and I focus on 66 00:03:43,800 --> 00:03:47,200 online scalable content, specifically, and what that 67 00:03:47,200 --> 00:03:51,700 means is that as a DA, I go out into the community and I create 68 00:03:51,700 --> 00:03:55,400 content online, that makes developers want to share tweet 69 00:03:55,400 --> 00:03:57,500 and talk about it. And essentially, the goal is to 70 00:03:57,500 --> 00:04:01,300 advocate for And give feedback back to product, to eventually 71 00:04:01,300 --> 00:04:04,000 improve the product prior to being a DJ. 72 00:04:04,000 --> 00:04:06,600 I was a customer engineer or an industry. 73 00:04:06,600 --> 00:04:08,200 It's also known as a sales engineer. 74 00:04:08,200 --> 00:04:11,500 And an interesting point about me is that I actually didn't 75 00:04:11,500 --> 00:04:14,600 graduate with a CS or computer science or engineering degree. 76 00:04:14,700 --> 00:04:17,899 So, I've had sort of a unconventional path to where I 77 00:04:17,899 --> 00:04:19,899 am today. In my spare time. 78 00:04:19,899 --> 00:04:24,100 I am a big performer, I dance. And I use a lot of that into my 79 00:04:24,100 --> 00:04:27,400 day-to-day work as a public speaker at Google interesting. 80 00:04:27,400 --> 00:04:30,300 You mentioned, you didn't graduate from CS degree. 81 00:04:30,300 --> 00:04:32,900 Can you share a little bit more? What's your journey like from 82 00:04:32,900 --> 00:04:35,600 the University and then the turning points in your career 83 00:04:35,600 --> 00:04:37,700 until you have this a deferral roll? 84 00:04:38,000 --> 00:04:41,500 Yeah, absolutely. So I didn't know what I wanted 85 00:04:41,500 --> 00:04:46,600 to do at University or even out of school while I was at UCLA. 86 00:04:46,600 --> 00:04:50,700 I was very undecided and I ultimately did a communication 87 00:04:50,700 --> 00:04:53,000 studies degree because I thought I wanted to go into 88 00:04:53,000 --> 00:04:55,000 entertainment by the entertainment industry. 89 00:04:55,000 --> 00:04:59,300 I knew that I loved being around production, and So in that 90 00:04:59,300 --> 00:05:02,400 major, I was able to study both interpersonal and public 91 00:05:02,400 --> 00:05:05,700 speaking, and then I did a few internships in the entertainment 92 00:05:05,700 --> 00:05:09,400 industry. I remember working at a YouTube 93 00:05:09,400 --> 00:05:12,700 start up for dance Channel and I also worked at Warner Brothers 94 00:05:12,700 --> 00:05:14,400 records. So I kind of did production 95 00:05:14,400 --> 00:05:17,800 assistant work here and there as well as some sales and I did one 96 00:05:17,800 --> 00:05:20,000 Tech internship as well. Throughout that time. 97 00:05:20,000 --> 00:05:22,200 I knew I had a fascination with technology though. 98 00:05:22,200 --> 00:05:24,700 I didn't know that I wanted to become extremely technical at 99 00:05:24,700 --> 00:05:27,000 the time. I ended up finding a new minor 100 00:05:27,100 --> 00:05:30,300 called digital humanities. Teas where I did research in 101 00:05:30,300 --> 00:05:34,100 analytics and visualization, but it focused primarily on the 102 00:05:34,100 --> 00:05:37,700 study of humanities. So I would study art and 103 00:05:37,700 --> 00:05:41,300 literature and history and we would visualize it and sort of 104 00:05:41,300 --> 00:05:44,100 modernize that practice. So, it was clear. 105 00:05:44,100 --> 00:05:47,900 I had an interest in the intermediary and fusion between 106 00:05:47,900 --> 00:05:50,600 Communications and technology. So when I graduated from 107 00:05:50,600 --> 00:05:54,000 college, I was applying all sorts of places and I ended up 108 00:05:54,000 --> 00:05:57,400 applying to and making it into Oracle as my first job. 109 00:05:57,400 --> 00:05:59,600 I didn't really notice. Too much about Enterprise 110 00:05:59,600 --> 00:06:02,900 technology at the time. And I did it sort of, as a Hail 111 00:06:02,900 --> 00:06:04,600 Mary. And I wanted to give it a shot. 112 00:06:04,700 --> 00:06:07,400 I knew that it was a large stable company with a well-known 113 00:06:07,400 --> 00:06:09,200 name. And I already knew I had an 114 00:06:09,200 --> 00:06:12,500 interest in technology though. I wasn't extremely confident 115 00:06:12,500 --> 00:06:14,400 because I didn't have a computer science background though. 116 00:06:14,400 --> 00:06:16,200 They were hiring for sales Engineers. 117 00:06:16,200 --> 00:06:18,800 So I knew that it would be a great entry point to learn both 118 00:06:18,800 --> 00:06:21,900 business and technical skills. So, when I started there, I was 119 00:06:21,900 --> 00:06:25,100 able to start with a lot of other college grads and I 120 00:06:25,100 --> 00:06:27,400 embraced it. I learned as much as possible 121 00:06:27,400 --> 00:06:30,900 and within In that year, I joined the business intelligence 122 00:06:30,900 --> 00:06:33,600 and analytics team after the first year and a half. 123 00:06:33,600 --> 00:06:37,400 I started to notice that cloud technology in the platform and 124 00:06:37,400 --> 00:06:39,900 infrastructure as a service regions and sections in 125 00:06:39,900 --> 00:06:42,300 technology, were gaining a lot of momentum. 126 00:06:42,400 --> 00:06:47,000 So I decided to Pivot and do post sales implementations for 127 00:06:47,100 --> 00:06:49,100 our customers. For our Cloud. 128 00:06:49,100 --> 00:06:51,900 Technology is on the platform and infrastructure side after 129 00:06:51,900 --> 00:06:53,400 doing that for a year and a half. 130 00:06:53,400 --> 00:06:58,200 I eventually ended up getting reached out to by Google, right? 131 00:06:58,300 --> 00:07:01,100 When you deal with this technology, especially when 132 00:07:01,100 --> 00:07:03,900 technology was not your background, is there any major 133 00:07:03,900 --> 00:07:06,800 challenges that you foresee along your journey, whether to 134 00:07:06,800 --> 00:07:10,000 keep up with the fundamentals about technology, or even to 135 00:07:10,000 --> 00:07:12,700 understand about technology products, are there any major 136 00:07:12,700 --> 00:07:14,200 challenges that you foresee them? 137 00:07:14,200 --> 00:07:16,800 And also how to overcome those? Yeah. 138 00:07:16,800 --> 00:07:19,700 So I think because I didn't come from an engineering or computer 139 00:07:19,700 --> 00:07:22,000 science background. A lot of the learning I did at 140 00:07:22,000 --> 00:07:25,400 the time felt like I was presented a problem and I had to 141 00:07:25,400 --> 00:07:28,600 go back and learn the foundation or the fundamentals of a base 142 00:07:28,600 --> 00:07:32,700 design or what a virtual machine was how to virtualize technology 143 00:07:32,700 --> 00:07:34,700 and then microservice architectures had just started 144 00:07:34,700 --> 00:07:36,800 becoming more popular eyes back then as well. 145 00:07:36,800 --> 00:07:40,000 So I really didn't have a huge context about how we're data 146 00:07:40,000 --> 00:07:42,700 centers and on-premise Technologies before and how are 147 00:07:42,700 --> 00:07:45,400 they now? So big challenge was working 148 00:07:45,400 --> 00:07:48,400 backwards in a sense, learning the fundamentals and foundations 149 00:07:48,400 --> 00:07:51,100 of computer science and Enterprise Technologies starting 150 00:07:51,100 --> 00:07:53,000 with the problem. And then going back and trying 151 00:07:53,000 --> 00:07:56,600 to understand the context of why it was a challenge and how they 152 00:07:56,600 --> 00:07:58,200 could solve those challenges using. 153 00:07:58,400 --> 00:08:00,000 Our modernized Technologies today. 154 00:08:00,200 --> 00:08:03,900 One of the ways that I found that worked for me was to just 155 00:08:03,900 --> 00:08:06,300 constantly be hungry to learn and leverage. 156 00:08:06,400 --> 00:08:09,000 A lot of the mentors who had been at the company for a longer 157 00:08:09,000 --> 00:08:11,700 period of time, and not be afraid to ask them for 158 00:08:11,700 --> 00:08:16,100 one-on-one sessions to sit down with me and go to a whiteboard 159 00:08:16,100 --> 00:08:19,800 and begin, to architect out solutions, that involve multiple 160 00:08:19,800 --> 00:08:23,000 products and Integrations between databases and between 161 00:08:23,000 --> 00:08:25,400 message, Brokers, Etc. So, I could truly understand the 162 00:08:25,400 --> 00:08:28,200 big picture as opposed to just all the fine grained details. 163 00:08:28,300 --> 00:08:30,700 At a very low level, thanks for sharing that. 164 00:08:30,800 --> 00:08:33,400 So moving on to your current role as a death row. 165 00:08:33,400 --> 00:08:36,200 I know, it's kind of like trendy these day to see death real 166 00:08:36,200 --> 00:08:38,000 role. You guys are popular in the 167 00:08:38,000 --> 00:08:41,100 YouTube channel linked in any kind of social media. 168 00:08:41,200 --> 00:08:43,000 Maybe you can share, what is a death roll. 169 00:08:43,400 --> 00:08:46,600 Yeah, so developer relations originally began because 170 00:08:46,600 --> 00:08:49,900 companies wanted a way to advocate for developers. 171 00:08:50,000 --> 00:08:52,800 You had sales teams, you had marketing teams who were able to 172 00:08:52,800 --> 00:08:54,900 reach out to customers and clients business, 173 00:08:54,900 --> 00:08:57,700 decision-makers and, of course, Market the products to those 174 00:08:57,700 --> 00:09:00,100 audiences. But when it came to developer 175 00:09:00,100 --> 00:09:03,200 challenges, it was very difficult for a group of people 176 00:09:03,200 --> 00:09:06,300 who had specialized skills in that area to empathize. 177 00:09:06,400 --> 00:09:10,100 And to be able to understand the deeper challenges that came with 178 00:09:10,100 --> 00:09:13,100 developers, especially those who were either leveraging API 179 00:09:13,100 --> 00:09:16,000 products, or we're working on creating customized Solutions on 180 00:09:16,000 --> 00:09:19,500 top of the company's platform. So because of this more 181 00:09:19,500 --> 00:09:23,500 technical approach and audience developer relations became more 182 00:09:23,500 --> 00:09:27,700 popular over the last 10 years. Or so now, the team that I'm on 183 00:09:27,700 --> 00:09:30,700 is New Google Cloud. Relatively speaking. 184 00:09:30,700 --> 00:09:33,500 We are one of the first developer relations teams to 185 00:09:33,500 --> 00:09:35,600 focus more on the online content side. 186 00:09:35,600 --> 00:09:38,600 And the reason is because the person who started that team 187 00:09:38,600 --> 00:09:42,400 notice that creating online content reaches a vast number of 188 00:09:42,400 --> 00:09:45,500 people and audiences online, especially those who do not 189 00:09:45,500 --> 00:09:49,000 typically have access to go to Tech events and see people in 190 00:09:49,008 --> 00:09:52,100 person traditionally before developer relations primarily 191 00:09:52,100 --> 00:09:55,800 focused on offering in-person events meetups and presenting at 192 00:09:55,800 --> 00:09:57,300 conferences all over the world though. 193 00:09:57,300 --> 00:10:00,000 That's still a huge. Focus today, online content has 194 00:10:00,000 --> 00:10:03,000 become even more prevalent in the industry, especially given 195 00:10:03,000 --> 00:10:06,200 covid and the remote working world where online and scalable 196 00:10:06,200 --> 00:10:09,400 content has become extremely effective at still, reaching the 197 00:10:09,400 --> 00:10:12,200 largest number of people and developers as possible. 198 00:10:12,200 --> 00:10:16,200 So that's what my team does is we do podcasts like this. 199 00:10:16,200 --> 00:10:19,000 We do talks online. We do meet ups but YouTube is 200 00:10:19,000 --> 00:10:22,600 such an incredible platform to reach such a vast majority of 201 00:10:22,600 --> 00:10:25,400 people even those that you may not have been targeting because 202 00:10:25,400 --> 00:10:29,000 all of this information has been democratized and made accessible 203 00:10:29,000 --> 00:10:32,100 to anyone make sense. So what are some of the major 204 00:10:32,100 --> 00:10:35,000 attributes that are required to be a good death row? 205 00:10:35,300 --> 00:10:37,300 Yeah. So the interesting thing about 206 00:10:37,300 --> 00:10:40,400 devrel is that we have so many people coming from various 207 00:10:40,400 --> 00:10:42,800 backgrounds. And the one thing I will say is 208 00:10:42,800 --> 00:10:45,600 that in developer. Advocacy specifically, most 209 00:10:45,600 --> 00:10:49,000 people need to have a technical or developer background in the 210 00:10:49,000 --> 00:10:51,200 product that you're representing or the language that you're 211 00:10:51,200 --> 00:10:54,300 representing for client library, for example, so public speaking 212 00:10:54,300 --> 00:10:56,900 is huge as well as domain expertise. 213 00:10:56,900 --> 00:10:59,200 And I would also say Developer empathy. 214 00:10:59,300 --> 00:11:02,200 Be able to understand when a developer has an issue really 215 00:11:02,200 --> 00:11:05,100 work towards solving their issues and listening to them and 216 00:11:05,100 --> 00:11:08,200 then providing feedback back to product in an actionable way 217 00:11:08,200 --> 00:11:12,000 where product can take your suggestions and be able to 218 00:11:12,000 --> 00:11:14,900 create a feature that will prioritize developers 219 00:11:14,900 --> 00:11:17,800 challenges. So I would say as a conclusion 220 00:11:17,900 --> 00:11:20,900 developer empathy, as well as public speaking and domain 221 00:11:20,900 --> 00:11:23,200 expertise. So you mentioned also in the 222 00:11:23,200 --> 00:11:27,200 beginning about you using your performance background and also 223 00:11:27,200 --> 00:11:29,500 probably gel that with Your death row row. 224 00:11:29,500 --> 00:11:32,300 Can you tell me more about it? How do you use your background 225 00:11:32,300 --> 00:11:36,000 in the performance entertainment doing production and to know? 226 00:11:36,300 --> 00:11:38,400 Yeah. So one thing, I didn't mention 227 00:11:38,400 --> 00:11:42,500 yet about my personal story, is how I transitioned from Oracle 228 00:11:42,500 --> 00:11:46,200 as a customer success and implementation engineer over to 229 00:11:46,200 --> 00:11:50,400 Google into developer relations. So, when I was about to leave or 230 00:11:50,400 --> 00:11:53,200 Cole, I wanted to actually go and travel and experience the 231 00:11:53,200 --> 00:11:56,200 world. And I also was trying to decide 232 00:11:56,200 --> 00:11:58,100 what I wanted to do next. What was my next step? 233 00:11:58,300 --> 00:12:02,200 Stone customer engineering was a huge experience and I found 234 00:12:02,200 --> 00:12:04,000 Success Through that. But I was still in this 235 00:12:04,000 --> 00:12:06,100 searching phase where I was trying to figure out what my 236 00:12:06,100 --> 00:12:08,600 true passion was. And I'm sure that you've heard 237 00:12:08,600 --> 00:12:11,600 the term, find your passion and you'll never work a day in your 238 00:12:11,600 --> 00:12:15,100 life, which I took to heart very seriously a little bit too much 239 00:12:15,100 --> 00:12:17,100 because I started to overthink that phrase. 240 00:12:17,100 --> 00:12:19,500 So I decided to look around and see what other people on 241 00:12:19,500 --> 00:12:21,400 LinkedIn were doing what my friends were doing. 242 00:12:21,400 --> 00:12:23,400 And it seemed like everybody at the time was applying to 243 00:12:23,400 --> 00:12:26,000 graduate school because of course, it's a logical step in 244 00:12:26,000 --> 00:12:27,600 your career to get more schooling. 245 00:12:27,600 --> 00:12:30,500 So I decided It to apply to Stanford thinking that I wanted 246 00:12:30,500 --> 00:12:34,500 to go to journalism school and try to do digital journalism, 247 00:12:34,500 --> 00:12:36,900 which was a new field. But as I was taking the test and 248 00:12:36,900 --> 00:12:39,900 writing my personal statement, I realized, while I was writing 249 00:12:39,900 --> 00:12:42,600 it, that I wasn't applying for the right reasons. 250 00:12:42,600 --> 00:12:46,000 I was really doing it because I was falling, others step to 251 00:12:46,000 --> 00:12:48,600 apply to grad school as a logical, next step. 252 00:12:48,600 --> 00:12:51,900 And I wasn't truly passionate about the field like most other 253 00:12:51,900 --> 00:12:55,300 applicants would be. So, I decided to move away from 254 00:12:55,300 --> 00:12:58,100 that approach and really reflect back on. 255 00:12:58,300 --> 00:13:01,700 What I wanted to do in the next two to four years, what skills 256 00:13:01,700 --> 00:13:04,100 would be most important and what did I enjoy doing? 257 00:13:04,300 --> 00:13:09,000 So I knew that I already had an interest and fascination with 258 00:13:09,000 --> 00:13:12,900 production performing but also technology, so I dreamed of 259 00:13:13,000 --> 00:13:15,600 eventually finding something that would allow me to do both, 260 00:13:15,600 --> 00:13:18,500 but I kind of just left it in the back of my mind and said, 261 00:13:18,500 --> 00:13:21,300 okay, I don't really know any roles that would merge those two 262 00:13:21,300 --> 00:13:23,300 things. So, I'll just see what happens. 263 00:13:23,300 --> 00:13:26,300 I'm just going to keep on going with the travel plan, then at 264 00:13:26,300 --> 00:13:28,000 the time, Google happen to reach out. 265 00:13:28,200 --> 00:13:30,200 About a sales engineering position or customer 266 00:13:30,200 --> 00:13:31,700 engineering. And I went through the interview 267 00:13:31,700 --> 00:13:34,400 process and eventually got the role, which I was super excited 268 00:13:34,400 --> 00:13:37,000 about. So as I was starting my journey 269 00:13:37,000 --> 00:13:40,400 at Google, I actually got reached out to, by somebody who 270 00:13:40,400 --> 00:13:44,000 was also a customer engineer and he was working on his own online 271 00:13:44,000 --> 00:13:46,900 content, for Google cloud and he asked me if I was interested in 272 00:13:46,900 --> 00:13:49,000 helping him and I thought, wow, this is interesting. 273 00:13:49,000 --> 00:13:51,900 We're kind of doing this small start-up within Google creating 274 00:13:51,900 --> 00:13:55,300 online content using our webcams and microphones and it wasn't 275 00:13:55,300 --> 00:13:58,100 funded by any means. It was just a Grassroots effort. 276 00:13:58,300 --> 00:14:00,600 To do this, we started running around the lobby is running 277 00:14:00,600 --> 00:14:02,000 around. The office, is trying to find 278 00:14:02,000 --> 00:14:06,100 quiet, space to film demos, and invite other people on our shows 279 00:14:06,100 --> 00:14:08,500 and have guests on our show. And eventually, we started doing 280 00:14:08,500 --> 00:14:12,500 that for about six months and devrel reached out to us to ask 281 00:14:12,500 --> 00:14:15,500 if we wanted to create online content in collaboration with 282 00:14:15,500 --> 00:14:18,400 them, on the Google Cloud YouTube channel, which we were 283 00:14:18,400 --> 00:14:21,600 thrilled to be involved with. So we started doing that. 284 00:14:21,600 --> 00:14:24,800 And through that, my work creating online content started 285 00:14:24,800 --> 00:14:28,000 to Bubble Up and get more attention and I was asked to do 286 00:14:28,200 --> 00:14:31,600 Larger opportunities like present and host the broadcast 287 00:14:31,600 --> 00:14:34,100 of our largest conference Google Cloud next. 288 00:14:34,100 --> 00:14:36,100 So through that. I just kept saying, yes, because 289 00:14:36,100 --> 00:14:39,100 they were challenges, they were exciting and I could do what I 290 00:14:39,100 --> 00:14:41,600 had envisioned and dreamed of doing and it started to become 291 00:14:41,600 --> 00:14:43,700 more real. To me eventually one thing led 292 00:14:43,700 --> 00:14:48,200 to another and now I started on a team of the first online, 293 00:14:48,200 --> 00:14:51,900 scalable developer Advocates. So that's exactly how I ended up 294 00:14:51,900 --> 00:14:54,200 in devrel, which was totally unexpected. 295 00:14:54,200 --> 00:14:56,300 But something that I wanted to do. 296 00:14:56,300 --> 00:14:58,500 One thing I will say though, is that it absolutely, Literally 297 00:14:58,500 --> 00:15:01,900 terrified me to join devrel because I knew it was even more 298 00:15:01,900 --> 00:15:04,900 of a technical role that's part of the tech engineering side of 299 00:15:04,900 --> 00:15:06,900 Google. I didn't really have any plans 300 00:15:06,900 --> 00:15:09,600 on becoming more technical or joining engineering given my 301 00:15:09,600 --> 00:15:12,800 background, but you know I said, hey, this is an exciting yet 302 00:15:12,800 --> 00:15:16,400 challenging opportunity and I've always been told that if an 303 00:15:16,400 --> 00:15:20,000 opportunity doesn't both Challenge and excite you then 304 00:15:20,000 --> 00:15:22,100 reconsider, so I said, you know what? 305 00:15:22,100 --> 00:15:24,200 I'm just going to try it. It's better just be more 306 00:15:24,200 --> 00:15:26,500 technical in the beginning of your career and challenge 307 00:15:26,500 --> 00:15:29,100 yourself because eventually when you You go into management or 308 00:15:29,100 --> 00:15:31,500 higher levels, but you'll start to lose that edge later down 309 00:15:31,500 --> 00:15:34,000 your career. So, I just took a chance and 310 00:15:34,000 --> 00:15:36,400 I've never looked back since, and it's given me so many 311 00:15:36,400 --> 00:15:39,600 opportunities to build my brand and become this Tech influence 312 00:15:39,600 --> 00:15:40,900 there. As you said, it's been a great 313 00:15:40,900 --> 00:15:42,000 experience. Yeah. 314 00:15:42,000 --> 00:15:44,300 Thanks for sharing that. I think I can relate to some of 315 00:15:44,300 --> 00:15:46,200 your sharing as well. Especially when you talk about 316 00:15:46,200 --> 00:15:48,900 the finding of passion and trying to figure out what you 317 00:15:48,900 --> 00:15:51,900 should do next, trying to find out what your strengths are. 318 00:15:51,900 --> 00:15:54,400 And what kind of roles that will excite you. 319 00:15:54,500 --> 00:15:56,900 I think these are very good sharing especially for those 320 00:15:56,900 --> 00:15:59,900 listeners who are also Still trying to find your passion or 321 00:15:59,900 --> 00:16:02,800 what you should do next. So advice from Stephanie here. 322 00:16:02,800 --> 00:16:04,200 Definitely, you should check it out. 323 00:16:04,200 --> 00:16:08,800 So about tech influencer, right? Given your online content and 324 00:16:08,800 --> 00:16:11,000 all that, how you should position yourself, most likely, 325 00:16:11,000 --> 00:16:12,800 as an expert, when you present that. 326 00:16:12,900 --> 00:16:15,600 So what are the basic things that you should know about being 327 00:16:15,600 --> 00:16:18,600 a tech influencer, especially for those people around that 328 00:16:18,600 --> 00:16:22,000 wants to position themselves as a tech influenza in any area 329 00:16:22,000 --> 00:16:24,000 that they want to Market themselves in. 330 00:16:24,300 --> 00:16:26,900 It's a growing field. And as I said, building your 331 00:16:26,900 --> 00:16:29,800 brand is crucial. In today's market with so many 332 00:16:29,800 --> 00:16:33,500 people online competing for that real estate and that are spaced. 333 00:16:33,500 --> 00:16:37,400 So, I would say that in order to become a tech influencer. 334 00:16:37,400 --> 00:16:40,900 It's all about sharing content. And in the beginning, you may 335 00:16:40,900 --> 00:16:42,900 not know. Okay, where do I get started? 336 00:16:42,900 --> 00:16:44,700 What do I share? I don't have the expertise. 337 00:16:44,700 --> 00:16:46,900 I don't have the knowledge. I don't have the authority, but 338 00:16:46,900 --> 00:16:48,700 it doesn't matter. Because everybody online is the 339 00:16:48,700 --> 00:16:51,100 same in the sense that they had to get started somewhere where 340 00:16:51,100 --> 00:16:52,200 people didn't know who they were. 341 00:16:52,300 --> 00:16:56,700 So I would say really Encourage Yourself to think about small 342 00:16:56,700 --> 00:16:59,500 pieces of information that you can You can sharing on LinkedIn 343 00:16:59,500 --> 00:17:02,600 on Twitter, on your social feeds and just start with anything. 344 00:17:02,600 --> 00:17:04,900 You can try to create a framework first. 345 00:17:04,900 --> 00:17:08,000 But if it's too, daunting of a task, just start sharing your 346 00:17:08,000 --> 00:17:11,000 thoughts, your opinions or just pieces of information that you 347 00:17:11,000 --> 00:17:14,300 find interesting in your field. Once you start to do that, then 348 00:17:14,300 --> 00:17:17,900 you can start building a pattern of framework a strategy around 349 00:17:17,900 --> 00:17:20,599 what your Niche will be. It might be helpful to start 350 00:17:20,599 --> 00:17:22,200 with that too. Maybe you just want to focus on 351 00:17:22,200 --> 00:17:24,599 networking content. Perhaps you only want to focus 352 00:17:24,599 --> 00:17:27,000 on machine learning, you can definitely begin with that as 353 00:17:27,000 --> 00:17:28,400 well. One thing that I like to To do, 354 00:17:28,400 --> 00:17:31,800 is I take documentation. I take articles and I break that 355 00:17:31,800 --> 00:17:35,900 down and start to understand the patterns and what my audience 356 00:17:35,900 --> 00:17:37,800 might want to know. What are the narratives that 357 00:17:37,800 --> 00:17:40,000 aren't being told to your audience today. 358 00:17:40,000 --> 00:17:43,800 For example, I begin to learn by understanding common technology 359 00:17:43,800 --> 00:17:46,200 architectures. Let's say, I want to focus on a 360 00:17:46,208 --> 00:17:50,200 broad Architectural Group of topics like streaming analytics 361 00:17:50,200 --> 00:17:51,900 or iot. Maybe you want to focus on how 362 00:17:51,900 --> 00:17:54,200 to scale your architecture. Is it maybe you want to focus on 363 00:17:54,200 --> 00:17:56,400 kubernetes and microservices? In my mind. 364 00:17:56,400 --> 00:17:59,000 It's actually great to become sort of a Generalist in this 365 00:17:59,000 --> 00:18:01,000 sense, even if you are considering yourself a 366 00:18:01,000 --> 00:18:04,000 specialist because you can create a broader narrative and 367 00:18:04,000 --> 00:18:07,400 story flow over. Let's say 20 topics over time. 368 00:18:07,400 --> 00:18:08,700 Once you kind of nailed down. Okay. 369 00:18:08,700 --> 00:18:10,500 These are the top 10 to 20 topics. 370 00:18:10,500 --> 00:18:13,600 I want to talk about overtime. Here's this broad story arc. 371 00:18:13,600 --> 00:18:17,600 Then you can start creating specific episodes or specific 372 00:18:17,600 --> 00:18:20,300 podcast episodes, maybe even it's just a picture that you 373 00:18:20,300 --> 00:18:23,200 want to share or an article or a gif and a quick caption. 374 00:18:23,200 --> 00:18:25,200 Then the next thing you want to think about is creating 375 00:18:25,200 --> 00:18:28,000 frequency around that. You need to make sure that you 376 00:18:28,100 --> 00:18:31,800 Are sharing this content, very consistently to your audiences. 377 00:18:31,800 --> 00:18:35,500 If you don't have consistency, then people will not see that. 378 00:18:35,500 --> 00:18:37,700 You are becoming an influencer in that space. 379 00:18:37,800 --> 00:18:40,200 Once you do that, you want to make sure that the content you 380 00:18:40,200 --> 00:18:43,300 share is valuable. It's perhaps opinionated because 381 00:18:43,300 --> 00:18:46,700 as you know, online people appreciate opinions, and it's 382 00:18:46,700 --> 00:18:50,100 targeted to your audience, it's solving one of their challenges. 383 00:18:50,100 --> 00:18:53,100 It's showing them something they didn't know before. 384 00:18:53,200 --> 00:18:56,900 The think about becoming a tech influencer is content is Queen 385 00:18:56,900 --> 00:19:00,500 and consistency. Quality and value matter. 386 00:19:00,500 --> 00:19:04,200 That's the trifecta of creating content that sticks and two 387 00:19:04,200 --> 00:19:05,900 books. I recommend about creating 388 00:19:05,900 --> 00:19:10,100 valuable content is content, rules, and made to stick. 389 00:19:10,200 --> 00:19:14,200 And I also follow Gary Vee on social media, because he is all 390 00:19:14,200 --> 00:19:16,500 about creating content. So, I recommend checking out his 391 00:19:16,500 --> 00:19:18,600 tips as well. Thanks for sharing that, 392 00:19:18,600 --> 00:19:21,700 especially for those of us who are still thinking about 393 00:19:21,700 --> 00:19:23,600 creating content. So I think just do it. 394 00:19:23,600 --> 00:19:27,500 Find your Niche, find specialty where you are good at obviously 395 00:19:27,600 --> 00:19:30,600 and then Start creating the content and be more frequent and 396 00:19:30,600 --> 00:19:33,300 consistent in terms of your message and in terms of value. 397 00:19:33,300 --> 00:19:36,300 So, specifically about format. I know there are few things that 398 00:19:36,300 --> 00:19:40,900 we can explore things like blog posts, YouTube videos podcasts, 399 00:19:41,000 --> 00:19:44,400 or any specific other content, are there any channels that 400 00:19:44,400 --> 00:19:46,400 basically more effective than the others? 401 00:19:46,900 --> 00:19:49,400 I've had this question before, and it's interesting. 402 00:19:49,400 --> 00:19:52,500 I think that depending on the audience, of course, everybody 403 00:19:52,500 --> 00:19:55,100 has a preference, whether they like to consume information via 404 00:19:55,100 --> 00:19:59,500 YouTube, or articles or perhaps live, Game on Twitch TV. 405 00:19:59,600 --> 00:20:02,200 There's live coding on there. For example, they are all 406 00:20:02,200 --> 00:20:05,700 valuable and you can build an audience through any of those 407 00:20:05,700 --> 00:20:09,700 means, if you follow my three tips around consistency quality 408 00:20:09,700 --> 00:20:12,700 and value of information. I think that there is something 409 00:20:12,700 --> 00:20:17,200 to be said, around YouTube and blog posts being something 410 00:20:17,200 --> 00:20:20,800 that's proven to be effective. I think those are two solid 411 00:20:20,800 --> 00:20:24,100 forms of mediums to use, but it doesn't mean that you shouldn't 412 00:20:24,100 --> 00:20:27,500 give live coding or livestreams the chance, because there's 413 00:20:27,500 --> 00:20:30,700 probably Less people on those platforms doing such a thing. 414 00:20:30,700 --> 00:20:34,200 So it could actually carve out a good opportunity for you to go 415 00:20:34,200 --> 00:20:36,100 there and start building your brand there. 416 00:20:36,100 --> 00:20:39,000 The other tip I'll say is, don't just focus on one medium. 417 00:20:39,000 --> 00:20:41,000 The key thing about creating content is sharding, your 418 00:20:41,000 --> 00:20:44,000 content, in other words, create one piece of content and then 419 00:20:44,000 --> 00:20:46,300 replicate it across mediums. And that's how you reach an even 420 00:20:46,300 --> 00:20:48,300 broader audience. So if you're creating an 421 00:20:48,300 --> 00:20:50,900 article, maybe think about doing a podcast, if you think about 422 00:20:50,900 --> 00:20:52,900 doing a podcast, create an article around it, create a 423 00:20:52,908 --> 00:20:55,900 video film yourself, doing the podcast less work on your part. 424 00:20:55,900 --> 00:20:59,400 And you really maximized. Expand your efforts. 425 00:20:59,700 --> 00:21:02,200 Thanks for the tips. I should also follow one of your 426 00:21:02,200 --> 00:21:05,900 tips as well going forward. So I've heard this quote before 427 00:21:05,900 --> 00:21:08,900 public, speaking is actually the number one fear in the world, 428 00:21:08,900 --> 00:21:11,600 even much scarier than being that itself. 429 00:21:11,600 --> 00:21:15,100 What are some of your advice for people, you know, want to do 430 00:21:15,100 --> 00:21:17,400 public speaking? Not necessarily on stage, but 431 00:21:17,400 --> 00:21:20,100 also recording their first YouTube video because I'm sure 432 00:21:20,100 --> 00:21:23,200 that will verify some of us really, really bad. 433 00:21:23,200 --> 00:21:25,600 Including me, first time. I did it taste like, wow, what 434 00:21:25,600 --> 00:21:27,000 am I doing? What am I doing? 435 00:21:27,000 --> 00:21:29,600 Yeah, can you I share some of your tips around that. 436 00:21:29,700 --> 00:21:33,000 So in my past, I had the opportunity to take public 437 00:21:33,000 --> 00:21:34,900 speaking in college. Since I was a communication 438 00:21:34,900 --> 00:21:38,100 studies major, but I also spoke on stage a lot because I had 439 00:21:38,100 --> 00:21:40,000 done pageants. I was a dancer. 440 00:21:40,000 --> 00:21:41,700 I was very used to performing on stage. 441 00:21:41,700 --> 00:21:44,700 And then in my first position at Oracle, I presented many times 442 00:21:44,700 --> 00:21:47,600 and in front of customers, as well, as in front of our 443 00:21:47,600 --> 00:21:48,500 colleagues. Luckily. 444 00:21:48,500 --> 00:21:51,500 I've had someone of a predilection to speak in front 445 00:21:51,500 --> 00:21:53,500 of others and onstage. But by no means, was it a 446 00:21:53,508 --> 00:21:55,800 natural tendency or natural skill for me? 447 00:21:55,800 --> 00:21:57,900 And a lot of people come up to me and say, wow, you're so 448 00:21:58,100 --> 00:22:01,100 Actually, I public speaking, you seem very authentic on camera. 449 00:22:01,100 --> 00:22:04,700 But that is something that I've built over the last seven years, 450 00:22:04,700 --> 00:22:06,600 at least. And it really takes practice. 451 00:22:06,600 --> 00:22:08,400 I think that's the key thing to understand. 452 00:22:08,500 --> 00:22:12,100 I joined an office club called Toastmasters and I think they 453 00:22:12,100 --> 00:22:14,500 have that at many offices. Many companies around the world 454 00:22:14,500 --> 00:22:17,300 and it essentially got you in front of a group of colleagues. 455 00:22:17,300 --> 00:22:19,900 You come up with a topic every week and you present for our two 456 00:22:19,900 --> 00:22:22,100 to five minutes and there's somebody who sort of critiques 457 00:22:22,100 --> 00:22:24,400 you or counts. How many times you use um's 458 00:22:24,500 --> 00:22:26,800 while? I didn't love that method. 459 00:22:26,800 --> 00:22:28,900 It really does help if you Have it available to you. 460 00:22:28,908 --> 00:22:31,800 If you want to give it a try. I personally find it better to 461 00:22:31,800 --> 00:22:34,300 Simply get yourself in front of a camera or in front of a 462 00:22:34,308 --> 00:22:35,300 mirror. If you don't want to film 463 00:22:35,300 --> 00:22:39,600 yourself yet and just speak for 2 minutes on any topic and then 464 00:22:39,600 --> 00:22:41,700 watch yourself. If you did film yourself and 465 00:22:41,700 --> 00:22:45,300 critique yourself, if you're comfortable with it and or send 466 00:22:45,300 --> 00:22:47,900 it to your friends or colleagues who you know, are better. 467 00:22:47,900 --> 00:22:50,100 Public speakers? Because I think when you watch 468 00:22:50,100 --> 00:22:52,800 yourself, you'll start to see that you might be looking off to 469 00:22:52,800 --> 00:22:56,300 the side or you might be using your hands in a weird way, which 470 00:22:56,300 --> 00:22:57,800 I definitely did at the beginning. 471 00:22:57,800 --> 00:22:59,300 I Know what I wanted to do with my hands. 472 00:22:59,300 --> 00:23:01,500 So I kind of kept them. Like I was holding something and 473 00:23:01,500 --> 00:23:04,700 it just looked really awkward. So I had to practice that but 474 00:23:04,700 --> 00:23:08,200 that really helped and then just getting on stage in any form. 475 00:23:08,300 --> 00:23:11,400 Maybe you're a community leader. Maybe you want to stand in front 476 00:23:11,400 --> 00:23:13,900 of your family and give a presentation about your favorite 477 00:23:13,900 --> 00:23:15,600 Netflix show. It doesn't really matter what 478 00:23:15,600 --> 00:23:18,700 the format or the topic is just practice getting in front of 479 00:23:18,700 --> 00:23:21,200 people, like I did with pageantry and just do it as many 480 00:23:21,200 --> 00:23:24,500 times as possible. I also took a course a couple 481 00:23:24,500 --> 00:23:28,300 years ago called speechless that we have available at Google 482 00:23:28,300 --> 00:23:31,100 sometimes and they offer virtual classes as well. 483 00:23:31,100 --> 00:23:33,900 They're based in San Francisco. But the reason why I like them 484 00:23:33,900 --> 00:23:37,300 is that you get one-on-one time with someone who will get you 485 00:23:37,300 --> 00:23:40,200 thinking and on your feet, actually standing up, doing 486 00:23:40,200 --> 00:23:43,000 silly exercises, that feel ridiculous to you, but it's 487 00:23:43,000 --> 00:23:44,800 really just to get you out of your comfort zone. 488 00:23:44,800 --> 00:23:47,600 So you might do a lot of weird vocal exercises, where you're 489 00:23:47,600 --> 00:23:50,100 just doing weird sounds and shapes with your mouth or 490 00:23:50,100 --> 00:23:53,200 perhaps, you need a, make up an improvised story about a 491 00:23:53,200 --> 00:23:56,800 princess or a prince, and they want you to just navigate 492 00:23:56,800 --> 00:23:59,700 storytelling and be Very improvisational about it and 493 00:23:59,700 --> 00:24:01,500 that just helps you to think on your feet. 494 00:24:01,500 --> 00:24:04,500 Be very comfortable taking questions from the audience. 495 00:24:04,500 --> 00:24:08,000 And also learn how to tell a story from an authentic point of 496 00:24:08,008 --> 00:24:09,700 view people, appreciate authenticity. 497 00:24:09,700 --> 00:24:12,000 No matter what field you're in. So just practicing that 498 00:24:12,000 --> 00:24:15,600 authenticity and not feeling so much pressure to be or look like 499 00:24:15,600 --> 00:24:17,800 someone else or sound like someone else is key. 500 00:24:18,100 --> 00:24:20,700 Yeah. So I think the tips of studying 501 00:24:20,800 --> 00:24:23,600 maybe in front of mirror, another tip that I learned 502 00:24:23,600 --> 00:24:26,700 myself as well is that you can even record yourself using your 503 00:24:26,700 --> 00:24:30,400 handphone be like, Vlog Style, 2 minutes, 10 minutes, whatever 504 00:24:30,400 --> 00:24:31,800 length. You are comfortable with and 505 00:24:31,800 --> 00:24:33,500 just watch it for yourself, personally. 506 00:24:33,500 --> 00:24:36,900 Criticize yourself and also think of yourself and does it 507 00:24:36,900 --> 00:24:40,500 sound good, confident, natural authentic, things like that. 508 00:24:40,500 --> 00:24:42,300 And then once you are comfortable, maybe you recall. 509 00:24:42,300 --> 00:24:44,400 It daily. You can share it with you people 510 00:24:44,400 --> 00:24:47,300 and ask for feedback because I'm sure there are exactly but who 511 00:24:47,300 --> 00:24:49,900 can give a good critical feedback for you to improve on. 512 00:24:49,900 --> 00:24:53,000 And as you continue that practice I think over the time 513 00:24:53,000 --> 00:24:55,800 you get more natural, at least that's in my experience. 514 00:24:55,900 --> 00:24:57,900 And also another thing that I found from your share. 515 00:24:58,000 --> 00:24:59,300 As well. Is that, obviously, you will 516 00:24:59,300 --> 00:25:02,100 find some awkward things. Either your sound, either your 517 00:25:02,400 --> 00:25:06,000 arms or your silence and your hands waving for me, especially 518 00:25:06,000 --> 00:25:08,200 doing this podcast. I learned that I talk a lot 519 00:25:08,200 --> 00:25:11,100 like, you know, right. So when I edited the episode 520 00:25:11,100 --> 00:25:12,600 basically, I learned. Oh, okay. 521 00:25:12,600 --> 00:25:15,100 I tell all these things. Maybe I should improve next 522 00:25:15,100 --> 00:25:17,300 time. So I think that's also yeah, 523 00:25:17,300 --> 00:25:18,400 partly. Good learning. 524 00:25:18,400 --> 00:25:21,400 So everyone will have their own story, their own quirks. 525 00:25:21,500 --> 00:25:23,200 You just have to improve over the time. 526 00:25:23,300 --> 00:25:25,500 You mentioned something about storytelling. 527 00:25:25,500 --> 00:25:29,200 Why is it so important? For example, Tech influencer or 528 00:25:29,200 --> 00:25:32,700 your death Rel or even like in general and people just want to 529 00:25:32,700 --> 00:25:35,100 present stops. Why storytelling is very 530 00:25:35,100 --> 00:25:38,100 important. Storytelling is hugely important 531 00:25:38,100 --> 00:25:41,500 because think about the last piece of documentation, you read 532 00:25:41,500 --> 00:25:44,800 for a technical product. Let's say it was for machine 533 00:25:44,800 --> 00:25:47,400 learning products. And this is fine, because when 534 00:25:47,400 --> 00:25:49,900 people write documentation, they're thinking, let me be very 535 00:25:49,900 --> 00:25:51,700 clear about it. Let me write the step by step, 536 00:25:51,700 --> 00:25:55,600 but it's hard for you to read it and to end sometimes or let's 537 00:25:55,600 --> 00:25:58,500 say an entire white paper, unless it has a It's story 538 00:25:58,500 --> 00:26:01,600 unless it draws you in. And usually, in order to draw 539 00:26:01,600 --> 00:26:03,700 your audience in, not only doesn't need to Target the 540 00:26:03,700 --> 00:26:08,300 developer persona, but it needs to really Target his or her 541 00:26:08,300 --> 00:26:09,700 challenge that they're trying to solve. 542 00:26:09,700 --> 00:26:12,600 So in order to tell a good story and needs to be an extremely 543 00:26:12,600 --> 00:26:15,500 solution-oriented storyline. So you want to make sure that 544 00:26:15,500 --> 00:26:18,300 you present that in the beginning of your presentation 545 00:26:18,300 --> 00:26:20,300 or your video. What challenge are we trying to 546 00:26:20,300 --> 00:26:22,400 solve here? Why is it relevant to you? 547 00:26:22,400 --> 00:26:24,200 And then you dive into step-by-step? 548 00:26:24,300 --> 00:26:25,800 Okay. This is how this product solves 549 00:26:25,800 --> 00:26:27,800 it or how this methodology solves it. 550 00:26:27,900 --> 00:26:30,500 And then you can wrap up by kind of reflecting back on what you 551 00:26:30,500 --> 00:26:33,400 said and summarizing or providing any caveats or next 552 00:26:33,400 --> 00:26:35,100 steps. So that's sort of a high level 553 00:26:35,100 --> 00:26:37,800 overview of how you should structure your narratives. 554 00:26:38,200 --> 00:26:41,300 Is there a way for us to improve our storytelling capability. 555 00:26:41,300 --> 00:26:43,300 We all see, for example, TED Talks. 556 00:26:43,300 --> 00:26:46,400 Obviously, they are like one of the best speakers in the world 557 00:26:46,400 --> 00:26:49,000 about storytelling and presenting their message. 558 00:26:49,000 --> 00:26:52,200 Is there any place where we can learn how to do the storytelling 559 00:26:52,200 --> 00:26:54,400 better? You presented a good example 560 00:26:54,400 --> 00:26:56,700 right there. TED Talks are known for great 561 00:26:56,700 --> 00:26:59,000 presenters, and great. Stories instead of just 562 00:26:59,000 --> 00:27:01,200 consuming that information. The next time you watch a TED 563 00:27:01,200 --> 00:27:03,600 talk. Why don't you watch the Ted Talk 564 00:27:03,600 --> 00:27:07,200 and really absorb the structure in which they tell that entire 565 00:27:07,200 --> 00:27:10,200 story and start to take notes. What are they talking about in 566 00:27:10,200 --> 00:27:11,700 the beginning? Why is it captivating? 567 00:27:11,800 --> 00:27:13,900 And then what's the next thing? They start to move into and how 568 00:27:13,900 --> 00:27:15,200 do they conclude the presentation? 569 00:27:15,200 --> 00:27:17,400 What's the takeaway? And why was it so memorable? 570 00:27:17,400 --> 00:27:20,100 And try to really analyze it if you have time. 571 00:27:20,200 --> 00:27:22,400 The other thing I'll say is again, practice practice, 572 00:27:22,400 --> 00:27:26,000 practice, if you can start to change how you do a quick 573 00:27:26,000 --> 00:27:27,800 presentation at work. Why don't you start by? 574 00:27:27,900 --> 00:27:30,800 By presenting The Challenge and then going into the solution and 575 00:27:30,800 --> 00:27:33,600 then a conclusion, that's very clear and direct see if that 576 00:27:33,600 --> 00:27:36,800 actually bodes even better with your audience and encourage 577 00:27:36,800 --> 00:27:40,400 people to actually take action. So both practice and analyzer, 578 00:27:40,400 --> 00:27:43,400 study are two things that I do. I've actually taken a couple 579 00:27:43,400 --> 00:27:45,900 classes on it. I've taken master classes, which 580 00:27:45,900 --> 00:27:49,200 is a startup company, that has some online classes, given by 581 00:27:49,200 --> 00:27:52,100 some very prolific, writers and TV storytellers. 582 00:27:52,100 --> 00:27:55,000 So, I've taken some courses on that even Disney. 583 00:27:55,000 --> 00:27:58,400 I know they have a couple free courses online about how Friend 584 00:27:58,400 --> 00:28:01,200 Disney, tell stories, and I view great resource to follow as 585 00:28:01,200 --> 00:28:03,200 well. So given in this current 586 00:28:03,200 --> 00:28:06,600 situation of people being locked down, working from home. 587 00:28:06,700 --> 00:28:09,900 Are there any difference between presenting on stage and also 588 00:28:09,900 --> 00:28:11,600 virtual? Absolutely. 589 00:28:11,600 --> 00:28:16,100 I mean, I have focused so much on Virtual from the get-go in 590 00:28:16,100 --> 00:28:19,900 terms of doing scalable content, but occasionally, I'll go to 591 00:28:19,900 --> 00:28:21,800 conferences as well. In speaking person. 592 00:28:21,800 --> 00:28:24,800 The largest difference between in person and online is that you 593 00:28:24,800 --> 00:28:27,400 just don't have audience feedback and sometimes it's 594 00:28:27,400 --> 00:28:30,400 really Helpful for some people to not have someone in front of 595 00:28:30,400 --> 00:28:33,300 them and other times, somebody will get into the studio and 596 00:28:33,300 --> 00:28:35,000 they'll start to look at the camera. 597 00:28:35,000 --> 00:28:36,500 And they might have a teleprompter and they just 598 00:28:36,500 --> 00:28:38,800 completely freeze because it's a new environment. 599 00:28:38,800 --> 00:28:41,600 You don't have people nodding and smiling at you, and giving 600 00:28:41,600 --> 00:28:44,600 you non behavioral cues, which if you didn't know, account for 601 00:28:44,600 --> 00:28:48,400 70% of how people understand communication, so that's the 602 00:28:48,400 --> 00:28:51,100 biggest challenge, right? Is being comfortable by yourself 603 00:28:51,100 --> 00:28:53,600 in your own skin and presenting the information without 604 00:28:53,600 --> 00:28:56,700 necessarily receiving any feedback from your audience in 605 00:28:56,700 --> 00:29:00,200 order to overcome that, Then it's just I would say to fold 606 00:29:00,200 --> 00:29:03,000 doing it a bunch of times in front of a camera without anyone 607 00:29:03,000 --> 00:29:04,800 there. And then the second is being 608 00:29:04,800 --> 00:29:07,600 very comfortable in the material that you are presenting. 609 00:29:07,600 --> 00:29:09,700 You don't want to just show up on the day of and wing, it 610 00:29:09,700 --> 00:29:11,700 unless you're good at that. But the way that you're good at 611 00:29:11,700 --> 00:29:14,100 that is usually because, you know, the material very well and 612 00:29:14,100 --> 00:29:16,000 you know, the story, you know what you're about to present. 613 00:29:16,000 --> 00:29:18,900 So, just go into your meetings and create content, having 614 00:29:18,900 --> 00:29:21,300 practiced a few times knowing what you're about to say, the 615 00:29:21,300 --> 00:29:23,000 same goes for on stage presenting as well. 616 00:29:23,000 --> 00:29:24,700 Right? So I still remember the first 617 00:29:24,700 --> 00:29:27,400 time I did like a live webinar as well. 618 00:29:27,400 --> 00:29:28,000 You're right. Right. 619 00:29:28,000 --> 00:29:31,500 It feels we're having nobody. You just saw the cameraman 620 00:29:31,500 --> 00:29:34,600 giving you feedback and cute. Yeah, I felt weird to me and I 621 00:29:34,608 --> 00:29:38,000 think the key here again is just to try it out experiment and see 622 00:29:38,000 --> 00:29:40,700 which format that you like, but obviously these days we are 623 00:29:40,700 --> 00:29:43,400 forced to do virtual. So I guess we just need to get 624 00:29:43,400 --> 00:29:45,400 used to it. So I think from your website I 625 00:29:45,400 --> 00:29:49,400 saw as well that you are trying to be more prominent in terms of 626 00:29:49,400 --> 00:29:51,200 helping people about their career. 627 00:29:51,200 --> 00:29:54,400 For example, CV writing. What makes you interested in 628 00:29:54,400 --> 00:29:57,700 doing this. Yeah, so I decided to start my 629 00:29:57,700 --> 00:30:00,100 own. I've stayed because I wanted to 630 00:30:00,100 --> 00:30:03,400 create a brand online and I think that's crucial these days 631 00:30:03,400 --> 00:30:04,900 is to build a brand around yourself. 632 00:30:05,000 --> 00:30:07,800 I wanted to diversify my brand, be on Google as well. 633 00:30:08,100 --> 00:30:11,200 I wanted to be known as Stephanie Hwang, and not 634 00:30:11,200 --> 00:30:13,600 necessarily stuffy Wong from Google Cloud all the time 635 00:30:13,600 --> 00:30:16,200 because I think it's key, you want to make sure you always 636 00:30:16,200 --> 00:30:18,500 have opportunities in all places, right? 637 00:30:18,700 --> 00:30:20,000 No matter what happens in the world. 638 00:30:20,000 --> 00:30:23,600 So that's one way of creating sort of like high availability 639 00:30:23,600 --> 00:30:26,000 for yourself. In terms of creating your brand 640 00:30:26,000 --> 00:30:28,400 outside of just one thing, not putting all your Your eggs in 641 00:30:28,400 --> 00:30:30,200 one basket that Tech joke right there. 642 00:30:31,400 --> 00:30:35,100 So yeah, I did that. It's called stuff are Wang.com 643 00:30:35,100 --> 00:30:37,500 and you're right. I do provide Professional 644 00:30:37,500 --> 00:30:42,400 Services and coaching and CV or resume reviews and edits. 645 00:30:42,400 --> 00:30:44,900 And the reason why I started that is because I started 646 00:30:44,900 --> 00:30:46,900 helping my friends and family years ago, doing this and they 647 00:30:46,908 --> 00:30:48,600 said, well, you're actually pretty good at this and it's 648 00:30:48,600 --> 00:30:50,700 really helpful. You should eventually do it. 649 00:30:50,700 --> 00:30:53,900 And as, you know, with covid and the quarantine people have more 650 00:30:53,900 --> 00:30:56,500 time on their hands and it was a great side project for me to get 651 00:30:56,500 --> 00:30:58,900 that up and running and start. Offer it to people. 652 00:30:58,900 --> 00:31:01,000 I'm hoping to build out additional offerings in the 653 00:31:01,000 --> 00:31:04,000 future and then on top of that, I'm actually launching my 654 00:31:04,000 --> 00:31:06,100 YouTube channel called stuff. You should know. 655 00:31:06,500 --> 00:31:10,900 And that's also another effort to create an online brand for 656 00:31:10,900 --> 00:31:13,400 myself and really build an audience. 657 00:31:13,400 --> 00:31:17,000 When I say build an audience. It means you are becoming that 658 00:31:17,000 --> 00:31:18,500 influencer. And if you don't like that 659 00:31:18,500 --> 00:31:21,900 title, you are just becoming a content creator and forming an 660 00:31:21,900 --> 00:31:25,600 audience that follows you for your brand and what you offer 661 00:31:25,600 --> 00:31:27,700 them. So, on that channel, I'll be 662 00:31:27,800 --> 00:31:31,100 Reading content around career lifestyle productivity, 663 00:31:31,100 --> 00:31:33,600 technology, trying to keep it targeted as much as possible. 664 00:31:33,600 --> 00:31:36,200 But so far, it's primarily around things. 665 00:31:36,200 --> 00:31:37,600 Like what we just talked about today. 666 00:31:37,800 --> 00:31:40,800 I like your joke about how you availability for us. 667 00:31:40,800 --> 00:31:45,300 Obviously having brand online. I think it's also something that 668 00:31:45,300 --> 00:31:47,800 all of us should think about what kind of brand you should 669 00:31:47,800 --> 00:31:49,800 have online. Either, maybe even in your 670 00:31:49,808 --> 00:31:52,100 social media. What do you want people to know 671 00:31:52,100 --> 00:31:53,500 you about? And I think, yeah, we have 672 00:31:53,500 --> 00:31:56,400 talked about so many channels and opportunities where you can 673 00:31:56,400 --> 00:31:58,900 do that. So in terms of, CV writing if 674 00:31:58,900 --> 00:32:01,600 you can share maybe some high General tips. 675 00:32:01,600 --> 00:32:04,800 Some of the key things that we should think about when we write 676 00:32:04,800 --> 00:32:06,100 us EV. Yeah. 677 00:32:06,100 --> 00:32:09,400 So I think that your resume should tell a story and that's 678 00:32:09,400 --> 00:32:11,900 very on brand, with what I've been talking about today because 679 00:32:11,900 --> 00:32:13,700 I've been talking about storytelling a lot today, but 680 00:32:13,700 --> 00:32:16,400 really everything does follow that framework. 681 00:32:16,400 --> 00:32:19,200 You should tell your own story. You should make sure that your 682 00:32:19,200 --> 00:32:23,000 resume represents your story. Well, and one of the things that 683 00:32:23,000 --> 00:32:26,200 you can do is not just put everything on your resume, but 684 00:32:26,200 --> 00:32:29,200 take a look at the positions that you You are aiming for or 685 00:32:29,200 --> 00:32:31,800 positions that you eventually want to reach later down the 686 00:32:31,800 --> 00:32:33,800 road. What in your resume will tell 687 00:32:33,800 --> 00:32:36,800 that story and gear you towards that direction. 688 00:32:36,800 --> 00:32:39,300 Make sure that you are putting yourself in a good position to 689 00:32:39,300 --> 00:32:42,000 get there. So the other thing I'll say is I 690 00:32:42,000 --> 00:32:45,200 really encourage people to unapologetically take ownership 691 00:32:45,200 --> 00:32:47,700 in their greatest achievements. So instead of just simply 692 00:32:47,700 --> 00:32:50,700 describing your job function and what you do at that company, you 693 00:32:50,700 --> 00:32:55,100 should really be describing your biggest impact and how you were 694 00:32:55,100 --> 00:32:57,700 integral to making that happen. And one way to do that. 695 00:32:57,800 --> 00:33:02,300 Effectively is to replace all your duties with measurable 696 00:33:02,300 --> 00:33:04,500 impact. So include some quantifiable 697 00:33:04,500 --> 00:33:07,100 metric for perhaps because it's easier for people to wrap their 698 00:33:07,100 --> 00:33:10,300 heads around that you want to be very specific about why how you 699 00:33:10,300 --> 00:33:14,400 did that and what the measurable outcome was in summary duties. 700 00:33:14,400 --> 00:33:18,300 Tell accomplishments so nice. So for those of you who would 701 00:33:18,300 --> 00:33:21,600 like to have the coaching in terms of CV writing definitely 702 00:33:21,600 --> 00:33:24,800 contact Stephanie and then you probably get more useful tips 703 00:33:24,800 --> 00:33:28,700 and even practical examples on how to To improve your CV. 704 00:33:28,700 --> 00:33:31,400 So, another thing that I want to talk about with you is about 705 00:33:31,400 --> 00:33:34,300 women in technology. Obviously, we have still this 706 00:33:34,300 --> 00:33:37,400 challenge in terms of number of women that is doing technology. 707 00:33:37,400 --> 00:33:41,500 So what are some of your message in terms of empowering women, to 708 00:33:41,500 --> 00:33:43,900 give it a try, to be more in technology? 709 00:33:43,900 --> 00:33:48,700 Me being a woman in Tech has been a very exciting Journey for 710 00:33:48,700 --> 00:33:50,200 me. I didn't even think that I would 711 00:33:50,208 --> 00:33:52,100 be in technology when I was in school. 712 00:33:52,100 --> 00:33:55,700 So for anyone that's even thinking about it as a 713 00:33:55,700 --> 00:33:59,000 possibility or you want to Pivot your Into technology or perhaps 714 00:33:59,000 --> 00:34:01,200 you're even in Tech and you just want to grow and continue to 715 00:34:01,200 --> 00:34:03,400 push yourself or maybe you're thinking of leaving Tech. 716 00:34:03,400 --> 00:34:07,100 I would really ask you to think about the impact that you can 717 00:34:07,100 --> 00:34:09,500 make in this male-dominated industry. 718 00:34:09,600 --> 00:34:12,600 And just understand that where I came from was very different 719 00:34:12,600 --> 00:34:15,900 than most people in technology. So don't use your background or 720 00:34:15,900 --> 00:34:18,500 your existing skill sets to, determine whether or not you are 721 00:34:18,500 --> 00:34:22,300 qualified for a position in Tech, use your drive, your 722 00:34:22,300 --> 00:34:25,500 mentality, your work ethic, and how much you've grown in the 723 00:34:25,500 --> 00:34:28,600 past couple years to push you to where you need to get in the 724 00:34:28,600 --> 00:34:31,300 future. I suffer still from imposter 725 00:34:31,300 --> 00:34:33,800 syndrome and I specially experience that when I first 726 00:34:33,800 --> 00:34:38,100 joined Google, but I now today use that as motivation rather 727 00:34:38,100 --> 00:34:40,500 than reasons to be self-conscious or lose 728 00:34:40,500 --> 00:34:43,100 self-esteem. Now, I funnel that into 729 00:34:43,100 --> 00:34:45,900 motivation to grow and the other thing is that if you surround 730 00:34:45,900 --> 00:34:50,000 yourself by people who are achieving something inspiring or 731 00:34:50,000 --> 00:34:54,300 a role model that you look up to use that, as additional drive to 732 00:34:54,300 --> 00:34:57,600 continue to push yourself in this field, because we really do 733 00:34:57,600 --> 00:35:00,700 need Need more women in, not just Tech, but in leadership 734 00:35:00,700 --> 00:35:04,400 roles in Tech and I believe that we need both men and women to 735 00:35:04,400 --> 00:35:06,800 continue to support one. Another as others have supported 736 00:35:06,800 --> 00:35:09,000 my work. If you see another woman's work, 737 00:35:09,000 --> 00:35:11,900 who should be noticed, send a tweet. 738 00:35:11,900 --> 00:35:13,400 Share. It, send an email. 739 00:35:13,400 --> 00:35:15,200 Give positive feedback and recognition. 740 00:35:15,200 --> 00:35:18,300 I've talked a lot today about how to promote yourself online 741 00:35:18,300 --> 00:35:21,300 and it's very important that we do that for other women in Tech 742 00:35:21,300 --> 00:35:23,600 because you wouldn't believe the power of social networking. 743 00:35:23,700 --> 00:35:26,000 Whether that's internal at a company or externally, that's 744 00:35:26,000 --> 00:35:28,700 how we make progress and get with women in leadership 745 00:35:28,700 --> 00:35:30,500 positions. The second thing I'll say is 746 00:35:30,500 --> 00:35:34,400 that I think managers and other Executives have to show visible 747 00:35:34,400 --> 00:35:36,800 commitment to ensuring that there's Equity diversity and 748 00:35:36,800 --> 00:35:39,700 inclusion of women and people of color in their team's I'm 749 00:35:39,700 --> 00:35:42,100 grateful. I've had incredible managers who 750 00:35:42,200 --> 00:35:45,200 make it a point to hire many women on my teams from all 751 00:35:45,200 --> 00:35:47,400 different backgrounds. Even myself who came from a very 752 00:35:47,400 --> 00:35:49,600 different background. They gave me a chance, and I was 753 00:35:49,600 --> 00:35:52,200 able to succeed in this field when I didn't have the 754 00:35:52,200 --> 00:35:54,900 confidence to in the beginning compared to where I am now, so I 755 00:35:54,900 --> 00:35:57,500 really do think opportunity and recognition for women need to 756 00:35:57,500 --> 00:35:59,500 come. All levels in technology. 757 00:35:59,900 --> 00:36:02,800 Thanks for sharing that. So regarding imposter syndrome. 758 00:36:02,800 --> 00:36:05,300 I think this keyword is definitely mentioned a lot of 759 00:36:05,300 --> 00:36:08,100 times in a tech industry. First of all, for those of us 760 00:36:08,100 --> 00:36:09,800 who are not familiar with this term. 761 00:36:09,800 --> 00:36:12,000 Maybe you can explain what is imposter syndrome. 762 00:36:12,100 --> 00:36:15,000 How do you know if you have it and like you gave some tips 763 00:36:15,000 --> 00:36:18,200 already, but is there anything else that we can do to improve 764 00:36:18,200 --> 00:36:21,200 not being too much influenced by this imposter syndrome? 765 00:36:21,500 --> 00:36:26,200 So imposter syndrome is this mentality or belief in which you 766 00:36:26,200 --> 00:36:29,200 doubt your accomplishments? For your talent because you have 767 00:36:29,200 --> 00:36:32,700 this internalized fear of being exposed as an impostor or a 768 00:36:32,700 --> 00:36:34,300 fraud. You know, you think to yourself. 769 00:36:34,300 --> 00:36:36,700 How did I get here? I'm not as smart as the people 770 00:36:36,700 --> 00:36:38,700 around me. I'm not as talented as some. 771 00:36:38,700 --> 00:36:41,200 I don't belong here. I absolutely felt that when I 772 00:36:41,207 --> 00:36:44,400 first joined Google and at different points in my career, 773 00:36:44,400 --> 00:36:47,100 when I switch teams, for example, so I'm sure many people 774 00:36:47,100 --> 00:36:50,300 face that it's probably has to do with both self-confidence and 775 00:36:50,300 --> 00:36:52,600 just being in a very challenging or highly productive 776 00:36:52,600 --> 00:36:55,300 environment, and maybe you have a lot of great, talented people 777 00:36:55,300 --> 00:36:57,600 around you and that's fine, but just think to yourself. 778 00:36:57,900 --> 00:37:00,800 Okay, I see them as highly talented and they bring a lot to 779 00:37:00,800 --> 00:37:03,600 the table in that skill or that expertise may be there. 780 00:37:03,600 --> 00:37:06,400 A machine learning expert for example, but what do you bring 781 00:37:06,400 --> 00:37:08,800 to the table? I had to get used to telling 782 00:37:08,800 --> 00:37:11,500 myself that I am different from the engineers around me. 783 00:37:11,500 --> 00:37:12,600 I'm different from the developers. 784 00:37:12,600 --> 00:37:14,900 I don't have that background. But what do I bring to the 785 00:37:14,900 --> 00:37:15,500 table? Okay. 786 00:37:15,500 --> 00:37:18,000 Well, let me think I bring storytelling. 787 00:37:18,000 --> 00:37:21,300 I bring public speaking and enthusiasm around that and it 788 00:37:21,300 --> 00:37:24,400 took a long time for me to get used to believing that in 789 00:37:24,400 --> 00:37:26,000 myself. And it took a long time for, I 790 00:37:26,000 --> 00:37:27,600 think other people to believe that in. 791 00:37:27,700 --> 00:37:29,900 Me. But time is everything just 792 00:37:29,900 --> 00:37:33,200 trust that in six months after you join a team that doubt will 793 00:37:33,200 --> 00:37:36,900 turn into experience and it will then turn into confidence. 794 00:37:37,000 --> 00:37:40,900 It just takes time and practice to get used to any change and 795 00:37:40,900 --> 00:37:43,100 adapt to a new skill or environment. 796 00:37:43,100 --> 00:37:46,000 Yeah, so I think for me as well, I definitely have impostor 797 00:37:46,000 --> 00:37:48,900 syndrome just like what you mentioned everyone has it. 798 00:37:48,900 --> 00:37:52,200 So I think the key for me at least is that you have to be 799 00:37:52,200 --> 00:37:55,600 self-aware first about that. The next key action is actually 800 00:37:55,600 --> 00:37:59,000 to acknowledge that and also obviously To think about other 801 00:37:59,000 --> 00:38:01,400 things that you're good at just like what Stephanie mentioned, 802 00:38:01,400 --> 00:38:03,100 right? If you focus on what you're good 803 00:38:03,100 --> 00:38:06,200 at, and maybe you would not have that kind of fear and try to 804 00:38:06,200 --> 00:38:09,100 bring that to the table. You that your work is at your 805 00:38:09,100 --> 00:38:12,300 school or wherever you are, try to focus on that and maybe 806 00:38:12,300 --> 00:38:14,700 expand a little bit. If let's say you want to have 807 00:38:14,700 --> 00:38:17,400 other skills that you want to excel as well. 808 00:38:17,400 --> 00:38:20,500 So over the time probably this impostor syndrome won't be, is 809 00:38:20,500 --> 00:38:22,700 such a massive things that you should worry about. 810 00:38:22,800 --> 00:38:25,200 But having said that we all have it from time to time, but you 811 00:38:25,200 --> 00:38:28,900 won't just disappear unless you really train yourself to be very 812 00:38:28,900 --> 00:38:31,400 confident and motivated and driven. 813 00:38:31,400 --> 00:38:33,400 So regarding women in technology. 814 00:38:33,400 --> 00:38:36,900 Why do you think there are some of these challenges since a long 815 00:38:36,900 --> 00:38:38,200 time ago? Even up till? 816 00:38:38,200 --> 00:38:40,100 Now? Why are these women are not 817 00:38:40,100 --> 00:38:42,000 prominent? What are some of the barriers 818 00:38:42,000 --> 00:38:43,200 actually? Yeah. 819 00:38:43,200 --> 00:38:46,800 I mean, I think that there is a long history of systemic issues 820 00:38:46,800 --> 00:38:50,300 that exist that create this sort of glass ceiling for women in 821 00:38:50,300 --> 00:38:53,300 technology, as you know, computer science and technology 822 00:38:53,300 --> 00:38:56,200 has primarily been male-dominated because the 823 00:38:56,200 --> 00:39:00,100 developer community and Communities have been usually 824 00:39:00,100 --> 00:39:03,500 focused on male programmers, engineers and computer science 825 00:39:03,500 --> 00:39:05,300 from the beginning. But also even outside of 826 00:39:05,300 --> 00:39:10,100 Technology seeing male CEOs and c-level, Executives has always 827 00:39:10,100 --> 00:39:13,000 been prevalent and that's something that most Industries 828 00:39:13,000 --> 00:39:16,200 face. So that coupled with technology 829 00:39:16,200 --> 00:39:19,000 being male dominated from the engineering perspective, create 830 00:39:19,000 --> 00:39:23,200 a more difficult path for women to become higher-ups in the 831 00:39:23,200 --> 00:39:26,200 company. I also believe that at times as 832 00:39:26,200 --> 00:39:30,300 I said earlier women, Men need to recognize women's work and 833 00:39:30,300 --> 00:39:33,400 really give them more opportunities to take stretch 834 00:39:33,400 --> 00:39:36,200 goals. I think that women often times 835 00:39:36,200 --> 00:39:40,200 do face impostor syndrome. They don't apply for the 836 00:39:40,200 --> 00:39:43,700 positions that they deserve because they usually apply to 837 00:39:43,700 --> 00:39:45,800 ones that they know they're qualified for. 838 00:39:45,800 --> 00:39:47,600 Whereas. I think I've seen a stat that 839 00:39:47,600 --> 00:39:50,900 men more times apply to positions that they might be 840 00:39:50,900 --> 00:39:53,400 under qualified for, but they're willing to take the chance 841 00:39:53,400 --> 00:39:55,300 they're willing to take that risk. 842 00:39:55,300 --> 00:39:57,500 So I also think it's important for women. 843 00:39:57,700 --> 00:40:01,700 You really understand that they can go for those stretch goals. 844 00:40:01,700 --> 00:40:03,300 They can really go for those positions. 845 00:40:03,300 --> 00:40:05,100 Even if you don't think you're qualified just yet. 846 00:40:05,100 --> 00:40:07,100 If you think, I still need another year before I should go 847 00:40:07,100 --> 00:40:09,100 for that promotion, you know, maybe I don't have as much 848 00:40:09,100 --> 00:40:11,800 experience as that guy and on my team who's going for that 849 00:40:11,800 --> 00:40:14,700 leadership position on my team or project manager for this new 850 00:40:14,700 --> 00:40:17,200 project that we're focusing on really push yourself to do that 851 00:40:17,200 --> 00:40:19,400 because I think it's the responsibility of everybody else 852 00:40:19,400 --> 00:40:21,500 to support women in technology. But I also think there's a 853 00:40:21,508 --> 00:40:25,100 mentality shift that needs to happen in order for women to 854 00:40:25,100 --> 00:40:27,600 push themselves and continue to persevere. 855 00:40:27,700 --> 00:40:29,200 Fear through these glass ceilings. 856 00:40:29,400 --> 00:40:32,100 Thanks for sharing that. So before we wrap up, I would 857 00:40:32,100 --> 00:40:35,500 like to ask you. Is there any great experience 858 00:40:35,500 --> 00:40:39,100 that you have found so far when you are doing your death roll, 859 00:40:39,100 --> 00:40:43,000 roll, any things that stand out, interesting unique, weird or 860 00:40:43,000 --> 00:40:47,000 whatever that is. Yeah, so I had such an 861 00:40:47,000 --> 00:40:51,300 incredible experience recently when I was able to start and 862 00:40:51,300 --> 00:40:54,600 land a project where I got to visit a Google cloud data 863 00:40:54,600 --> 00:40:57,600 center, and create a video around it and I'm very grateful. 864 00:40:57,700 --> 00:41:00,800 Full for that experience because less than 1% of googlers gets, 865 00:41:00,800 --> 00:41:04,500 you visit a Data Center and see its interior and it all started 866 00:41:04,500 --> 00:41:08,100 because I have incredible team of supporters at Google that 867 00:41:08,100 --> 00:41:10,800 were able to give me an opportunity to reach out to the 868 00:41:10,800 --> 00:41:14,000 right people and create a story that had never been told about 869 00:41:14,000 --> 00:41:15,900 how we handle security at Google. 870 00:41:15,900 --> 00:41:19,400 We actually have six layers of Defense at Google and a lot of 871 00:41:19,400 --> 00:41:21,800 people are like, oh, this is like Ocean's, Eleven trying to 872 00:41:21,800 --> 00:41:23,300 break into somewhere. And, you know, it's like very 873 00:41:23,300 --> 00:41:26,700 Mission Impossible style. So it was really cool, being 874 00:41:26,700 --> 00:41:29,300 able to go in and see, See, get my eyes skin. 875 00:41:29,300 --> 00:41:32,200 Do biometric scanning, go through a circle lock, see what 876 00:41:32,200 --> 00:41:35,100 the data, center floor looked like, and sounded like and see a 877 00:41:35,100 --> 00:41:36,900 lot of hard drives getting shredded. 878 00:41:36,900 --> 00:41:38,900 So that was just an incredible experience. 879 00:41:38,900 --> 00:41:41,000 And then on top of that, I was able to work with an amazing 880 00:41:41,000 --> 00:41:43,800 camera crew with drones very high production. 881 00:41:43,800 --> 00:41:46,400 So, you know, that was it. Perfect example of me, being 882 00:41:46,400 --> 00:41:49,000 able to get that dream experience of working, both in 883 00:41:49,000 --> 00:41:51,900 production at that level and then also really cool technology 884 00:41:51,900 --> 00:41:53,600 and the physicality of Technology. 885 00:41:53,700 --> 00:41:55,600 Everything in the cloud isn't really in the cloud. 886 00:41:55,600 --> 00:41:58,500 It leads back to a Data Center. And so Hope is to one day, 887 00:41:58,500 --> 00:42:01,400 create more videos around the physicality of the internet and 888 00:42:01,400 --> 00:42:04,900 where your data resides and how it actually moves around the 889 00:42:04,900 --> 00:42:06,200 world. Nice. 890 00:42:06,300 --> 00:42:08,000 Yeah, so I saw that video as well. 891 00:42:08,000 --> 00:42:09,500 You being in the Google data center. 892 00:42:09,600 --> 00:42:12,300 I think for those listeners who are interested to find out, do 893 00:42:12,300 --> 00:42:15,000 check out on the YouTube and you'll find Stephanie exploring 894 00:42:15,000 --> 00:42:18,300 Google cloud data center going through all these six layers of 895 00:42:18,300 --> 00:42:19,500 security. Lastly. 896 00:42:19,500 --> 00:42:23,000 I would ask you this question in which I always ask my guests in 897 00:42:23,000 --> 00:42:25,100 the episode. So Stephanie, can you share with 898 00:42:25,100 --> 00:42:27,400 us? What are your three technical? 899 00:42:27,600 --> 00:42:30,300 Leadership wisdom that you want to share with the audience. 900 00:42:30,600 --> 00:42:33,200 Sure. So, the first one that I will 901 00:42:33,200 --> 00:42:37,000 leave with everyone is luck, is where preparation meets 902 00:42:37,000 --> 00:42:39,500 opportunity. As I've told through my stories. 903 00:42:39,500 --> 00:42:44,100 I had a very convoluted route to where I am today, but a lot of 904 00:42:44,100 --> 00:42:45,500 people are like, wow, how did you do that? 905 00:42:45,500 --> 00:42:48,200 It seems like you've had a lot of luck and I say that to myself 906 00:42:48,200 --> 00:42:50,500 all the time, like, I've had luck to get to the position. 907 00:42:50,500 --> 00:42:53,700 I'm in, but I really do think that preparation needs to meet 908 00:42:53,700 --> 00:42:55,300 opportunity in order to give you that. 909 00:42:55,300 --> 00:42:57,500 Look remain, curious. Let your intuition. 910 00:42:57,700 --> 00:43:00,600 Tell you, when opportunity doesn't feel right and when you 911 00:43:00,607 --> 00:43:03,400 think you should learn more in a certain skill and just say yes 912 00:43:03,400 --> 00:43:06,300 to challenges that allow you to get out of your comfort zone, 913 00:43:06,300 --> 00:43:08,800 and challenge you continue to say yes, to those opportunities 914 00:43:08,800 --> 00:43:10,500 to speak, at the next largest conference. 915 00:43:10,500 --> 00:43:12,100 For example, just get yourself out there. 916 00:43:12,100 --> 00:43:15,000 The second one is that for public speaking practice makes 917 00:43:15,000 --> 00:43:16,600 perfect. Public, speaking doesn't come 918 00:43:16,600 --> 00:43:18,800 natural to most people. It's a crucial skill in today's 919 00:43:18,800 --> 00:43:20,300 market. And in order to build your 920 00:43:20,300 --> 00:43:23,000 brand, definitely focus on practicing public speaking. 921 00:43:23,000 --> 00:43:25,700 And then lastly, as I've mentioned before content is 922 00:43:25,700 --> 00:43:27,900 Queen. It's similar to the Ray's 923 00:43:27,900 --> 00:43:30,000 location location, location. In this sense. 924 00:43:30,000 --> 00:43:33,400 It's content content. Content, expand your brand, this 925 00:43:33,400 --> 00:43:36,800 way and doors will open for you. If I've learned anything as a 926 00:43:36,808 --> 00:43:38,500 content creator over the last couple years. 927 00:43:38,500 --> 00:43:41,400 It's that consistency quality and value matter. 928 00:43:41,400 --> 00:43:44,100 That's the trifecta. Thank you for your wisdom. 929 00:43:44,100 --> 00:43:47,600 Definitely, those of us who want to build online personal brand, 930 00:43:47,600 --> 00:43:49,900 for example, or also producing content. 931 00:43:49,900 --> 00:43:51,600 Stephanie. Thank you again, for being part 932 00:43:51,600 --> 00:43:54,000 of the show today. There's so many things that I 933 00:43:54,000 --> 00:43:57,100 personally also learn myself trying to build my personal 934 00:43:57,100 --> 00:43:59,600 brand. Stephanie, thanks so much, and 935 00:43:59,600 --> 00:44:01,900 hope to see you again one day. Thank you so much Henry. 936 00:44:01,900 --> 00:44:03,200 It was great talking to you today. 937 00:44:04,100 --> 00:44:07,800 Thank you so much for listening. I hope you enjoyed this episode, 938 00:44:08,000 --> 00:44:10,800 share it with your friends and colleagues who would benefit 939 00:44:10,800 --> 00:44:14,700 from listening to this episode. And if you liking this podcast, 940 00:44:14,900 --> 00:44:17,300 I would love if you subscribe and leave me your valuable 941 00:44:17,300 --> 00:44:20,200 review and feedback. It really helps me a lot. 942 00:44:20,600 --> 00:44:23,200 Stay tuned for the next technology, you know, episode. 943 00:44:23,300 --> 00:44:25,000 And until then. Goodbye.