but I didn't know what I was doing. So that role, that role isn't necessarily coding. It puts you in, not at all. Okay, they say it puts you near it. Right. Right. Right. Okay. Yeah. So, so I started as a medical records analyst, not coding at all, doing more administrative things and, you know, scanning papers, things of that nature. And then from there, we actually had a coder position open up at that same health system, and they knew that I was certified and that I was about to graduate with my RHIT, so they asked me if I would like to interview. And I said, yeah, of course, you know, why wouldn't I? So I interviewed, and they were amazing. I was actually about to go on maternity leave at the time, and they said, you know, you can just start whenever you get back. So that's that was my first coding job. Yeah. That's awesome. How long were you in that position for? I was with that. I finished that position and it was about six or seven months I'd say before I moved to contract coding. Okay. And what would you say to someone watching you struggling to get that first position? What would you tell them? Definitely have a great resume. I think that a lot of it has to do with your interview skills and how confident you are in the way that you speak about yourself, or I like to call it selling yourself, but not in a negative way. You don't oversell yourself, but understand where your strengths and your weaknesses are and make sure that you can use your words to properly convey that to the person that is interviewing you