This is my 2nd story. Like the first one, the events in this story are also factual. I hope you enjoy. Happy reading!
*
Very few things in life will cause a man's pride to suffer more than finding himself unexpectedly without a job, a means to support his family. It's a sick feeling that doesn't go away. Every day of unemployment deepens the feeling of dread. It's a physical glooming, like being punched in the gut every morning, a deprivation of self-worth. It doesn't matter how supportive the wife and kids are. Pride is a tricky thing. Once taken away, only the pride-stricken man himself can restore it. And the way to restore it is by finding a new job. Being the bread-winner again.
This is the situation where I found myself in 2009. Laid off from a good job. My name is Joe. I have a wife and 4 grown kids, 2 of them just out of college, the other 2 were about to start. In 2009 I was 48 years old and liked to consider myself a well-rounded man. I enjoy a geek job by day, when I'm actually employed, and working with my hands in the yard and garage on weekends. Not the typical nerd. I'm athletic, play in a softball league, pickup basketball games. Tall and somewhat rangy, I have salt-n-pepper hair, mostly salt, blue eyes, always smiling. Love to swim and stay in shape. And I can be a little too prideful.
By trade, I'm a software test manager. I started out as software developer in the late 80s, but didn't like being confined inside a virtual box of bits and code. The part of my job I enjoyed most was testing my code, testing the associated applications, and testing code that other developers produced. I like breaking things. Always have. I also like software technology. Combining those 2 things led me down the path of my career. I learned myriads of software tools that bent, stretched, and eventually broke software applications. It was fun. Geeky fun, but still fun to me.
Living in the suburbs of one of the 5 biggest technology cities in America, there never seemed to be a shortage of companies who could use my services. I led teams of application testers in the pursuit of software quality assurance. I saved companies money, sometimes a lot of money, but the savings had to be derived through statistics and projections of software bugs, production issues, a reduction of hours spent by developers fixing bugs, and the ability for companies to push their software products to market quicker because of this. I wasn't actually earning money for companies.
The oil and gas industry fell on hard times in the late 2000s. Companies downsized and cut corners to save money any way they could. Software testing was an expense. A luxury. A non-revenue bearing workstream. So this is how I found myself laid off one day from a really good gig, and it took 7 months before I found a new one. I networked my ass off while unemployed. I worked as hard or even harder at finding a new job than I did while actually on a job. As it turned out, I didn't find a new job. The job found me.
In the span of one long but fulfilling day, I was called by a technology lead for a global consulting firm, interviewed on the phone, in person, and received an offer that same day. Just like that. Seven months of soul-searching, pride-wringing, finances-fretting, and it was entirely alleviated within 8 hours. I thanked my lucky stars.
The very next day I reported to their downtown office, and was immediately sent to the client site for which I would potentially be working. Through the expedited interview process, I was told that the client had to approve me for their project. If their decision was negative, I would be let go. Simple as that. Fortunately, the client loved me and wanted me to start with them immediately. Huge sigh of relief. I returned to the consulting office to finish the paperwork process. I was to report directly to the client site the next day to begin work on the project.
I was hired to be the test manager for a very large public sector project to design, build and implement a new city government court case management system. The system was to be an end-to-end software application configuration, starting on one end with the software processes behind officers issuing tickets, warrant checks, through the entire judicial process, jail, release, and everything software in-between. A large team of consultants, myself included, teamed with dozens of subject-matter experts from the city in a co-development effort to design the software architecture and applications. The project was located on an entire floor of a city office building. Every inner wall was removed to promote an open project collaboration. The project was scheduled to last 5 years and it proved to be the most fun, most interesting, and greatest learning experience I've had in my career.
I became engrossed in the project, truly loving every minute of work during the lengthy 2 year architectural design cycle. Once software development started, code being slung, new faces were brought into the project to assume various key roles. Since I was the test manager, I needed to know every single aspect of the immense system functional behavior, as it was being built. All of the functionality needed to be documented from end to end, so a team of documentation experts was brought in. I was elected to work with the documentation team, since I knew the most about what they needed to capture. I was to spend 2 hours every morning with the 4-person team, then we would split up and do our stuff for the rest of the day. They would produce the documentation, I would work with my team of testers in validating the system behavior.
The docs team was made up of two men and two women. They were professional, courteous, very sharp, and seemed to be extremely good in what they were hired to do. We made a good, dynamic group for the time we spent together. I would walk them through a piece of system functionality that I projected onto a smartboard screen, showing them all the possible routes a user could take through the system, answering their questions, and they would go off and create the user manuals and technical manuals and whatever else they needed to document. We got along great together. We worked hard but we also joked around, had fun, kidded, and really enjoyed our working relationship. Of course we got to know each other personally too.
One of the guys, Lawrence, was married for a long time and although he was deeply religious, still shared some risqué humor. The other guy, Tavares, was younger and engaged to a lovely young lady. He was kinda quiet. The team lead was Gretchen, who was in her mid 50s and obviously very much in love with her husband; pictures of the two of them scattered around her desk. She talked about him, their children and grandchildren every chance she got. I envied her for her life happiness. And then there was Kelly.
I felt a physical attraction to Kelly almost right away. Where I was tall, 6'2", she was short, barely 5'0", if that. The top of her head was well beneath my chin. I'm not skinny but more lean than muscular, with broad shoulders, around 205 lbs. Kelly was not thin but not at all unappealing, weighing around 140 very sexy lbs. Lovely shoulder-length auburn hair, big beautiful blue eyes, a gorgeous round face, plus-sized derriere that looked so sensual when she moved, and really large boobs that stood out on her short frame. She wore pretty dresses that displayed just a hint of cleavage, enough to make me wonder what the rest of her looked like. Kelly, like me, was married, but her home was 200 miles away. She took the job on the project because it paid nearly twice as much as she'd ever earned before. She rented a small apartment downtown that was a quick cab ride to our project office and took the 'superbus' home after work on Friday late afternoons, returning Sunday evenings. Kelly was around 10 years younger than me, but her spouse was a dozen years older. She spoke fondly of him although I could tell something was missing in their relationship. She could probably see something absent in my marital relationship too. I think we're both emotionally transparent.