Why I Learned Python as a PM

Three years ago, I decided to learn Python. Not because my job required it. Not because I wanted to become a developer. I learned it because I was tired of being dependent on engineering bandwidth for problems I could solve myself.

The Trigger

I needed to analyze three months of Jira data to identify patterns in our sprint completion rates. The data was in CSV exports. I could have spent hours in Excel with VLOOKUP formulas, or I could learn enough Python to write a script that did it in seconds. I chose Python.

That first script was terrible. Hardcoded file paths, no error handling, variable names like x and temp. But it worked. It processed the data in under a second and produced the analysis I needed. I was hooked.

What I Built Over Time

From CSV analysis, I moved to API integrations. I wrote scripts that pulled data from Jira's REST API, calculated custom metrics, and generated reports. Then I discovered FastAPI and started building actual services. Today, I maintain an internal capacity planning tool and am building an Engineering Intelligence Platform.

What It Unlocked

Python gave me three things. Autonomy — I can solve my own data problems without filing tickets. Credibility — engineers take me more seriously when I understand their tools and constraints. And perspective — writing code, even simple code, gave me empathy for the challenges developers face daily.

The Path I Recommend

Start with data analysis. Pandas and basic file operations. Then move to API consumption with the requests library. Then build something small with FastAPI. Each step builds on the last, and each step makes you a more effective PM.

You do not need to become a software engineer. You need to become a PM who can speak the language and solve your own problems. Python is the shortest path to both.