I mentioned it in a previous post and shouted about it on Facebook.
I have a new job!
I got the news last Thursday, literally as I was walking out the door to hit the road for my vacation in North Carolina. I resigned my position as a Data Management Associate at PPD and accepted a position as a Clinical Database Programmer at Medpace. I start at Medpace, a contract research organization, on July 28th. Medpace is located in Norwood, making it a slightly longer drive and across the river so I’ll be fighting the traffic, which I’ve been very lucky to have avoided so far. It is very close to Xavier, though, to that will make it easy when school starts back up in the fall.
Established in 1992, Medpace has partnered with leading pharmaceutical and biotech companies to bring promising new drugs to market. Medpace combines efficient clinical trial management with comprehensive regulatory consulting to provide Sponsors with exceptional support during the drug development process.
The integrated services at Medpace include: clinical development plan preparation, project management, regulatory document preparation, safety surveillance, clinical monitoring, data management, statistical analysis, medical writing, quality assurance auditing, and regulatory submissions.
(Warning – long-winded post ahead!)
Why a new job? I can summarize it by saying I felt PPD was not providing me with the career opportunities I desired and that I did not believe in the company’s managers, products, direction and priorities. I’ve whined and complained about the company and shared my misgivings and concerns previously, but I bit the bullet and muddled through it, trying to focus on the future. I reached my breaking point recently, though, so I’m moving on to better opportunities.
I started at PPD Global Central Labs (GCL) over three years ago in the Client Support Services department. Nine months later, seeking to return to a job where I used my degree and computer skills, I transferred to Data Management and have been there since. I started as a Data Management Associate in Data Transfers and two and a half years later, that’s still my job title and job description. During that time, not only was I responsible for data transfers, but 14 months ago I was offered and accepted the additional role of RDA programmer. (The RDA – Remote Data Access – is the company’s website that allows clients to view patient information and results.) At the time, I was one of three RDA programmers, but within a few months, that number was reduced to two and as of the start of 2008, I was the only one left. It’s been well over a year that I’ve had these dual roles, and though I consistently get strong performance reviews and positive feedback from internal and external clients, I still do not have a job title, description or pay that reflects it.
Towards the end of last year, development began on a new website (PPD Clicks), not necessarily to replace the RDA, which was on PPD GGL’s “old” system, but to more or less extend the functionality to GCL’s new system. My fellow RDA colleagues and I were not initially included in the requirement meetings and other discussions involving the development of this new website, but after making enough noise about the importance of involving the people that deal with the current website and have almost daily interaction with the users, I got myself included in the process. Eventually, this led to me being assigned the task of supporting Clicks and training users on the product, which was released early June. For those of you counting, this now made three separate and distinct roles I held within the company. Yet I still had not been promoted and my job title and job description were woefully out of touch with what I was actually doing.
Typically, the “career ladder,” as flimsy as it was, involved two years of service as a Data Management Associate before becoming a Data Management Specialist. The role of Specialist involved more responsibility, and when my two years came and went with no promotion, the reason I was given at the time was that I was not going to have this additional responsibility due to my other roles. However, I was promised in February that my name would be submitted for a promotion in April.
April came and went and I heard nothing. Another month passed and then the calendar page flipped to June. Having endured 5 months of potential lost income and experience under a new job title, I again inquired about my position. This time I was ignored and heard no response to my query.
While that was one huge sore point for me, one that made my blood boil each time I thought about it, I endured, figuring I would eventually be rewarded for my service. However, the proverbial straw that broke the camel’s back soon came.
The data transfer group was down three employees since the start of the year and we were extremely busy and frustrated. We voiced our concerns to the manager at our group meetings, but nothing could be done due to a hiring freeze. (There was also a freeze on overtime, and as much as I tried to make sense of how a smaller than normal staff could do the same amount of work without incurring overtime, the fuzzy math was just not working for me. I guess I have to be a manager to make sense of it.) It turned out that the hiring freeze was really not so much of a freeze after all. The finance department hired two new employees and the company created and filled two new director positions. One of these director positions was in the Data Management department. We already had two managers/directors for a reduced-size department, so we all scratched our head and wondered, aloud and to our manager, why another director was needed when we needed more “down in the trenches” employees. Additionally, this director would not have any direct reports; we would all still report to our current manager. The creation and hire of a new director role did not send a good message to the department and left a very bad taste in our mouth.
The final piece of the puzzle came when our manager announced the “hiring freeze” would be lifted for our department and approval had been granted to hire one (just one) new employee. And the position profile that had been posted was for a Data Management Specialist. Yes, that is the very position that I should now hold and which supposedly required two years of experience as an Associate.
It was at this point that I knew it was time to move on from PPD, that I was not and would not gain the business and management knowledge and experience, or the compensation, I was seeking to reach my goal of being a successful entrepreneur. (There were several other factors besides the three I mentioned that led to this decision as well, but I won’t/can’t go into those details. And in hindsight, I did gain a lot of experience and learn important lessons, only it was in what not to do.)
It was a bittersweet pill to swallow. I hate throwing in the towel and having to start over. I very much want to stay at one company for years and invest myself in the company and it’s people, products and services. I had started doing this at PPD and very much liked the feeling. I’ve worked very hard to get where I was, with the multiple and varied roles and responsibilities. My name was out there and I was being noticed by the people that mattered. I did like what I was doing and did appreciate the opportunities I had been given. I liked my co-workers, my hours, the location. There was even talk of making me a Product Manager for PPD Clicks ***.
But I needed to put this aside and think about the future. The patterns where there, that this wasn’t a one time oversight and I would continue to bump my head on the ceiling and against the walls placed by upper management.
It only made sense, given I enjoyed the type of work I was doing, to search for another company in the pharmaceutical industry. It didn’t take long for my search to lead to Medpace. I was cautious viewing it this way, but it seemed God laid the opportunity in front of me, opening a door for me to walk through. First, there was much talk (again) at PPD about Medpace, the former employees that were now working there and what they had going for them (Medpace is planning an IPO). Second, when I ran the Flying Pig 10k, there was a employment brochure in the swag bag. Seemed out of place to me, so I took notice. Thirdly, one of my co-workers sent me a CareerBuilder profile for a job at Medpace, a job that was very similar to the data transfer portion of my job at PPD. These were several of the coincidences that I ultimately prayed about and got the sense they weren’t coincidences after all. As Einstein is quoted as saying – “Coincidence is God’s way of remaining anonymous.”

So I applied, interviewed and got offered a position at Medpace. While I was more than ready to leave PPD, it still was not an easy decision. I tried very hard not to let emotions or compensation get in the way. Not only will I be making 14% more starting off at Medpace than I did after three years at PPD, Medpace also pays four times more towards tuition reimbursement. (Added bonus – they have a business casual work environment and jeans are allowed! Woohoo! And they have a 24 hour fitness room with a free personal trainer.) Hard to not like that, but there is so much more than the financial aspects of the decision. Given my experiences at PPD, I knew the types of questions to ask during my interview and what cracks in the foundation I needed to look for. No company (well, almost none) is perfect, and Medpace is no exception, but the cracks and issues I did find do not appear significant or that they will hinder my career, at least from my perspective at this time.
My vacation also came at the perfect time, giving me time away from the frustrations of the office, the chance to clear my head and look at the situation from a more relaxed perspective. I talked it over with some friends and my parents to make sure I was seeing things clearly and considering all aspects of the decision.
On top of me leaving for Medpace, so are two of my fellow co-workers, with a third potentially leaving in the near future. This is in addition to the dozen or so former PPD employees that are already working there. (See my Sinking Ship posts.) This actually made me hesitant, wondering if Medpace really wanted us or was just trying to hurt the competition. I talked it over with my co-workers and we ultimately concluded (correctly or not it remains to be seen) that Medpace recognized the talented and hard-working team that was laid on their doorstep and didn’t want to pass up the opportunity to bring us on board, even if they didn’t necessarily need all of us at present. (On a side note here, you would think PPD would have learned by now to include a non-competition, non-solicitation clause in the contracts, something Medpace wasted no time in mentioned or having me sign, which was a bit scary.)
So, while it will be a different environment at a new company, it won’t be a total shock – I already know about the industry, the job and quite a few of the people. In fact, the thing I’m most concerned with is being bored. Given all the hats I was wearing at PPD, it’s going to be more of a shock to me having just one role.
I am determined that this will be the last time I “start over” at a company. I will work my way up the career ladder at Medpace, hopefully faster than I did at PPD since I have more experience and lessons under my belt, and get a management role within a few years. I want to get my internet café and bookstore off the ground and running in the mid-distant future.
I still have two weeks left at PPD and I am trying my best to leave them in the best shape possible and not burn any bridges. Management is actually making this tough. I’ve been disappointed in how they are handling the loss of three talented employees, each of which are doing his best to help during this transition. Seeing this just re-affirms I made the best decision.
Here’s to moving on, better career opportunities and taking additional steps towards achieving a life goal!
*** Being Product Manager of PPD Clicks would have been a truly great career opportunity. However, I realized how much I was forcing myself to sell and believe in the product. I didn’t like the interface, disagreed with the direction upper management was taking it and did not feel it was a challenge to our competitors’ products. As PM, I would have some influence on the future direction, but my vision differed from the decision makers and it felt like I was trying to steer the Titanic. How could I possibly be an effective Product Manager in this environment, regardless of what it would have meant for my career? Have you seen the
“tree” comic on project management? I’m frequently reminded of that in relation to this particular product.