Resources
Jun 9, 2025 |
56 min
|
632 views

Data Science Career Growth | Pallas Horwitz | Data Science Hangout

To join future data science hangouts, add it to your calendar here: https://pos.it/dsh - All are welcome! We'd love to see you!

We were recently joined by Pallas Horwitz, Analytics Consultant & Professional Development Coach, to chat about data career growth, effectively communicating business value in the AI era, navigating workplace dynamics, and future-proofing data science careers.

In this Hangout, we explore how data science projects, even those that don't yield expected results, contribute to valuable organizational learning. Pallas emphasized that what might seem like a "failure" is actually an opportunity to learn what doesn't work, saving future time and resources. This broader definition of "impact" helps data professionals frame their contributions effectively on resumes and in conversations, by focusing on moving business conversations forward and enabling informed decision-making. She also highlighted the importance of translating technical insights into language that resonates with business stakeholders, often by understanding their underlying goals rather than just their explicit requests. This approach helps turn a "not yet" into a yes by empathizing with the audience and understanding what they care about.

Resources mentioned in the audio recording and zoom chat.txt:
πŸ”— Pallas Horwitz's Coaching Calendar β†’ https://tidycal.com/pallashorwitz/45-minute-introductory-session
πŸ”— Pallas Horwitz LinkedIn β†’ https://www.linkedin.com/in/pallashorwitz/
πŸ”— Posit Conf 2025 Virtual Experience Registration β†’ https://posit.co/blog/posit-conf-2025-virtual-experience-registration/
πŸ”— How to Network in a Non-Slimy Way by Ted Laderas β†’ https://laderast.github.io/articles/2021-09-13-how-to-network-in-a-non-slimy-way/how-to-network-in-a-non-slimy-way.html
πŸ”— Libby Heeren's talk, Stop Networking and Start Making Friendsβ†’ https://www.youtube.com/watch?v=V3XdLVAwmX0

If you didn’t join live, one great discussion you missed from the zoom chat was about the role of Excel in data analysis, with many participants affirming that there's "no shame in excel!" and even calling it "the gateway drug to data management". The chat also highlighted the importance of networking, with attendees sharing personal success stories of finding jobs through connections made in unexpected places like the gym. You really should join live!

β–Ί Subscribe to Our Channel Here: https://bit.ly/2TzgcOu

Follow Us Here:
Website: https://www.posit.co/
Hangout: https://pos.it/dsh
LinkedIn: https://www.linkedin.com/company/posit-software
Bluesky: https://bsky.app/profile/posit.co

Thanks for hanging out with us! πŸ’›

image: thumbnail.jpg

Transcript#

This transcript was generated automatically and may contain errors.

Hey there, welcome to the Paz at Data Science Hangout. I'm Libby Herron, and this is a recording of our weekly community call that happens every Thursday at 12 p.m. U.S. Eastern Time. If you are not joining us live, you miss out on the amazing chat that's going on. So find the link in the description where you can add our call to your calendar and come hang out with the most supportive, friendly, and funny data community you'll ever experience. Can't wait to see you there.

And with that, I would love to introduce our featured leader today, Pallas Horwitz. She's an analytics consultant and a professional development coach. Pallas, thank you so much for being here. So excited to be here. Thank you for inviting me.

Yeah, of course. And I, I learned about Pallas through a mutual friend of ours, Mark, and Mark is not here today. Mark, if you're listening later, we miss you. He actually, he's hiking right now, but he messaged me and said to say hello to everyone and he wishes he was here. Yeah, he's hiking the Grand Canyon, which is amazing.

Well, Pallas, if you could introduce yourself for us, that would be great. A little bit about you and something you like to do outside of work for fun.

Okay. Well, I'm Pallas. I've been doing data things for about 13 years now. Spent half my career in the gaming industry and half my career in tech more generally. And I've definitely worked my way up starting entry level and then growing into a lead and then manager and then director. And it's just interesting to see, you know, how things have changed every five years. There's new trends, new tools. And outside of work, I'm a big movie buff. I like really old movies, like 1930s, 1920s. And all that stuff's available on streaming now. YouTube's great for that stuff. So I've watched a lot of old movies.

Oh, that's awesome. I think that we probably have some cinema files in our, our group as well. Well, I wanted to pop in the link one more time to questions, make sure that I've got it to share with everybody and remind everybody that when you ask questions in Slido, you can also vote for other questions. So if you pop into Slido, look at the questions that everybody else has asked, upvote ones that sound interesting to you and ask your own. But I get to start because we don't have any questions rolling in here yet.

Framing project "failures" as organizational learning

So one of the questions that I had initially for Pat was when I first talked to her was like, Hey, you know, a lot of data science projects actually fail. And a lot of like analytics initiatives fail. It's something that as data scientists, I think we've all dealt with. And so one thing I've struggled with when I'm writing my resume, or I'm talking about my experiences, there's always this question of like, well, what impact did you have? And I'm thinking, Oh, well, that project got canceled or that project failed, or, or that whole initiative got canned. Is there a way you can think of to like some advice you could give for people on how to phrase or structure things or approach things in that situation?

Yeah, I think a lot of times when we think about impact, we think, therefore, the company made this decision, they launched this feature, they made this amount of money. And there's a broader definition of impact, actually, when we try something out from a data science perspective, and it doesn't work, well, we actually just learned something new, we learn this data isn't predictive of this outcome, we learn this technique falls short. And sometimes the absence of something working saves the business time, it means we don't need to invest further there, it means we can ask other questions, we can focus on other hypotheses. And that in and of itself is valuable, you are moving the research of your company forward when you find out something doesn't work, because it means, well, someone else doesn't need to do that. You've saved time, you're moving forward.

And so I think, you know, when we think about these, these research studies, or these analysis techniques, it's not just about what answer did you get? But what are your business stakeholders care about? And how do you move the conversation forward, you know, that our role is data people is to help business leaders make informed decisions with confidence. And so if our data can't inform this, the solution, well, that's okay, then they can rely on their business intuition. And that's valuable for the business stakeholders to know. And so it's not, it's not a failure, it's still a learning, it's just a different flavor of learning.

It's not a failure, it's still a learning, it's just a different flavor of learning.

As you're saying all this, I'm sitting here trying to think of things that I could have done differently, or ways that I could have talked about all of these failures differently. And sometimes they were failures that were completely outside of the data product itself. They were failures on a leadership level or strategic level, failures of communication. But I still learned from those. I think that's a great takeaway.

Project management frameworks for data work

All right, well, I have another selfish question. Let me check and see what we have here. Ah, we do have some questions in Slido. Okay, I will hold my selfish questions for a minute. We have an anonymous question that if you are in Slido, I will just highlight it. So everybody can see it. But I'll copy it into the chat as well. Which is what data project management framework have you found most success using and I really like this because I've worked in all kinds of project management environments. And some of them I really don't like. So I'd love to know your opinion.

Oh, that's a hard one. It is.

So the truth is, you know, these projects are broken into phases, we need to understand the question, we need to decide on our technique. And then we actually need to do the analysis and iterate, etc. And, you know, I've worked on product development teams that use agile, I've worked on teams that use Kanban. And none of these are actually a great fit for data projects, because there is so much ambiguity. And so it's really, it's not that there is a best path here, it's about understanding how to chunk up your work and set expectations. Because if you know how to set expectations with your stakeholders, the actual project management framework itself is less important, but the framework is there to drive decisions, drive timelines, drive prioritization. And for data projects, it's often better to have a conversation, and then square peg round hole it into whatever company or whatever process your company is using. But I've never seen a process that like fits perfectly and seamlessly where you don't need to have that stakeholder conversation.

Yeah, nothing is perfect. I feel like it's tough because teams are made up of individuals and individuals are all completely different people. And often, when I'm saying like, I've worked in project management styles that were really, really terrible. They were terrible for me, but they were not terrible for some other people on my teams. And that's always tricky, right? It's like, it's almost like teaching, everyone's going to be a different type of learner.

Investing in your own skill development

One thing I also am curious about is something that I struggle with personally, advocating for taking the time to like sharpen your own axe. And we've talked about this on the Hangout before. But my question is, instead of like, hey, how do I convince my manager that I need time to sharpen my axe? How do I convince myself that it is okay to say, I need several hours a week to skill build when that doesn't have a product at the end of it to hand over to somebody?

It's a little bit, it's a little bit goes back to our conversation about failure. And it's only failure if you don't take into account the learning opportunity and the fact that you're moving the conversation forward. If you are hyper laser focused on, I have to figure out the root cause of what drove this metric, or I have to just project out, forecast, whatever thing I'm forecasting. You're not thinking more holistically. And, you know, as AI becomes more and more popular, AI is able to, you know, point to these different techniques and methods.

And what actually AI can't do, though, is add that, you know, human je ne sais quoi. And, you know, if we think about how can you be the best creative thinking human that is going to connect insights better than the people in the AI, you know, models around you, investing in your skill set is going to make you better. And sometimes it's not just about getting explicit permission from your manager, because if you want to spend two hours a week, your manager is not going to know what you're doing for two hours a week, you're going to be able to slide that in just fine. But it's about recognizing your impact doesn't come from just, you know, spending more time in Python and R, typing at the keyboard, trying to fit this model, your impact comes from your ability to think holistically. And you're not going to be able to think holistically without taking a step back and figuring out what do I need to invest in for myself, so that I, you know, like, it's invest in yourself for the sake of helping drive investment in your company. And you have to put your career first because no one else is going to do it for you.

You have to put your career first because no one else is going to do it for you.

Communication failures between data and business teams

Oof. That is true. And that is so, so hard to swallow. Sometimes I really struggle with this. If anybody else does, I'm with you. We have another anonymous question in the chat that I really like. So I will highlight that for everybody in Slido. So you can see it and I'll put it in the chat here as well. And it is, given all the different teams and all the different people that you've worked with, what repeated forms of communication failures have you seen? And how can you now overcome them preemptively?

Well, there's a lot of usage of words like failure in these questions. And I really try to move away from that mindset. You know, things are not so binary in terms of success and failure. But I'd say the constant throughout my career, regardless of whether I'm at a startup, if I'm working on slot machines, hair extensions, you know, helping out Facebook in India, the common thing is, I'm not going to be able to do that. The common thing is, people who are drawn to data careers, think differently, oftentimes, than the business people around them. And that means they also communicate differently. They focus on different things. I've been called pedantic many times in my career. Sometimes I take that as a compliment. And sometimes, whatever, I brush it off.

But it's, I fixate on the details, and I'm paid to fixate on the details in ways that no one else around me is. And so the biggest theme in my career is, we're talking past each other. The business stakeholders don't fully understand my skill set, my tool set, and what I can actually accomplish. And until I really took a step back and spent more time talking to my stakeholders, I didn't really understand what they were trying to accomplish. And so it's really about having that conversation. You know, we all would love to just focus on coding, and not have to worry about the human element. But the truth is, those human connections and those human relationships, understanding what matters to the people around you, that's actually what's going to help you drive your impact forward. That's how you're going to build trust.

That's how, you know, when your model doesn't produce the results you were hoping for, when you have that relationship, and you have that trust, and you have that understanding with your stakeholders, that's going to give you grace. And they're like, oh, you worked really hard, and now we know this methodology doesn't work out, and you can try this other thing. But that doesn't work unless you talk to each other. And there's this art to understanding, what are the questions my business stakeholders meant to ask? Because sometimes they don't even know how to word their questions. Because as I said, they don't understand our skill sets and our tool set most of the time. And so how do you learn how to translate what they meant to ask you for?

Yeah, that's a good one. My degrees, while they are statistical and mathy and stuff, come from a college of business. And so I got a bunch of business courses. And that was one of the biggest business analytics lessons for me in school. It was like over and over again. People are not going to know what they want. But it's the same education that my husband, who has an arts degree and worked in marketing and branding and logo creation, it was the same thing. He was taught, no one's going to know what they want. And half the job is you helping them figure out what they actually want, and then translating that into the stuff that you can give them.

Domain knowledge vs. deep technical expertise

Fantastic advice. Thank you, anonymous asker, for your wonderful question. We have some non-anonymous questions popping up here. But I want to follow up with an anonymous one again, because it's right in line with what you just said. You said, I just want to stick to coding, and maybe that's not the best thing. This question is, as an R expert, R coding, programming language, I'm often encouraged to learn more about business context. Should coders go deep into domain knowledge or rather focus on building strong bridges with business experts? I feel I'd rather stick to what I do best and just code in R.

So, I mean, that's a hard one. This is a really personal choice. Thinking about what you should be doing is a bit of a trap. Because, you know, I guess in the first three to five years of your career, you have to check a bunch of boxes, and it's about learning how to be effective and do effective analysis, find statistically significant results. And so you should be focusing on your hard skills those first three to five years. From there, when you play to your strengths, you're naturally going to be more inspired, more curious, and you're going to work harder than the people around you. And so if you focus on what you should pick up, well, all of the other people who are naturally inclined to that are going to do it better than you. And so if you force yourself, well, everyone says I should be doing this in Python, and then you force yourself, well, the problem is there's going to the next generation is going to be doing that much faster than you, and they're going to work harder than you and get further ahead than you. And so it's not about what you should or shouldn't be doing.

But it's about where do you see yourself in five to 10 years? When the next technological sea change occurs, what are you doing now to make your skill set and your career trajectory robust against the next technological change?

You know, when I first started writing data pipelines, it was all in Bash, and I was managing a Hadoop server, and it was miserable. And I should have become an expert in Hadoop and Bash, and that skill set would serve me not at all today. It does help me have empathy for my data engineering partners. But if I had just invested several years in becoming really good at that, it wouldn't have helped me get to where I wanted to go. And so there isn't an easy answer here, but just recognize, if you're only bringing one thing to the table, eventually the technology is going to move past that one thing. And so how are you going to future proof yourself?

Awesome. And I wish that I had a better answer, too, because I've really struggled with this for a really, really long time. People are telling me I should do this, or I'm being really encouraged to do this, and it doesn't come easy to me. And I'm thinking, oh, I just must have a willpower problem where I should be able to power through and do this thing.

And it turns out, no, what benefited me most was doing the thing that came more fluidly to me and more easy to me, and really prioritizing it. So thank you, anonymous question asker, that was great. And there's a sort of follow-up question that flows really nicely to this from Arsenis in Slido, and so I would love it if Arsenis could unmute and ask that for us, and I will highlight it in Slido so everybody can see it, pop it in the chat.

Cool. Thank you, Libby.

Hey.

Yeah, thanks for joining us. Is it Paula's side? Thank you for joining us today and sharing your experience with us. So my question is, given all the ambiguity around data-related titles and role definitions, what are some of the ways that you think a data professional can best communicate their skills to the market so that they can actually land in a role that makes sense for them? So yeah.

Yeah.

Communicating skills to the market

So one thing you can do is, if you just spend a lot of time on LinkedIn and if you can find people who are already in the roles that you want to have, how are they talking about themselves? If you can reach out, even if companies aren't hiring, if you can network with people who run teams who have the type of role you want to have, reach out to that person, especially if they're not hiring, because that means they aren't getting a lot of outreaches, and just see if they'll have a casual coffee chat with you. You can make a guess and blindly have hypotheses about how you should market yourself, but the best way to test your hypothesis is talk to the people that you would sell your experience to and find out what lands the most with them. Let them tell you what they're looking for and what the market wants.

You can make a guess and blindly have hypotheses about how you should market yourself, but the best way to test your hypothesis is talk to the people that you would sell your experience to and find out what lands the most with them. Let them tell you what they're looking for and what the market wants.

Yeah.

That's where I always get the advice to talk about your impact. We'll talk about the business impact you had. And I'm like, on all these data projects that like went nowhere or failed or like an app that nobody used. It's always so tough. Okay.

Arsenis, thank you so much for your question.

I have the same question over and over again.

And it's always a struggle.

I have a question from Rachel that I wanted to let her talk about. Rachel, do you want to ask that one?

Yeah, Pallas, when you were talking about helping people translate their ideas into a language that resonates with stakeholders. I was wondering if you could give us a specific example or one that like comes to mind for you right away.

Yes, just give me a moment to think of one.

Okay.

Translating data ideas for stakeholders

I think a common theme is stakeholder asks for dashboards. I want to be able to slice this dashboard by date, country, blah, blah, blah, blah, blah, like 10 to 15 micromanaging slices the data. And whenever I get those sort of requests, my initial thinking is, yeah, you don't know what you're actually looking for. You just want to ask for everything just assuming if I if I work for a week or two, putting together every different slice of this dashboard, you'll finally have that magic aha moment.

And so you don't actually know what you want. And so whenever I get a very detailed ask that has like 10 to 15 different sub segments in it, that tells me let me go have a conversation with that person. What are you trying to accomplish with this? What are you going to do with this data? What are you going to do if the data is informative and it validates your hypothesis? What are you going to do if the data negates your hypothesis?

What are you going to do if the data is muddy? And then I check to see, do I get different answers? Because if the stakeholder tells me, well, if the data is positive, I'm going to do X. And if the data is negative, I'm going to do X. And if the data is blurry, I'm going to do X. Well, now we no longer have a data driven decision.

This stakeholder already knows what they want to do. And so understand why they want to do it that way. And then think about what are the pitfalls? Well, the problem is they're not thinking about this long term holdout. And this idea they have, they're not taking into account all of the users that aren't going to have access to that feature.

So instead of just providing them a dashboard of all the 10 to 15 different cuts, I'm going to also provide them information on how things are performing over and above the holdout so they can actually see what level of incremental value they're driving. They didn't ask for the incremental value functionality. They didn't ask for the holdout visibility. But that's going to actually tell them if they're on track to accomplish their goals. And so you have to understand what they want to accomplish.

And then you have to use your own statistical knowledge to figure out, based on what's in my toolkit, what can I easily provide them that will actually answer their questions?

Thank you. Do you ever see it going the other way as well, where a data scientist has a really great idea for something, but they have to convince stakeholders that this is something they should pursue and then putting it in their stakeholder language?

That happens all the time, because sometimes the things we want to pursue, in order to explain them, we have to go into a level of mathiness that no one actually wants to listen to. And that's hard. You know, it's pretty common for the first time I pitch ideas for them to be rejected. And I often think of in a business context, when someone tells me no, that means that this idea is not yet a fit for where the business is.

And so once I think about, okay, this idea is not yet ripe, what are the things that are holding the idea back? What do they care about right now? How can I turn a not yet into a yes? And that, again, you have to empathize with your audience and understand what they care about to get that no to a yes.

I like that. I also like thinking about listening to stakeholders and the way that they are saying things and the words that they are using to describe them in all of your conversations, and then ask yourself if you are using the same language back to them or not.

One thing that's always been challenging to me here is that the advice always seems to go towards the data scientist or the analyst or the data people to talk more like stakeholders, but the advice doesn't ever seem to go the other direction. Like, hey, business people, learn more data stuff, be more data literate, talk more like a data scientist.

I would love to emphasize that it can go both ways. Both sides can be more aware of how the other is talking.

I also wanted to call in some stuff that's happening in the chat because it's been really, really great. We were talking about the anonymous question of, like, I'm encouraged to learn more about business context, but I just kind of want to code. Marlene had a great bit of advice there. Marlene, would you be willing to hop in and talk about the hiring market right now and how all that stuff is going?

Oh, yeah. I can go on. And I want Pallas to have her time because she's awesome.

All right. Quick minute for Marlene.

So I'll speak from personal experience. I was unemployed for almost a full year. Imagine trying to live on your savings and almost being ready to empty your retirement account after a year because, frankly, it's just hard to pay for things on unemployment. So I very quickly, I have, like, a lot of coding background, but I've also just been like a figure it out as I go person and I will handle the task at hand and whatever's on fire, I put it out and that kind of deal.

In the job market, I got several applications that asked specifically, how much experience do you have in health care? How much experience do you have in HR? How much experience do you have in this? Right. And depending on what I was applying for, if I put less than one year, my resume went into the dumpster. Like, I could just tell I wasn't even getting responses back.

If you are experiencing this, I feel for you. My heart goes out to you. It is not easy. Cry yourself to sleep, rock yourself, whatever you need to to get through it. Call mental health lines if you need phone a friend. But it is really rough.

I highly suggest I'm not saying lie, but I think it's worth going into an interview and saying, I know your company does this. I haven't done a lot in that. But here's what I've studied in just prepping for this interview. And I want you to know that I can learn the domain knowledge very quickly. But these are the tools that I have ready to go. That's going to take your company to the next level.

All that being said, I got to second round interviews doing that, and it was great. But what got me the job was knowing somebody. So build your network.

I love this hangout for so many reasons. Thank you so much. You have Ted and Marcos and all the folks that I've made friends with here, Rachel and Libby, too. These are the folks that help you realize, like, there's a world outside of unemployment.

So other than mental health, right, it's good to just know who's hiring and what. You know, I think I peened one other person on this call and said, hey, I'm interested in a job that's kind of in your field. Like, can you give me like the ups and downs of your field? And even that was valuable because I realized very quickly I didn't want to go into that work. So build your network. That's what we're all here for. It takes a village.

And there's my quick diatribe. Does that help, Libby? Yes. Awesome. And that is really valuable, like finding out what you don't want. It can be super, super valuable. Because what you do want, you're looking at a really broad target. Like of all of these things, what do I want? But when you figure out what you don't want, it tends to be pretty specific and easy to avoid or steer clear of.

Awesome. Thank you so much. And you can say you want the code, but the truth is a player is going to hear, I have to hire somebody to do something manually that ChatGPT can do, unfortunately. So instead you have to do the data science speak where I translate things more. And like Pallas, like I can think about your greater needs and put it in data speak to feed to a ChatGPT model and or confer with other scientists. So I'll also tell you that you have to learn how to kind of speak that language a bit now or else employers aren't going to hear it. They're just going to think you're going to be overpaid for a lot of extra work.

Keeping up with an evolving field

Well, speaking of like ways that our our industry is sort of evolving, Rohan had a question about this very, very thing. So I would love it if Rohan could unmute and ask his.

Hello. Can you guys hear me? Yes. Great. Hi, Pallas. So my question is, given how quickly the data science field is evolving, do you have any best practices or tips on basically keeping up or staying ahead with the data science field?

I'll be very honest. One of the reasons I went into management and leadership was because staying on top of the latest coding trends, it was something I should be doing, but it was not a natural strength of mine. Whereas understanding the needs of technical stakeholders and business stakeholders and connecting those dots, that was something that I knew I was particularly good at and the people around me weren't.

And so if you think about the things that you do better naturally than everyone around you, and then you think about, well, how is AI going to magnify that? How can I leverage AI and what's coming next to enhance my strengths? That's not a very specific answer, but that's like a lot of what I do in my coaching practices, helping people understand their strengths and then figure out how do you now future-proof yourself and make sure that when that next generation, because I'm a millennial, and so Gen Z came up and they were hungry, and next Gen Alpha is going to come up and they're going to be really hungry too. And so what are you going to do that's unique to you that no one else can be as you as well as you can? Like you're the best at being you.

And so what are you going to do that's unique to you that no one else can be as you as well as you can? Like you're the best at being you.

It's a lesson that we've been trying to teach ourselves since childhood, right? Like be yourself, just be you, you're great. And yet some of us, I mean, I'm almost 40 and I'm like, wow, it's taken me a really long time to embrace that lesson and realize that me as myself, I do have value. The things that I like to do do have value. Yours, everybody, you do too.

All right, Rohan, thank you so much for the question. Let's move to Cecilia and Cecilia cannot unmute, but she would like to know what drew you to coaching after such a strong technical and leadership career? I bet it just came along with the territory of leadership, huh?

I mean, the favorite part of my job was having one-on-ones with my team. And I was laid off two months ago on April 1st. And I had to think about, all right, well, the market's in a weird spot. What do I want to be, how do I want to be spending my time?

Well, in my job, my favorite way to spend my time was having one-on-ones with my team. Wait a second, coaching is just all one-on-ones. I'd have to figure out how to meet people and how to connect with people. But there are ways that I don't need to find a company to pay me to have one-on-ones with people. I can just talk to the people directly. And if I'm providing value and they want to meet with me and I want to meet with them, we'll figure out how to make it work.

And so, you know, I'm only two months into my coaching career, but I'm really enjoying it so far. And I've had a lot of fascinating conversations. And, you know, I am seeking my next role. Coaching was just something that was going to help keep me busy while I was unemployed. And it's possible my coaching takes off and then full-time employment doesn't make sense. We're having a bit of a race condition here to see which happens first.

Yeah, I feel like the question of how long you've been coaching, though, is not like two months. If you're a leader, you've been coaching people for years and years and years. The pay structure is just different because freelancing is difficult, as I will attest.

Stakeholder management strategies

Cecilia, thank you for your amazing question. I have another question here from Lolo. If you are able to unmute and ask, that would be great. If not, let me know in the chat and I can ask for you as well. And I will put your question here in the chat.

Sure, that's fine. Hey. Hey, hello. Yeah, so I was just trying to pick your brain, trying to refine my approach when it comes to stakeholder management. When you're interacting with business stakeholders, is there any particular fundamental structure you use that you recommend during meetings? And what's usually the most crucial agreement or insights that you hope to take out of those meetings?

So the first thing I do, if I have a particularly difficult stakeholder that I'm not winning over, I'm going to ask them for a casual coffee chat. I want to get to know them interpersonally. I want to know what they do on the weekend. I want to hear about their pets. I want to see photos of their pets or their kids or whatever. I want to build a connection where they're going to give me the benefit of the doubt. Because once they see me as a human, they're going to be more inclined to be patient with me, to listen to what I have to say, to not jump to conclusions. And I'm going to be doing the same for them because now I care about them as a human as well.

The trap is to think of your stakeholders is just like barriers or obstacles or another subsystem or just like a technical component and their people. And it's rare for, especially for technical people, it's rare for a technical person to reach out to a business stakeholder and say, hey, I just like to get to know you better and about your career and how you got to your position. And when you actually show interest in people, the dynamics of the conversation changes and then you're having a dialogue as opposed to people just shutting you down.

Because once they see me as a human, they're going to be more inclined to be patient with me, to listen to what I have to say, to not jump to conclusions.

Awesome. Thank you so much, Lulu. I hope that that helped answer your question. I heartily agree. And I don't think I need to tell anybody that I'm a fan of making friends with everybody that you talk to and instead of networking, just make friends.

I also will say one thing that I find really helpful is just avoiding corpo-speak. It helps people see you as an actual human being and not a corporate avatar of yourself. And so when you want people to, like Paola said, give you the benefit of the doubt, trust you, have real conversations with you, be patient with you, talking like a regular human being, like you're their neighbor can be so helpful.

Career landscape changes and future-proofing

Alrighty. I have a question from Zach and it has an asterisk. So I will ask it for him. And that is, how do you expect the career landscape to change in the next few years? But Zach, I wanna pin onto the end of this and say also like, how have you seen the career landscape change because you've been in data for a really long time?

Yeah. I mean, when I started my career and I know that this is gonna make everyone on this call cringe a little bit, but I'm gonna say it anyway. I did most of my work in Excel when I started my career. And then we moved to automation and I learned SQL and I learned Python and I'd used R a bit in college. And then I learned some machine learning techniques and then it became Bayesian. And then it turned in more into deep learning. I was like, oh, that's wizardry. I'm not ready to learn. I'm gonna hire someone else to think about that stuff.

But I've seen the sophistication grow and grow and grow. And now with AI coming, there's almost like this critical point where just being a tech, it used to be the more technical and the more statistical wizardry you knew, the easier it was to get a job. And now I think there's this pendulum swinging the other way, which is if you're just a technician, it gets harder unless you're one of those few that have the PhD that are working on the LLMs, helping open AI and Claude and chat GPT and all of that stuff. If you're not in that niche domain, just being a technician probably isn't enough.

And so how are you expanding your impact in terms of maybe as a data scientist, you wanna expand your impact, but you want it to be technical still. And so you wanna demonstrate, well, I can do all of my data engineering as well as all of my data science, as well as all my analytics engineering and dashboarding, et cetera. And so you wanna demonstrate that you have extra value because you don't have just the typical data science skillset. Maybe you're a technician, but you also wanna learn how to do some software development as well, or you wanna show that you can build apps with AI. How can you be more than just the person who writes models in R and Python? How can you be something plus that?

Yes, I like that. And I've gotta say, no shame, no hate to Excel. We all still use it. And there's so much Excel love and support in the chat right now. If you are listening or watching this later and you're like, oh, I use Excel. I also love Excel. So do we all, yes.

And Excel is, as several people have said in the chat, I think Excel is a gateway drug where you're like, Excel is fantastic until it's not, and then you need something more. And that's often how many of us end up coding or doing code-first analytics is because we needed that. So Zach, thank you so much for the question.

GitHub profiles and job candidacy

I have a question from Kyle as well. Kyle, I don't know if you are available to ask this. I want to say, I don't think that you are, but maybe, let me see. Yeah, I can ask. There he is, yay, thanks. Yeah, thank you.

So I have a friend that works in the industry and I know it's a sample of one, but when he's evaluating candidates, he looks at their GitHub profile. So how much does your GitHub profile weigh into job candidacy? And do you find it to be more important than other tangibles?

Not how you have profile. I'm just gonna put that out there. I think it really depends on the role and the type of company you're interviewing with. There are companies where absolutely that's a non-negotiable. And you need to have that, and you need to have recent, it's not just you need a profile, you need recent commits in a language that they care about working on a problem that's similar to the problems they work on. And so this goes back to a question from earlier, which is, talk to the people that are in the roles you want to have, talk to the hiring managers, especially the ones that aren't currently hiring because they're not swamped with LinkedIn requests, but talk to the people who are managers at companies you want to work at, and they can tell you how important that is.

Over my career, I've only had two roles where I actively checked the GitHub commits, and it was because it was a really niche problem I needed them to solve. And I needed to know that they had very, very relevant domain experience, but I haven't checked GitHub profiles for most of the roles I hire for, but that's not true everywhere. It really just depends on the actual industry itself and the type of company you want to work at.

Awesome, thank you. And pulling in some stuff from the chat verbally, Marco says, we never decide to interview based on GitHub, where he works, but we do look at it if you link it in your resume. So if you're going to link it, make sure that it's nice to look at or presentable. My own GitHub is an absolute mess. I use it for demonstrating things to people, and so I'm constantly just putting random stuff in there to help people practice.

But I like the call out that you don't have one, and I have never had a cohesive and beautiful GitHub portfolio either. I don't want people to think that you cannot survive without it, but it is nice being able to have something out there that you can talk with people about. Thank you, Kyle, for the great question.

Showcasing confidential work

Let's see what else we've got, and do a time check here, because we've got about 15 minutes left. Um, there is a question here from Inger. If you are available to ask that live, I would love it if you could unmute. There you are, hey.

Hi, everyone. Hi, thanks. Thanks, Pallas, for being here. My question is, I think, something maybe we already have touched on, but so I'm relatively new to data science as sort of a professional pathway, so I'm still learning conventions and norms, and I often kind of struggle to figure out how to showcase skills and data-related achievements when the projects that I want to highlight are confidential, so just thoughts about strategies or suggestions for demonstrating expertise without violating confidentiality.

Yeah, that's hard. You know, you can talk to the company where you're doing these projects, and say, you know, hey, I'd like to showcase my work. What if I scrub all the labels, scrub all of the identifying context? Is there a genericized version of this you'd be comfortable with me showcasing? They're gonna say yes or no, and then they're gonna nitpick with you over how much you need to mask the details of the analysis, and if they do say no, well, I bet that there's a hobby or a small business near you where you could apply a similar technique to solve a similar problem, and you can go in from the get-go saying, hey, I wanna showcase my work, or do an analysis on movies or sports or something like that. You can always do a pet project that repurposes the technique you used, but doesn't actually rely on their data, but usually the easiest route is figuring out what's the obfuscated version of what you did that the company would be comfortable with you going to the market with.

Thank you, and just as some sort of support for you, Morgana in the chat is saying yes, and I will say I've had the same struggle where I did data work that I absolutely could not talk about totally under NDA, government stuff, a lot of people who work in government can't talk about what they do. I am right there with you.

I will also say that it's totally valid to struggle while you're in the moment, while you are working on the project, to think about that, oh, I need to find some way to document this for posterity for later. Because as you're in your job, doing your job, you're not actively thinking about the fact that later you're gonna need a different job. So don't beat yourself up too much for that, but I will say I've been in that same struggle bus, and I've been in interviews where they're like, can you tell me about a time when you did this? And I'm like, oh, wow, well, that was five years ago, and it was under total NDA, and I can't tell you anything, but I can tell you sort of this, and not having that code to share is such a struggle. So I hear you. Thank you so much for the great question.

Maintaining stakeholder engagement vs. external vendors

Sarah, I have a question from you, and Sarah, last time your Zoom name was different, so we couldn't find you. Hopefully we can find you this time to unmute and ask your question. Yes, thank you, Libby, appreciate it.

So my question is, do you have any advice for maintaining stakeholder engagement for in-house data science requests or projects before they turn to an external vendor product? You know, in a fast-paced world, which there's lots of pressure to show excellent results quickly, this can be challenging.

Yeah, that's double-edged sword, actually, because depending on the speed they wanna move at and the stakes of the decision, you know, you could intercept the train, but you might not like the consequences of doing so. You know, when they're making decisions potentially to evaluate, you know, putting you on a project or going with an external vendor or third-party solution, you know, have that conversation and find out what goes into this decision matrix, how are you evaluating how to make this decision? You know, and then be honest. You know, if I were to take it on, this is what I can bring to the table that going externally won't be able to accomplish, and this is why you should go with me instead, and also be honest with the trade-offs.

But by the way, you know, I haven't, you know, I don't have experience in this particular domain or I haven't done this specific layer. It will take me a bit longer. And then, you know, be really honest, which is if you were the business stakeholder and you just heard the argument you made for why they should go with you, would you choose to go with you, or is there enough risk here that they really do need to go with an external solution? And, you know, obviously, the context and the details really matter, but put yourself in the mindset of the business stakeholder and understand how are they going to make this decision, and is it really in their best interest to keep it internal versus going external?

Great points. Also, maybe think about the opportunity costs of them choosing you for maintaining it in-house, because if there's other things that the data science team could be doing that are much more valuable than that thing that they're potentially gonna vendor out,

it might be a hard sell for them.

My two cents. I'm giving my two cents on everything, Pallas. I'm so sorry. This is the Pallas and Libby advice show today.

Thank you, Sarah, so much for your question. We have a lighthearted question from Joseph, which this one popped up in the beginning and I missed it, which is, so what old movies should we be watching on YouTube tonight? Give us an old movie recommendation.

So there's like a 1930s version of Dr. Jekyll and Mr. Hyde that I just adore, because they do all of these different, they're very experimental with how they do the screens. They're a little bit racier with the implied romance, and it's just got that little bit of extra edge right before the studio system really comes in and puts the hamper on everything. And I don't actually remember the name of it outright, but if you just Google like Dr. Jekyll and Mr. Hyde movie from the 30s, that's my favorite one.

I feel like Rachel just put an IMDb in the chat. That's 1931, Dr. Jekyll and Mr. Hyde, and I am looking at a clip right now that is priceless.

All right, awesome. We're all gonna go look that up.

All righty. More questions in Slido. Thank you, Joseph, for that lighthearted one. I love those.

Let me take a second and look at all of these fantastic questions because we only have about eight minutes left and I wanna be able to get in a few more if we can. Olivia, I forgot how when we would collect the questions through Slack, we were also like starring to say like, oh, here's some to pull to the top and you're doing this magical thing of reading them while you're talking. It's difficult.

Actually, I wanted to let everybody know I'm getting some DMs that are asking me to ask questions. If you could put those questions in Slido, that would really help because I'm trying to, like I said, I'm trying to captain the enterprise right now and do many, many things at one time. So keeping them in Slido really helps me out.

Explainability and interpretability in the age of AI

Salmita, who always asks amazing questions, by the way, Salmita, question asking queen, has one with an asterisk, so I'm gonna ask it for her. With the increase in vibe coding and LLMs writing code, do you think that explainability and interpretability in data science have risen in importance? So as data scientists, like should data scientists be better decision makers than they are coders? Really interesting question.

I'd like to say the answer is an easy yes, but I'm hesitating and I'll explain why.

I have been in situations where it's really hard to make the business decision and no one knows the right answer. And so they turn to the person who can produce the most sophisticated math. And so while I do think interpretability, explainability is really important, there is always going to be that one category of problems and let's call it 20% where no one knows the right answer. So they're gonna defer to the person who can make the most complicated math and be a little intellectually intimidating. I don't think that's the way you can actually build your career, but I don't think that category of problem is going to go away. So I do think in general, explainability, interpretability is very important, but that one category I think is always going to exist because when humans don't know, we don't like the unknown. And so that thing we understand the least that seems really confident, let's just go with that.

My two cents on this one is that trust in AI is a very interesting topic and it's something that's evolving and being studied a lot, but it's been studied also just as like trust in predictive models in general, outside of LLMs or before LLMs. And a lot of times when you look at the results of those studies, humans were trusting their own judgment more than a computer output of a prediction. And so having that human being in the loop is definitely, I think, still really valuable to a lot of people individually when it comes down to them making a decision. So keep that in mind and use that as ammo when you're talking to other people.

Career advice: mentoring at any level

So I wanted to tuck a few more in. We only have about five minutes left. And there was a question from Nellie that I really, really liked. And I think that it's a great career advice type question that's fantastic for you. So Nellie, if you are available to unmute and ask that, that would be fantastic. And if not, I can ask it for you.

Mic down. Okay. Can y'all hear me? Yes. Thank you. Okay, cool.

So my question was, how can I continue to be a leader and mentor in a space when I'm now sort of at the bottom? Like I used to mentor freshmen when I was in college. I used to coach synchronized swimming. So I had a lot of these leadership mentor opportunities, but now I'm in my first full-time job and it's in data, which is not my actual degree, but I really enjoyed it and kind of did it during my coursework. But how can I continue to use those mentoring skills even if I'm sort of like towards the bottom of the chain per se?

You actually have a really important accomplishment in this market, which means you have your first data job and there are a whole bunch of people out there looking right now and they have not gotten their first data job. And I bet they'd love advice about how you actually accomplished getting your first data job. How did you transition into this career? How did you get to a place of paycheck stability? That's really, really valuable. And so don't discount just what you've accomplished in the past six months to a year. There are a lot of people who are trying to accomplish those things and haven't figured it out yet.

Absolutely. Yes, and someone, George, said in the chat, you can mentor upwards too. Like there are people above you who need your perspective as a person who is lower on the chain and it's really beneficial for them if they know what's good for them.

And I will also say there's an episode of The Hangout from years ago with Namrata Shetty. I will put that in the chat right now where she talks about mentoring and she's like, I'm only a few years into my leadership journey, but I am mentoring because I'm further up the ladder than somebody. There's somebody underneath me on the rungs of the ladder and I can help them. Maybe I can't help everybody, but it's still valuable. So go watch her Hangout as well.

Memorable career advice

All right, a few minutes left. Can we tuck one more in? Nellie, that was a great question.

I feel like I want to just ask a generic career advice question. We ask this of everybody. Like what's the number one most memorable piece of career advice that you can leave us with after today, Pallas? Or just something that comes to mind that was really impactful for you personally. Yeah.

I'll drain you of so much advice already today.

The one that was told to me that was, so I was in the gaming industry at the time, making video games. I'm sure there are people on this call who work in healthcare, and this advice does not apply to you guys, but it applies to everyone who's not in healthcare, which is I adjusted an analysis. The results were awful. The product was going to die. We were going to have to pull the plug. I felt so responsible that I produced the analysis that was going to kill the product. And a friend of mine told me, it's just an effing video game. No lives are at stake. And I think sometimes, we devote so much of our waking lives to our analysis and understanding the data that we forget to have perspective. And again, this is not for the healthcare people. This is for everyone else. Lives are not at stake.

And I think sometimes, we devote so much of our waking lives to our analysis and understanding the data that we forget to have perspective.

Sorry, healthcare people, lives might be at stake for you guys.

I really appreciate that. And you know what? As I was asking you the question, what's one that made a really big impact on you? Mine is sort of the same. I had a manager say, Libby, there are no analytical emergencies. Like you can chill out. It's okay. Cause I'm very hard on myself. That's the feedback I get from managers. Like Libby, you're so hard on yourself.

Thank you so much, Pallas for hanging out with us. This has been wonderful. I hope you've had a good time.

Thank you. No, this has been great. And it's a shame that I wasn't able to like read the chat as well and answer more questions. Cause this is how I love spending my day. This is why I've opened a coaching practice because there's nothing I enjoy more than just like thinking about things, talking to people and then helping them learn how to think and talk as well. So thank you so much for including me and thank you all for all of your wonderful questions. Yay.

I wanted to make sure we left one minute to talk a little bit about your coaching practice too. Cause I saw some of your posts on LinkedIn. I didn't know if there was anything I'll share about that. I just put her LinkedIn in the chat, everybody. Yeah.

I mean, I'm just getting started right now. I have some evening availability for folks, but yeah, I have a link to my calendar on there. By all means, sign up, you know, we'll talk for 20, 30 minutes and talk about what are you looking for? Is this a great fit? What sort of structure do you need? I do do a sliding pay scale for folks depending on where they're at their career. And sometimes it's a fit and sometimes it's not, but you know, I think I'm a friendly person. I'm not going to bite, you know, come chat with me and we'll see what makes sense. Thank you so much.

Thank you, Pallas. Everybody, if you would like to save the chat, there are three dots at the top of the chat box. You can click those and then click save chat and you can take all the resources with you. Thank you for hanging out with us on this beautiful Thursday. And next week, I hope that you come hang out with us because we are going to have Karen Healy and Jonathan McPherson, two of our keynote speakers for Posit Conf that are coming up. And if you know either of those guys, you know that it's going to be a really, really interesting discussion. So come hang out with us. Can't wait. Have a wonderful week. Thanks for being here.

Libby, you just reminded me when you were talking about the conference chat next week, if anybody is thinking about coming in person and maybe like nervous about going alone or not knowing anybody, I was thinking next week's hangout might be a good opportunity for people to just get to know each other a little bit better so you have a buddy when you're there in person. So know someone who's thinking about going, you're not sure if they want to, maybe invite them to next week's hangout too.

That's a great idea. All right. Fantastic. Thank you, everybody. I'll see you next week. Bye.