1. How did you find your career?/QUOTE]
Went to work for a little growing place that advertised for conference call operators. That led to techie titles Field Engineer, Lead Product Support Engineer, etc... to Manager.
2. Was it based on your interests at the time or was it strictly for money?
At first, 100% for the money. I had a personal computer of some sort since 1984 as a kid and an interest in tech, but that only helped later.
3. How often have you changed careers so far?
Depends on how you define "career". All have been tech related, many have had a telecom bent if not pure telecom. Always been the guy who would get handed a tech problem even if I'd never even seen the widget before, whatever it was, and go fix it. Most of the job titles were all over the map.
4. Are you happy or just stuck in it at this point?
Days when you get to fix the problems and make things better are great.
Days sitting around waiting for stuff to break are just "okay". You'd rather be doing something else other than warming a chair for a paycheck. Call me when it breaks. That's why I designed it not to fail and to fail safe. And we have cellular data now. I started this crap when companies thought getting us pagers was too expensive and we fixed stuff via modem remotely.
Days where everyone is bitching about some problem the company has deemed not-worthy of fixing even if you know it would only take a few days to do it, are not great. "Can't we fix that?" Yeah, we can. But the boss said not to work on it. Sorry.
Days watching people struggle with PCs who really shouldn't even be in the job roles they're in if they don't know how to use the things at a basic level (and knowing companies don't train basic computer skill anymore), are really bad.
Days spent fixing the exact same problem you fixed 20 years ago, and 15 years ago, and 10 years ago, and 5 years ago, and last year, are a mixed bag. Usually half the company is freaking out and super relieved when you fix it, but you're thinking "I warned them about this stupidity and they didn't listen.", while you smile and fix it, at 2AM.
Biggest change in the industry from when I started was software release cycles were on schedules of about a half a year to a year when I started. Now they're literally daily or multiple times a day in some cases. None of the code got any significantly better really. Same dumb bugs as 20 years ago.
Not stuck, but not that interested anymore in watching the next generation figure out the same problems the previous ones did.
Paycheck is great. The industry seems to at least pay for experience. But money is not 100% why I'm doing it anymore and I'm probably going to leave the industry over lack of reasonable vacation time sometime in the next year or two.
Tired of finding or knowing ways to save people lots of money on systems and still missing things like the Gaston's fly-in because the companies think they have big problems that only one person can fix and can't afford enough people to kick us out for a month or two a year. This crap isn't that hard.
People seem to recognize I do good work. They talk about "how well all this stuff ran" when I was there. Last place said they'd hire me back, when I talked to them at lunch one day. "We just fired your third replacement."
So at least I have that whole "reputation" thing going for me at this stage. LOL!
Successful small IT companies get bought out. Mergers are horrible almost always, unless you have equity. And a lot of it. Everyone jostling for a deck chair on the Titanic.
Been pretty seriously considering quitting tech and getting a pile of ratings and seeing where the chips fall. In a much better place to do that now than when I was 20.