Please login or join to subscribe to this thread
The job title doesn't matter as much as the experience. In most of my PM roles, my title was something else and I have seen many "PM" job descriptions which are more administrative than project leadership.
Part of the value in the PMP certification is that it does require experience performing PM job functions but many of those functions are not exclusive to the PM. Technical principals/leads for example, typically plan and manage their team's own work, essentially managing projects within larger projects.
When applying for a PM position, demonstrating that you can perform the essential job functions will carry much more weight than someone who has a certification, but can't show the experience. It could get you in the door in an entry level PM/project administrator position and pass some HR application filters, but for roles with significant responsibility, hiring managers will probably look more at your experience than your certs.
You can double check with customer care, but the current PMP requirements include having the prerequisite experience (36 months leading projects if you have a 4 year degree, 60 months without), when you apply to take the exam.
You need to have had end-to-end (full lifecycle) experience leading projects. In general, solo (i.e. you were PM and sole contributor) projects are not considered eligible, and there does need to be substantiating evidence of the role you played in case your application gets audited.
Kiron is totally right and to answer your question: Certifications are merely a proof that you have in-depth knowledge but are not a proof that someone is capable of doing the job.
I agree with Kiron. However, job title is not important.
You mentioned that projects where you're PM and sole contributor are not eligible to count toward the PMP certification. This is news to me. Does this mean that my freelance software development work, where I developed all of the software myself, can't be counted?
To be clear there were always multiple stakeholders, providers of expert judgment and technical expertise, at least two lawyers, etc. involved. I managed all of their involvement. But I wrote all of the actual code myself.
You've answered your own question: software development work is not project management work.
Please login or join to reply