From RD to PM: A Half-Year in the Trenches
This article details the speaker's experience transitioning from a System Engineer (RD) role to a Project Manager (PM) position at a tech company specializing in laptops. After three years of feeling burnt out as an RD, they decided to resign and pursue a different career path.
Landing the PM Role
An opportunity arose when a former colleague noticed their resume and suggested them for a PM role. The speaker had prior experience collaborating with PMs, which gave them some insight into the job. The initial thought of being on the other side and "chasing" RDs was appealing, leading them to accept the offer.
The Reality of Being a PM
The speaker quickly realized that being a PM was more challenging than anticipated. The role shifted from dealing with code and bugs to managing clients and colleagues, requiring a constant awareness of others' perspectives. Problem-solving often depended on external help, while their own responsibilities revolved around daily reporting and tracking progress.
-
Difficulty communicating with some RDs led to project delays.
-
The speaker felt caught in the middle, facing pressure from management regarding project progress while lacking the direct ability to assist the RDs.
-
Their previous experience as an RD proved helpful in navigating technical discussions and preventing engineers from misleading them.
Internal vs. External Pressure
According to the speaker, internal pressures from engineers accounted for roughly 30% of their overall stress. The biggest burden stemmed from dealing with demanding and inconsistent client requests. Clients would frequently change requirements, exhibiting poor memory, while the speaker was expected to agree and relay these changes to the RD team.
-
When clients imposed unrealistic deadlines, the speaker would agree to "try their best" despite knowing the impossibility of meeting the demands.
-
Their approach was to delay as much as possible, recognizing it as their remaining leverage.
Reflections on the PM Experience
The speaker realized the PM role required strong social skills, high emotional intelligence, and the ability to accommodate illogical client demands – a stark contrast to their direct and straightforward style as an RD.
A Return to RD
After about six months as a PM, coinciding with a post-pandemic hiring boom, the speaker decided to resign and seek RD positions at other companies. They viewed the PM experience as a valuable, albeit brief, chapter.
Key Takeaways
-
The role involved constant communication between departments.
-
PMs acted as translators for clients.
-
Ultimately, PMs shouldered the responsibility for project outcomes.
-
The speaker emphasizes the respect they have for those working in the PM field. Despite the difficulties, the experience proved beneficial for their future career endeavors.