{"id":81464,"date":"2024-01-25T21:24:13","date_gmt":"2024-01-25T21:24:13","guid":{"rendered":"https:\/\/www.prodpad.com\/?p=81464"},"modified":"2025-01-13T16:24:56","modified_gmt":"2025-01-13T16:24:56","slug":"do-product-managers-need-to-code","status":"publish","type":"post","link":"https:\/\/www.prodpad.com\/blog\/do-product-managers-need-to-code\/","title":{"rendered":"Do Product Managers Need To Code?"},"content":{"rendered":"\n

Product Management today isn\u2019t the same beast it was ten years ago. Processes shift, methodologies rise and fall, and new tools are constantly changing how we do things. One recent hot topic that tends to<\/a> crop up<\/a> on Reddit<\/a>: Do Product Managers need to code?<\/p>\n\n\n\n\n\n



I sat down with ProdPad’s Head of Product, Kirsty Kearney-Greig,<\/a> to get her take on the question after gaining over a decade of experience in the tech field. Is coding a must-have skill for Product Managers<\/a>, or just an added bonus in your toolbox?<\/p>\n\n\n\n

\"A\"<\/figure>\n\n\n\n

So, should product managers learn to code?<\/h2>\n\n\n\n

Whether or not to learn how to code isn\u2019t just about adding another skill to your repertoire; it’s about the need to understand the core of what makes digital products tick. But, as with most things Product, this isn’t a black-and-white issue.

A lot of people represent knowing how to code as some sort of superpower in our tech-driven world. After all, for PMs it promises a better understanding of the products we manage and a closer connection with the engineering teams.

However, how necessary code really is for PMs isn\u2019t set in stone. Not all Product Management roles require much technical expertise, let alone being able to actually sit down and bash out lines of code. And there’s a beauty in focusing on what PMs do best: bridging the gap between business needs, user experience, and technology.

Kirsty was pretty direct when I asked her if Product Managers need to code:<\/p>\n\n\n\n

\n

\u201cMy general answer would be no, I don’t think that Product Managers do need to code<\/strong>. Unless you’re working in a specifically code-focused product. Of course, knowing and speaking those languages, understanding the difference between backend and frontend, databases, that kind of stuff is useful, I think.

\u201cBut I wouldn’t expect any of my PMs to sit there and, you know, write out some JavaScript. That’s not their job. Their job is to be defining problems, and understanding that side of things.”<\/p>\n<\/blockquote>\n\n\n\n

When is knowing how to code useful for Product Managers?<\/h2>\n\n\n\n

Of course, there are always exceptions to every rule. When I asked Kirsty if there were times when having some specific coding knowledge would be a benefit for a Product Manager, she did have a pretty solid exemplar:<\/p>\n\n\n\n

\n

\u201cUsing one of our customers as an example, Liz Love<\/a>, who used to work with us, now works at Secure Code Warrior<\/a>. It’s a platform to learn how to code, basically. When they were hiring a PM, they obviously wanted someone specifically who had coding knowledge and experience, because part of the product is an interface in which you’re learning and editing code.

\u201cSo, if your product is about teaching people how to code or it has some sort of specific coding focus, then having some basic coding knowledge can be useful. But, as a general rule, I don’t think you need<\/em> to know how to code.\u201d<\/p>\n<\/blockquote>\n\n\n\n

Chatting with Kirsty, it quickly became clear that the context of your product and company plays a significant role in how important knowing code is. If you’re working on a tech-heavy product or in a very early-stage startup environment, coding knowledge can be invaluable.

Of course, it also helps if you can speak the language of your Developers, and if you\u2019ve got your head around the intricacies of how their development process works. But for many other Product Managers, especially those in less technical domains, the story might be different.<\/p>\n\n\n\n

Learning your engineers\u2019 languages<\/h3>\n\n\n\n

If you don\u2019t need to be able to write code yourself, does that mean you can just go ahead and ignore that side of the Product knowledge base? The answer may shock you! (Spoilers: it won\u2019t shock you.)

Of course you can\u2019t just ignore it, you fool! Don\u2019t be so damn lazy! I’ll let Kirsty explain why coding\u2019s still something that needs to be on your radar:<\/p>\n\n\n\n

\n

\u201cI don’t think you need hard coding skills. But what you do need<\/em> to have is a technical understanding of your own stack and the product that you are managing, what it’s built on, and what it uses. That\u2019s so you can speak the same language as the Engineering or Development team when they discuss what you’re working with.\u201d<\/p>\n<\/blockquote>\n\n\n\n

That having been said, it\u2019s not just about being able to discuss things with the Devs and know what they\u2019re going on about:<\/p>\n\n\n\n

\n

\u201cIt can also be useful to have a basic understanding of things like frontend code, HTML, and CSS, because it can allow you to speak the language of your designers as well. Having some SQL knowledge can also be quite useful for data analysis. But having enough of a working understanding to talk about something isn\u2019t the same as needing to know all of the ins and outs.\u201d<\/p>\n<\/blockquote>\n\n\n\n

Staying in your lane<\/h3>\n\n\n\n

The essence of being a PM often lies in strategic thinking, problem-solving, and user advocacy, skills that don’t really require any specific coding prowess. PMs are the orchestrators who ensure all parts of the product symphony play in harmony, and sometimes that means leaving the coding to the experts.

As Kirsty puts it:<\/p>\n\n\n\n

\n

\u201cA Product person’s job isn\u2019t to have all the answers yourself, but to surround yourself with the people that know more than you do in a specific subject matter. And Developers do coding day-in, day-out. That’s their<\/em> job.\u201d<\/p>\n<\/blockquote>\n\n\n\n

So, do Product Managers need to learn to code? Kirsty\u2019s take is that most of the time you don\u2019t need it, but there are exceptions to the rule. It’s more about aligning your skills with the needs of your product and team:<\/p>\n\n\n\n

\n

\u201cThere\u2019s a very well-known Venn diagram where you have three circles: business, design, and tech. Of course, Product people are at the center of that diagram, but most people are aligned to just one of those circles, or a couple of them, rather than all three.\u201d<\/p>\n<\/blockquote>\n\n\n\n

Essentially, learning to code is a personal decision that hinges on your career path, interests, and the specific demands of your role. And, of course, all of those can always change!<\/p>\n\n\n\n

What are the advantages of knowing code as a product manager?<\/h2>\n\n\n\n

According to Kirsty, and other fine Product folks out there, there are several compelling advantages of having some coding skills in your toolkit.

Firstly, enhanced communication with technical teams<\/strong>. Understanding the basics of coding can go a long way toward bridging the gap between Product Managers and Developers.

It’s like knowing a bit of the local language when traveling to a foreign country \u2013 it goes a long way in building rapport and respect, and it makes getting things done quicker and easier. Improved communication fosters a more collaborative environment where ideas flow more freely and technical constraints and possibilities are understood more quickly.

Another advantage is that you\u2019ll have greater autonomy and problem-solving ability<\/strong>. Some PMs, especially those in fresher start-ups, might encounter occasions where a basic understanding of code will allow them to independently troubleshoot minor issues or understand the feasibility of a feature without needing to pick the brains of their technical team. It empowers Product Managers to make more informed decisions and makes for a smoother product development process.

Plus, a Product Manager knowing how to code could gain a competitive edge in the job market<\/strong>. As Kirsty pointed out in our conversation, while it’s not a mandatory skill, it’s certainly a valuable one. In some companies, especially those with a heavy tech focus, a Product Manager who can understand and contribute to technical discussions is a significant asset.

It’s important to be aware that these advantages come with a caveat. Coding knowledge is beneficial, but it’s just one part of a much larger skill set required for effective product management. And in Kirsty\u2019s mind, it\u2019s not always the most important area to focus on:<\/p>\n\n\n\n

\n

\u201cIn my opinion, it\u2019s more important for a Product Manager or Product person to have a really good understanding of how to conduct research and problem-solve, and how to ask the right questions.

\u201cCollaboration as a skill is way more important than coding, I think. Being able to multitask is definitely a big one too. Empathy is a huge one. All of those skills are way<\/em> more fundamental than being able to write a line of code.\u201d<\/p>\n<\/blockquote>\n\n\n\n

The key, then, is to find a balance that works for you and your specific role.<\/p>\n\n\n\n

Are there any disadvantages to knowing code as a product manager?<\/h2>\n\n\n\n

While discussing the merits of being able to code as a Product Manager, you also have to consider the potential downsides. There are a few scenarios where being too involved in the technical details can lead to some tricky challenges.

One notable problem is the risk of role blurring<\/strong>. Product Managers, especially those with a technical background, can find themselves drifting toward more hands-on coding tasks. This shift can distract from what should be your primary role – strategizing, understanding the market, and focusing on the user experience. There’s a delicate balance between understanding the technical aspects and becoming too engrossed in them – the old \u201cwoods for the trees\u201d analogy.

Another concern is the possibility of narrow focus<\/strong>. A deep dive into coding might inadvertently give you tunnel vision, leading you to prioritize technical elegance over user needs or business goals. As a PM, your strength lies in holding a broader view, and synthesizing all sorts of diverse inputs to guide your product strategy. Squinting too hard at just the technical side can skew this perspective.

It’s also worth mentioning the large time and effort investment<\/strong>. Learning to code isn\u2019t a trivial pursuit, or a quick fix. Unless you\u2019re a savant of some sort, it\u2019ll take a lot of your training time that could have been spent honing some of the other essential skills in Product Management. For some, this investment could have a big payoff, but for others, it might not fit with their career trajectory or what they actually spend their time doing day-to-day at work.

Basically, as a Product Manager, it\u2019s important to give some thought to how much technical depth is going to be helpful with your specific role. If you\u2019re going to get to grips with code, make sure it\u2019s complementing, rather than overshadowing, your broader responsibilities.<\/p>\n\n\n\n

What do Product Managers need to know about code?<\/h2>\n\n\n\n

Ok, coding might not be an essential skill for every Product Manager. But we\u2019ve established that some technical understanding can help to make you a better PM. So, what exactly should PMs aim to know?

Learn your tech stack:<\/strong> It’s crucial to have a grasp of the technologies that underpin your product. This doesn’t mean you need to know how to build it yourself, but rather understand your tech\u2019s capabilities and limitations. Knowing whether your product is built on HTML, CSS, JavaScript, or Python, for example, and why those differences matter, will help you with making informed decisions and communicating effectively with your engineering team.

Understand basic technical concepts:<\/strong> Familiarity with basic coding concepts, even if it’s just the fundamentals, can go a long way. Things like understanding what an API<\/a> is, how databases work, or what the difference is between frontend and backend development. You\u2019ll be able to have more meaningful conversations with your Dev team and can help them translate the technical details into more business or user-focused language.

Develop your data analysis skills:<\/strong> Everything is data now. Having some competency in data analysis is incredibly, and increasingly, valuable. This might involve basic SQL knowledge or understanding how to interpret user data to inform your product decisions. These skills enable you to draw insights from your data and then use them to guide your product strategy.

Ultimately, as Kirsty pointed out, the depth of technical knowledge you need as a PM really depends on your particular product, industry, and company size. In some cases, a deeper understanding of the tech might be helpful or even required, say if you\u2019re a founder of a very early-stage start-up and need to knock up a quick MVP<\/a> of the product.

In other cases, just being on nodding terms with code as a Product Manager might suffice, so you know what the Devs are saying without wanting or needing to teach them to suck eggs. The key is to focus on building the level of technical knowledge that\u2019ll empower you to make better product decisions and communicate effectively with your team, without wasting your time going down the rabbit hole.<\/p>\n\n\n\n

Will coding skills come up when interviewing to be a Product Manager?<\/h2>\n\n\n\n

Every business has its own definition of what a Product Manager\u2019s job entails. Some don\u2019t even use the same job title, for God\u2019s sake! It\u2019s almost impossible to know going into an interview exactly what your day-to-day at that company will entail, but you can easily hazard a guess depending on the vertical of the company you\u2019re applying for.

To give a direct example, ProdPad is a SaaS B2B product company. Seems like a pretty techy, data-led environment, right? But we don\u2019t expect our PMs to know code. Here\u2019s our Head of Product Kirsty\u2019s view on it:<\/p>\n\n\n\n

\n

\u201cI wouldn’t expect there to be any coding questions in an interview. Unless, like I said, maybe the environment or platform or products you are interviewing for is specifically some kind of coding environment.

\u201cOne thing they may ask you about is what languages the previous products you’ve worked on have been built in, or what frameworks you\u2019ve used. That\u2019s just so they can establish whether your experience maps to what they’re using, to see if you already have a technical understanding of it. But that’s all I’d really expect in a typical kind of PM interview question.

\u201cIt’s not something I’ve come across as a common question at all, and it’s not something I\u2019ve ever asked when conducting an interview either.\u201d<\/p>\n<\/blockquote>\n\n\n\n

In many product manager interviews, especially for roles that are not heavily tech-centric, coding skills are unlikely to be a primary focus. However, interviewers will still often be looking for an understanding of technical concepts, the ability to communicate effectively with technical teams, and a general awareness of the tech stack used in product development.

For roles that lean more towards the technical side, such as a Technical Product Manager, you can expect deeper discussions around technical topics. These might include questions about specific programming languages, technical challenges you’ve faced, or how you’ve worked with engineering teams in the past.

It’s also not uncommon for interviewers to ask about your problem-solving approach in technical scenarios. They could be interested in how you translate technical challenges into business impacts or UX improvements. This doesn’t necessarily require coding prowess, but a solid understanding of the technical side of Product Management will help you give a good answer to these sorts of questions.

Ultimately, while hardcore coding skills are very unlikely to be a deal-breaker for many Product Management roles, demonstrating some technical aptitude and a willingness to engage with more technical subjects could well stand you in good stead. It shows that you\u2019re a well-rounded candidate capable of bridging the gap between the technical and the non-technical.

But again, it\u2019s absolutely not vital!<\/p>\n\n\n\n

What are the best coding languages for Product Managers who do need to code?<\/h3>\n\n\n\n

While there’s no one-size-fits-all answer, some languages are going to generally be handy for PMs wanting to improve their understanding and communication of the Dev process:<\/p>\n\n\n\n