Rejected a year later….

In 2018 I made a career switch. I finished my time with the United States Army and began looking for a job as an IT Project Manager, because the role most closely matched my skill set, my training, and my degree.

I followed the formula of finding mentors, updating the resume and LinkedIn and applying for 2-3 positions a day. Some places wrote me back to tell me when I was no longer being considered a candidate. Most never provided any feedback. Eventually I landed a great position that is the start of a promising career and so I figured that phase of things was behind me. Then I got a letter from a position I applied for in August of 2017. 17 months later they told me that I did not get the position I applied for.

First off, let’s give the company credit for writing back. Most didn’t and the place where I currently work had to involve my manager initially rejecting my resume because it’s so “non-traditional.” He’s come to learn that my non-traditional experiences have allowed me to quickly adapt and be significantly functional.

I did find the situation humorous, but wonder what the talent situation was like at the company. I do hope they don’t have issues with maintaining a talent pool to be successful. I wouldn’t have applied had I not believed in what the shop did and the products they produce. I also hope I didn’t burn any bridges as I did write a bit of a tongue-in-cheek email in reply. Email is bad at conveying humor, so I’d like your (yes, you dear read) opinion on my response and any suggestions on how I could have worded this better. Here’s the exchange:


SUBJECT: Software Producer / Project Manager / Product Manager – COMPANY NAME

Jacob Roecker,

Thank you for your application! We are a growing company that is constantly on the lookout for new talent. That being said, we hire based on the needs of the company and we are always accepting applications. If we need an additional candidate for the Software Producer / Project Manager / Product Manager and we like your resume, we will contact you to set up an interview. Thank you for your patience. 


Here’s my reply:


It’s good to hear from you.  

My records show I applied for the position in August of 2017.  That’s over a year ago.  In the meantime I did a 7 month internship with an agile software development company in Boise where I served as the Director of Leader and Organizational Development managing 5 different project managers and several million dollars worth of projects.  A

fter the internship I’ve been working on an SAP S4 implementation where I was in charge of the system integrations (including international integrations in China and Mexico).  I’ve also finished publishing my fourth book and graduated with honors in my Masters in IT and Project Management.

It strikes me as odd that it takes more than a year to reply back to a position especially since I’m the sort of person who can pack a lot of experience in a single year.

As your email states, if you need an additional candidate, please let me know.  I’d be happy to continue the dialogue.

What do you think? Too harsh? Leave a comment below.

2 thoughts on “0

  1. Jacob, while your comment was undeniably warranted, and you were careful to put it mildly, whether it was too much or not depends on your desired outcome. If you simply wanted to point out the slowness in their process without being too harsh, you nailed it. If you were really interested in a continued dialogue with that company, I think any calling out on their efficiency may not be the tactic that encourages them to engage, except perhaps to snarkily defend themselves. You could have improved chances of a positive response and dialogue if you have offered to help them fix that problem. However, referring to their response timeline as “odd” may have just put their hiring staff on the defensive.

    1. We all could be better communicators. I’m certainly no exception. Thank you for pointing out how improving one word could make a big difference.

Leave a Reply

Previous post Is Anyone Reading This?
Next post Book Review: Project to Product
%d bloggers like this: