Susan Gerock8:11
It is so funny because I am truly the accidental technologist, and I'll tell you why. I was working for a manufacturing company in Central Virginia, and I had done some different jobs there. I had started out working with them on a very large bid that we were doing for a government contract. And when we did not get that bid, I probably should have lost my job, but they had been very pleased with the work I had done, so they said, 'You know what? Let's stick her somewhere else in the company, just to kind of keep her around.' So they put me in our engineering department. My background is in political science and economics, so I have really no business in an engineering department for a manufacturing company, but there I was. And so I thought, 'Well, you know, if I'm here, I really need to find a way to contribute.' I was pretty young, I was probably 23, 24 years old at the time. So I started doing a lot of technical writing for them, really because the engineers were really, really good at the technical stuff but not good at the communications type of thing. So I started doing technical writing. I actually went to school at night to learn AutoCAD so that I could start doing some drafting and some online drafting, and that was one of the things the company noticed: 'Wow, she really picks up computer programs very quickly.' I did not have a computer background at all, but any time new software would come in that they wanted somebody to look at, they'd throw it at me and say, 'Figure out how to use this.' I think I started out on Microsoft Project 1.0 or something like that, so I'm really aging myself desperately at this point. But when the company was preparing for the year 2000, they had all kinds of custom code that was very old that needed to be retrofitted, and they took one look at it and said, 'We can't do that. There's no way on this earth. We're going to have to get an off-the-shelf system.' So they bought JD Edwards, which crosses a lot of different disciplines, and they were implementing JD Edwards at the company. They asked me to represent the engineering department and the sales department in the implementation. So I was on the project team. Once again, it was something like, 'Wow, I really get this. I like this.' Our president noticed that and he said, 'You know what? I need to move you to IT.' So before I knew it, I was in an IT job, which also involved me being responsible for payroll, which is not something I ever would have wanted to sign up for, for a manufacturing company that had multiple shifts and multiple types of shifts. So I had to be able to explain to people who'd come in and say, 'My paycheck doesn't look right,' and I had to be able to explain to them, 'Here is how we calculated your paycheck because you were on these different shifts.' So I certainly had a lot of interesting times, let's put it that way. During this time, I had met my husband and we were getting married, and he lived in the Washington, DC area. And so since my job prospects in DC would be much better than his in Central Virginia, we decided that I would move to DC when we got married. Well, when I started looking for jobs, here came a recruiter and said, 'We're looking for somebody who knows JD Edwards, and oh by the way, it's a real estate company.' I said, 'Okay, that's fine.' So as I was going through the interview process, they said, 'You know what? We know you know the technology, so we're comfortable with that. We feel like you have good customer service skills, good people skills. We can teach you the real estate.' And a real estate technologist was born in 1995. And really from that point on, my career for the most part has been in real estate technology, whether it was in consulting, whether it was in serving from more of a vendor standpoint and servicing companies that were in real estate. I've spent a lot of time, especially coming up on the application side of the IT business in real estate, so really having to understand all of the business applications, understand a real estate company's processes and requirements. I've spent most of my career in public companies, so understanding that dynamic as well. That's been the journey. And people keep saying, 'What do you want to be when you grow up?' And I think that is still yet to come. Who knows what the next career might be?