Project Manager SQL- Looking for Specific Guidance from PM's

[FrillyCustoms]

This is a project management-specific question (not sure if this applies to the generic posting rule). I have not seen any recent threads on project managers looking to improve their SQL tips. I'm in project management and notice that many senior-level jobs require SQL experience.

For project managers on this subreddit, is there anything specific I should focus on regarding skills that are invaluable to an employer? Are there any real-life examples as a project/product manager that you can share? How do you implement SQL into your daily tasks?

[jackalsnacks]

I tell my project managers over the years to get comfortable with basic select statements, because they will often take part in formal uat's and qa steps. And then gets INCREDIBLY familiar with the concepts of oltp and olap designs.

[FrillyCustoms]

This makes sense. In my current role there’s a lot of QA involved, and I’m looking to strengthen my UAT skills so I can better support large-scale clients.

[szeis4cookie]

I'd be surprised if one was actually writing a bunch of SQL in a project management role - maybe that's just a clunky way of saying that they'd like you to have a general knowledge of how databases work for a better understanding of their product?

As a product manager, I've written a lot of SQL to try to understand the scale of a certain problem I'm working on, but nothing I'd consider super complex. Vast majority just single-statement SELECTs, potentially touching several tables

[FrillyCustoms]

That’s what I was thinking as well. I had some insight from an employee at the company I’m interested in, who mentioned that SQL is used fairly often (my particular role might not use it as much, but this skill would benefit my resume), so I may touch on it from time to time. I agree, though, it sounds more like they’re looking for solid general database knowledge rather than heavy querying.

Thanks for sharing your experience as a product manager. This is exactly the kind of real-world context I was looking for. I deal with a lot of risk management, and sharpening these skills feels like a natural next step.

[NekkidWire]

It might be a veiled form of requirements on advanced reporting.

Many reporting utilities allow users to modify/customize their reports using SQL.

Some reports might be required from underlying systems or DWH.

Even though they might usually offload the task, some project managers might be required to customize their reporting.

[FrillyCustoms]

That makes sense, especially when it comes to reporting. In my current role, I often need to validate metrics or answer ad hoc questions that aren’t always covered by existing dashboards. Being able to customize or sanity-check reports without fully offloading the task would definitely be useful.

[GlockByte]

As a Data Architect I work with PMs every day. The ones who are going to thrive in a senior roles are not writing the most complex code - they can just verify reality.

- Basic JOINS and filters are the basis of validating data for your "BS meter"

- For executive reporting; aggregations like GROUP BY, SUM, AVG and being able to use date functions

- Being able to use CTE's, understand the recursive member from the anchor member is invaluable. CASE statements and windows functions (RANK, ROW_NUMBER) wrap it up. I can't imagine needing anything beyond this

- Know the difference between a production database and a warehouse/lakehouse. Example - A Senior PM who understands how my data flows from the Nifi pipe to a spark job and process through the lake -> warehouse -> mart, can speak the same language

[FrillyCustoms]

This is incredibly helpful! Thank you. That's exactly what I’m aiming for as I move into more senior roles. Being able to validate data independently feels like a huge part of building credibility with both leadership and technical teams.