Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Angie Chang: With us today, we have Joy Ebertz, who’s a principal software engineer at Split. She leads the backend team from a technical perspective and prior to Split worked at Box for years. In addition to designing software and writing code and running, she writes a blog, which I’ve really enjoyed reading over the years. I’m really excited to welcome Joy here today. Welcome, Joy!

Joy Ebertz: Thank you Angie. Awesome.I’m excited to be here. Today we’re gonna be talking about feature flags. And I know Angie just gave me an amazing introduction, but I’m gonna go through this real fast again. First of all, who am I? As she mentioned, I write a blog on Medium. I like to read, especially fantasy. I like to bake, especially pies, and I like to run especially really long distances on trails. But none of that is why you’re here today.

Joy Ebertz: Who am I professionally? On my blog, I write about running, but I also write a lot about diversity, equity, and inclusion. I write about career topics and I write about tech technical topics. Over the years I’ve worked at a few different places. I was at Microsoft, a really tiny startup. I was at Box and I’m currently at a company called Split.

Joy Ebertz: I’m primarily a backend engineer these days I mostly work in Java. I’ve spent a lot of time splitting monoliths into microservices and thinking about microservice architecture. I’ve also spent a bunch of time over the years working on REST API design and thinking about APIs in general. And I’ve also worked at both Box and Split on authorization and authorization frameworks. And why any of that’s relevant to the topic of feature flags is that Split happens to be a feature flag company. We might happen to think about feature flags a little bit more than the average user out there.

Joy Ebertz: Today I’m gonna be going through just a brief introduction of what are feature flags and then I’m gonna talk through some of the typical use cases we’re gonna go through and then we’re gonna go through some of the more unusual ones. We’re gonna talk about removing dead code load and stress testing, evaluating tech costs, parity testing, and logging.

Joy Ebertz: First of all, what are feature flags? There’s a few other terms you might have heard floating around feature toggles, feature flips, feature switches, conditional feature. And for some really odd reason we happen to call them splits, I don’t know, but basically all of these are different terms to indicate something that is con code, like code branches that’s controlled biographical graphical user interface.

Joy Ebertz: For example, it’s gonna look something like this where you have an if statement that basically just says if the split is turned on, or sorry, if the feature flag is turned on, then you’re gonna do whatever’s in that first block of code, and if not, then you’re gonna do something else. Then on the UI side, you might be able to set it up so that you know, your QA testers get the on treatment, or maybe everybody located in Boston also gets that on treatment. And then everyone else gets the off treatment. And this basically lines up so that then your QA testers and your folks in Boston get routed to that first block of code while everyone else gets that second block of code.

Joy Ebertz: What are some of the typical use cases around these? The biggest one is releasing features. I’m gonna get a little bit more into depth than that one in a second. But the next one is production testing. By this, I just mean you’re able to turn on a new feature or a new fix or something in production for only, like I mentioned before, your QA testers or maybe only the team that’s working on it so they’re able to actually test things on your production environment with your production hardware without impacting all of your users at once A/B/C testing. Being able to test out multiple versions of a website to see what resonates best with your users. And I have the C in there instead of just A/B testing, because sometimes you might have more than two different variations, right?

Joy Ebertz: Like maybe you’re testing a red banner versus a blue banner versus a green banner. That might be an option that you’re doing custom packages. This is basically just being able to give different feature sets to different sets of users. You might have a free set of users and you might have a paid set of users and maybe even have like a business package or an enterprise package. And each of these sets of users have a different feature set that they can see. This is one way to control which users see which features temporary UI customization.

Joy Ebertz: This is one of our, our more interesting features. Basically it’s the ability to actually change things in your UI without changing codes. How this might be used is if, let’s say there’s a storm in Boston, then maybe your customer success folks can update the feature flag to put a banner on the top of the screen that just says expect some delays, thank you for your patience or something, right? And you can then target that to only show up for your customers who are located in Boston. And then I mentioned I was gonna talk a little bit more about releasing features. What are some of the things there?

Joy Ebertz: The first piece is separating deploy from release. Deploy is like the, when you’re actually shipping your code to the cloud, right? It’s when you actually put that code on the servers versus release is when customers start seeing a and how this is useful is because these are both risky, right? And so having them together, it’s really hard to tell which part went wrong if something does go wrong. But by separating them, it makes them both lower risk and it means that you’re able to figure out and quickly roll back from either one if something goes wrong.

Joy Ebertz: The next one is canary or ramped release. Instead of just turning on a feature for all of your users at once, you can slowly roll it out. You can say, first let’s try with the freezer user free users, or maybe we try with 1% of traffic, or maybe we try with a few companies who have agreed to beta test something and then you can get feedback and check your metrics and so on and so forth. And if things look good, then you can increase that until you roll it out to everyone. And I sort of alluded to this already, but it’s also a big off switch. So something does go wrong, it’s very easy to turn that back off and roll back to a known good state. Okay? That’s basic feature flag use cases that are fairly common throughout the industry.

Joy Ebertz: But what are some of the more unusual or advanced use cases? The first one I’m gonna talk about here is using them to remove dead code. First of all, why is your code dead? You might have a method that’s no longer referenced, and I’m sure a few of you’re gonna say, oh, but my IDE can tell me this, right? But maybe you have an endpoint that’s never called, so it’s hard to tell from an IDE with an the actual endpoint, you’re like, your API endpoint is called or not, or maybe you have a parameter input parameter into a method that just never has certain values. Like an if block never gets hit because it just never has that value and these can all stack on top of each other. It might be the case that you have a method that looks like it’s called with certain parameter values, but maybe it never has some of those because the endpoint that would’ve passed those is never called, or maybe the method itself was never called because it’s called from do endpoints, right?

Joy Ebertz: it becomes very, very difficult to tell which pieces of your code are actually in use. One of the obvious ways to do to like try to solve this is to just pepper your code with log statements, right? We at Box, one of our developers actually came up with a lot of this Dave Shepper, but he had a tool that would just go in every branching statement. You add a log line essentially, and it’s just saying this code is not dead. And you have a unique identifier on there so that you can find which actual line was hit later when you’re looking through your logs. The problem with this is since most of us are in software, we know logs are expensive. <Laugh>, especially if you’re peppering all of your code, this is gonna get very, very expensive, right?

Joy Ebertz: One way to solve this is you can wrap the whole thing in a feature flag, right? And then you can just maybe only turn this on for 1% of traffic, right? And then maybe even only leave that on for, let’s say five seconds. And then you can go back to your logs and check which lines of your code were actually hit. And then when you go in there, you can then start sorry. And then you can remove those log lines from your code and then you roll it out to a little bit more and then remove more log lines and eventually any of those log lines that are still in your code are probably not in use anymore. And so you can roll it out to a hundred percent and leave it there as long as it makes you comfortable. For most of the features that we have, this is, you know, probably a couple of weeks maybe a month at most.

Joy Ebertz: When I was at Box, at one point we were working on some authorization code and looking at removing some of that and we were permissions, people get touchy about permission, so we actually left that one on for, I wanna say a year because we weren’t quite comfortable removing it until then. But anyway, once you’re comfortable, then at that point you can assume any of those log lines that are still not showing up in your logs are not being hit anywhere and you can go ahead and remove that entire code block.

Joy Ebertz: Okay, next, use case load and stress testing. I know a lot of, you’re probably familiar with tools such as Gatling or JMeter, and these tools are great. They allow you to basically write a set of test cases and run them repeatedly at like higher and higher rates against your systems, and this is a great way to tell or to load and stress tests. sorry, back up a second.

Joy Ebertz: Load testing is making sure that a new system can handle expected load. Stress testing is trying to figure out the point where that new system falls over. As you might be able to see by sending a bunch of test requests to a system, you can do both of these things. However, the big problem with those is you’re relying on a set of test cases written by a developer and it usually doesn’t reflect actual traffic patterns that you might be receiving through your site. Even if it does, you’re probably gonna have to spend a lot of time in order to get those realistic traffic patterns. One thing you can do instead is actually mirror your traffic and that basically means that you send your traffic like normal to your existing system and at the same time you send an asynchronous request over to the new system.

Joy Ebertz: And what’s nice here is that as I’ve kind of indicated with the arrow, you can start with that ramping like we talked about before. Initially you can just send 1% of your traffic to the new system and then slowly ramp it up. And what’s nice about this is then if your system new system does fall over, it’s much easier to see exactly at what point it fall over. And at least in my experience, it’s often much easier to debug what went wrong if you’re right at that inflection point rather than way over it. A lot of times when you’re way over, everything’s blowing up, everything’s falling over and it’s really hard to tell what the initial problem was. This allows you to find that exact point when things went wrong. And then stress testing. If you wanna go beyond your current traffic patterns, you might be able to start or you can start sending the same request multiple times to the new system.

Joy Ebertz: Maybe you sent it once and then you wait five seconds and you send it again. And this will allow you to send more traffic to the new system than you’re actually accepting your old system. And I fully admit that this is not quite realistic either, since you’re like, resending requests isn’t something that happens all the time with traffic, but it should still hopefully help with a slightly more realistic traffic pattern than you’re gonna be able to come up with in tests without a lot of time spent on those tests. Okay, that was load and stress testing. Next we’re gonna talk about evaluating tech costs. As you might have predicted, this is a very similar setup to that last one. The key for this one though is again, with the mirrored traffic, instead we’re going to just turn it on for a very specific length of time.

Joy Ebertz: Depending on what your traffic patterns normally look like, you’re just gonna pick something that’s representative. Maybe this is a week, maybe this is a day if your days look fairly similar – every site’s a little different, right? But the idea here then is, once you’ve figured out how much it’s gonna cost for that representative period, you can go ahead and then just extrapolate from there, and calculate what you think it will cost for the year, for example. One thing with this one, we’ve actually done this a few times at Split, you might wanna do it more the POC side of things. We’ve done this a couple times just as a, like, we’re considering this new technology, we have no idea if it’s a good idea, we’re just gonna like kind of gut check and you know, with a POC try to figure out what it might look like.

Joy Ebertz: But we’ve also done this… one of our more recent ones, we did this actually in pretty late stage. We were cleaning up an entire data pipeline system, replacing with something entirely new, and like we were pretty sure we wanted to go with this new thing, but we wanted to make sure we wanted this like last validation before we really started doing things. They weren’t going to completely blow the budget outta the water, right? It was a nice gut check at the end to make sure we were in the realm that we expected to be in.

Joy Ebertz: The next use case I wanna talk about is verifying parody or parody testing. This is also sometimes called tap compare testing and this is pretty similar. The other ones one of the key differences, while it doesn’t matter for the other ones, when you send the mirrored request. For this one, you wanna wait until you already have the response from your old system. And this is useful because then we’re gonna go ahead and send the request again to the new system, but we’re gonna compare the responses from these two systems to each other. And if they’re different, then we’re gonna go ahead and log it.

Joy Ebertz: And where the feature flag is useful is, again, because logs are expensive, right? We don’t wanna be spamming our logs and especially if something does go wrong, then we can go ahead and turn off the logging while we try to debug and figure out what happened or maybe turn it on just for a particular user while we try to debug exactly what’s causing the difference, while all other traffic continue can continue to flow to the new system to continue to load test it, but maybe not parody test it anymore. And this is one that we’ve used a few times at Box, when we use this, it was for our authorization system, we were replacing part of that, and we actually discovered that we had forgotten an entire feature, like an entire feature was something that somehow nobody noticed was missing.

Joy Ebertz: But because we had done this parody test, we caught it before this was the new system was rolled out to a single user, so we impacted zero users in the process, but we were able to find that we had a problem here. Another use case we had at Split recently is we were replacing a database with a completely different data system and it aas a nice way to ensure that the data coming out of the new database matched what was in the old one after we had migrated everything and done all of the various other pieces, it was nice to be able to verify that yes, the new data does match our old data and everything makes sense.

Joy Ebertz: Okay, last use case. Controlling logging. I kind of touched on this before, but logging is expensive. There’s this like tension between, do you log a lot and pay a lot of money versus do you log not very much and then when you know a problem happens, you’re totally in trouble, right? Like you don’t really wanna be in either of these situations, right? It’s kind of a problem in both cases, <laugh>.

Joy Ebertz: One way that a lot of people solve this is by basically, trying to reduce your logs, but then have a way to be able to through configuration, turn them on if things are going badly. And specifically, one way you can do this is through a feature flag. And I guess we’re currently working on doing some of this. We’re adding a library, like a wrapper library on top of the logging, which does a number of different things. But among the other things that it does is it enables us to put a single feature flag into that library that we’re adding. And this is nice because it allows us to quickly turn on and off the logging without having to push actual configuration in order to change those logging levels. And these are just to kind of give an idea of why that’s useful.

Joy Ebertz: In order to change the feature flag, and this is assuming that like maybe I need to get an approval on it and like, people aren’t quite instantly there. Like let’s say it takes 15 seconds in order for me to make a change and somebody else to come in and improve it versus this was one of our recent runs. It took 26 minutes of pipeline to get a change from, developer merged into our staging environment and then another six minutes to deploy that to production. And granted, an emergency situation, you might be able to bypass a few of those things in there, but we’re still talking on the order of seconds versus the order of minutes. And that can really matter when you’re talking about downtime or you’re talking about a real issue.

Joy Ebertz: The other nice thing about this is because it’s a feature flag, you can start to do more fine grain control too. So if you know that the issue is only affecting certain types of users or certain organizations, you’re able to then basically target only those people or only those organizations, which allows you, again, to limit the number of logs that you’re storing. But at the same time you know, you’re going to be able to get the information that you need or it might other be, might be other information maybe it’s certain profile types.

Joy Ebertz: Maybe it’s only affecting people in Boston which you can again use. Or it might even be that you happen to know that the problem is likely in the stack trace. So maybe you want to just log things from that stack trace and ignore all of the other, all of the other information out there. It’s also possible to do not just based on the user and the request, but also based on the actual classes and that side of things as well. So which, which pieces of code are you increasing the logging for? Awesome.

Joy Ebertz: This was a whirlwind trip through feature flags. Just a quick recap. I covered what feature flags are some of the typical use cases and then I went into some more interesting use cases around using them to remove debt code load and stress testing, evaluating tech costs, parody testing, and logging. I’m out of time actually, so if you have any questions you can go ahead and email me, or this is my blog as well.

Angie Chang: Thank, thank you, joy. That was excellent. I, like I said, I love Joy’s blog. I ever highly recommend to read it for both career and technical advice. And the feature flags topic has been always – I always see it on Twitter – so I’m really glad that this talk helped educate me on what it is. Thank you again, Joy.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Sukrutha Bhadouria: I hope y’all are having a great time so far in the conference. We’ve been having one great session after another. It’s been amazing for me at least. I do wanna remind everyone to please post on social media, all the amazing things y’all are hearing, learning, and listening to today. Use the hashta IWD2023 for International Women’s Day and the hashtag ElevateWomen because we want you all and us all to lift as we climb.

Sukrutha Bhadouria: All right, so now we have the wonderful Moriel, who’s a principal systems architect at Wikimedia Foundation in New York. She’s a physicist turned software engineer turned systems architect, currently work working on modernizing Wikipedia’s architecture. She’s also an open source enthusiast, and we are excited to hear about neutrality.wtf. Welcome!

Moriel Schottlender: Thank you so much. I’m so excited to be here. And it seems like I have gone from one thing to the other, to the other, and that’s I guess, part of changing, growth, I don’t know. But now today I’m gonna talk to you about neutrality.wtf, a case study in gendered language flipping tool, which is a mouthful but hopefully we’ll learn something and share something today. First of all, at me, I am originally front end development very much a open source enthusiast. I do a lot of localization work and support and languages. I hoard domains, which I assume a lot of you do too. And I’m a principal systems architect at the Wikimedia Foundation. We operate Wikipedia and I also apparently do a pretty good you know, self cookie that I was actually very proud of that one.

Moriel Schottlender: Let’s delve in. What is neutrality.wtf? We all know that the gender gap is real, but the gender gap is not just about how many articles we have about women or non men. The gender gap is also a little subtle. The gender gap is about how do we talk about both genders? And sometimes, or a lot of times, even when we do have articles about women, we tend to talk about them, not quite the way we talk about men, but it’s really hard to differentiate, to see it. And we hear a lot of people say kinda like, well, you wouldn’t say that about a guy, would you, wouldn’t you? I don’t know. And this is where the idea of that tool came up.

Moriel Schottlender: I was like, is there a way for me to kind of test this hypothesis to see if we flip around the gender terms and we read an article or read whatever it is online, can we identify problems or does it is not a problem? I don’t know. That’s where it came from.

Moriel Schottlender: This is what it looks like. This is the article about Ada Lovelace in Wikipedia. And so if you move it you know, pass it through neutrality.wtf, it’ll just replace all of the terms from male to female and from female to male. All of the gendered language will be just flipped around. And so now you can read about Ada Lovelace as if she was a man. And then now you can say, would I say these things about a man? And I’ll let you decide. I think, for the most part, probably okay, but there are cases where it might not be as okay. And this is the point of this tool to kind of flush those out. This is an example.

Moriel Schottlender: This is the beginning of the article matriarchy in Wikipedia. This is from 2018. The problem that I’m gonna show you today was actually fixed, which is very exciting. But I was thinking, okay, if I passed matriarchy through a neutrality.wtf, everything is flipped. Well, now it’ll describe patriarchy, which technically is the opposite, right? Would it look the same? Would it sound right? And so I did. And oh, it didn’t sound exactly right. There were a couple of things where if you went to the article about patriarchy, you didn’t see there, most notably in mammals, to the exclusion of females, probably not what we want. Good news is that these things were fixed, were removed from the article. But that is the point of this tool. To also clarify, we do have limitations and there are very known limitations. The first thing is gender itself is not binary, and this tool is not making any statement about the gender being binary.

Moriel Schottlender: On the contrary, there’s a lot of explanation that is exposing the fact that gender is not binary, but gendered language, especially in English, tends to be binary. This is only making the point about gendered language. There’s also a limitation about one-to-one replacement of language, which this tool is doing. This tool is dumb. This tool is just looking for words and replaces them, which means we have problems with language processing or language context. There are verbs versus nouns, for example, count can be replaced by Countess, Count Dracula, for example. But I also count from one to 10. Is that count test from one to 10? Probably not. The system is a little dumb. We do have those mistakes happen. The idea is to make it a little bit, you know, funny, also to make the point. We do know, this said, there’s also ambiguous words.

Moriel Schottlender: We lack context. And a lot of times the demeaning terms. So if you see something written about girls, when you actually talk about women, we know that it is demeaning. When we flip it around and suddenly talk about boys, it’s not as demeaning, so it might not always deliver, right, the actual impact, but it works.

Moriel Schottlender: I’m an architect. Let’s delve into the actual tech. How did this happen? Well, this all happened in the 2017 Wikimedia hackathon. As you can see, this is me in my telltale hackathon. Look, I am overly caffeinated, but barely awake, hackathon. This was an idea for the hackathon. We took articles from Wikipedia specifically. The tool works, by the way, outside of Wikipedia as well. You can do do any sort of article, but Switzer and PHP based on a one-to-one replacement, JSON dictionary, and it has a hackathon architecture.

Moriel Schottlender: What does that mean? Well, hackathon architect is a hopeful one. I started writing this and I was saying, I know that I’m gonna write something that I want to basically just have work and never deal with it again, so I want to make it right. I’m going to separate concerns. I’m going to create two repositories, one for the front end and one for the backend. I’m gonna use it as a submodule. I’m gonna like separate everything. And that was great, except it didn’t really work. While we were working on this in the hackathon, everything started kind of like mis-mashing together. The business logic was all over the place. The caching was everywhere. The front end was fetching and the business and the back end was kind of like, you know, interpreted. It was, it was crazy. It ended up being very, very, very, very tangled, which means it was a monolith in disguise.

Moriel Schottlender: I attempted to do decoupled. It was not decoupled at all. But look, as a hackathon project, it works, right? Like it’s just, it’s there. I put it out there. People use it, it works. It’s great. So why should I touch it? Well, it didn’t really work for me. The environment kept going stale. I had to keep going after kind of like upgrades and stuff and libraries. And then the caching layer was all over the place and started filling up my hard drive and moving to other things became really, really problematic. Managing the hosting was bad. And then monoliths in general, a very annoying because a little tiny bug, suddenly you have to fix everything everywhere because there’s no separation of concern.

Moriel Schottlender: I wanted to be lazy. I wanted to just let it live online without me constantly running after this. And the way to do that was to reconsider my architecture. Let’s think about this better, especially since it’s been a few years. Technology is new, there’s other options. Let’s figure it out.

Moriel Schottlender: How do you approach thinking about a new architecture to your thing? Well, the first thing is to think about what are the standards? What do I want? Like what am I aiming for, right? What I want is to make sure that it’s loosely coupled. It means that it’s made out of pieces that I can replace seamlessly. They’re not like directly touching one another so that I can, if something happens and I want to replace the middle layer or the top layer or whatever, I can just replace it. It needs to be easily maintainable. I needed to retain the same behavior, but allow for more features without constantly maintaining this. This was very, very important.

Moriel Schottlender: I had to make sure that I don’t run after everything all the time. And then there was another set of kind of standards that I wanted to add. This is open source. And because it’s open source, other people can come and just contribute. And that’s great. But it also means that I need to make sure that the separation of concerns are very clear. Because if someone else comes in and just adds code in, I need them to understand what is valid and not valid to add, right? And so it makes it everything a lot like easier to review and avoid diluting whatever I worked really hard for the con separation of concerns, even if changes, which is what I want to make sure, right? Like this is not a constantly like worked on project. I could leave it out there online and come back to it like months and months later. So I wanted to make sure that that works. All right.

Moriel Schottlender: Thinking about all of things, I came up with basically a three component, very broadly architecture. Okay? This is a plan. I’ll have a standalone Node.JS library. This thing is going to be relatively generic just to do replacement of terminologies inside HTML pages. And then I’ll have a microservice that takes the very, very generic and brings it into the specific, so it does all the translation needed to do a specifically neutrality.wtf replacing gendered languages thing. And I have a web front end that is completely decoupled and I can replace it any time. The standalone library, it has to be scoped and this is one of the biggest problems. We’re gonna touch on it in a minute. It has to be very, very well scoped. It does something very specific.

Moriel Schottlender: A black box, it goes in, goes out, HTML in, HTML out, does the replacement internally. It means also that it’s testable because it is very scoped. If I go in at some point in the future and I want to replace some functionality or add something, I can be sure that all my test pass and all my expectations are there, so it’s a lot easier than like a humongous monolith where who knows what I just touched on and what I did. And it’s open, so shareable. Some people can just take this library and do other replacements of other things. I don’t know. All webpages will have replaced cats to dogs or some images to other images, whatever it is. You have like a very kind of generic library or as generic as possible library to reuse. What it is due, it’s kind of a black box.

Moriel Schottlender: It accepts HTML string, it parses it into a document, performs all of the replacement. It’s accepted string and library sorry JSON replacement. It replaces everything. It serializes his backend, hands it over as a string. That is completely replaced. That is what it does. And then I have the microservice. The microservice needs to be the bridge between that backend, that like engine into the front end that can be like visible to users. And it does the product specific behavior. It validates all parameters. It does the fetching of the remote page because the library itself doesn’t know if it does fetching or whatever. It doesn’t know about HTTP or whatever. All it knows is about HTML documents. The micro server does it that. It handles all errors. It’s calling the library and it returns the output in a way that the front end can present it, which brings us to the front end.

Moriel Schottlender: The front end, straightforward. Decoupled. It can have multiple versions. I might have a web or mobile web or a browser extension, whatever I want, I could swap it around. And it needs to be accessible. It presents the interface. It has explanation pages on it. It accepts user input input, validation, all that kind of stuff. But then we need to consider complexity. There is an overlap a little bit between the microservice and the Node.js library here. What do we do about this complexity, right? Like I have overlap here. Which piece should do? What should the microservices always do the web specific stuff. It sounds right. But if I go with a very simplistic, then there’s a lot more complexity in the microservice, right? The microservice needs to do a lot more. If I go with a really complex library that can do anything, then now I’m risking making it unusable because it can do so many things that nobody knows how to use it, which we see online a lot, right?

Moriel Schottlender: But there’s another consideration here. The actual action of parsing and HTML string into a document is expensive. It takes time. And so if I do it twice, I’m actually doubling the amount of time that it takes the system to respond. I need to make sure that I only do it once, which means that if there are certain things that might be web specific but required to be done before I while I parse it, I might have to put it in the in the library, right? What do I do? You know, what happens? Where should the complexity live up, down in the middle? Well, like many architectural concepts, it depends. There is no clear answer here. I don’t have like a direct answer of this is certainly where you need to do it. What you need to do is consider your complexity and understand that no matter what you do, you never lose it.

Moriel Schottlender: People online say, I just reduced all complexity. You did not. You moved it somewhere. Okay? Either you did it consciously and you’re aware of the trade-offs or unconsciously and you’re going to encounter it later. When you think about complexity, you have to kind of think about it clear. What will help you with that is examine the trade-offs. What does it mean? Put it in here. Doing it more simple, less simple. Root yourself, right? With an actual use case. Yes, the standalone replacement library should be very generic, but it also is aimed at a use case. Root yourself with that. Because if you start thinking about anything it can do, you’ll never get away with it. Everything will be possible and then nothing will be possible. Root yourself with that. Consider your performance concerns. Those are external things that come at you that might need to kind of formulate where you put your complexity.

Moriel Schottlender: It dictates where that boundary exists. And that is totally valid. And then beware of diluting the actual meaning of the component you started out with. Like, you know, thinking about a microservice, a library and they have meanings. And if we lose track of where complexity lives, we can actually lose like the actual thing we want the library to do, right? We put so many things in it that now it can do so many things that it doesn’t actually do the thing we want it to do, right? Try to kind of like re remain with like what is the goal of this component? What do you wanna do? The trade-offs, the external stuff. And most importantly, document all your decisions. And this is important generally, but it is even more important when you have an open source thing that other people may come in and ask, why did you do this? Right?

Moriel Schottlender: With that said, here is the new architecture. As you can see, I have three main components to it. The web front end, Vue.js incidentally, but it could be anything else. There are clear boundaries here. The caching layer is very clear. The microservice does the operation to simplify the no, the the Node.js library. And I even added a little bit. If I want a browser extension, I can just use the npm package. It is generic enough to do that, right? And it is reusable. You can just use it. And this is what it looks like. You feel free of course to go neutrality.wtf to use it. It is open source. PRs are welcome. And that’s how it works. To summarize, always, always when you architect, when you think of code, even before you decide to re-architect anything, always consider your complexity.

Moriel Schottlender: Whoever tells you that you need to do something like complex misses the point that complexity always exists. And you need to do to have like a very conscious choice of where don’t just ask could it do this? Cuz that is very easy for engineers to do. We ask, could it do also this? And the answer is usually, of course it can. We’re engineers, we can do everything. Ask yourself, should it do this? Because if you get away at the end of it with a library or a component that does everything, then it’s probably not one component. It should be many or whatever you, you end ended up with like a tiny, tiny monolith again. So as so should do this it’s okay to want to be lazy. I know it’s counterintuitive. Everybody’s kinda like work hard. You should work hard, but you work hard.

Moriel Schottlender: And that’s true for engineers. If we actually think about it. Engineers are lazy in our core. We worked really, really, really hard on stuff to do stuff for us so that we don’t have to do them right? How can I end up having least overhead is a totally valid question that is architecturally sound. It is totally okay to do that. And then you decide what the trade-offs are so you know what to invest in. And it’s okay to decide, you know what, I’m going to take a little bit longer to do this thing but it will save me time later. That’s perfectly good. And that also means try to use external tools. Why make everything in-house? You don’t always have to. You have external tools. Preferring those usually is better. Not always. Sometimes you do need like very specific but make a conscientious choice.

Moriel Schottlender: It’s very easy to jump into directly. Oh no, nothing exists like that. Or whatever exists is not good enough. I’ll just create my own. That is usually what we call code smell. You need to really ask yourself if that’s actually what you need to be doing. And there’s another thing here underlying all of this conversation that I didn’t touch directly, but I touched a little bit. Working in the open, working in open source has a lot of benefits. A lot of benefits for the way that you work and for the architecture that you produce because it forces you to kind of think in a collaborative manner. Even if you don’t collaborate, even if no one ever produces a PR to your code, it doesn’t matter cuz you put it out there. So the first thing is that it kind of gives you permission to put it out there, even if it’s not really ready, you’re just out there.

Moriel Schottlender: And that’s important because we tend to only put out there things that are perfect. Don’t wait until it’s perfect, just put it out there. You get help from people. It forces you to put very clear boundaries on everything and it encourages you to document everything which is superbly important, even for yourself in a year from now to know why you just did what you did because you don’t remember. Trust me, I don’t remember what I did three months ago.

Moriel Schottlender: And finally, I think we don’t say that enough. Have fun with your projects! When you have fun with your project, it shows you’re excited about them, you’re passionate about them, and it shows also for hiring managers and for the public and for great products, and you keep on working on them. Find things that make you happy and passionate and work on those.

Moriel Schottlender: If you want more information neutrality.wtf is online. Feel free to use it, please. It’s on GitHub. PRs are welcome. Issues are welcome. And you can also talk to me. I’m “mooeypoo” almost everywhere, Twitter, Mastodon. And if you want to follow me around, go to moriel.tech to see what I’m up to. Thank you very much. It’s been a lot of fun. And go on and be passionate with your projects. Open source. I think I’m slightly ahead of time, which means I have time to look at questions. Potentially. There’s a lot of comments.

Sukrutha Bhadouria: Hi, this was absolutely wonderful. I was following the chats. <Laugh>, someone said, we all love your voice,

Moriel Schottlender: <Laugh>. Oh, thank you <laugh>.

Sukrutha Bhadouria: Anyway, I wanted to say thank you for, oh my gosh, I just noticed your handle. It’s so clever.

Moriel Schottlender: Ah-Ha. Yes.

Sukrutha Bhadouria: Yeah, your social media. <Inaudible> <laugh>. Anyway, thank you so much for your time. This was absolutely insightful and besides loving your voice, your content was amazing.

Moriel Schottlender: Thank you. Thank you. It’s been absolutely fun and I really hope that you know, we get more and more of these conferences. They’re really important and they’re awesome. I’ve been learning a lot,

Sukrutha Bhadouria: <Laugh>. Absolutely. We wanna keep this going. Thank you everyone. Bye.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Angie Chang: We’re here with Shanea Leven, the founder and CEO at CodeSee, a developer tool that helps developers and teams better onboard, refactor, and understand code bases. And before starting CodeSee, she led teams that delivered high quality products and features for leading companies including Google, Docker, eBay, and CloudFlare. Welcome, Shanea.

Shanea Leven: Thank you so much for having me. I’m really, really excited to be here. I’m excited to give this talk. As Angie said, I’ve been in dev tools for more than 10 years.

Shanea Leven: One thing that I know about the the experience is that it has always suck onboarding to a new code base. Every developer, whether you are at a new company or contributing to open source if your application isn’t hello world, you must onboard to that code base. And so therefore you must like learn the code base and learn how it works before you can actually modify it. And I showed up today with a secret <laugh>.

Shanea Leven: Are you ready? I figured it out. And the secret is, in order to learn a code base, you need to pair, you need to pair all the time for all time 24/7. And that’s the end of the talk. <Laugh> Mostly kidding. But for those of you who, for whatever reason <laugh> can’t pair every second of the day when you’re trying to learn a new code base, maybe, you’re just starting an open source or maybe you’re just getting getting your foot in the door in a new area, it’s not comfortable for you or you’re in a different time zone or you’ve got zoom fatigue.

Shanea Leven: I wanna share some tips with you all today and kind of make sure that you all know that it does suck and it does get better <laugh>. I’ll start by telling a story. This story is about Shane <laugh> and her and her first day at Acme. And Shane is, you know, bright-eyed and she’s bushy-tailed and ready to ship some code.

Shanea Leven: She’s ready to prove herself, but like I said before much like you all probably you’ve got, she’s got to learn the code base first. So pretty soon, Shane finds out that onboarding to this legacy code base of the company that she just joined totally sucks. It’s really hard, it’s time-consuming, and Shane is personally having a really hard time. Why is it in fact that onboarding is so hard?

Shanea Leven: Well, when you are onboarding to a new code base, this is all of the things that you need to know but, you know I have this saying that every code base is like its own unique plate of spaghetti. It’s not exactly the same every single time. But in general, some tips to follow should get you started. Tips are broken down into three major parts.

Shanea Leven: First, you need to know the code or the system. You need to understand how to work with work with the code or work with the team. And then finally, how do you just be a human? What is the reality of being a human being and how that affects your day-to-day life and engineer? First, you need to understand when you’re onboarding to a new company’s system you need to understand the code of the system.

Shanea Leven: You need to understand how actually the code is connected. What are all the execution paths? What are all the function calls? What other functions called other functions? What are the actual details? What is the high level architecture? What are all of the domain objects? What are all of the nitty gritty details when it comes to working with the team? You need to know what is the code review process?

Shanea Leven: What’s all the design patterns? What are all the testing patterns? What are all of those gotchas in the code? The things that you just kind of hold in your head or the team holds in their head, and it’s not really written down. What are all of the deployment procedures? And finally, you need to know and deeply kind of understand just the reality of being human.

Shanea Leven: As developers, our main goal is to shift things. It’s to write code <laugh>. It’s not meant to write everything down. And so when you don’t write all of these things down, when your team doesn’t write all of these things down it gets out of date and it’s very, very hard for you to understand. And many times that information is not in the code. Repetition and retention. Turns out that when you join a new company you’re trying to onboard to a code base for the first time, or you have a new team member who’s trying to do the same you’re only gonna retain about 30% of what you’re told in your first week.

Shanea Leven: Even though you know you’re likely going to really need to understand, or you someone told you, or you told your team member, you’re likely gonna need to tell them again. Turns out it’s really, really hard to learn code. The turns out that the way that we learn code hasn’t changed in about 50 years. The process of reading code and understanding in and of itself is insufficient. We read code one line at a time, and we imagine how our systems work. That’s what we do. That’s just how it has always been. There’s very little to help us make sense of the code. And the data could be abstracted with types, it can be completely missing if you’re writing, if your company happens to use an un typed language. And reading is actually the most manual way to extract information out of code.

Shanea Leven: Therefore, reading and understanding code then takes at least 60% of our time and effort, you know, everywhere from between like onboarding as we mentioned. But then you have to read in deep dive when you’re debugging, when you’re doing code reviews or when you’re doing future work. And then at the same time, we’ve got these huge, huge systems. Like we actually have 10 times more code than we’ve ever had. And those systems are constantly changing.

Shanea Leven: While you are trying to understand the code, your teammates are shipping code like at the exact same time. It’s literally changing from under you. No wonder that Shane, and probably, you all when you’re joining a new company is gonna have a hard time <laugh>. But that experience, your sucky experience, is literally about to get worse. Because onboarding unfortunately isn’t a single point in time, it’s constant, it’s constantly onboarding to new things. Here are a few examples.

Shanea Leven: During Shane’s onboarding, Tommy over here ships a new feature. And that feature needs to get integrated with Shane’s feature. Guess what? She needs to onboard to it. Then, you know, after a couple weeks, she gets added to an on-call rotation. And then at the middle of the night, your system goes down and surprise <laugh> when you are, are in the middle of the night and the system goes down. This is not a normal part of your area typically. You’re onboarding again, you’re just doing it at two in the morning. The only option at that point is to just figure it out when people leave. Because we are constantly always visualizing everything in our heads, those mental models that we keep go out the door when people leave, whether that person is leaving voluntarily or unfortunately in today’s market involuntarily.

Shanea Leven: They were typically the only ones who kind of knew how that cool widget feature thing worked. And there’s no documentation at all. And now it’s your problem <laugh>. You’re just onboarding again. In another case, restructuring you know, teams get moved around. An individual person, the flip side of that could get promoted. Like your org might be restructured and then therefore your team’s responsibilities have changed. You’re onboarding again. And in the promoted case, it depending on like how fast that team ships code, the person’s knowledge is actually gonna get outta date really, really quickly as they are trying to onboard to their new responsibilities. In fact, you’re just kind of stuck onboarding. Again big refactors, many people don’t know this or consider this, but when you’re trying to complete like a big refactor project, it’s just actually one big onboarding.

Shanea Leven: For instance, when you’re trying to refactor a monolith into microservices, you’re trying to like break things down, or you’re trying to, you know, go back from a microservices to a monolith or, you know, some gradation of service microservice, not so micro services. In between all of those things, you need to really deeply understand how all of the variations work, what are act, what’s actually kind of helping or happening under, under the hood. And so you need to actually onboard to the whole code base so that you can make sure that you know how all of the parts are involved and how they’re connected so that you can ensure that everything gets into the new system without breaking. And then finally every single time you do a code review when you’re working on your new team is like its own little mini onboarding experience.

Shanea Leven: Essentially you need to like read the code in your head. You’re trying to remember the related code and imagine how it all works together. And that’s just another mini onboarding. And then you are just taking that code and kind of blowing it out to years and years and years of legacy code, people coming in and out, maybe acquisitions, maybe someone completed that half refactor and there’s a bunch of teched. You’re just kind of constantly onboarding. You’re probably wondering at this point, Shanea, I thought you said that you would help <laugh>, so I’m gonna help you with some tips now.

Shanea Leven: Here’s what you can do to not have that sucky experience as much as you can. It’s broken up again into three parts. Advice for the team, advice for the onboarding, and advice for continuous onboarding. Again, advice is in general and there are always exceptions. You know, some people thrive where some other people struggle.

Shanea Leven: Advice for the team in general – Start small in scope and expand strategically. you wanna provide some small early wins. Choose some tasks that help your teammate build confidence and help you build confidence trying to require learning as few new things as possible for each task. Make sure that if you’re on the flip side, that you are trying to ask for, you know, compact things and make sure that you write things down. There’s actually a lot to learn when you’re learning simple things. It’s typically more than you realize.

Shanea Leven: Problem solving in a new code base is actually really tricky, and it’s sometimes really hard to feel confident that you’ve considered all of the edge cases. So goal is to have, you know, build your confidence as part of the new team. You can start them out in a small part of the code base as possible, learn all of the relevant pieces without getting overwhelmed. You don’t wanna start your new onboarding and a huge challenge that people have been avoiding. You can ask a lot of questions if to make sure that you are not falling into one of those cases as well, but also try not to stay on super tiny things for long. You wanna start small but build consistently. Whoops.

Shanea Leven: I like to have the first task to be updating the docs for something. There’s a lot of little details that you can use to familiarize yourself with just by creating the code review, filling out the code review template, getting it approved and merging it. You don’t have to worry about having to get feedback on your code. Also, correct anything that wasn’t right in the repo setup instructions or write them up if you know they don’t exist is another great way. You can write up a small and commit a small personal bio to the repo with maybe time zones, communication preferences like Slack or email technical experience or fun facts. It can be really helpful on our remote team and, you know, be creative to try to get through the whole process, see that whole process, get that out of the way, and then you can focus on your code.

Shanea Leven: Once you’re ready to get into the code, make sure that you don’t need to understand all of the details about how the entire system works to get the task done. That helps you to build confidence that you did it right in the first place. You can gain a bit of confidence just by be feeling like you’re an expert in some small piece. And then growing out from there, so few examples, a bug fix in an area that’s well tested a small team task that other folks know how to solve, but just haven’t gotten around to yet. You can walk through the code that they’re gonna touch and some of the patterns to use to change it. So all that you really need to do is get familiar, write the code and not have, actually have to figure out how to solve anything.

Shanea Leven:  Another example might be a very isolated feature with minimal risk of breaking anything. Like change a button on a link or have an endpoint return. One more attribute. Tech desk tech debt is really great. Early task, even, you know, some tedious things like upgrades or maintenance. As a new team member, you can feel like you accomplished something good and you’ve learned something and the team will really appreciate you for it. And then this is key. You wanna let each task kind of grow from there. Maybe more tasks in small tasks in new areas, but ideally, you know, slightly larger tasks in the same area. Again, your real job here is to help them feel or help yourself feel confident like you’re an expert in that area. And as soon as you can be kind of the go-to person the better.

Shanea Leven: Advice for you as the onboarding again. You’re wanting to look for a few specific things to kind of wrap your head around the code base when you’re thinking about the code and the system and how it works. So you wanna know what are the domain objects? What are the users in your system? What are the key flows?

Shanea Leven: Couple of examples might be you know, if you’re in an e-commerce platform, that might be understanding where, what, how do you define a product? How do you define the shopping cart? What’s the flow from pricing or discounts or adding something to the cart? In dev tools, it might be how do you define a code base? What is a dependency or a commit or a pull request in ed tech that might be, you know, an assignment or activity or a lesson or a grade.

Shanea Leven: And some user examples in your system for e-commerce might be like a customer or a seller. And in dev tools, it might be a developer or team lead. And in ed tech, it might be teacher or student. And then you wanna make sure that you understand the key flows. Key flows in e-com might be, you know, customer makes a purchase. What are all of those steps that they go through in the system? Seller lists the product. What happens in your architecture in dev tools, it might be, developer creates a new commit, what actually happens or system analyzes the code base, like what triggers what or what calls what, how do you understand those details? And in ed tech, it might be something similar like teacher creates an assignment or student answers a question. It might seem silly, but these are really good things to just get down and get a full end-to-end understanding of.

Shanea Leven: Some best practices you want to ask and be comfortable asking. Lots of people will know some of these things, but it’s better ask in the first couple weeks. Don’t be afraid and constantly ask questions because it will help you make your lives a lot easier. Exploring the marketing site might be a great way to kind of wrap your head around stuff. Oops. reading the docs. You might want to, whether that’s like user docs or dev docs, but you don’t wanna a hundred percent trust the docs. <Laugh> You wanna read to kind of get a big picture. But you don’t wanna necessarily a hundred percent think that every detail in the are gonna be correct. And whatever you do, please write stuff down. Draw it out so you don’t have to ask again or figure it out again. Again, you will forget 70% of the things that you learned in the first couple of weeks.

Shanea Leven: You wanna start from the key flows and then expand to the architecture. You know, make sure that you start there and maybe draw them out. What are the key components? How do they talk to each other? You wanna start piecing these things together to try to get a picture of the architecture. What are the most important components in your system? What is responsible for each of those domain objects or use cases? And how do they talk to each other?

Shanea Leven: This is an example of a monolith. Again, once you’re starting to put things together, you wanna make sure that you have an example like this that will help you to get a full picture of your system. Again, best strategies would be asking a teammate, reading the tests is a good way. Just reading the code and creating a diagram or diagramming things out yourself, and then double-checking with the team to make sure that it looks right.

Shanea Leven: Next you want to understand the low level things. What are the frameworks? Not just, you know, that your company uses React. You really want to know that they use Red React, React Router, React Query, functional components, and the React Testing Library. You want to kind of deep dive and get a detailed understanding of what are all of the underlying frameworks best strategies to kind of learn this. You wanna make sure that you at least go through some basic tutorials or guides for each framework and library. You wanna know how to use the tools that you’re using. You wanna be able to understand the coding patterns, what coding patterns are encouraged, which ones are discouraged? Every company is gonna be different.

Shanea Leven: Some best strategies to learn. This might be, you know, looking at recent code reviews to see how things are done most recently. You wanna read the code and then use a tool like GitLens to find that code review. When you’re working on a task and read to decision point, you wanna ask a teammate what that pattern likes to use before you say it’s done and ask for the code review. You want to understand the development process. Questions that you should probably look to answer might be, you know, how do we commit, how do we do a code review? How do we deploy, how do we plan a new feature? How do we give status updates and how do we retro? Next you wanna look out for code-based kind of tribal knowledge. You know, if you make a change here, you also need to make a code change over there. You don’t wanna touch this function because if you do without proper knowledge of how to do it, site performance might go down.

Shanea Leven: You wanna start to understand all of those things and look out for it. And then again, write stuff down. I’m gonna say this multiple times. It is gonna be very, very helpful for you. Don’t try to have it in your head. It will be again, cuz you’re gonna forget. Take notes. Drawing out diagrams is, like I showed before, is very, very helpful. Adding comments to the code will help everyone if they’re not there. And try to update the documentation as you go. So advice for teams. You want to make it easy to learn some of these things. If you’re on the team and you’re accepting in new teammate you want to know, have them understand what are the domain objects and the user flows and the key flows. You know, how do the key flows fits in the architecture? What are the frameworks? What are best coding patterns that we’re following and avoiding, and the development processes I mentioned. So here’s a thought.

Shanea Leven: There are lots of tools. You might be thinking, oh, there’s a tool for this, or there might be a tool for that. There’s a tool for notes. There are tools for reading code, but they’re all separate tools. And likely they’re still gonna get out of date because they aren’t connected to the main thing that you’re trying to learn, which is your code. So why should we actually have to draw out key flows by hand when the computer already knows how to run our code? Why in fact, do we have to keep reminding people about patterns and processes? You know, it’s really easy to miss stuff and we don’t on our current teams make it easy for our team members or you as the new onboarder to learn this stuff. And turns out that computers are actually much better at automating some of these things than the manual reading code line by line in our brains.

Shanea Leven: And again, every code review is a little mini onboarding experience, but our tools don’t really help us to onboard. They help us to just comment on a bunch of lines that are listed alphabetically.

Shanea Leven: For continuous onboarding, what if we could actually achieve that goal? What if all of the maps and the key flows and diagrams were all drawn out for you? What if you could just start from a file and expand until you understood the architecture? Or what if your teammates reminded you of the patterns that you should follow? Like right here, right there in your PR. What if you know every PR you could understand the impact that your code change has on the rest of the architecture? That is what we’re actually building at CodeSee. You could absolutely just use a tool like CodeSee.

Shanea Leven: There are lots of other tools as well in the code visualization space. It’s a new exciting space that’s really designed to help you feel comfortable and confident learning all of the code, even as as it’s changing out from under you. Try to invest, invest or advise your team to try to use, whether it’s CodeSee or not, some kind of tool to help you feel confident in the process. We can solve a lot of problems with having our tools help us to onboard a bit more. In conclusion, onboarding is hard. It sucks, but it can be easier. Thank you so much for listening to my talk.

Angie Chang: Thank you Shanea. That was excellent. You ran a little over, so I’m gonna have to stop us now. Thank you so much. And I know you’ll be back tomorrow with a workshop, so don’t miss out on that. It is one of the most what is it? Bookmark sessions if you look at the schedule. Amazing. We’re definitely excited. Really

Shanea Leven: Excited to see.

Angie Chang: All right, see you tomorrow.

Shanea Leven: Bye.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Sukrutha Bhadouria: Our next talk is gonna be given to us by Katie. Welcome Katie. Katie is a Senior Insights Analyst at Sony Interactive Entertainment. She’s a digital analyst focused on multi-platform customer behavior and insights. At PlayStation, she analyzes the customer journey across digital storefronts leads, A/B tests for digital merchandising and champions data-driven thinking across the organization. Welcome.

Katie Egeland: Thank you Sukrutha. Hi everyone. I’m Katie. And my talk today is about data storytelling and the skill that I think is most important in when you think about data storytelling and how it can really set you apart from from your peers. Before we get started, just a little about me. As mentioned, I am I work at Sony Interactive Entertainment, also known this PlayStation. I’ve been here for a little over five years, and I’ve worked on web analytics as well as commerce and customer journey analysis.

Katie Egeland: In addition to the video games, I also have worked in the international education and beverage industries, and I do enjoy gaming. Some of my, I hate picking favorite games, but some of my favorite game genres are action, adventure, term-based strategy. And I also enjoy any games that have plants in them. When we talk about data and data storytelling, you know, data’s everywhere these days and a lot of companies say, I wanna be data driven.

Katie Egeland: What does data driven really mean? It’s important to remember that just looking at numbers or having numbers doesn’t make you data driven. And as analysts, we often get asked for numbers, but those aren’t really the end goal. Nate Silver sums it up well here. He says, the numbers have no way of speaking for themselves. We speak for them, we imbue them with meaning, we being the analysts who are getting numbers and translating that to our stakeholders and businesses. But what kind of meaning are we looking for in the numbers? What is, what is the data for?

Katie Egeland: What is the point of getting those numbers and sharing them? The real point of it is to make decisions. And in order to help people make decisions from numbers, what do we need to do? We need to communicate. That’s how we really turn data into actions. And communication is more than just putting numbers in a page or building a dashboard.

Katie Egeland: We have to make sure we’re communicating data in the right context, making sure whether that we’re resonating with the people we’re sharing it with and what they care about, and actually addressing that, the problems that they’re trying to solve. And if we can do those things, then we are really being effective in our data communication. And I don’t think this is only for analysts. I think this applies to anyone who has to supply numbers or present data to others. We can use the same ways of thinking.

Katie Egeland: When we talk about communicating data and telling those stories, really the key to that is connecting with your audience. You’re trying to give them a message. In this case it’s data, what it means, what actions they might take from it. And when we do that, we often focus on a few questions. One is the what question, what data is needed? What are the metrics that we need to get?

Katie Egeland: What questions does our stakeholder need answered? The other question is, how will I get it? How will I analyze it? Where do I need to go to find this data? What methodology do I need to use to analyze it? What code do I need? How do I clean the data up so that it’s usable? And often we, we stop here, and these two questions are really important to get started on any project, but if we can go a little beyond just these what and how questions, that’s where we can start to dig into that effective communication of our data. And in order to do that, we can think about a few other questions.

Katie Egeland: One is, who’s going to see it? This is, you know, really key to understanding who you’re communicating with knowing how much they already might know about the topic what level of detail they might be looking for. If you’re communicating something to an executive, they’re probably gonna be interested in much more high level insights and not so much detail as an engineering or marketing team.

Katie Egeland: And then also, when you think about who, you can think about what other data might be relevant, even if it’s not something that they directly ask for, if you have an understanding of the angle that they’re coming at things from and the other things that they’re involved in, you might be able to, to find other data to, to give them supplementary information that makes the data that they’ve asked for more, more useful to them.

Katie Egeland: Lastly, the most important question in my opinion, is why, why do they want this data? And this isn’t to ask, you know, oh, why do you want me to do this work? But it’s really to help you as the analyst understand what problem is that data addressing and what actions or decisions are going to come off of this data request. In order to think about all of these questions, I wanna run through a couple of examples of common scenarios that analyst finds themself in and talk about how we can apply this framework.

Katie Egeland: First, reports and dashboards, these are really common. Any analyst is gonna have fulfill many requests for these. And these can actually be a little tough because often when you get a request to create a report or a dashboard, the KPIs and the metrics are already set. You might just have a, you know, a list of, here’s everything I want on this dashboard, but even still asking some of these questions can help you do a better job.

Katie Egeland: Who uses the dashboard? Who’s going to be looking at this on a regular basis, especially if it’s a recurring report. Understanding again this executive report. Is this for troubleshooting some kind of issues or monitoring for issues? Wfhat metrics are actually going to drive action? A lot of times in requests like this, you get a long list of metrics, but which of those metrics are going to, when they change, actually alert someone and say, we need to make a change because this metric changed.

Katie Egeland: There’s also a few things you can do when you’re building these and thinking about visualizations. Using those visualizations wisely, not just putting a bunch of fancy looking charts on it. Charts can really help you drive actions.

Katie Egeland: My personal favorite is trended charts, so showing something over, over a mid or long period of time. Often we might put some type of metrics on a dashboard and look at week over week, quarter over quarter, year over year changes, but those don’t really tell the whole story. If you put a metric onto a trended chart, you might see a little bit of a dip in your week over week numbers. But when you look back over six months, you can see an overall upward trend. Having that better context gives you more information about where things are are trending.

Katie Egeland: Another trick I like to use on reports and dashboards is using conditional formatting. It’s pretty common to see things go up or they’re good. You see green things go down and they’re red. But going a little bit beyond just that if you understand what are the benchmarks or what’s the threshold of something changing where we actually need to take action, as opposed to, just any up or any down is green or red. If we can incorporate those into the reports, it makes it a lot more easier for the person consuming that to understand, oh, this is, you know, red in, in a negative way that I really need to look into it and change something as opposed to this is dipped, you know, some very small amount since last week.

Katie Egeland: And then another, my last tip on here is checking in with the requester of your reporter dashboard after a few weeks or a few months that they’ve been using it. Especially again, if it’s something that’s recurring or they’re referencing often, and you know, asking them, what parts of this are you using? Are there areas where you wish you had more information? Are there actually parts that you’re not really looking at all, even though you wanted to see those, those numbers initially, and having that conversation to understand what is actually useful for them.

Katie Egeland: Lastly, I think remembering that having numbers isn’t the goal. Sometimes when you make a request for reports and dashboards, your goal personally might be, well, I need to send those numbers to my boss because they’re asking for them. But the point isn’t just having the numbers. It might be for you to put in an email, but ultimately those numbers are, are going to be used for something and to, to drive some kind of action.

Katie Egeland: And so even if you’re not an analyst, even if you’re not the one building that dashboard, asking those questions of the people that you’re sending it to so you can really understand how they’re using those numbers and what type, what type of actions they’re driving. Deep dives. These are the other, I think major scenario for a lot of analysts. A deep dive is a bigger analysis project. Usually it’s gonna be questions that explain behavior or make some kind of recommendations to your business stakeholders. And these can often take many hours, many days even, you know, months to, to complete. There are a lot of effort and, you know, asking these questions is, is just as important, if not more.

Katie Egeland: Again, that question of who, who’s going to see this analysis, how are they going to use it? Understanding if it’s an explanatory or an exploratory analysis. Explanatory is looking at, you know, what happened, why did it happen, what what factors contributed to it? Exploratory is looking at where there’s opportunities what potential solutions might be in making those recommendations and understanding the di the difference in what’s being asked.

Katie Egeland: Another big one for me is understanding if your requesters already have a hypothesis. Sometimes when you get a deep dive request, the people asking it might already have a hunch of why they think something is happening or, or where things are trending. And if you know what their kind of hypothesis is in advance, it’s not. You can tailor your analysis and cherry pick and, you know, just build something to support it. But if you, for instance, see something that might be contradictory to the assumptions that they have, you can anticipate the questions they might have and know that there’s going to be potentially additional skepticism if what you’re showing goes against what they thought was going to be the case. And then again, always connecting us back to what decision or what course of action is this deep dive going to to help influence.

Katie Egeland: Sometimes you might be in a situation where people just wanna know, know more about a topic, but it’s not quite clear what action might come off of it, given that these deep dives can take such a long time really pushing on what are the outcomes, you know, that we can expect from this and, and how might we take this information and use it after it’s finished When you’re putting together deep dives, there’s a few things I think are really important.

Katie Egeland: One of those is starting with a summary of your key takeaways. I like to say that spoilers are good. You shouldn’t hide hide your takeaways at the end. It can be tempting as you’re building a story to, you know, start with, here’s the question, here’s how we investigated it and, and wait till the end to reveal your, your answers to those.

Katie Egeland: But if you start with your key takeaways right up front, you really hook your audience, you get them engaged, you, they know where you’re heading and they’re gonna be more interested in understanding how you got there and how you’re proving your points. Also including context where you need to. And this can be as simple as just taking screenshots, providing in explanations of a particular feature or experience. Even if you’re presenting to people who are quite familiar with, with the product you’re talking about, they may not be completely familiar with the exact feature or nuance that you’re, that you’re covering.

Katie Egeland: And making sure you have that context so both they can understand it and you understand it, them yourself is really important. Lastly, using the appendix to tailor your content to different audiences. If you produce a presentation that has 30 slides, depending on who you’re presenting to, you may not need all of those slides. For every, every audience I mentioned earlier, executives, they’re usually not gonna be interested in really long detailed presentations. They’re gonna say, what’s the key takeaways? What do I really need to know? If they have additional questions, you can pull those things from your appendix. But being really mindful of who you’re presenting to and how to use a time wisely when you have with them.

Katie Egeland: And then I think engaging, asking questions when you’re on the receiving end of a deep dive is really important. Nothing’s worse for an analyst to spend many, many hours putting something together and kind of get nothing back from the people they present it to. But when you’re asking those questions, making sure you’re, you’re thinking about them and curating them a little bit for yourself and saying, okay, if wanna know more about this, how is that going to help me in my job? How is that going to help me take some kind of action in the future to avoid creating a lot of extra work of kind of nice to know questions that might be interesting but might not actually have a lot of value in the end.

Katie Egeland: What I want you to take away from this is that the key to communicating anything is making it resonate with your audience. And if you can make it resonate, it helps drive action. And in order to do that, we want to, you know, again, think about these, these four questions that I’ve been talking about. One of them is the what metrics actually connect to actions? What are the key takeaways? Not hiding those, making sure they’re really clear upfront because they’re more important than the actual numbers that support them.

Katie Egeland: The question of how providing context, providing the right level of detail depending on, on who you’re showing this to. And using visualizations with a purpose and as a tool to help people understand what action they should take. That question of who understanding who your audience is, working hard to curate what you’re presenting or showing to them, to their needs, their level of expertise and the actions that they can actually take themselves. And again, again, for me, the most important question is why asking questions. What it is you’re, what it is you’re trying to, to communicate. What’s the actual purpose of, of the analysis and remembering that the point isn’t just the numbers, it’s the action that comes off of them.

Katie Egeland: Now, I didn’t come up with all of this myself. This comes of course from many years of experience pulling data and presenting it and communicating it to people. But there’s a few resources I wanted to highlight here for you. One is a book called “Resonate” by Nancy Duarte. And she has many books about different styles of presentations. Some of them are data focused. “Resonate” is actually not about data at all. It’s really about visual storytelling and how to connect with your audience and break down your idea and what you’re trying to communicate and structure a story so that it really resonates with the people you’re talking to. The other one I really love is “Storytelling with Data” by Cole Nussbaumer, Netflix. And this is a little bit more straightforward data storytelling. It includes great tips for in improving your data visualizations, making them clear, making the action clear with what you’re trying to communicate, and also the importance of including context and making sure your audience understands that.

Katie Egeland: And once again, I’m Katie. If you have questions or you want to chat about data, storytelling and communication, feel free to hit me up on and thank you very much.

Sukrutha Bhadouria: Thank you Katie. People have so many amazing comments for you. We talk and even the reference to the book, the Storytelling with Data book being the best <laugh> book they have read, it’s really

Katie Egeland: Good. Yes.

Sukrutha Bhadouria: Yeah. Some people have shared their stories in the comments as well, so when you get the chance to take a look… Yeah. Well I wanna thank everybody for attending this session. It was very insightful. So thank you so much Katie, and thank you for taking time out on a workday, busy workday to have great Women’s Day with us.

Katie Egeland: Thank you everyone. Appreciate it.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Angie Chang: Aashima Lakhanpal is a search product lead at Google. She spent a decade selling ads, inclusive teams, and writing dad jokes. Having managed global teams across Europe, Asia, and America, she’s on a mission to make teams bias free with training and group exercises that can inspire teams of all sizes to feel included and achieve their potential. So welcome Aashima.

Aashima Lakhanpal: Thank you so much. Hi everyone. I’m glad you all are here to celebrate, you know, Women’s Day and to elevate yourself. This is fantastic. I am Aashima LakhanpaI. I in my day job am a search product lead for retail <laugh> In simple terms, what I do is I channel product feedback to teams at Google based on whatever inputs I get from customers, retailers on search shopping. If you have questions on what do I do exactly, I’m more than happy to connect one-on-one later. But for now, that’s the easiest way I can say what my job is. But that’s not why I’m here.

Aashima Lakhanpal: I’m here today to tell you something about why I’m, what am I passionate about? And you’ll hear that in exactly a minute more. Let me give you a quick question so that you get a sense of where am I headed to now? It said that we receive 11 million bits of information every single moment. I would love to hear from all of you, what do you think is how much of this to we consciously process? Feel free to drop responses in the chat, but I’m curious to understand if, you know, you have guesses on this. Out of 11 million bits, how much does a human brain consciously process? Oh, <laugh>. Okay. 5%. I see that. Yeah.

Aashima Lakhanpal: Well, surprisingly, out of this 11 million bits of information that we receive, we actually only consciously process 40 bits of information, which means 99.9% of the times were actually making decisions based on our subconscious or our unconscious biases I like to call it. Imagine the amount of decisions, like which coffee do I want, which elevator to take. Simplest of our decisions, we’re actually taking as fast as our subconscious brain can process, which is the topic that I’m here for, to talk about is that, well, ladies and gentlemen, bias is something that has been a part of all of our lives for so long, driving almost 99% of our decisions, and we have never ever given it a second thought.

Aashima Lakhanpal: This June, I complete a decade in tech, which is 10 years of working in tech. If someone asked me at the beginning of my career, I would laugh it off and think, well, I’m not gonna be here for long. But ten years is, is what I have done in in tech. And as I look back at my ten years in, the one thing that stands out to me is that I have had a lot of first moments, only moments as as a woman, as the only woman in the room, as the first woman in the room. And it’s been a proud moment, but also quite learning because I have had time to contemplate what these first moments mean. For example, if I remember my first ever conference, it was for an automotive company, and I was supposed to present these really cool gadgets and say why data is going to help these cool gadgets, et cetera.

Aashima Lakhanpal: I remember that session bombing because the entire audience was, you know, room full of men. I don’t know if they wanted to hear what I had to say. That was my very early entry into understanding a room full of men and feeling like, oh, is this something I’m going to experience every time I enter a workplace, a room full of bias? Got to a few years later, I received my first international job opportunity and I remember thinking, well, this is great. I’m gonna be abroad. I’m gonna relocate.

Aashima Lakhanpal: I was also double questioning myself. This means I have to relocate my entire family. Am I doing the right thing? Is this the right thing? I should be focused on building a family. I don’t know if I’m doing the correct thing, which is when I also realized in addition to being at the receiving end of a bias, I am now the person who’s also causing bias. That’s how human brains are. This ten years has taught me one thing. It’s that you are biased.

Aashima Lakhanpal: I am biased. We are all biased. This is a byproduct of being a human. Each time we see a decision, we’re making a judgment, and that’s how our biases erupt. So while if you ask me, is this a good thing, is it a bad thing? Well, it’s a thing. We’re living with it, we’re taking decisions based off of it. Good or bad, the first step to understanding these biases is acknowledging that they matter. It’s important that each time you enter a room, know that every person there has some sort of biases including yourself. And if you can acknowledge that, that’s step one taken. Let’s figure out what does this mean for, for all of us, right? We’re all working in this, this, you know, tech space where we’re constantly working with teams, we’re working with people in remote setups, we’re working with people in global teams, we’re working with people in diverse multicultural teams.

Aashima Lakhanpal: All of this makes it even more complicated because imagine if our personal lives are so much of bias being trickled down into our decisions. Now think about how much biases enter into our decisions at our workspace. You know, think of simpler decisions like hiring a new person for the team or who gets this project. Imagine all of those decisions being taken and now the amount of biases that help those decisions. So as I went through Covid in 2020 and I kind of worked remotely, a lot of these questions always bothered me that, well, Aashima, I know what biases I have, I’m learning as I grow, I’m learning what means, you know what, what, what kind of biases have I seen as an Asian person, as a woman? I mean, I’m not, you know, ignorant of the fact that as I entered this workforce, I was really docile.

Aashima Lakhanpal: I would hate questioning someone. My biggest bias was that I couldn’t talk to a senior person in the room because I felt it was rude to question them. Now cut to so many years later, my first thought in this process is that, well, now that we’re all working remote, this is only going to get worse from here. How else do I talk to a room full of people who probably have similar passionate interests, but are so diverse in how they operate? How do I take benefit of the fact that we are all biased? What can we do from here? So here is what I decided to do. I kind of made a framework for myself, and I urge all of you to think about your own frameworks as you start to work with different teams, global teams, you know, different people coming from different motivations.

Aashima Lakhanpal: I kind of put a framework for myself to say, each time I work in a new project or in a new space, I would love to understand where this person comes from. And the easiest way to do that, you don’t need too much of research into this, and I’m very conscious that this is also a biased process. But the idea here is to say, look, each time I’m in a new space, I’m gonna try asking someone what is their main motivation or what drives them to work better? And if I can club that into four main buckets, I have a better way of working with each of them. Now I will come to the end and promise I will make this worth your time to say, well, what do you do with this four style model? And what’s gonna benefit us in the long term?

Aashima Lakhanpal: I will come to that. Let me first little tell you a little more about what this model looks like. I kind of said, okay, look, each workspace typically has one of these four people. And this is how I simplified this for my decision making. I said, well, typically someone says, I love working with people. It’s my passion. I wanna feel like I’m working with family with home. It’s this person is showing you traits of a relator. He’s this person who’s actually meant to build more relationships and he drives off a lot of energy of this particular trade. This person could be called a relator.

Aashima Lakhanpal: The second type of person I would see is someone like an influencer. They are the people who kind of love winning others over. It’s almost like they like viewing you day in and day out because that’s how they operate. You know, they’re the swift talkers. You see them sometimes. I’ve personally been at the brunt of someone who’s been an influencer and felt, look, am I being, you know short sold because this person is so good at what they do. But that’s what influencers do. They kind of persuade you to an idea or a concept, and they do it really beautifully. And I’m sure you see it in some teams yourself too. Even if you are in college school working through some, you know, recently created teams, you will always find this one influencer sitting in your team ready to talk about something.

Aashima Lakhanpal: The third kind of person I’ve typically found is a strategic person. They can literally spot a trend from a mile away, talk about any concept, and they will try finding trends in saying whether this exists, what kind of issues, consequences, problems they can already, it’s almost like they have seen five steps ahead in advance and it’s a good thing because that’s the part that excites them.

Aashima Lakhanpal: The final part is someone like an executor, which I personally relate a lot to. It’s from the idea of, you know, how many people get a high when they kind of tick things off their list. This is me. I love being the fact that I’m so productive. I have done ten meetings today and I’ve kind of ticked so many other things off. That’s my motivation to work, is that I love to implement things and kind of push them until I see it till the end. Now, I know that this is, you know, a typical workspace.

Aashima Lakhanpal: You may have someone fall into one of these four buckets, but I, like I promised, I’m gonna tell you what does this mean? If you are working in a team like this, I realize the benefit of all of us being biased or having judgments or making decisions based on biases that we have is the fact that you can actually benefit from a team member who has a strong motivation like this.

Aashima Lakhanpal: For example, in my case, the fact that I have been an executor and I have loved working, you know, to tick things off my list, I would make a great pair with an influencer. Imagine me and an influencer working together on a project. We could actually make this project look so better than it already is just because my skills and their skills are complimentary.

Aashima Lakhanpal: I urge you to think that each time you enter into a team, think about what is actually complimenting you and anyone else’s skills. And that’s what I call a strength spotter. It’s an easier way because look, we’re all biased. We’re gonna operate from decisions that, that are from our own biases. We could be the ones causing it, we could be the ones at the end of it. But I actually love the fact that this framework helped me think, look, I am a person who’s an executor.

Aashima Lakhanpal: What is the best thing I need for this project in order to move forward? I’ve also had examples where someone like a strategic person and a relator have worked really well. Now imagine if you’re trying to get a project right off from the ground, this relationship builder can actually go and bring anything that that kind of, you know, brings that relationship in. And a strategic person can help you build that framework. So many times you’re just missing those one, two parts that this other person in a team can bring.

Aashima Lakhanpal: As I promise that’s my takeaway for you here, which is the next time you are in a team, right? Remember these three things, acknowledging biases is never going to be out of fashion. Each time you are a person in a room that you feel is awkward, remember that someone else is also feeling awkward.

Aashima Lakhanpal: I love the fact that my manager asked me this question and she’s a female manager by the way. She asked me, Aashima, how are you feeling and how did this make you feel? I remember the power of this question because it meant that wow, someone actually understands where I come from. The next time you are with someone else, acknowledge someone else’s bias. It’s never going to be out of fashion. You’re going to uplift someone so much that is gonna make their day. It’s your key differentiator. And so is it mine?

Aashima Lakhanpal: Working in teams only going to get tougher. We’re gonna adjust to a new reality. Remote, global, complex teams, diverse teams, multicultural teams, it’s going to get better or probably as I say, complex. But if this gets more tougher, learn that your team members key motivation and learn how to pair it with yourself. There is no harm in realizing the fact that these decisions are being taken based on how we think or belief or our system. t’s almost like saying biases is, is going to help you take these decisions, learn your team member’s key motivation to pair it with yours. That was my strength supporter model that I had. I might, and I’m very conscious that this is again, bias at its best because I have simplified it to no extent.

Aashima Lakhanpal: I would love to hear from all of you if you feel like there is anything that has helped you personally work through a team as you work through biases, their own yours and what has helped it work better. But let me know if there’s any more questions here. Oh, I love the comments, ladies. I really appreciate all of this. It makes me feel like you all have been in the same boat at some point and this is a fantastic way of saying we all acknowledge each other’s status where we are at.

Aashima Lakhanpal: Thank you for sharing these comments. It means a lot. I see Susan, your question, which pairs best, in my opinion, it totally depends on the project that you’re trying to do. I have noticed myself work better with an influencer if I need to kind of market my project a little better. Like I am an executor and I feel like I really wanna get extra hours done to get this out. But when I pair myself with an influencer, I feel it’s fantastic. They know how to market it, they’re kind of filling the holes that I don’t have. I also have seen an executor work really well with a strategic person just because they kind of build the bigger picture and I’m kind of, you know, filling in the gaps. I kind of feel like it totally depends on the project, but you can make a pair out of anything.

Aashima Lakhanpal: It’s just a matter of knowing what that motivation is and how you can pair it with you. I love Jennifer, your comment. It is better to lead with your dorkiness, but I I really appreciate this comment. It means so much. Which type of struggle do you collaborate with most and what strengths do you lean on to make it successful? I have worked through three different global jobs and all of them have involved working with people from totally different cultures. I remember working in Ireland at one point and I could feel no relation whatsoever to the audience just because I have been an Asian all my life. It was very difficult to understand what motivates a general Irish person to say, I’m going to go to work today. And that was my, my struggle is because I couldn’t understand where someone comes from.

Aashima Lakhanpal: Marketing was in general an issue. I couldn’t understand what meant work was, you know, what kind of work could I get for myself? Just kind of setting that example or an idea of where does someone come from? You’re not going to live their life. It’s going to be tough to walk in their shoes, but even if you can get an inkling or a fraction of an idea of where someone comes from, it makes it so much more easier to take that journey together. And I think that’s where my struggle has mostly been. It’s just understanding that now I’m in a new setup. It’s an entirely new vulnerable environment. How do I understand where this other person is from? Sarah Love that lead with Dorkiness. That’s absolutely happening. Thank you Susan. I know an executor cuz I feel like I always put in the hard hours and yet at the end of it when someone says, well, you didn’t challenge us enough, it almost feels, you know, that I’m breaking my heart because, you know, it is just a bias that I’m learning to live with and working around.

Aashima Lakhanpal: But yes, I, I appreciate the perspective too. One challenge is multiple time zones and setting a meeting time. Greta, I cannot plus one this comment so much just because having, you know, living ha I have an entire family in India and each time I’m trying to get basic things done and, you know, making time for my parents, making time for my family here, it just seems like a massive task to kind of understand that, you know, just showing someone that I’m trying to be inclusive is an appreciation in itself, which is what I started doing here. Each time I had a festival back home or each time I had something that was important to me, I made sure that my team members were aware of it too, just because that would just drive home the point that, look here is my motivation to doing what I’m doing, or here is the motivation why I’m doing it.

Aashima Lakhanpal: I think people are in general nicer because they want to pick up on things that you’re learning, doing, et cetera. But I I generally love the fact that we have so much more to learn from each other as teams that it makes me excited that I love the fact that people here are accommodating and I say, look, I’m trying to adjust this time to make it work for you. Just acknowledging that is enough for me and I think that’s done wonders for my wider team too. Shannon, I love the fact if you feel like you know, your main trait is a relator you would absolutely pair well with someone who’s a strategic person, especially because you are the person who’s going and building out that relationships and driving off people’s energy.

Aashima Lakhanpal: A lot of people I know, especially in the tech space sometimes kind of feel like this, it does the opposite for them when they’re trying to build this relationship trait. You know, it’s, it’s an effort, you know, it’s wearing them out, but this strategic person can actually bring in those extra traits and see those five steps ahead. I love how you’re thinking about it.

Aashima Lakhanpal: There is a project, this is a perfect way of thinking about how better to pair your team members. Like how better to think about who works better in pairs. So absolutely. Plus one to that. Michelle thank you for sharing. You had a project in the rest, were in Germany and India. They asked me for my preference. That is fantastic On your end, Michelle. I think these are smaller things and you do not even, I can’t even begin to place how much it means for people who are in different time zones to know that someone else has appreciated their calendar.

Aashima Lakhanpal: I really think that’s a plus one to saying, well I acknowledge where this is coming from. So yes, absolutely. Plus one to that. Melissa, someone who’s worked with a team mostly in India and East Africa, it’s tough. I agree. It is absolutely tough and it’s a nightmare at some points. But I like I keep saying, acknowledging step one, step two I think is, you know, your action always kicks in. You’re always doing the right things by saying, look, I’m trying to adjust the calendars to the best way I can. I wonder how these categories pair with Myers–Briggs. Jennifer, you bring a fantastic point and I think this is a good, good insight into this is that Myers–Briggs has evolved over a point. It feels like, you know, what we used to ask before in terms of, you know, where do you fall and what kind of personality trait are you that has become better with time.

Aashima Lakhanpal: We also have more modified versions. Anisha, you are pointing out to StrengthsFinder. That’s another fantastic way and I urge all of you to take a look at these tools. Sometimes they’re a fantastic way of throwing an insight into are you this person or not? They are more detailed, they’re more technologically advanced in terms of how they’re asking you the right set of questions.

Aashima Lakhanpal: In fact, StrengthFinder gives you all of your 35 plus strengths listed out for you. And that’s a fantastic thing if you’re trying to analyze yourself. Like it helped me understand how much of these traits were needed, which were my dominant traits, which were my lesser dominant traits. Kind of gives you an insight into where can you lean more. But this is fantastic because these are tools that are actually helping you guide to understanding yourself as an individual. I had just, like I said, this is bias at its best giving you a four point decision to say, look, here is what you can do for the next time you’re trying to work in a team better.

Angie Chang: Thank you. Thank you so much. This is an excellent talk. I think we have lots of questions. If you’d like to hang out, I’m sure people will like to chat with you in the lounge. Thank you again. Absolutely.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Sukrutha Bhadouria: Our next talk is by Odette. She is the head of growth at Onramp, a company that builds technical apprenticeships for companies. Before Onramp, she spent over 12 years at Girls, Inc, where she worked with corporate partners to design and skill programs for girls of color in Oakland and New York City to explore careers in STEM and finance. What an amazing, amazing journey. Welcome, Odette.

Odette Nemes: Thank you. Thanks for having me. And can we please give a shout out in the chat to this Girl Geek X team? They have just been working their butts off to put this fabulous conference together so that we can all celebrate International Women’s Day and Women’s History Month together. Thank you to the team. It is so much work. And you’re at the homes stretch today. So here we go, y’all welcome. We’re gonna talk today about the talent system and how it’s broken and finding better ways to hire. As was shared, my name is Odette. My pronouns are she, her and ella. And I’m the head of growth Onramp. If I don’t get to your questions, feel free to reach out to me over email or on LinkedIn. My contact information is there.

Odette Nemes: First and foremost, I wanna ask you to brace yourselves. I’m a straight shooter. I was born in Puerto Rico and I grew up in Jersey, so I can’t help it. I called things out and we’ll see how this goes. I wanna just start with my identity. It’s important for me. It frames this presentation of my journey and my transition into tech – and now working to change the talent systems. I’m just really honored to be here today in the space with these powerful women and to celebrate this great day.

Odette Nemes: It starts with how I grew up for me and my interest. I was always really interested in everything that girls quote unquote weren’t supposed to be interested in – so talking about I love sports, I still play sports, I’m still getting injured. I loved math, I loved science, I love tech. And I even really liked girls. So everything I wasn’t supposed to be doing, I was in it. I check a lot of boxes basically, like a dream for a tech company, right? For their diversity survey, I can give them all the good stats.

Odette Nemes: I was born in Puerto Rico, I moved to the States when I was five. I’m an immigrant. I’m an English language learner, I’m a single mom, I’m a lesbian. And I took all of that and I took it to Duke University. I applied to the engineering school and got in and I just, I didn’t feel connected, you know. We hear the story a lot, you know, as far as I could tell. In the room, I was always only Latina. I always, the only lesbian that I could tell that was out at Duke, right? And sometimes the only cis woman in this space.

Odette Nemes: I felt incredibly isolated, disconnected and I couldn’t understand how was engineering relevant in my life and my experiences. I didn’t have any mentors. I didn’t have any community. I ended up transferring out of the engineering school, and I graduated with a degree in psych.

Odette Nemes: That led me to start working with girls of color a couple years outta graduation at Girls, Inc, really working to expose girls of color to careers where they were underrepresented, specifically in STEM and in finance. I just didn’t want anybody else to feel like I did, right, to change majors, to not continue on a path cuz they felt like they didn’t belong. It was just an incredible waste of potential. It was almost 20 years ago now, man.

Odette Nemes: I worked with a team to develop curriculum to teach middle school girls of color, HTML to teach them design thinking to teach them game design and object oriented programming. It was all very cutting edge 20 years ago. And we scaled that across the country and now, you know, happy to see all the programming out there for girls in getting them into tech. I was there for 12 years and then I left to stay home with my daughter, Camila, she’s there in the picture. And then I had my second child, Lucas. And I was very over the stay home life at that point, and that unpaid work is terrible. They’re really, really difficult.

Odette Nemes: I started looking for work for paid work that is. And then the pandemic hit. I had my kids at home with, cause this, all the preschools and everything was closed and nobody was hiring. I dug in to stay home and my marriage started falling apart, and I ended up getting a divorce. Here I was, I was at home unemployed with two little kids and out of work for three years. And I needed to find a job where I could pay my mortgage in Oakland, in the Bay Area. We know how expensive it is and to support my family on my own. It was just incredibly, incredibly stressful.

Odette Nemes: And the only way that I thought I could make this happen was to get into tech. So I got a lot of no’s. As I started applying for jobs, people were not taking my experience seriously. There’s a lot of bias from folks for people transitioning into tech, you know, non-profit work not being real work. And you know, there’s just so much talent out there outside of tech that needs to be leveraged. But I’ll get into that later. Lucky for me, my network pulled through, right?

Odette Nemes: But the hiring process shouldn’t work like this, right? It puts us women, it puts queer folks, it puts of color at a tremendous disadvantage. It’s just another example of how the talent system is broken with companies only reviewing applications cuz of referrals. Let’s be real – people who look like us, we’re not in-house to be making any kind of referrals. My former coworker of mine, you see on the slide there, Jennifer Tae from Girls, Inc, she told me about this place, Onramp, and I was like, what the heck is Onramp?

Odette Nemes: The first thing I saw was that the founder and the CEO was a black woman. And I was like, okay, Leticia Thomas, what’s going on here? And then I saw that the entire team was underrepresented from top to bottom. And you know, there were folks that had transitioned into tech.

Odette Nemes: They worked at boot camps, they worked at Google, at Amazon and DEIand startups. And they were trying to solve for the issue of why so many folks were graduating from boot camps or were self-taught and they weren’t getting hired. And at the same time, there were so many companies saying they wanted diverse talent, folks from different walks of life, and that they couldn’t find qualified folks. They were working with 75% Bipoc folks, 67% women, 25% LGBTQ. And I thought, all right, this place just looks for real, right? They’re practicing what they preach and the people that are in charge are represent the people that they’re serving. And you rarely ever see that.

Odette Nemes: I interviewed, I got the job, the universe aligned for me the week before my first day, my kids’ daycare opened up one week before I started my job after being closed for a year. Thank you. Still thanking the universe on that one. That’s where I am now, at Onramp.

Odette Nemes: We set up apprenticeship programs at companies like Twitch and Blend and Vanguard and Coinbase and Amazon and Pandora and working with companies to figure out what are the job skills the applicants really need?

Odette Nemes: How can we upskill them and train them these career changers to make sure to fill that gap and support the companies with their systems, right? How are we supporting their sourcing, their screening, their training to set up career transitioners for success?

Odette Nemes: I’m super thrilled, you know, to be able to do this mission-aligned work and life-changing work as 95% of our apprentices convert to full-time employees and they’re tripling their salaries. Feel free to drop in the chat. I’m gonna try to follow it if I can, you know, if anything of my story resonated with you and if there’s anything you wanna share about your path that you’re proud of, right?

Odette Nemes: I know that we’re virtual but I’d like to bring, you know, as many folks into the room as possible into this space. And I think it’s critical, right? That we tell our stories, we build connections and to remember, right, that when, when life gets really hard, you know, and we’re facing these difficult obstacles we can accomplish our goals, right? Still, and that it’s really hard to do it by yourself.

Odette Nemes: Let’s get out there, let’s get connected and let’s build our network and let’s remember how resilient and powerful we are, right? It’s amazing and it’s no small feat that we are where we are. Everybody in this room, in this space together considering all the obstacles, you know, that you all have overcome. Take a moment now to be proud of yourself. It’s Women’s History Month, and we’re all making history, right?

Odette Nemes: This story’s a dime a dozen, people being the only in spaces being the first. Y’all are leading teams, you’re leading companies, you’re changing cultures, you’re starting companies, you’re being bold. So pat yourself on the back. But let’s also remember that it doesn’t have to be this way, right? It should not be this hard at all. This system should not be built this way. It should not be this hard. Thank you to the powerful and amazing women that are here.

Odette Nemes: Let’s dig into what we can do about creating change. We all know that talent system is broken, okay? It’s amazing that we’re all here and especially when it comes to the positions that you’re in, in tech. So throw in there, think about your experience. I’m not trying to give anybody PTSD right now, or you know, anything really difficult to think about, but think about when you were going through application process, applying for jobs, promotions, anything.

Odette Nemes: How is the talent system broken? You know, share some examples if you want. And if you don’t wanna go that route, you know, going back down memory lane, what would you like to see changed in the talent system? So let’s dive in and get all levels set here on how the talent system is broken.

Odette Nemes: First I wanna say that we don’t have a talent pipeline problem, right? We have a systemic oppression problem, all right? There’s not a talent pipeline problem. I’m sorry. A a minor example of this – at Onramp, we have 60,000 people on our platform trying to get into tech. Just a tiny, tiny example right there. There’s not a pipeline problem. People, there are systems in place, you know, that are keeping us out of these roles and we need to change it.

Odette Nemes: First and foremost, when we’re talking about sourcing screening, yes, recruiting for only university. I see it there in the chat. I see you Angie. Then we’re hiring folks. Degrees being required. We can’t do this, okay? We can’t keep going to the top colleges and looking for the CS majors. The stats are out there.

Odette Nemes: 83% of Latino folks and 76% of black folks do not have college degrees, okay? Do not have college degrees. So if you’re recruiting at universities, you’re gonna eliminate automatically 80% of black and brown folks approximately. All right? Not a good tool for you.

Odette Nemes: The next piece is referrals, right? I got my job from a referral. I imagine most of the people in this space got a job that a referral, right? 85% of jobs are hired by referral. 85% are hired by referral. But get this, this is the killer. 91% of white people’s friends are white. Okay? Sit with that for one second, please.

Odette Nemes: The 91% of white people’s friends are white, okay? So we’re talking about 85% of jobs are filled by referral. 91% of white people’s friends are white. How in the world are black and brown women getting into these spaces? We’re not in the room to be referred. We’re not connected on LinkedIn. We’re not Facebook friends, we’re not texting, we’re not on Instagram. We’re just not connected, okay?

Odette Nemes: We cannot keep using referrals as the only system. I know that talent folks are strapped and it’s so hard and it’s easier to just look at the folks who are flagged. But we can’t, we can’t keep doing that, and expect different results. So the same deal. We’re looking in the same places, we’re looking in the same communities. We can’t do that when 95% of white people’s friends are white. We need to be in different spaces.

Odette Nemes: Another piece is poaching. And you all know the recruiters are coming after you. But the majority of the folks that are being poached are cis white men. Cuz there aren’t enough of us in positions to even be poached yet. The other piece we’re looking at is bias and interviews. We just listen to that talk on bias, man, that was some kind of sta there. So looking at bias, just your names on your resume, your experience. How about the whiteboard interview, huh? That some of you have struggled through. Yeah, that’s not assessing anybody’s skills. You can share in the chat how you feel about all that, but interviews are, the process is not done well. And I saw in the chat there at three to five interviews, it’s just, it’s not okay. The other piece is there’s no investment in upskilling, right?

Odette Nemes: Okay. Not none, but much less. Now, the research shows that upskilling retains employees. We’re looking at 98% of tech workers consider strong training and upskilling and important feature of prospective employers and companies use to invest millions of dollars in upskilling, but they don’t anymore, right? They pass the buck to the applicant now. That’s not helping our cause. And the last two things really are reviews, promotions, and mentoring. Read the research, go ahead, check out the lean-in studies.

Odette Nemes: There’s a lot of research out there about women of color. We’re not being reviewed in the same way. We’re not even giving feedback the same way, right? And then we don’t have the mentors or the sponsors we’re overlooked for promotions. The cycle is endless. And I’m not even gonna go here. We could have 18 different workshops on toxic work environments and how they’re not supportive for underrepresented folks.

Odette Nemes: I’ll leave that there. Here we go. The solve for this. Stay with me. In my mind, a great solve is the apprenticeship. Okay? It’s addressing the issues that I just highlighted. All of those issues talked about in with our barriers in, in our talent system here and apprenticeship can address.

Odette Nemes: First of all, let’s level set. There are some folks in the room that know what an apprenticeship is or has had experience with it. Please start in the chat, throw in there anything you know about apprenticeships, your experience with it, any companies that have them. The kinds of positions. Let’s just get everybody here on the same page. We’ll run through this quickly that apprenticeships are earn and learn programs. They’re combining formal learning with on-the-job training experiences. The candidates are getting training and mentorship and they need to develop the proficiency in targeted areas, and they’re also developing soft skills. They’re guided and supported by an advanced expert in the work.

Odette Nemes: And most important, I’m gonna say it again. You earn a wage during the program and then you have the opportunity to convert to full-time employment different than an internship, right? We have the apprenticeship and then you can convert immediately after. You don’t have to be in college. You don’t have to wait two years to come back. It’s immediate. It’s a full-time conversion. It’s a full-time employment. I’m sorry. They’re also from four months to two years. And I’m only talking about the US here. I’m sorry.

Odette Nemes: If you’re looking abroad, the federal governments and other countries invest in apprenticeships way better for many, many years. And their programs can be four years. They can be looped in with college degrees, but not so much here in the us. These programs target folks with zero experience, so never have coded a day in their life. Never had any experience in the position of life to some that have experience like WeWork with folks who have graduated from boot camps. Onramp. That’s why you can book at apprenticeships from four months up to two years.

Odette Nemes: And what kinds of apprenticeships are out there, right? We have registered apprenticeships. They, you have to register ’em through the Department of Labor or through individual states, and then you have to complete a certain number of hours, training components, and then really document what the on the job training looks like. And they’re meeting different competencies and at the end you get a certification or credits. And then some companies, they don’t register them and they just do them on their own. Different skill sets and positions from software engineering to developers, IT to marketing to data analysts, scientists, TPM, cybersecurity.

Odette Nemes: And you can do an apprenticeship <inaudible> and set it up. Then the specific populations, are you gonna be working with caregivers for returnships, justice involved folks, veterans, folks of color, women, it looks all different ways. And then the federal government here, they’re starting now, right? To invest, not starting, but made a new investment of billions of dollars to the Department of Labor and Department of Commerce in the infrastructure.

Odette Nemes: The state of California in itself has invested 231 million in its state budget for this year. What is the landscape? Feel free to screenshot this cuz I’m not gonna read for you. Everybody here knows how to read. But apprenticeships.me is a nice place to just get the lay of the land on software engineering apprenticeships. A lot of individual companies do them at Onramp. We set them up for other companies.

Odette Nemes: Then they’re various positions. You can look at the Department of Labor website to find them on an Accenture or great leaders in this space. And then we’re looking at different demographics looking at veterans or caregivers or previously incarcerated folks. And then third-party intermediaries. Everybody’s not on here, okay? It’s just a start for you all to reference. There’s so much work out there that you can dig into.

Odette Nemes: What are the benefits? Why are we talking about this today? First and foremost on the DEI side, obviously we’ve hit this over the head. We need different systems. The other part is with an apprenticeship, you bring in a cohort model, so they’re not gonna go in as an only, right? This really impacts inclusion and belonging and you’re building your ecosystem. When we said 91% of white people’s friends are white, well now you have people of color and then they’re gonna bring in their friends, right?

Odette Nemes: If we’re hiring 85% by referral, well let’s get the referrals in for the underrepresented folks then career changers. Man, I’m imagine there are plenty of career changers in this space. We’ve heard so many different paths from so many different leaders today. But you acquire many, many skills in the different jobs you have. Career changers are more productive, they’re curious, they’re agile.

Odette Nemes: Think about it, somebody who’s doing a bootcamp on the side while they’re juggling a full-time job or they’re taking care of their family while they’re learning to code at night. These are folks that are agile, they’re curious, they love learning. They’re gonna learn new technologies, which is what you have to do to be successful. Anyway, these are all the traits that you’re looking for in folks.

Odette Nemes: What our partners say is the Onramp apprentices are promoting faster than university grads, and we really think that’s cuz of the soft skills that these career changes are bringing. The other part why you wanna do this is, is impacting the DNA of the company. Start early if possible, right? Some companies here have 10 employees, 50 employees, a hundred employees, starting, get some apprentices in play. You’re creating a culture that values your employees, you’re mentoring your diversity, you’re upskilling.

Odette Nemes:It’s a little bit more difficult to move the needle later, you know, to have that huge of an impact on your DNA, but it definitely still impacts your teams no matter the size of the company. Then it’s a strategic investment, right? You’re getting, you’re investing in your future leadership and employees are feeling invested. They’re staying in their positions longer. The apprentices are trained so they have a different kind of commitment to you, and these are your future leaders. All of you who are looking for, we need mid-level talent, we need senior talent, it’s diverse. Well, your apprentices are eventually gonna be that.

Odette Nemes: How does this help you quickly? It helps you retain the employees that you have in place now. It’s giving them mentoring and leadership opportunities. It’s changing your culture. Forget this diversity theater. This is a real change here right now cuz the layoffs and the pandemic fatigue, the morale can be a little low. You’re gonna be bringing in energetic and engaged teammates. You’re doing a lot of cross-functional work and building up your cohesiveness and mission aligned work. People are tripling their salaries, you’re changing lives. They’re buying their first homes, cars, paying off loans. This impacts generational wealth, right? This is impacting lives, families, communities, and people are staying in their roles.

Odette Nemes: They’re feeling less burnout and you have more balanced employees. Why now you might be like, oh, they, why are you talking about this now? The economy’s so bad, folks are getting laid off. I think that there’s not a better time than now to be putting this in place, right? You’re hiring, you’re gonna commit to hiring in an equitable way. Right now is a time when talent teams are not overwhelmed with filling headcount.

Odette Nemes: Get your systems in place now, right? Get these intentional systems, these equitable systems in place. Now build the infrastructure and then scale it. You know that the economy’s gonna turn, we know these companies are gonna start hiring again. Once they’re ready, you have all your systems in place, then you scale and you can bring in even more apprentices and change your culture.

Odette Nemes: There’s also a lot of partners out there that can support lean teams at this point. We know a lot of diverse folks getting cut right now. How are we gonna find diverse folks? Let’s do this through apprenticeship and digging into values for sure. And people are looking for jobs now, right? They’re looking for signals. Well, companies are really committed to DEI. This is a great way to send that signal.

Odette Nemes: You’re bringing in folks at a lower wage, right? Because they’re entry level, but you’re also retaining them longer and there’s lower churn. Of course it’s that’s good for business and you can get federal and state funds to support your work. What now? How do you make this happen? Hopefully you’re thinking that, right? Oh, this sounds great on it. Think about how are other ways that you’ve changed, made change happen in your company. What were the keys, right? This is similar to setting up an apprenticeship program. You need to enlist others, you need to be that evangelist.

Odette Nemes: You don’t need your entire company, you just need one major champion, right? And then you need somebody to be able to sign off. Maybe that’s you also in this room for sure and sign off on things. And you need your advocates around you. And then you need to think about your mission and your needs. So what are the goals of your company? What’s going on with your headcount? Do you need, what are your needs, right? Do you want entry level folks? Do you want higher skilled folks? Are you looking for future leadership? What’s the mission alignment with the population that you would wanna target in your apprenticeship? Or are you just looking for top diverse entry level talent? Well, take it. Then you need direct supervisors and mentors, right? Because the apprentices need to be supervised and and mentored by the right people.

Odette Nemes: You need those champions that are really gonna do a great job with your pilot. Of course, you need your headcount to convert folks at the end and then your pilot has to be con successful. You need great conversion rates. Then people are gonna be like, oh, it’s what those apprentices, I want them on my team too. And the budget of course can come from eng and L&D and HR and DEI, as you need to find the right talent.

Odette Nemes: Make sure you’re recruiting, you’re sourcing, and you’re interviewing for potential. Okay, no whiteboard interviews, please. And that you’re training is on point. So last things before we go, I just wanna share a quick story about Jomarie, she’s a Dominican woman who went to a private high school on scholarship and took one computer science class in high school.

Odette Nemes: Nobody looked like her. She thought she didn’t belong. She went to college, she got her BS in nutrition sciences. And then after college she became a sales manager at anthropology in Urban Outfitters. And after that, she moved into recruiting. She was there for five months, the pandemic hit. She lost her job and she went to a bootcamp.

Odette Nemes: When she completed the bootcamp, she heard about Onramp through Twitter, and saw that we had a position, an apprenticeship with Twitch. She got the apprenticeship and now she’s been done with her apprenticeship. She’s been a software engineer for a year and a half, and she’s been promoted twice in a year and a half. You can see her on the stage here. She was presenting with the Secretary of Labor, Marty Walsh, sharing her story and spreading the good word about apprenticeships.

Odette Nemes: She’s able to help out her family now and live in San Francisco, rent and afford her rent, live her life. And she’s giving back. Now she’s mentoring apprentices, delivering workshops on self-confidence and communication and how to ask questions. Jomarie could be your next teammate out there.

Odette Nemes: The moral of the story people is that we need you, right? Like, yes, this is personal for me. I need to pay my bills, put food on the table. But no, the reason why I really work on ramp is I want a better world, you know, for my kids, for future generations and for underrepresented folks that are out there now. We wanna see as many apprenticeship opportunities out there as possible.

Odette Nemes: And really it only takes one person, right? It only takes one person’s idea in a company mobilizing folks internally to create these life-changing opportunities. It’s time to step up, it’s time for us to change the world and get these opportunities out there for folks. Let’s do this. That’s all I’ve got for you all. Thank you for the time. And if you have any questions or wanna reach out, feel free to connect with me on LinkedIn or through email.

Sukrutha Bhadouria: Thank you so much, Odette. This was very, very insightful and so many people have written positive comments and you know, their own experience and their own insight through their own diversity efforts. Thank you so much. Thank you to everybody who has been attending the session so far. We’ll see you soon. Bye.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Angie Chang: We have with us today Spandana Govindgari who is a staff payments engineering lead at Meta in New York. She has helped build and scale payment experiences to support social commerce across Instagram, WhatsApp, and Facebook shops and marketplace, helping process billions of dollars at TPV, which I looked up, means total payment volume. Before, she worked at Apple and Snapchat. And think she’s gonna talk about that during her talk, so I should hand it over and say, welcome Spandana!

Spandana Govindgari: Thank you Angie. Thank you for the wonderful introduction and also for having me. This is an awesome opportunity. Welcome everyone to Elevate! Hope all of you are connecting with each other. Just getting a lot of talks in great learnings. I’m here to talk about specifically stepping out of your comfort zone. I’ll be talking about why, when, where to transition to when you are feeling stuck, what comfort zone really means, and how to leave it, and how all of this can truly help you grow your career. But before we start just a little bit more about me.

Spandana Govindgari: My name is Spandana. I am currently a tech lead at Facebook working on payments. I graduated from Cornell in 2015 and ever since tried to really diversify my work experiences. I’ve been in the industry for now six to seven years, but have worked in my own startup. I worked at a pre-IPO company called Snap, which was really small back then, and also at really large companies like Apple and now Meta. So most of this talk will be oriented towards career growth for a software engineer. And I’d like to like just get a sense of like who’s in the room. How many of you here have just started working with less than one year of working experience? Awesome. And how many of you have been a software engineer for over a year? Feel free to like, use emojis or however you want to or comment here on the feed as a lot more people here have worked, looks like over here. And we also have some you know, new folks here.

Spandana Govindgari: This talk will be useful normally for like people entering the software engineering industry right now, but also for folks who have been over a year and are at a point where they’re feeling like they’re in a comfort zone and like, don’t quite, okay, what do I do next? Or how to leave it. And if there are like three takeaways I would want you guys to take from the talk, here they are.

Spandana Govindgari: It’s important to transition from corporate to startups specifically for growth as the main factor. Every day you have to continue to develop your skills as a software engineer. If you’ve been in this field, you know, every single day things are changing, new things are coming up – upskilling – it sort of becomes your core – learning new languages, so frameworks, libraries, and becoming familiar with them.

Spandana Govindgari: And the third important point is, it’s not required to really transition to management to grow. And of course, like I’ll go through each one of them and how I really arrived at all of this advice or insights from my own, like personal work experience. If you look at like, my own career journey, I’ve transitioned almost every two years. The longest I’ve worked at actually one single company is right now at Meta and reaching my fourth year. And I did this transition very early on in my career when I was feeling like I am entering comfort zone or I am in this comfort zone. I think like when you guys go back to like, when you’re starting your career, most of us are really just desperate to get a job offer.

Spandana Govindgari: Some of you may have chosen to work at a startup, or some of you may have wanted to work at a big company, and that’s that’s one of the like hardest crossroads you’ll find yourself where you have to make a decision. I was in a similar crossroads when I started. I had two offers, one from Uber and one from Apple. At that time, Uber was a really small startup, and Apple was a giant and still is today. Both of them are really good companies. I had good team, lots of learning and at the very beginning of my career – how do you choose which company to start off or kickstart your career with?

Spandana Govindgari:  I’d say like, the most important thing I focused on was really like mentorship and where I could find a solid mentor who would have the time to help me grow. And I got exactly that at Apple. This laid a strong foundation for me to leave my comfort zone. Later on in my career journey, I thought I’m just, you know, going to continue to work, work up the ladder in one company.

Spandana Govindgari: But as I was hitting my one year mark, I started realizing I’m already feeling kind of stagnant. I was feeling like, you know, I’m not learning anything new or I’m growing. Basically I felt like my learning curve has reached to peak and everyone’s learning curve is different. I’ve listed here some signs that you should really watch out for when you should transition.

Spandana Govindgari: And I’ve spoken to a lot of other software engineers as well, fellow female engineers about some of these signs where they felt like either stuck or kind of fi trying to find new opportunities for transitioning. And some of the signs are really like, you know, not learning anything new, important sign, getting stagnant, having conflicts in your team that are beyond resolution.

Spandana Govindgari: Not getting rewarded, not getting enough visibility, which is a very big one for women overall. You’re feeling dissatisfied, going to work. When you see all these signs, that’s a great way to know that it is time to transition and why should you transition, right? If you look at the bubble here, the bubble is where your comfort zone lies. But outside is where the magic happens. In your comfort zone, you feel safe, you feel like you’re in control, you know all your teammates, you know your, the company, you know how it works. You have a cushion, right?

Spandana Govindgari: But you are still finding yourself walking into it every day feeling dissatisfied, disinterested. That is why you leave your comfort zone in order for you to grow and really achieve that fulfillment and satisfaction. And in order to leave your comfort zone, really like three things should happen. First of all, you need to conquer your fears. You should be open to learning and thereby you are going to grow. And that’s the reason you should transition. You know, as soon as you are feeling like you are in your comfort zone, but you know, how do you get out of it really? There are fears on the other side, uncertainties. There’s just new challenges that you may not be familiar with, right?

Spandana Govindgari: In order to really get out of your comfort zone, start with your own workspace and try and find opportunities that are kind of out of your own role or out of your own team first. Take the baby steps and then take the big steps. If you’re not able to really find opportunities within your own team or within your own company, then look for opportunities outside.

Spandana Govindgari: You should consistently be on the lookout for these opportunities because they will not just walk to you if you are not specifically looking for them. And how do these opportunities really look like? They come in the form of helping your recruiting team hire or interview candidates. They come in the form of mentoring other women engineers. These are all that go above and beyond your role, but in some way, extending your comfort zone so you can con your fears, find mentors, right? Remove those excuses that is stopping you from leaving your comfort zone.

Spandana Govindgari: And then you will find this crossroads. Really, you have two choices in the tech industry in order to grow. First of all, you know, if you’re at a big company, work at a startup. If you’re in a startup, work at a big company.

Spandana Govindgari: It’s important to diversify these experiences earlier on in your career because once you’ve worked at, I guess, like both sides you’ll really understand the industry as a whole, how it works, and kind of be ready to take on anything that comes your way.

Spandana Govindgari: Startups offer various different things than corporates. Obviously. They offer accelerated growth. You get to take on a lead role you know, more responsibilities, more I guess like roles you can play within a startup and more learning. Big corporates, they come with their own advantage, right? Like, there is slow and growth, maybe lesser responsibilities. Your work is defined, but it’s a stable environment for you to really grow, experiment, conquer those fears slowly.

Spandana Govindgari: And no one’s really like pushing you to sort of fill this gap. They offer really two different kind of experiences. And it is important that you have experience of both. You can in the future delve into something deeper. And however, regardless where you work in a startup or big corporate, every software engineer comes across another crossroad.

Spandana Govindgari: This is a crossroad. You have to choose between going to management and continuing down the IC ladder. And this path is something that is laid out and is standardized across the industry, and many think management is easy, I’m gonna get wider visibility. However, it’s not always straightforward within management as well. There are some skills that are super different if you’re becoming a manager versus like an IC.

Spandana Govindgari: And today I’ll talk more about what it means to really continue down the IC path because it is a road less traveled. And something I have traveled as as well when I was at, at these crossroads and decided to choose the IC path. Most people think I’m just gonna go pick management. It’s sort of a promotion. Right? But that is the perception. Reality is, it is not, doesn’t matter, you’re a manager, an IC.

Spandana Govindgari: It’s the impact that you’re making that really versus like all the reward, the visibility that you get within a company. If you look here, I’ve listed basically some of some of the essential roles and responsibilities as you are climbing up the ladder. Let’s say you’re at that principal IC level, or that director or manager, senior manager level, the kind of words or that stand out in the IC role is collaboration, avoiding duplicate work, understanding the domain, executing, mentoring, building relationships, and giving back in a manager’s role. Or as you are climbing of the management ladder. Or really the standout words are coaching, building culture, planning, roadmap, determining what each teammate does.

Spandana Govindgari: Giving feedback now, you can see is like stark difference between what you wanna do versus like the reality in terms of what actually an IC does as they climb up the ladder versus like a manager. Based on this, you can decide through the, through that important crossroad of yours, whether you wanna continue down the IC path or the management path.

Spandana Govindgari: In industry, it is fairly common to switch between both. You’re an IC go to, you are like, I wanna try management, go ahead, do it. If you’re a manager, you are no longer interested in doing management, you can switch back and continue doing IC work. And none of that means like you’re promoting, you’re getting promoted or you’re getting demoted. Both of them are separate tracks and both of them you know, do work that definitely impact the org.

Spandana Govindgari: That is why we have wonderful, great ICs still in a company and not everyone’s a manager. And we also have managers and directors helping kind of grow the org. But they are just focused on very, very different things. I decided to actually choose the IC route and not go through management yet in my career because, I wanted to deeply focus and execute within my domain and develop a deep understanding of payments over. And, you know, like you may be seeing mostly in your own company, and it’s very common to like see you know, maybe like your role model or some I see just transition to management and that those sort of examples I guess are very common within the industry overall.

Spandana Govindgari: Where do you, I guess, like to look for when at least I was, I was starting out as like, who are those strong IC women engineers? I can look for who are these role models? And surprisingly, like, you know, Marissa Mayer – she was the first female engineer at Google. She was an IC, her IC work you know, eventually contributed great deal to Google led her to the path. She did eventually, you know, she became the CEO, which is like a management path, but it is important to shine light on the fact that she was, she started out as an IC, Ruchi. Ruchi Sanghvi is the first female engineer at Facebook, eventually went down this VC route, which entirely different. But she was an IC as well. Both of them built great products. They were significant in the company’s growth.

Spandana Govindgari: The work that ICs do is really, really important. You can choose to take the re road less traveled, or the one that is often, but it is important to leave your comfort zone in order for you to really see what’s on the other end where the magic really happens. With that, thank you everyone. I hope you’ve learned something from this session specifically about identifying science for when you are in your comfort zone, and then how to leave it confidently in order for you to really grow your career. Thank you.

Spandana Govindgari: I’m happy to take some questions because I know we ended a little early, I will also post my LinkedIn if you guys want to connect with me post session. Always looking to connect with more women. Oh, Angie. Hi, you’re back. No, do you wanna answer questions? Yeah, sure, so I see the first question.

Spandana Govindgari: How can you recognize when you’re out of your comfort zone versus truly out of your depth for your current level? This is a great question. When you’re out of your depth for your current level that may not mean you, you’re out of your comfort zone. And what that means is there’s just more room for learning versus com comfort zone really means, you know, that learning has peaked.

Spandana Govindgari: I feel like you can always address the depth and you can almost go deeper, but there is some point where you may want to explore that depth at a different company with different challenges. I started at Snap within payments and then I decided I’m going to explore payments more deeply at Facebook. Snap was small company. I wanted to work on payments at scale which is a different problem. You really can go deep at a company like Facebook that’s handling billions of, you know TPV.

Spandana Govindgari: Transitioning and leaving your comfort zone ultimately also improves the depth at your current level. I hope that answers your question. Any other questions?

Angie Chang: Is there another question or is that,

Spandana Govindgari: Yeah, there is one more. I hear so much about coaching, giving feedback, and building culture for managers. However, I’ve seen only one manager do that so far. What does the ground reality of what managers do? The, that is terrible <laugh> The ground reality is that managers are supposed to be coaching, giving feedback, and building culture every single day exclusively if they are, if you, you are seeing only one manager do that so far in your career or I guess your company is important to also like, have a conversation with your HR about what manager role means at your company and what the roles and responsibilities look like and how you could become right a, a manager yourself. If the responsibilities are different, it’s important to like, take the slide as an example and ask your HR team to really lay out, you know what, I’m an IC, please, you know, these are my responsibilities, this is the level I’m at. How is it different from what a manager is doing? Can I please, you know, get a rundown? And having that clear distinction helps you really understand the, the differences in roles and responsibilities. I would advise you to definitely be in touch – feel free to talk to your HR team on your career growth team that’s laying out what these roles and responsibilities look like.

Angie Chang: Great. Is that the last question? Okay. Thank you so much Spandana for joining us today on International Women’s Day. I think we’re gonna be jumping into a final speed networking round. A little bit of housekeeping before we go to do that. All of these talks are recorded in Airmeet right after the session ends. You can replay it by going to your schedule on replaying. If you have a meeting and you miss out, it’s okay – come back. This event’s still going on tomorrow. It’s free. Tell your friends there’s a career fair people are hiring. And there’ll be also really great talks and workshops on how to get your resume together, how to, and how to negotiate, offer, understand a company culture, et cetera. I encourage you to tell your friends, come back tomorrow and we’ll see you then. Okay

Spandana Govindgari: Bye. Thank you everyone. Thank you Angie.

Angie Chang: Thank you.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Angie Chang: My name is Angie Chang and I’m the founder, co-founder of Girl Geek X. I’ve been organizing events in the San Francisco Bay Area for over 15 years, and this is our first virtual career fair. I wanna take a little bit of time, one minute away, from our keynote speaker to talk a little about the sponsors that are supporting us today, cuz they are hiring and as you know in the headlines, there are layoffs and your friends are probably looking for jobs. Please tell them about this free event that’s happening right now today!

Angie Chang: There are recruiters from Autodesk, Cadence, United States Digital Service in Washington D.C., CodeSee and Dematic. And I’m gonna tell you a little bit about their booths. If you wanna go check them out at 12:00 to 1:00 PM today, there’ll be recruiters there. A quick rundown of those booths, I walked around this morning and they look amazing. You should go look at them and meet the people at these companies. They’re very friendly and they love answering your questions about the industry, their jobs, what it’s like to work there, how to get your resume into tiptop shape.

Angie Chang: I hope you’re going to a lot of the sessions today are very, very useful toward getting your resume and interview to be in a place where you can be successful. So Autodesk’s Booth has round tables with recruiters from Tech, Sales, and G & A. They also have a women’s group network that is gonna be there. So please go talk to them at noon to 1 Pacific time. There’s also Cadence and they have round tables for Cadence Careers and to learn about Cadence, culture or life at Cadence. So please go check out Cadence Booth at 12 PM to 1 PM today.

Angie Chang: United States Digital Service in DC has posted round table times in Eastern Times, so I’m going to just tell you them Pacific Time cuz that’s where I am and I had to do this math this morning. The design table is currently, I think occupied and there’s someone there in the USDS booth. They have a Talent roundtable at 10:00 AM Pacific. They have a Product roundtable at 11:30 AM Pacific. And their Engineering roundtable, if I’m doing the math correctly, is 12:30 PM Pacific Time. Go check out the USDS booth for their tables at those times. And CodeSee’S Booth has posted a sign that they’re in the lounge and that their CEO is going to be giving a developer workshop at 11:30 AM Pacific time today if you wanna learn about how to stand out in this job market, for developers who are current and aspiring.

Angie Chang: And last but not least, Dematic’s booth has a round tables about Culture and Dematic Careers. Please go check out their booth and talk to their recruiters and staff today in their booth. I saw the lounge table, they had lots of people there, so go talk to them when you have a chance. They’re really great and nice people.

Angie Chang: And now it’s time to our keynote speaker. So without further do, I am going to introduce you to Judith Syau. She is a senior software engineer at Stripe. She works on internal tooling and prior to Stripe she worked at startups in IoT and Consumer Marketplace and she’ll be talking to us about understanding company’s culture before accepting a job offer. So welcome our keynote speaker, Judith!

Judith Syau: Thank you so much Angie. Thank you all for joining and hope you’re having a great time at the Girl Geek X Elevate Conference so far. My name is Judith and I’ll be talking about how to understand company culture before accepting the job offer, so hopefully you can come out of this session with some useful tips and tricks that you can use throughout the rest of this conference and beyond.

Judith Syau: My name is Judith, I use she her pronouns, and I’m a software engineer at Stripe based out of San Francisco. Stripe is a payments processing platform for the internet and I’ve been working at Stripe for the last two and a half years as a full stack product engineer and currently on a team building internal collaboration tooling. Prior to Stripe, I worked at a couple other startups. I’ve actually worked at three different companies in the first three years of my career.

Judith Syau: The thing about startups and smaller companies is that it’s really hard to get a good sense of what working at a company is like unless you personally know someone there, which is why I’m here today, to share strategies you can use to research company culture so it’s less daunting to go out of your comfort zone and consider you’re working at a company that you don’t know much about.

Judith Syau: In today’s session, I’ll be covering ways to research company culture throughout the entire interview process, starting from networking strategies before you apply all the way until receiving and negotiating the job offer. And if there is any time left at the end, I’ll also be answering questions in the chat. Definitely keep interacting in the chats and let me know your thoughts throughout the talk. Cool.

Judith Syau: Let’s start off with some networking strategies. Why is networking important? Networking is important for referrals, which get your foot into the door when a cold application doesn’t work. How do you build a network at events such as career fairs, conferences like this one? You can get contact information of not only recruiters at the career fair, but also your peers at networking sessions and follow up afterwards via email or connecting on LinkedIn.

Judith Syau: You never know how valuable a connection is and it could be the key to getting your next job if there are specific places you want to work at. You can search for employees on that you share experiences with, such as people who went to the same college or worked at a previous company together or are part of the same community and use that as a starting point for connecting.

Judith Syau: Often that shared connection is what gets people to respond. So like if you have a mentor at school or work or know someone a little bit more senior than you in their career, you can also leverage their network and ask them to introduce you to people. And there are also several tech communities and groups out there that have job boards, networking and mentorship events. Even if you don’t have an existing community, there are plenty of them online that you can find. If you have a favorite networking strategy that I didn’t mention yet, feel free to share it with others in the chat. Cool.

Judith Syau: After building up a network and scoring the interview, let’s go over some useful questions to ask. First of all, make sure to tailor your question to the who you’re interacting with so that you can get the most useful information. For example, you might be interacting with the recruiter or an interviewer for the same role such as engineer or a potential future manager or a hiring manager. And let’s go over some examples of these questions.

Judith Syau: Questions about the day-to-day job are good to ask someone who shares the same role that you are interviewing for such as an engineer. You could ask what are your favorite or least favorite parts about the job? What is the most stressful part about your job? Or what is the on-call rotation like? For example, if you’re working on a team or product that’s supporting multiple regions across the the globe, different countries, different time zones, you might be getting paged at odd hours and that’s something that you might want to think about before you accept the job offer.

Judith Syau: And then you should also ask people how they would describe their work-life balance. For example, right now I can tell you that I can make time for it to take a brush painting class at 3:00 PM on Tuesdays and Thursdays. This means I can shift my schedule to work East Coast hours on parts of the week. I also block out some time in my schedule to volunteer to teach a high school computer science class on Friday mornings. A couple years ago when I began my career, my answer to that question would be very different. I would say that I often stay late at the office for free dinner at 7:00 PM and then play board games with my coworkers afterwards. So, work-life balance goals might be very different at different stages of your life.

Judith Syau: Questions about diversity, equity, and inclusion are good to ask recruiters. They often have the most up to date data about this. So for example, you could ask what ERGs or employee resource groups are at the company. For example, this could be like like women or parents or for example my company has like an east and southeast Asian employee resource groups and we do we celebrate like lunar New Year and we have like book clubs and, and things like that.

Judith Syau: Another good question to ask is what is the ratio of underrepresented minorities in leadership? Companies often will like brag about their diversity statistics being, you know, better than average, but the more you go up the career ladder, the more like the more senior and more leadership positions, the more the numbers dwindle. And lastly you can ask what has your company done to support current event? For example, during the Roe versus Wade Supreme Court decision, several companies made public statements about covering abortion related travel expenses. If there’s a current event that might be applicable to you or that you care a lot about you should definitely ask about what the company’s stance is and how, what they’re doing to support employees. Cool

Judith Syau: Next we have career development questions and these are good to ask a hiring manager. A good question to ask is what does it take for someone to be successful in this role? Maybe the manager already has some expectations that they can share with you. This could also be reworded as what would success look like six months down the line? And what advice would you give to someone who just joined?

Judith Syau: And what is the performance review process like? If you are trying to get promoted soon, you you could ask this question to see if the expectations align with what you’re aiming for. And then lastly, an interesting question to ask might be, why is this position open? Maybe the team is trying to backfill someone who left either by choice or not by choice. Or maybe the company is growing really quickly, like they want to double their headcount by the end of the year. And all of this could have implications on the company culture. I know I talked about a lot of interview questions, but there are probably plenty more that would be useful to ask. Share your favorite interview question in the chat if you have one <affirmative>. Cool. Other than asking questions during the interview process, you can also do some research about what public thinks about the company.

Judith Syau: First, let’s start off with company trajectory. Public companies will publish their quarterly earnings call, which shows how their financials perform against expectations. You can also look at how their stock is doing.

Judith Syau: For startups, it’s a bit more complicated because company financials are private and Crunchbase is an online resource that shows the series of a startup startups fundings and valuations, which is how much investors think the startup is worth. Down rounds are when a company raises money at a lower valuation than they did previously, which might indicate that they are not doing so well.

Judith Syau: However, keep in mind about the macroeconomic situation as well. For example, it’s possible that all tech companies are not doing well at a certain point in time, or certain spaces might be having a particularly hot moment like AI is right now. And not too long ago there was web3, so there are always trends in tech, some are successful long term and others might have up and downs. And you should keep all of this in mind

Judith Syau: For a public image, you can look at news articles about the industry including peer companies and competitors. For example, I work in the FinTech space, so I’m always keeping up with news about other FinTech companies. Also, company policies and reactions towards global events such as return to office policies or layoffs can be pretty indicative of the culture as well. For example, like their messaging towards departing employees or even just how they are, they treat their departing employees. Many founders and leaders are super active on social media and some of them even write blog posts and those are pretty telling of how they run their business. This could be from their like Twitter accounts to like each company’s blog section. And lastly, some companies will list their values on their website and that often defines their culture as well.

Judith Syau: Now that we know what the public thinks, how do employees themselves feel about the company? There are several online resources that reveal employee sentiment and I’ll share a few here. Blind is an anonymous forum where people can chat about their tech companies and it requires your company email to sign up. Glassdoor is very similar and has anonymous employee reviews. Comparably is a report card that rates company culture based on several employee reported factors. And lastly, we have social media where influencers post content about their role in tech.

Judith Syau: It’s important to look at multiple resources and remember to take them with a grain of salt. Someone who posts anonymously will have a very different agenda than someone who’s posting on their personal social media for their image. But one thing you can look at is current trends. Maybe if a bunch of employees are feeling a certain way about a policy that was implemented in like the last six months, that might be super relevant to you, but something that was had that happened like five years ago is probably not as relevant. Always remember that culture can change as a company grows or goes through formative events or goes through leadership changes.

Judith Syau: Let’s say you’ve done all your research and have an offer in hand. How do you make sure that you are getting paid what you’re worth? The first thing about offer compensation is to always negotiate. Every component can be negotiated including salary, stock and bonus. And you don’t know unless you try you might be even able to negotiate other benefits or maybe working hours or even your level at the company.

Judith Syau: And even if you don’t have competing offers, you can still look at data and use that to negotiate and see if you are getting a fair deal. Let’s so there are several crowdsource databases on available online. The first one that I really like is levels.fyi and I like this because not only does it show the different components of compensation such as salary, stock and bonus, it also shows people’s levels as well as their years of experience.

Judith Syau: I’ve personally, I’ve successfully negotiated my level when I accepted an offer before. That is something you could look at like to see if your years of experience line up to the offer that you’re getting. Glassdoor also has has a lot of anonymously reported salary information as well as LinkedIn and candor. Someone in the chat asked a question – are these tips more geared towards large or established companies? For a lot of these resources, obviously there will be more data on large companies, but personally I’ve used these to interview at small startups and surprised like what information you can find out there. I think the tech community is very big and a lot of people will be interviewing or talking to the same companies even if they are very small.

Judith Syau: For governments jobs, they publish all of their salaries online, it’s public information and if the company sponsors H-1B visas, the H-1B visa salaries are also all available online. And if you live in a state that has salary transparency laws, for example, California now requires all companies to publish like a salary range for the role. That’s super important information that you can leverage. Some other states might have be required to reveal the salary ranges if you ask them or if you pass the interview a certain interview stage. Definitely look up the applicable laws for your state that you live in and use that to your advantage. And for startups it’s a little bit more complicated because a big component of the compensation is equity. And for this, there’s a super useful guide online called Holloway’s Guide to Equity Compensation that shares like what is reasonable percentage of equity to expect at different stages of a company.

Judith Syau: And definitely share any other information you might have in the chats that I haven’t listed above. Hopefully you’ve learned something valuable in this session and are able to apply a combination of these strategies to understand company culture a little bit better and maybe even use that during the career fair later on today. Thank you all for joining. I’ll be answering questions in the chat for the remainder of the time. I think we might be at time. Feel free to stick around or use or contact me on LinkedIn or via my email. And hope you’ll enjoy the rest of the summit.

Angie Chang: Thank you Judith. That was really a great talk on company culture and how to evaluate. I like the part about networking to get your foot in the door, especially if you don’t have a referrals or an in in the industry. It’s a great way to get that in. There’s plenty of people here who will like to refer somebody, so I’m gonna say thank you so much for joining us and we’re gonna be hopping over to our next session soon. Thank you, Judith.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Sukrutha Bhadouria: All right. Hi everyone. Welcome. We have an amazing speaker here, Korene Stuart is the Director of Programming at G{Code}. She volunteered for Black Girls Code Miami, then became Tech Lead, hoping to increase the number of underrepresented women enter into tech careers. That’s so amazing. She has facilitated career and scholarship workshops at Girl Develop It.

Sukrutha Bhadouria: We’re so excited to welcome Korene, who will lead a workshop on building a technical resume. This is so important. All of us struggle with it, especially when we’ve been in the workforce for a certain amount of time, or even when we just graduated. So Korene, your session’s going to be super important for all of us.

Korene Stuart: Hopefully, hopefully I can give a lot of gems and people can walk away knowing exactly how to start their resume. So, <laugh>, thank you so much, Sukrutha. I really appreciate the welcome. Thank you. Thank you. I’m gonna start sharing my screen. So welcome everyone.

Korene Stuart: Welcome to building your technical resume. My name is Korene Stuart, and I am a director of programming at G{Code}. A little bit about me. I taught myself coding at first through freeCodeCamp and then went on to a nonprofit bootcamp and then became a programmer eventually getting into project and program management.

Korene Stuart: It was a contrasting journey for me through and through, as I did not know anyone in tech. When I decided to begin prepping for a career in tech, I only wish that I had received this information when I was starting out. It would’ve been a easier transition for me. I have spent a significant time around career preparation and have worked hand in hand with recruiters.

Korene Stuart: This presentation is the culmination of information I’ve acquired over the 10 years, and this has helped my mentees tremendously. Before we go on, I just want to say you are here because you want to invest in yourself and it requires time and effort and introspection to become your best self. So please take a moment to give yourself a hug for the great job that you’re doing. Let’s just get into it.

Korene Stuart: What is a technical resume? A resume is a snapshot of a person’s professional background, education, certifications, and work experience. But a technical resume has to specifically emphasize technical skills. It should include your technical expertise and knowledge in various areas such as programming languages, databases, software development methodologies, networking, and other technical domains.

Korene Stuart: It should include details about your specific projects, certifications that you hold, and other relevant technical accomplishments. This resume should be a succinct story about your past work life and a hint at what you desire for your future work life. And we’ll get into that a little bit later.

Korene Stuart: All right, so these are the three types of resumes that you can use. There’s a whole host of different resume templates that you can use, but these are the three that recruiters are used to seeing. You have reverse chronological resume, functional resume and combination resume, and I’ll be giving a brief explanation of what they are and show you what they look like.

Korene Stuart: This is the reverse chronological resume. These resumes are the most frequently used. Most recruiters expect to see these. They’re easier to read. These resumes start by listing each of your past jobs and reverse order your recent position being first. And then for each job title you would provide the employer employment year, and the basic requirements or accomplishments of each job. You would also provide performance figures wherever possible.

Korene Stuart: This is a functional resume. This resume focuses on a person’s skills and abilities rather than their chronological work history. It’s used when there are gaps in employment history, or when a person is changing careers and wants to highlight transferrable skills.

Korene Stuart: It helps a person stand out from other candidates by emphasizing their unique skills and experiences rather than just your work history. And it starts by listing your core competencies or areas of expertise and talent. It will then follow up with a short summary of past job titles.

Korene Stuart: Here we have the combination formatted resume, which showcases both skills and experience equally, downplays employment gaps shows career progression by providing a chronological work history and can target specific job postings through tailoring to specific job postings by emphasizing skills and experiences that are most relevant to the job.

Korene Stuart: With this resume, you demonstrate that you have the right industry transferrable skills, even if you haven’t actually had the title. As you can see, the format allows more for space for skills and the description for those skills more so than the chronological resume. All right.

Korene Stuart: Now for today’s session, we’re just gonna be focusing on the standard reverse chronological resume, the one that everyone’s used to seeing, and all that entails. Even if you were to start with this reverse chronological resume, you find that maybe you just don’t have enough to really tell your story through it. You can always kind of funnel that into a different resume.

Korene Stuart: Let’s pretend we are building our resume and I suggest you start with a blank document instead of a template, and I’ll tell you why in a bit and why that’s important. First, most likely when applying for technical positions, your resume will be going into an ATS, and ATS stands for applicant tracking system. It sorts through resumes, scans for keywords, and generates a score based on the number of hits.

Korene Stuart: It’s best to create your resume from scratch and use the enter and tab keys to set your spacing resume. Templates often contain columns, headers, footers, and text boxes. And the ATS has a hard time reading fancy formatting. If you’ve never created a resume before and have no clue where to start, you would simply just search online for simple resume examples.

Korene Stuart: I am going to give you or provide to you a supplement that will give you a link to some of the documents that I have in my bank so that you can use them in case you can’t find a very simple resume to kind of mimic after. And you can mimic the simple rresumes organization with basic spacing and alignment tweaks on your word processing program, whether that’s Word or through another program.

Korene Stuart: If you absolutely must use a template, then go to one without columns, rows, text boxes, and other complicated features or colors. The easiest and cheapest way to build a resume is to use a free template from a popular document processor or job search engine such as Google Docs, LinkedIn, or Indeed,.

Korene Stuart: Whether you use a template or start from scratch you would save your document as Word or PDF. Okay. So for resumes that won’t be scanned by software, you don’t have to be as careful about making it ATS-friendly. However, your resume’s format should still be simple. A complicated layout that’s hard to follow will turn off hiring managers – I have seen it myself.

Korene Stuart: Now if you’re pursuing a more creative role, I always suggest that you have two resumes, one that you can send through the ATS and one you can send to the hiring manager. And if you’ve never really applied for jobs, I can tell you that usually, you can send your resume through the ATS or any other system that they have, but then usually the recruiter or someone who’s talking to you preliminarily, they will ask for you to send them your resume again, ok?

Korene Stuart: All right. And be sure to choose a clean, current, and easy-to-read font. I would say choose sans-serif fonts that are easy to read, like Arial and Helvetica. For font size, go with 11 to 12 points. Depending on how much you are attempting to fit on one page, the lowest you should go is 10 points. For emphasis, make section headings by setting them just one point bigger than your general content. And now what do we do at the beginning, right?

Korene Stuart: Because it’s already overwhelming thinking about all the stuff that you have to put together. I always say put your name first, <laugh> email address, and phone number at the top. When starting your resume, it may seem intimidating. The first thing I would start with is putting your name at the top. That’s it. For some reason, it just seems to ease things a little bit. From there, type your name and contact information at the top.

Korene Stuart: Center it in a large font size, such as 14 or 16 points. Skip your address. You can include just your city and state, your email and phone number. And depending on your role, you might want to put the link to your portfolio. Put your margins at one inch on each side for more space. You can then reduce them, but not smaller than half an inch, and that would only be for the top and bottom.

Korene Stuart: Keeping the margin rules will lessen the chance of your information being cut off due to incompatibility. You won’t really have that problem though if you do it in a PDF so I always save mine as PDFs. I suggest everyone does the same. Please make sure that your email address is professional, such as a combination of name, initials and numbers.

Korene Stuart: I always say that remember that you are a walking brand. The best way for a recruiter to remember your name is to see it. My email has always included my name. The last time I had an email without my name, it was, and you would never guess, okay, in high school I had hotsuga@yahoo.com. Okay, but I no longer have that. It’s not available, so don’t email me there. And please don’t use your current work email or work number on your resume for obvious reasons. And if you are a student, do not use your university email because you may eventually lose access to it. Okay? All right.

Korene Stuart: Now you’re gonna organize your content in order of importance. After starting with your name and contact information, we’re gonna go on to the rest of the content. You will prioritize your key skills and knowledge and experience, your strongest projects. Strongest projects. Most resumes are in reverse chronological order, but don’t use that if your prior experience is more irrelevant than your current position. You can use another method like a combination or functional resume that I’ve shown you previously and that you can get that template from the document that I’m gonna provide to you.

Korene Stuart: Towards the top, under your contact information, you should write a heading, which could be summary or objective. You don’t have to actually write summary objective – you can just write it. It is up to you. But this is where you would write your professional statement, and I think that it’s really great to have a professional statement.

Korene Stuart: I think that when recruiters see professional statements, their eyes go right to it because if you’re able to really kick out a really great professional statement, it summarizes your whole resume. It just makes things easier for recruiters. Okay. You’ll use an objective in your resume if you’re straight out of a college or want to bring attention to the fact that you wanna transition to a new role. For example, you’re moving from a position of teaching to front end web development.

Korene Stuart: After professional statement, we’re gonna move on to your work history. You can name it “professional experience”, “relevant experience”, or “work history”. After experiences, you would then have a heading title “education” or “education and training” or “education certifications”, whichever is more relevant to your resume.

Korene Stuart: It’s important for you to use spacing, bold, italics, underlining and adding capitalization consistently. To add for your headings, select a slightly bigger font size than your general content and set them to bold. Capitalizing them can also make your content stand out. As for your subheadings, such as company names and positions held, use bold and italics to set these apart from general content.

Korene Stuart: You can come up with your own ways to emphasize sections and headings, but make sure you are consistent. If you bold a name of a company name, all other organizations must appear in bold. If you italicize a position, all other positions held must be italicized. Okay?

Korene Stuart: Now we’re gonna begin to kind of destruct the headings. Highlight your strengths in the summary or objective. It’s good to include key words that will generate hits on the tracking software, and make sure that your keywords are coming straight from the job description. It should be one or two sentences that highlight your experiences, key skills, and traits.

Korene Stuart: If you have issues coming up with a summary, write your experience section first. It will help you come up with ideas. For instance, you could write systems administrator with over two years experience in network security database management, IT infrastructure, provide specifics, but it must be concise and avoid using excessive adjectives. For instance, experience, hardworking, detail oriented, it’s just too wordy. Avoid vague objectives such as looking for an opportunity to grow.

Korene Stuart: They will list your technical abilities in a skills bank. I also provide that for you in my supplemental documents that I’ll be be providing for you. People often struggle with trying to come up with skills bank, but if you keep that record throughout the time that you’re working, you’ll find that it’s so much easier.

Korene Stuart: On a technical resume, a key skills section is vital. List your skills in a bank for quick, quick reference and to generate ATS hits, then detail how you’ve put them to use in your experience section. Organize your skill bank and subcategories if possible, such as operating systems, software, and programming languages. Look at the job description and use the keywords from there. Be careful to only include abilities you actually have and use. If you have basics, then say that. But if you haven’t used Java for a while, please do not include it. Only include your most relevant experience instead of your entire work history.

Korene Stuart: Use strong action words and measurable quantities to describe how you’ve utilized your skills. In technical fields, using jargon is sometimes unavoidable, but you should not use it unnecessarily. Include key facts in each experience, subheading, the title of your position, the name of the company, the city and state of your office, the start and end month and year.

Korene Stuart: Use bullet points under each position. If you can, quantify and list the most relevant job responsibilities. Let me go back up to the bullet points. Please use bullet points. It makes it easier to read, instead of everything just looking like a paragraph pushed together. White space is very important on the resume, and I know that if you have a lot of experience or education, it’s tempting to put it all on there, but just be careful that it doesn’t look like a cluttered mess – it can be very overwhelming to read.

Korene Stuart: Using bullet points helps the reader to keep track of what they’ve read, even when scanning the application. Use strong verbs such as “designed” or “implemented” instead of “writing”, “responsible for” or “duties include”. Write verbs in present tense for current jobs. Use past tense for prior experience.

Korene Stuart: Make sure to emphasize measurable accomplishments instead of just listing duties. Focus your content on actions results and how you made a difference in past positions. It can be really hard to think of all your accomplishments off the top of your head, so get in the habit of keeping what I refer to as a brag book. This is just an achievement journal where you would write an entry anytime you are assigned to one-off projects, you accomplish writing a new program, solve an issue that’s been frustrating your employer or client, implement waste reducing or improvement of processes, or spearhead a campaign.

Korene Stuart: Back to the resume. Be sure to include awards and specify business value when known. Please, when you are introducing something new or you’re spearheading a campaign, try to get what the business value is. We miss out on a lot of that because we just don’t ask. Please make sure if there’s business value that you know it. Add your contributions to building a team or project or product. Avoid leaving gaps in your employment history. While you should include the most relevant information, do your best to avoid showing gaps of six months or more. Even if the job you’ve held for the past two years is unrelated to the one that you’re applying for, included, it is just better to include it instead of someone asking you about the gaps.

Korene Stuart: I find that most people still learn during their gaps, so if you weren’t exactly working during the gap, then include the learning experiences or the volunteer work during that time. All right. And if you don’t have much experience or you’re a recent graduate, start with the skills bank, then the education section followed by any internships, academic projects, freelance work, or other related experience. If you’ve held at least two or three relevant positions, put your experience section before education.

Korene Stuart: Make sure to include your college or university degree and any accolades that you’ve received. Do not include your GPA or year of graduation unless you are a recent graduate. Just leave it off if you have a lot of certifications. There’s no need to put your bachelor’s unless it is relevant to the position. These are for the people who are transitioning. If you have a lot of education experience already, there’s really no need for you to put your bachelor’s. It depends, okay, if you’re still enrolled in school, include the year you expect to graduate. And that goes for certifications too.

Korene Stuart: List the degrees in descending order of relevance and advancement. And again, do not list multiple degrees or certifications if it’s not relevant. You can add a section for training and certifications if necessary. And if you have the room, because when you’re thinking about a resume, it is like a treasure landscape – it should only be put on your resume if it’s relevant to the job that you’re applying for. All right?

Korene Stuart: Now if you have one or two more than one or two certifications, you can put them in a separate section, title, training and certification. Mention the title, certifying authority, and date of the certification. Make sure to tailor your resume to specific job postings and as tedious as it sounds, you need to customize your resume for each job application.

Korene Stuart: The best hack I have strategically figured out is find out the three job roles that you want to do the most and only apply to those positions, instead of being all over the place and applying to 30 different job roles. I find that people who are strategic about their job search get less stressed even though they have less interviews and they get less frustrated. You are being laser focused on those three jobs, allowing you more space and time to genuinely connect and network for the roles that you are actually desiring. All right.

Korene Stuart: Make sure you read the job posting carefully. Identify the skills it lists and edit your so it targets that specific position. Say for instance, if a job description lists project management skills and your resume is thin in that area, you’ll need to include details that are true about executing a project through from start to finish.

Korene Stuart: Keep a master copy of your resume that includes all your past positions and technical skills and from there, when you apply for a job, customize that master copy, then save it as a new document with a title you’re applying for and the date.

Korene Stuart: The general rule for resumes is to try and fit it into one page, onto one page. If you have more than seven years, it is okay for you to have two pages. Name your resume, your name, job role… don’t name it “resume”. Please do not name it “resume”. Please, please, please, please for everyone out there who are looking at resumes and right now they’re celebrating because please do not name it resume. Cuz when we go back to look for your resume, we have to kind of dig through a database of resume.pdf or resume.dox and it can be a very painful effort. Okay?

Korene Stuart: Try to submit your resume in PDF formats, and I am going to include and provide the link for you. That’s about it. If anyone has any questions, I am open to that. I am going to include the… I know that’s a lot for a resume, right? <Laugh>. Oh, but I see people saying thank you for the transitioning advice. Yes. And that, that link that I just provided for you actually has a resume for a teacher transitioning into tech. And although you may not be a teacher, you would find it helpful if you’re transitioning into tech. All right?

Korene Stuart: Let me give you my contact information as well. Let me see if we have any questions. Okay. I always encourage students to include the links to their LinkedIn and GitHub profiles on the resume. Do recruiters and or hiring managers actually look, actually, look at these? I am glad that you asked that because they look at it, okay. Even when I look at resumes, if someone includes their LinkedIn, I go straight to it. I don’t even know if I spend six seconds on the resume, I go straight to the LinkedIn.

Korene Stuart: Now I do look at both, but it’s just something about having that that LinkedIn profile on there that makes you want to look at that. And the GitHub profiles, if you have a technical position they do look at GitHub profiles. Now, I can’t promise you how long they look at them, but they do look at them, okay?

Korene Stuart: Yes, if you have a LinkedIn profile, and I shouldn’t be saying if you, you should have a LinkedIn profile. If you don’t have a LinkedIn profile, I need you to create one today, okay? Let’s see. I was already asked on the feed, but I joined the question, what about resumes length? And I think I answered that. What should be on the LinkedIn profile if this is more important than resume?

Korene Stuart: I’m not saying that it’s more important than the resume. I’m just saying in combination with your resume, you should have a LinkedIn profile. Number one, it makes things so much easier for networking, okay? When you can put everything on your LinkedIn profile, you can just network with your LinkedIn profile. I give out my LinkedIn profile to almost everyone that I meet. So it’s just such an easy tool to use.

Korene Stuart: It’s not, you know, I just wanna reiterate, it’s not more important than your resume, okay? You gotta, you have to take time to work on your resume. But you should have a LinkedIn profile and try to get some connections. You don’t have to be on it every day, but try to get some connections. If you are a job seeker and you are not on LinkedIn, you are missing out. Just the information alone that I get on LinkedIn from the recruiters and I have so many recruiters on my LinkedIn feed, the information that they give out for free is crazy. You should be on LinkedIn. Should you put every single job you’ve had on your LinkedIn? Absolutely not, treat your LinkedIn like you would your resume. Everything should be geared towards what you’re looking for on your LinkedIn and your resume.

Korene Stuart: Remember I said the resume is a hint at what your future work, what you want for your future work life. You should be putting titles on your resume and I don’t know if I said that or if I emphasized it enough. You should be putting titles if you are going for software engineer, that’s what you should have on your resume. That’s what you should have on your LinkedIn profile. Some people have told me not to put it in my part-time work when I was a student. It depends on what your part-time work was. Is it relevant to what you’re seeking? Jennifer asked that Eunice act, how many bullet points are too much in the resume? Under each job description, do not put a whole bunch of bullet points if it’s not needed. Try to summarize what you did, what you did.

 Korene Stuart: For instance, if you held two projects, you were you were in charge of two projects, try to see if you can put that on one bullet point. If you have had a lot of responsibilities, try to see how you can summarize that as much as possible, but you shouldn’t have two or three. All right? I’ve seen resumes like that, you know, don’t have two or three bullet points cuz that, that’s crazy. <Laugh> let’s see.

Korene Stuart: Does relevant projects play a role in a technical resume if you are a career changer or early career? It depends on what the relevant projects are. If you have a relevant project that’s not relevant to what you are trying to apply for, then don’t put it on there. And I don’t know if I answered that correctly, if that’s what you were trying to say. Greta put, you may have addressed this already, how to address gaps in time taking care of sick family member. I would say that if you, cause a lot of times I noticed that my mentees, some of my students, they are always learning. I am a learner. There’s never been a time when I wasn’t learning something. If you are learning something, even though you’re taking care of a family member, then make sure that you’re including that in your resume.

 Korene Stuart: If it’s just a gap where you’ve done nothing during that time at all, that’s relevant to what you’re seeking, then that’s something that you would just have to explain. There’s really no way of getting around that. Do you provide resume advice for designers? Well, all resumes are basically, they have some similarities, commonalities if you’re a designer, your resume depend and see, it also depends on what kind of company you’re applying to. Because I’ve seen, and I mentioned that in my presentation, that if you’re a designer and you’re trying to really stand out from the pack, you have one resume for the ATS that goes through the ATS if you’re applying to a large company, but then you also have another resume that you present to the hiring manager and you don’t even have to wait for them to request it from you.

Korene Stuart: You can have another resume cuz I’ve seen it where a digital marketer made their resume look like a Facebook profile. You can send that to them by email by just requesting the hiring manager’s email and sending it to them directly. This is another reason why I say you must, you need to have a LinkedIn profile. You need to figure out what companies you wanna work for, what kind of culture you wanna work for you know, get those people’s names and just contact them. Not saying, well, I wanna work for your company. That’s it. Like, no, make genuine connections saying, I wanna know what you do. I wanna know how I can help your company. You know?

Korene Stuart: If you’re a designer, there’s a lot of things that you can do to bolster your resume to make sure that it stands out. Especially if you’re going to go to a company that really loves innovation and creativeness, I would definitely have two resumes for that position. All right. I see that people are talking about resumes getting passed along.

Korene Stuart: Any tips on managing career change from one industry to another when you’re already an established professional in one industry and trying to transition to a new one? Katie, I’m glad you asked that question. People have the tendency that when they’re transitioning from a company, they’re like, oh, I’m going to start entry level. I’m gonna start from the bottom. I say hogwash, okay, you don’t need to start at the bottom. Okay? I’ve done it and I’ve mentored people through it.

Korene Stuart: You have many transferrable skills, you may not even recognize it. And that’s why LinkedIn is very important to identify people who are within those companies, have conversations with them, see where the see where the similarities are in the positions that you’re trying to attain. And just start kind of you know, doing projects or maybe even volunteering to get any skills that maybe you lack, but use the skills that you have.

Korene Stuart: If you’re a manager in one industry, you can certainly be in a manager in another industry, right? Yes. It helps for the manager to have some technical know-how or knowledge that they’re able to guide their people you know, correctly or appropriately, but you’re still a manager. You still have those skills and, and, and, and, and you are able to contribute to your company. Please don’t start at the bottom, right? That’s advice. See what skills are transferable and see where you can fit in in that company.

Korene Stuart: Someone put, how do I prevent age bias if I have over 30 years of experience? Don’t put it <laugh>, don’t put it. If you had a job for, I don’t know, you know, if you had different positions in, you know, that culminated into 30 years of experience, it’s really not necessary for you to put all of that on your resume. And, and trust me, I get that. There is age bias, so I wouldn’t put it and I don’t know what your resume looks like, but try just putting the last two positions that you had. All right.

Sukrutha Bhadouria: This was wonderful. I see all the comments in the questions, so engaging and, you know, a really insightful workshop. Thank you so much.

Korene Stuart: Oh, no, thank you. It’s a pleasure. Thank you,

Sukrutha Bhadouria: <Laugh> Bye everyone.

Korene Stuart: Bye.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!

Angie Chang: A talk from Ginger Holt. She’s a senior staff data scientist at Databricks. She develops forecasting and predictive models for revenue, sales, et cetera, and has worked at Meta, Walmart Labs, HP, and BP, and she’ll be sharing with us advice for how to take control of your career. Welcome, Ginger.

Ginger Holt: Thanks, Angie. Thanks to the organizers and thanks for attending my talk on taking control of your career. This is a joint talk with my husband, Haitham Hindi, for this talk we’ve combined our collective knowledge on this topic, which is the result of over 30 combined years of a technical experience in the tech industry. In November of 2019, my husband Haitham was offered a job at Amazon as a principal researcher. We were pretty shocked he didn’t even wanna apply since we didn’t wanna leave the Bay Area, but I encouraged him to do it. I said, it’s really good practice for the job you want. As it turns out through those interviews and conversations that he discovered that it was actually his dream job. I was torn on one hand, it was a really great opportunity for his career. But what was it?

 Ginger Holt: What would it mean for my career? Would this mean I would have to compromise my current trajectory and management? We had two small children, so does this make sense to uproot them from our community and our environment? A few days later, I talked to my manager at Facebook about this decision. I wanted to explore if I could do a transfer to another role in the Seattle office. Mind you, this was pre Covid, so it never even occurred to me that I could do my job remotely from, from another location. But to my surprise, the leader of the organization offered an even better solution for me, which was a geographical change with the same role. And he said that we could make it work because of the team that we had built and the foundation and tooling that we had built, which set us up for success in the near term.

Ginger Holt: And it really hit me in that moment. The work that I had put into growing my career allowed me to navigate unexpected changes that were happening. The reason I share this story with all of you, because you will have, or you have already faced some unexpected changes to your personal or professional life. And if we face that change with a mindset that we can actually have some control and use these lessons, and I’m gonna share to navigate those unexpected situations, both me and my husband have learned some of these lessons the hard way. If I can help anybody navigate those changes, and that’s, that’s my goal.

Ginger Holt: And more specifically, there are five lessons which can help you take control of your career. A little disclaimer there about the opinions being just of me and my husband, not necessarily the companies we work for. Alright, so the first lesson here is to create clarity consensus and inclusion. I thought this cartoon was pretty funny. Let’s solve this problem by using the big data. None of us have the slightest idea what to do do with I’m a data scientist. I find a lot of these big data cartoons and data science looks pretty funny, I wanted to share that one. I’m gonna talk through this kind of lesson in with an example which is some of the work that we’re doing at Databricks.

Ginger Holt: We’re building some data science tooling to unify forecasting across the company. I’ve got a lot of my experience in the forecasting field and building something that’s very generalizable like generalizable across the company or to our customers. It really requires a clear problem statement, which is agreed upon by all the data scientists who’s who are doing the forecasting and all the stakeholders that are using those forecast and converting a bunch of standalone forecasts and processes and models into one unified framework. It requires simplification. For example, building a, a data structure, which can work with lots of different models. You load your data once, and then you can try a bunch of different different models. It also requires unified and notation and visualization so a lot of people who are using this tool can more easily onboard and work more efficiently with each other.

Ginger Holt: And finally, people need to see the value, so they want to be involved in the project. This unified forecasting framework also helps speed up what I call death by iteration, right? You solve a problem and then something changes, so you can quickly update things with new data or new use cases because of your, your clarity and your simplification. It also allows other people to quickly copy other people’s homework. Instead of reinventing the wheel and having many authors and developers involved increases both the quality and the accountability of each person involved. A little bit more on this invent and simplify concept.

Ginger Holt: As systems grow, you know, complexity naturally grows with it. And when you’re simplifying is going against entropy. It’s definitely harder work to simplify. And it’s often essential to simplify in order to scale. If you wanna do a generalize to lots of different use cases, right? You need to simplify first.

Ginger Holt: Another concept around this is to synchronize your tech code, your tech, your technical documentation with the code you’re writing. It represents best practices and notation. You can catch bugs as people understand the intent of the code, right? Looking at those side by side, it preserves knowledge in the team. With turnover, churn it opens up the system quickly to innovation from non-coders ideas, from PMs, whoever, and then it helps ramp people up quickly.

Ginger Holt: Another example. I’ve got a bullet here. Always try the simple approach first. An example of this in forecasting is, with forecasting models you always wanna compare your accuracy to a very basic or a naive model. You know how much value the complexity you’re adding adds to the problem. All right?

Ginger Holt: Lesson number two is to apologize for and fix your mistakes. Fixing mistakes demonstrates humility, honesty compassion, courage, and trust. And not fixing mistakes either demonstrates a bad leadership or a bad team culture. It can result in increased technical debt recurring problems with your code or your system, and it reduces time that you have to do truly innovative work. It can also damage our relationships and, and careers, some of these mistakes that I’ve made and, and others you know, inappropriate comments or remarks a wrong math or algorithmic step being too harsh with your criticism, right?

Ginger Holt: A lot of times this happens in chat. You know, when it’s, when it’s strictly non-verbal communication, you go back, you read it, and the tone sounds bad or not as you intended. It it’s always good to apologize for those scenarios. And another example is in making a bad investment decision. Like either you invested in a project that was too risky or something.

Ginger Holt: Another example is think about a trading situation – Have you ever held on to a stock for too long after losing a lot just to then lose more? When you make a bad investment, change it, close it out, move on mindset around these mistakes and apologies. I used to have a very, very unhealthy mindset about making mistakes, you know, feelings of shame, fear of looking weak really often held me back from making apologies.

Ginger Holt: Other times I was just too proud of the situation didn’t really seem fair. To the benefit of my career, and even mo more so my marriage, my mindset around mistakes and apologies has shifted to a more, more healthy state. Through past experiences, mistakes not doing, not giving those apologies, right?

Ginger Holt: I’ve learned that being generous with apologies it really rebuilds trust demonstrates humility, courage. And now I try to think of mistakes more as learning opportunities, right? There are also opportunities to express empathy or regret if you’ve hurt somebody’s feelings, whether or not it was your fault.

Ginger Holt: Lesson number three is to actively manage your career, and actively manage and plan your career. And I’ve got a diagram here of a model, predictive control framework, so you don’t have to really know much about optimization, but in this framework you have a plan of what, what happens in the future, right?

Ginger Holt: In this case, you have a plan of what you wanna become in 5 to 10 years, and then you work backward from that, and you figure out a plan in the more near term you execute the first step of that plan, and then you step back and you, you evaluate feedback from yourself and also people around you. With that feedback, you then iteratively replant. It’s a very iterative process. You can also do scenario planning in this framework. Different scenarios, A, B, and C, you know, some of the unknown conditions that you could use in this, this scenario. Modeling is different economic conditions, right? Technology shifts industry changes, things like that. And by doing this model predictive control, using this framework, what you end up doing is you, you minimize later regret that you may have, right?

Ginger Holt: You thought through uncertainties and you planned the best way you could with, with what you knew at the time. And once you have that plan, right, share your plan, share it with your manager, your public plan with your manager and you can use it, use that plan to push back on projects that you don’t wanna do or that you don’t think are, are creating additional value for your portfolio or you know, it’s not aligned with what you, what you wanna do long term. And through this process, right? You come, you come to know yourself better, right? What makes you happy? What do you love to do? A lot of times we just don’t spend the time to check in with ourselves and think about these questions, right? Do you like theory or implementation journey or goal oriented, abstract or detail oriented, things like that.

Ginger Holt: I’ve done this in the past is to just at the end of the week, kind of assess how you spent your time that week and kind of rate the different tasks that you had and different jobs and projects that you’re working on to see kind of how your fulfillment is working on different things.

Ginger Holt: Lesson number four is to be an effective self-advocate. And I would say in general women struggle with this more than men. There’s data showing that women minimize their contributions compared to men when they’re doing self-assessments for performance reviews. And as you grow in your career, more of your work will entail advising others or helping junior colleagues. People have a strong natural bias to believe things in their own favor, right? They may think that they came up with an idea when you were the one who was steering them in that direction, or giving them giving them those ideas.

Ginger Holt: Make sure you document those ideas and direction that you’re giving to others. This is a big part of your your value that you’re adding and your years of experience can save others. A lot of wasted effort, and you should get credit for that.

Ginger Holt: Another thing is to increase your visibility by presenting and sharing your work as much as possible. Get face time with the execs. You can sign up for office hours or ask questions and meetings and don’t think of it as, you know, you have to make a big presentation and show them what you’re working on. Just ask them questions, you know, what keeps ’em up at night. Get their have a ability to communicate at a very high level what you’re working on, and get their feedback, feedback on that.

Ginger Holt: Mentorships and sponsorships have helped me become a better self-advocate by learning about what other other people have done. And the person that you’re advocating for yourself should have high standards. You can follow – if you’re in research, if you’re a researcher – follow your research heroes on Google Scholar.

Ginger Holt: Keep tabs of new research problems and ideas that can inspire you and think about your current projects as items in your portfolio that will help you get the next better role or opportunity on high value projects. Do a really beautiful job that that makes you proud of your work. And then on lower value projects, do solid work, but finish fast so you can get to those high value projects.

Ginger Holt: It’s also good to know your market worth. You can, you know, passively job hunt and collect data for that. Lesson number five. The final lesson here is to not do not passively tolerate problems. People probably know what happens to the frog in the boiling water. Many of you may not know about what happens to the red kangaroo. Even though it’s a much stronger and larger than the dingo, which is basically a a 30 pound dog, the dingo can defeat it by nipping at it many, many, many times over a long period of time and eventually tire the kangaroo out. That’s how the dingo is successful.

Ginger Holt: There are many things in life that can nip at you and, and break you eventually. Some examples. Office gossip, right? Office politics, bad managers colleagues that have no integrity, anything toxic to your mental health. Being in a company culture that doesn’t align with your own values. Having leadership that’s not transparent or having a path to career progression that’s not clear or it’s not aligned with your skillset. Instead of waiting around to get nipped to death with any of these things, leave, leave the situation, whether it be leave the project, your team, your company whatever. It’s not a good thing. And thank you.

Ginger Holt: I’d like to say thank you to the organizers. Thank to thank you to the participants. Thank you for listening. I’d also like to thank my company. This is a picture of my team here Databricks, our data science team. Thank you for their support and allowing me to participate in this conference. If you found any of this interesting, you wanna look, look into some of the references, I’ll post these slides on my LinkedIn page.

Ginger Holt: I also dedicate a portion of my time to mentoring and, and helping other people’s other people grow. Please feel free to reach out to me via LinkedIn or email. Also Shout out to Databricks. We’re hiring data scientists, software engineers machine learning engineers. Please out reach out to me if you’re interested, and I can share more information about job opportunities at Databricks. Let me check here the references here. Let me check this, the chat here. If there are any questions. I think we have one minute left.

Angie Chang: Thank you so much, Ginger, for that talk. Yes, it was excellent. There’s lots of great and people cheering you on. And thank you for sharing your, your content on LinkedIn. Yes. All right, we’re gonna hop to our next session now. See you on the other side everyone. Thank you. Thank you.

Like what you see here? Our mission-aligned Girl Geek X partners are hiring!

• Check out open jobs at our trusted partner companies.
• Watch all ELEVATE 2023 conference video replays!
• Does your company want to sponsor a Girl Geek Dinner? Talk to us!