My Application for the Project Delivery Coordinator position at Jacobs was greatly influenced by the job description. The job announcement clearly outlined responsibilities and needs for the job, making me assess whether my project coordinator background would be appropriate. Key elements such as supporting project teams, managing communications, overseeing administrative activities, and coordinating with clients, as well as sub-consultants, aligned with my previous work in project coordination; thus, I considered applying.
Once I began working, I realized that many of the responsibilities indicated in the list matched with the reality of the work. The necessity to help project/program managers create reports and contribute to budget tracking was an integral part of my day-to-day tasks. I also appreciated how being independent was in the job description since most of my activities involved working independently with different things to be done, something that I used to struggle with, but ultimately enjoyed.
Differences also existed. The job description involved such tools as Oracle reports, Excel, and MS Project. Greater emphasis was placed upon project life cycle proficiency and client relationship development than I had anticipated from the beginning. I had experience in some processes of project life cycles, but needed to learn more processes and more technical tools of fiscal management. This was more detailed than I had originally thought from the job description. The job description represented overall responsibilities accurately, but day-to-day aspects of the position evolved as I learned through hands-on experience. The job description provided me with an understanding of expectations, but the fine lines in day-to-day operations did not become apparent until I adapted to the job.
2 replies on “Week 3: Job Description”
Thank you for sharing your experience! I found it really insightful how closely your role aligned with the job description, especially in terms of supporting project teams and working independently. It’s encouraging to hear that the responsibilities listed gave you a clear understanding of what to expect and even helped you grow in areas like independent work.
I also appreciated your point about how some of the day-to-day aspects, like fiscal tools and project life cycle details, weren’t fully captured in the job posting. That resonates with my own experience—I’ve noticed that job descriptions often highlight the broad strokes, but the finer, more technical aspects only emerge once you’re fully immersed in the role. It’s interesting how you described needing to learn more tools and technical processes on the job; it sounds like that presented both a challenge and a learning opportunity for you.
Your post made me reflect on how important it is to go beyond the job description when evaluating whether a position will be a good fit—both in terms of skills and workplace expectations. Thanks again for sharing your journey!
Hi Shumin,
I really enjoyed reading your post! You did a great job explaining how the job description helped you assess your fit for the Project Delivery Coordinator role — especially how your previous project coordination experience aligned. It’s interesting that the description emphasized independence, and I liked how you reflected on your personal growth in that area. It’s great that the company was upfront about that expectation, and it sounds like you were able to rise to the challenge.
I also relate to your experience with discovering more about the role once you were actually doing the work. Job descriptions can only cover so much, and like you mentioned, the day-to-day reality often fills in the “fine lines.” I think your point about learning more technical tools like Oracle and MS Project is an important reminder that job descriptions often assume a level of familiarity that isn’t always immediately obvious to new hires.
Your post really highlighted how job descriptions can set a strong foundation, but true understanding often comes through experience. Great insights.