gun.io mini series w/ victoria stahr, talent growth

full transcript

auto-generated from the audio, so expect a few typos. the audio is the source of truth.

Hello, hello. Thanks for listening to Guidance Counselor 2.0. Listen, I want to give you a quick rundown of what this podcast is and what you're about to get into as you listen to these episodes. We had Guidance Counselors in middle school. We had Guidance Counselors in high school, but we didn't really have Guidance Counselors in college and now as professionals, we don't really have anybody to turn to to ask a quick question to learn something about the job search or to navigate your career. And so that is what I want this podcast to be for you. I want it to be a tool for you to navigate the job search and your career.

So that being said, I hope you enjoy this episode. And if you need to reach me, social media at T D S N T D E S E Y N. And finally, please rate and review this in the app store because I want this to be discoverable for others so they can navigate their careers. Hope you enjoy the episode. All right. All right. What's going on? Everybody. Happy hump day. We made it. Hope day. Still wish, uh, pretty sure it was a guy. I wish Geico never went away with hump day. It was Geico or all stay. I can't. Do you remember? I was like, y'all?

This feels like a weird like, very interesting question. Yeah, where it's like, oh my gosh, what one was it? I think that was probably a different memory of what it was. Bear steam, bear steam thing is wild. Yeah. Yeah. We can go down a road. Yeah. Yeah. Two roads for nine, 30, and one. Yeah. Yeah, we're actually not talking about going. How about conspiracy theorists? So thanks, 30 minutes. Congratulations everybody. But for those of you tuning in, welcome, good morning. I'm really excited for this little series I'm doing. Basically just highlighting and helping educate you all what gun.io is. I'm very thankful to be here.

Meant to amazing people like Victoria already in my second week. I'm actually over meeting right now to be totally honest because I'm so excited to be here. I just want to meet everybody and then I get exhausted. I have eight meetings today. So it's just, it's absolutely insane. But excited with it. Hang on Victoria. or what she does, what gun.io does. And so you get a little bit more information. And I'm going to have more individuals on the show over the next upcoming weeks so you can learn more about who we are, put faces the names because you're going to do with Victoria a lot.

If you sign up to gun.io and you sign up for our platform, you are going to work with Victoria. So that's why I really want to get her on the show first, because all my dev friends, once you get on gun, you're going to work with Victoria. So that's why I wanted to have her on. But for those of you tuning in, welcome, say, hey, we'd love to hear from you. You know, I talk about this all the time. This is a networking platform. I've done this for three years now. What I've realized is this is kind of a 30 minute meetup where I just talk and have guests, but you can like network in the chat.

So if I were you, I would comment, say, hey, even if you're watching this in the future, I would still comment because there are people who legitimately come through and network off on the back of the comments, which is what I encourage. I would also network to everybody, every guest I have on the show with Victoria and anybody else. I'd also hop on over to Unicorn Funders because the guy can't have too many podcasts, other podcast and I would network with all the founders I have on the show. And if you continue to do this time and time again week after week, you're going to develop a pretty vast network.

Um, and so again, go network Victoria. Second off, uh, ask questions. This is a, this is a very informational type of show today. A lot of the stuff that we go over is kind of career stuff, not heady. When I say heady, I just mean like kind of in the clouds a little bit. This is very much of a Q and A, like if you want to know about gun, how we do things, please ask. And then I want to give a shout out to that conference being the official coffee sponsor of the podcast, drinking it right now. I just key noted that conference last week.

But Clark sells a dear friend of mine is the only conference I have their own coffee beans and I'm a big coffee nerd. So go check them out. And then of course, gun.io just for being an amazing coming to work for. I want to give a shout to the people who are tuned in. Marie, it's good to see Ricardo, Matt, Roberto, Eugene, what's going on? He knows the drill. You know the drill. Connect Kevin. It's good to see y'all. Good morning from Arizona. LinkedIn user, great to see you. Don't know who you are. Great to see you. Jordan, what's going on? Just got the baby down for three hours of fussing.

Bless you, dude. Bless you. Been there. Done that. Mark's good to see Ryan. Zach, good to see you as well. Can't wait for him, Ghosted. Yep. It's another little series. I'm doing with my friend Alicia Novin network network network exactly. All right, so Enough of me running my mouth want to give a shout out to Victoria Victoria if you want to give a quick Quick overview just just about who you are and uh, and we'll just go from there Hi. Yeah, thank you for having me around here Taylor. Hi. Good morning everyone This is awesome to see the comments actually like this little scroll happening Yeah, I know.

I'm sorry. I'll try to have the chat. You will always throw it up. Don't worry. You just can't talk. You can't manage that. Hi everyone. I'm Victoria. I am a developer relations team member at Gundadeo have been since 2020. So it's been a good three, three and a half years now. And I primarily work with the talent side of the Gundadeo platform. So I help with anything community related, especially if you are interested in the platform. I will likely be the first person that you meet and interact with. And probably a few times as you go through, we have an onboarding and approval process that we have set up.

So you'll interact with me quite a bit as you sign up through the platform. If you have any questions about the platform, they usually get directed to me to answer, but I'm happy to be here. Yeah, I'm happy you're here. And Todd, it's good to see Amanda Lobster. I love it. So Victoria, So Victoria and I are chatting and I'm trying to talk to people not I'm trying not to beat work over y'all's heads for 30 minutes and talk about some personal stuff So Victoria, what are you passionate about right now? Victoria and I chatted about today. So what are you passionate about right now?

That's not work. Yeah, it's very exciting And I'm very new to it. I'm talking like two weeks into it. I just got a bonsai tree So anyone how do you spell that? BON SII It's a bonsai tree new to it. So if anyone has me. Oh, it's like the Japanese. Yeah. Yeah. Yeah. Just got a five year old bonsai tree and I'm taking care of it. I'm very excited. It's a cute little morning routine that I have set up with my cat. I go feed the cat, feed the bonsai tree. It's not worth. I mean, it's pretty great. Well, and so we got to talk about your cat and then what's your cat's name?

his name's Killian. He's an all-black Halloween kitty. He's also three years old. I got him a little bit after I started the gun. That's awesome. Yeah, so I love it. Trees and cats. I love trees and or cats. Messes Victoria. If you have any tree, if you have any like plant advice for Victoria, please reach out to Victoria because she's new. She's new in this journey and here we go. Look at this. I have four bonds that's going to be in It's never mind Matt. Come on, man. You get them planted. You get them planted. So all right, gun.io. I know I've already been kind of spreading the good word, but in your words, just what is gun.io?

Yeah, in my words and from my perspective, gun.io is a platform, more of a community based platform that does help developers link with clients. But more so from my perspective, it is more of a community based platform. And typically the reason that I do describe it in that way is because the way that we have it set up, not everyone is always looking for their next role, but they're interested in having those conversations. So it's definitely a space where we provide great opportunities for developers that are interested or as they're open to opportunities, but then there's also that space to really connect and network with other developers that are doing similar things or want to talk about the bad ass things that they're working on, which is really the side that I'm passionate about.

I love when developers are brought on to engagements, that's, you know, a big part of what we focus on, but also just the interactions that I have on a daily basis and really getting to know members of the community space is what I, is what Gandhaya is to me more person. So, so let's talk. So let's talk about, no, no, I do want to talk about this, right? Yeah. You would have messed about this. So I'm meeting with Victoria twice today. I'm a very lucky man. I got her this morning that we're chatting some communities that this afternoon. And, and, and, and I do want to go ahead and address something that I've been getting a lot of DMs about and that gun.io's platform is more geared towards the senior folks.

So, so can you talk about that and, and literally just, just in full transparency to you all on the Victoria and I are going to talk about how do we engage the zero to five-year range as well. That's actually our call this afternoon. Victoria, we should just do our call here. But basically, talk about the platform and really what we're targeting right now. Yeah. So, current iterations, probably the best way to describe that. I do think of the platform as sort of like a living and breathing thing where there's always change in progress being made with with how we work. But currently, we do primarily focus on senior software developers.

Typically, more or less five or more years of experience is sort of the baseline for minimum qualifications within the platform. But it ranges the spectrum of different industries, different technologies. We're focused on sort of the content and context of your previous work to understand that and understand the ways that we could potentially help you land your next gig. It's very much a personalized experience or an individualized experience where you wanna have that understanding. So we do primarily look at experience just overall, okay, about trajectory, to try to get a better understanding of an individual and the best ways that we could potentially help. Yeah, absolutely.

And then Brian says right here, is there a rollout plan to add junior devs? So again, Victoria and I are gonna talk about this. actually today, and just some ideas we have. You know, again, the nature of gun.io, and Victoria's been your way longer than I have, so Victoria correct me if I'm wrong, but essentially, hired gun is where the name came from. Essentially. And when you're in a hired gun stage of your career, you can't have any like learning time, right? It is throw it into a project and go. So that's been our focus, and when I say, I mean, gun's focused for a long time.

I know we are getting into more full-time 40-hour, like direct higher contract, contract higher as well. Yeah. So again, things may change, but just kind of set in the stage. Like, would you say that's relatively accurate? Yeah, since we primarily work on a contract model, that's going to see where, that's going to be a majority of the roles that we see come through on the platform currently. There are options for contract to hire salary physicians. Typically within the contract space, there's not a lot of ramp up time involved. So we are looking more for expertise in areas for that right fit, just because clients are booking a certain set of hours, at least initially or for the first iteration of a project and continuing from there.

So there's not a lot of that ramp up time built into that, because it's on an hourly contract model. Yeah, absolutely. So yeah, I mean again, Brian, We'll definitely, that's something that is on our roadmap for sure and just how to engage folks. We have some ideas. So Victoria, so I want to talk about the developer journey through just kind of signing on. So can you talk about it from going to literally just gun.io and then kind of walking through that journey just to set expectations? Yeah, absolutely. So as you log into the web app or visit the web page and go to sign up as a developer, there is going to be a questionnaire that you'll initially go through.

It's pretty quick. It's pretty easy. But that's going to help us outline if we're at least potentially a right fit or not for your job hunting purposes, mostly around the technologies that you use, years of experience, things like that, just to help us get a good baseline. And then from there, if you are able to access your profile space from there, you'll be able to set up a onboarding session call. That would be with me. I host those in small groups every week. There's sessions every day, but that allows me to interact with individuals as they're joining the platform and to give a little bit more insight into how we work and what we're looking for more specifically.

So within those onboarding conversations, we focus on profile completeness, sort of that competitive nature aspect of joining the platform and in the application process and why that context and that detail in the profile is important or outline your work histories or ways to outline where histories are important. From there, profiles do go through a review. I give everyone a couple of days to make adjustments just so that way could be tailored a little bit. We then do an individual review of all profiles and make a determination from there on, once again, sort of hour perceived ability in helping you land a role based on that information that is in your profile but also based on what we've seen historically on the platform.

So there's a lot of variables that sort of go into that consideration. If you're not a right fit for the platform right now, know that it's not indicative of your abilities as an individual, but more on our ability to get you placed on an engagement. There's options to reapply in the next year for reevaluation, or you get moved to a one-on-one approval interview that is a technical conversation. It's not code challenge related, but you do speak to things that you've worked on in the past technically. Once again, it's more for our understanding of how we can best help you move forward on the platform. We want to get to know you as an individual and understand your work background to help you move forward in that process.

Yeah, Todd, and I'll answer this. Is it just senior developers? I mean, here's the deal. I haven't been in the, I mean, I've only seen two weeks of data from jobs. We haven't, I haven't, we haven't, I haven't gotten paying anything for accessibility, but I will tell you Todd, you're a senior engineer, right? You are a senior in your career. You could join on and then the way this works, again, Victoria, please correct me, is get on the platform. It's another channel to engage in. Because my talk, was it Monday? It was a Monday's talk, Monday's show? I talked about different communities to get involved in.

I listed a few. Well, Gunn's got a community, right? Our Slack channel, our platform is a community. And so if you are senior in your career, Todd, like you, you can get on the platform, you can network with other engineers. We do have a jobs channel, which Victoria, we funnel everything through, right? Like a job's channel on Slack, where we post all of our jobs. Yes. And then if we do get accessibility position, Todd, you'll see it in the jobs channel. And so there's a couple of ways, yeah, that you would receive that notification to. We do match based on skill tags that you list in your profile.

And so you could also receive email notifications. Okay. That, I didn't know that. Help you get notified around opportunities that might be a good fit for you. But everything does get posted in our community space as well. Yeah, so I tell people, I've talked with quite a few of you already who've wanted to join the platform. And I tell you good data in, good data out, right? So the more time that you can spend entering in the information on your profile, the better we can do to match you, right? Some of you, do you want to expound on that? That's just it. Yeah, the more context that we have, which is why we like to have those one-on-one conversations, just helps us understand more of your work and how that aligns more specifically with client expectations as well.

Once again, noting that most of the roles are going to be contract based, clients are looking for pretty specific overlap in their job description and what they're viewing within a profile or application. So it's not only that you've used the technology, but it's in how you've used the technology. Almost anyone that's applying for a role you might have interested has used that technology. And so it's I want to know how you've invested in or a similar industry or similar environment, things like that help add some of that detail to a semi-gray area. We want to make sure that we have that information not only from the developer side, but it's also why we have conversations on the client side before we post anything to make sure that we can align that right fit with any developer that's interested in a client that's interested in hiring.

We want to make sure that we're facilitating I go working relationship. Yeah, absolutely. Can you and I'm kind of backtracking a little bit, because there's just so many things that I'm back here. There's a lot. So can you talk about the on? So somebody fills out a profile first. Now let me ask you this. So if you get rejected, is the most common reason for rejection just overall years of experience? Or could you be a senior in your career and still get rejected? And if so, what's the most common reason? So we can just help educate kind of some folks on the front end. Yes, you still can have over five years of experience and not be a right fit for the platform.

Like I said, we do look at a number of variables that whether that's historic client need, current client need. We also look at the developers that we have approved and applying within the community as well. and look at sort of those tech stacks and those experiences and how those are lining up with client expectations as well. And so there's a number of things that we focus on, but it is primarily focused on that work history space and understanding that. I think what is important to note in that is that just generally the competitive nature of joining the platform translates into the competitive nature of the application process.

So if we are not confident that we would be able to help you land an engagement, once again, it's not indicative of your ability. It's just based on more of those factors in whether or not we think that it would be helpful to you to be applying for roles, just generally within this space. That makes sense. And then so talk about, so somebody could spend an hour filling out the application and still get rejected. I just want to set that expectation with you all. At the end of the day, we're doing the best we can over here. So again, I want to go live and I want to have a real conversation about this stuff because I've had people messing me up already.

I got rejected it's like I got a check in on it and actually for most people who got rejected so far It's because of years of experience overall because I just wasn't knowledgeable not yet now. I am hence hence why hanging out with Victoria So again, just be patient and again Victoria and I are gonna talk this afternoon together on like what we can do if you do get rejected You still want to be a part of the platform. You still want to be a part of the community What can we do there? So we're gonna talk about that We don't have an ironed out yet the next thing I want to talk about so alright So you go through, you go to gun.io, you fill out all the questions, you fill out the application, and you get accepted, and then the next thing is the 10, the 10 engineer onboarding calls, kind of what I call it, right?

Or like, is that right? There's an onboarding call, yes, and it's in small group sessions, yeah. Small group sessions, yes. It's not always 10. That's the number that I popped into my head. So talk about the onboarding session. Yeah, it's split. I consider it to be split into three parts. So the first part is me just displaying a lot of information around profile completeness, what we're looking for, and sort of four sections of your profile to really break that down, primarily focusing on that work history space and that detail involved there. The middle part, I like to do a brief round of introductions with everyone that's in the session, just so that way it's not me talking at people for 30 minutes.

But that does help Taylor the second half of our conversation based around what individuals are hoping to get out of the platform. That allows me to add some context, some clarity, just speak to things a little bit more, more specifically for those individuals in that session. And then I do go over what the next steps look like, as well as setting expectations for that timeline and then open it up for just sort of any general additional questions. Because I want to make sure that everyone at least leaves the session understanding sort of how we work, whether that's in the onboarding process or beyond. So it's a pretty open conversation and outside of that first chunk where I do go over our sort of expectations in the profile.

Yeah, absolutely. So how many, I'm just curious, how many sessions you have a week with these? Yeah, right now we're at 15 sessions a week. Yeah. Yeah, that's your heart. That's a lot. It is. But I like meeting everyone. I think that's it's a really good way, just out of the gate to already start to get to know individuals as they're joining. And it's also really interesting, at least from my perspective, that's also where I really start to see some transforming as far as like the types of developers that are looking for work or the type of work that they're looking for those tend to emerge in those onboarding sessions as well or alongside what we're seeing on the job side.

So it's always really interesting to sort of note things as I'm meeting with people just by talking to them. A hundred percent. John comes in, what's the average acceptance rate. The average acceptance rate for sign up through the approval process is a little bit under 10%. So developers that are looking to sign up for the platform and go through the onboarding approval process is around 10%. So it is competitive to be able to join the platform. I didn't know that. I didn't know that. That's that's intense. That's good. But here again, here's the deal folks, it's not personal. We, what we're trying to do, again, what gun is doing in my perspective is very different.

And to be honest with you, the reason why I went to gun.io is because gun has built the thing that I was imagining when I was at make out. They built the platform, because for those of you who are part of my discord, it's exactly what I was doing. I was posting jobs. So we have to maintain a certain level of quality. And so that's why we're picky, right? Because at the end of the day, our network is our net worth with a gun. And so again, if you do get rejected because of lack, because the different skillset or years of experience, it's not personal, we promise.

But again, Victoria and I are going to come up with ways to engage you all who still want to be a part of the brand because we do want as many brand ambassadors as we can. Yes, Victoria has a really fun, cool job. I'm going to be also working at gun is like really fun and cool because it's just community building and brand building within the engineering community, which obviously we all have a passion with and Tages is good to see a brother hope things are well across the sea shot Tages You gave a killer keynote at that conference last week with myself. Love you man So we do the onboarding call and then the tech out so we so we have an entire I don't want to dive into too much of the dev We're all side because I'm bringing David G on I think next week or the week after but talk about Can you kind of just give a hint on kind of like what's next after that?

Yeah, so So post onboarding as you go through the rest of the approval process, like I said, that is going to be a technical conversation with a developer relations team member. Everyone on the developer relations team has been hired from the Gundotherio platform, come from really strong technical backgrounds, engineering management backgrounds, and are totally awesome to have conversations with, especially around your previous work. They're also going to be a heavy part of the application process for any role. So getting to talk with them, having them have a good understanding of your work background is just a nice, mostly nice bonus, but it's part of the process.

It's not even really a bonus. It's just the human element. Yeah, yeah. It's the very much a human oriented experience. And so having those one-to-one conversations is really great. Post approval call, if your profile is approved to be a part of the platform, you are invited to be a part of the Guernaro community. Within that community space, just to touch on it a little bit, we do host events every week. I host open office hours, so that way anyone that's interested in having a chat, they have questions. I just want to talk about something that they're working on. It's really interesting. Do we have a colony for that or something I can share?

If somebody wants to join the office, how can people sign up? Because I'm sure there's a lot of people on the chat who may just want to hop in. Yeah. I can send out a call and link it every week. So we'll get some set up. But I do host those every week, which is great and fun. A lot of really good conversations happen there, whether that's around some of the product features that we're rolling out, whether that's just around things within the application process for any individual developer or just being brought up generally, or even just things that people are working on. tends to be a good conversation, especially if a few people come from related fields.

It always feels like I'm just watching people talk. But it's super interesting and really fun to see those interactions happen. And then we also just host some learning sessions around the application process within the platform itself. We've held resume sessions, cover letter writing sessions, just more, I guess, tool-based or asset-based sort of opportunities for those that are wanting to learn a little bit more in those areas and looking to build out more spaces for us to have those interactions which we'll talk about later. Definitely. Yeah, Victoria and I like talk about this later. Talk about this later. If you have any more questions, please ask as we wrap up here.

Victoria, as we wrap up, there's always a few questions that I asked. The first thing is, is there anything that you've I talk about tech trends because I typically have developers on, but anything you've watched or read, or I know we talk about bonsai trees and everything else that you're watching or listening to or reading right now, that you like? I am a big podcast person during heads down time. And so the Wall Street Journal podcast around tech and business is one that I usually listen to every day. They do post every day. and really big in on the Azure Cline podcast as well. Just a little bit more longer form around one topic.

Let's me sort of sit and listen while still typing away on things, but it feels like it helps touch on a lot of different areas, but that Wall Street Journal one definitely relates more to trends we see on the work side, which is nice. I love it, I love it. Yeah. But the last question is around career advice, right? So the show's called Guidance Counselor 2.0 because we had guidance counselors in middle school, high school and college, but now as adults, you don't really have them per se. What would be your biggest piece of career advice to younger Victoria? Yeah, probably a lot of things.

But I would say the biggest piece of career specific advice to a younger me would be more around, maybe I don't know how to resist, but like the financial aspects, if you have the option to opt into a 401k, especially one that's matched. And I'm sure that that probably seems very common to most people now, but it's not something that you really touch on in high school or college really. And so as you're entering the workforce, you're like, oh no, like I'm young, making money and you can do whatever I want, but then you, as you can't hold it, you're like, okay, like, it's probably safe somewhere where I can't reach it.

Yeah, exactly. So that's the biggest me to younger me. I love it. I love it. Except for okay people. Marie comes in here. Are any good suggestions you'll have for anyone preparing to join the platform? I mean, here's, I mean, I'll let you answer as well. For me, it's not really preparing more than just spending time to enter in good data into your profile, right? Yeah, so this question gets asked, I think in a number of different ways, but same vibe every time. So as far as looking at specific tech stacks or trying to follow those around those down, is not the best way to approach at least this platform.

Because clients are looking for expertise in the technologies that they're looking to hire in, it's gonna be focused more on what you have focused on throughout your career. If that isn't a number of areas, I do let developers know that if you're a generalist, I think that's awesome, I think that's badass, but it doesn't work well on the platform because clients are looking for consistency, I would say within certain areas. So my best approach or my best answer to this question is to understand where you're hoping to get out of the platform generally, the types of roles that you're interested in pursuing, and tailor your information towards that.

That's going to be the biggest benefit to you and having your profile be consistent, but also stand out to clients with all the relevant information. I would also say that relevant information is always gonna be like my number one bullet point. You can take out a lot of the fluff, anything high level, and really focus on your specific tasks and your impact within any previous environment. Yeah, yeah, for sure. Yeah, it's not necessarily like, it's not like you need to prepare anything. Yeah. Yeah. And then Todd comes in here again, if I have 25 years of accessibility that keeps you from being placed with a job that says it's called for time.

I mean, listen, this is more of an issue in the hiring space, Todd. I mean, I will tell you this, gun, we are passionate about having senior folks on our platform to be able to place them the projects. I will tell you between Victoria and our dev rel team who I'm gonna start having on as well from a matching perspective. I don't believe this will happen with us because we're so close, not only to the engineer with Victoria and the dev rel team, but also the client side that, I mean, Victoria, I don't see this happening because we'll be your advocate in this situation. Yeah, so in the application process for any role, we review all applications individually, so there's human eyes on your information and we're looking for, let's get in that right fit, facilitating that good relationship, but focus on your previous work, so that content and context within your work history and how that aligns with what a choir is hiring for.

So in that process, we'll typically select the top three to five applicants from that and present them to a client personally. I'm sure that the rest of the dev royalty and we'll touch on this way more in depth. This is sort of like the high level overview part of it, but that does allow us to advocate for you in that process as well. Like this is why we're selecting these top three to five because of XYZ reason. This is why you should interview or hire them. So that takes away sort of that view, I guess. Yeah, exactly. What is the average duration of contracts? I mean, it seems to vary a lot.

Historically on the, it varies. So we see a good range of, we call short-term to be three months for longer, and then long-term to be six months or longer. You won't see a lot of roles that we post to be shorter than that once again because we wanna make sure that anything that we do present it has been through our clients' team and is going to be a meaningful engagement, especially for the talent that we have within the community and within the platform, knowing that the onboarding and approval process is competitive, we want to make sure that the roles that you're applying for are interested in are going to be beneficial in helping you learn and grow and are going to be cool opportunities.

I think historically on the platform, the average engagement duration is 15 months, but I think that might be a little bit of a scooter some that have been running for very long time, which is awesome. But I would say that they do tend to fall into the long term space. Yeah. Yeah, Marie. Yeah. It's to me six months short to me six months, six months, especially on a platform that was built for part time and freelance. That's long, right? Yeah. Part time freelances like 10 hours a week for three months or like, you know, 30 hours and that's it. Right. So, so again, yeah, I hear you, but but even then like right now, like I'm, I'm in our job channel right now, like we have a direct higher role that just got posted three to six months, three to six months, six plus months, six plus months, long term, salaried.

So I mean, again, like, you know, it definitely leans more at least the roles lately. It seems to have leaned more toward long term stuff. Yeah. But anyways, cool. All right, y'all. Well, that's it. Victoria, thank you. Hopefully. Thank you guys. Appreciate y'all hanging out. Hold on, we've got more questions coming out of these roles more full time. Yeah. It so again, it looks like John, for me, lately, it looks like it's more full time roles that have come in lately. And full time is considered to be 40 hours of work per week and most part time rolls will be looking for at least 20.

Yeah, yeah, yeah. Cool. I love the questions, y'all. Thank you. Thank you so much. Victoria, stay on real quick seconds about you. But y'all have a great one. And we'll see y'all tomorrow, 930 am central. Y'all take it easy. See you. Bye y'all. Hey, you did it. You listened to an entire episode and I am very grateful because you know why? There's a lot of podcasts out there. There's a lot of episodes. And I myself rarely finished an entire episode. So I appreciate you so, so much for listening. Quick reminder, please rate and review this podcast in the App Store. I want this to be discoverable to others and the only way that happens is if you take the time right now and rate and review it.

Please. Like right now. unless you're driving, then don't do it. So thank you again. If you need to reach out to me at T. Dustin on all social media handles, and I hope you have a fantastic day.