The Job You Were Hired For No Longer Exists

Three years ago, I could describe my job in one sentence. Today it would take a paragraph. And I'd still leave things out.

Figma just published their 2025 "Shifting roles" report, and the core finding is a number: 48. That's how many distinct tasks product development professionals are now responsible for. Not 48 things spread across a department. 48 tasks landing on individual contributors and small teams who were hired to do maybe 15 of them.

I read the full 43-page report. What follows is what I think matters most, and what it means for how you hire, structure teams, and build your own career.

The 48 Tasks, Mapped

Figma organized the 48 tasks into six categories: research and strategy, design, development, content creation, marketing and sales, and collaboration and management.

The first three categories are expected. Product people do research, design things, and build things. Fine.

It's the last three that should make you pause.

Content creation includes writing blog posts, producing video and motion graphics, and managing social media content. Marketing and sales covers SEO keyword strategy, digital ad creation, email marketing templates, landing page design, and lead generation funnel optimization. Collaboration and management includes high-level project planning, resource allocation, KPI identification, and development briefing and handoff.

Those aren't product tasks in the traditional sense. They're functions that entire specialized teams used to own. And according to Figma's data, they're now sitting with the same people who are also shipping features.

The report found that 70% of product development professionals are already doing work outside their core discipline. Not occasionally. Regularly. As part of what the job has become.

The Design-Development Wall Is Gone

The report confirms what many teams already feel: the boundary between design and development has dissolved on most modern teams.

Figma's data shows designers writing production code, and developers making design decisions without waiting for a spec. This used to be the "unicorn" conversation. Now it's closer to baseline, especially at startups and growth-stage companies.

The reason is simple. When a developer is building a component and the spec is ambiguous, they're making a design decision whether they call it that or not. When a designer knows exactly what they want and has the tools to prototype at high fidelity, handing off to a developer for pixel-perfect implementation starts to feel like an unnecessary step.

According to the report, the overlap between design and development is now where a large portion of actual product work happens. Teams that still enforce a hard wall between the two are creating friction at the exact point where they need speed.

This doesn't mean designers replace engineers or engineers replace designers. Both roles need their depth. What's changed is that range is now expected alongside that depth, on both sides of the line.

Marketing Landed on the Product Team

Here's the section of the report I read twice.

Tasks 37 through 43 in Figma's taxonomy are pure marketing and sales work: social media content creation, digital ad creation, SEO and keyword strategy, marketing copy and content management, email marketing template creation, landing page creation, and lead generation and conversion funnel optimization.

Product development professionals are doing these tasks. Not marketing teams. Not growth teams. The people building the product.

In large organizations with dedicated marketing functions, specialists still own these areas. But on smaller teams, at startups, in any company where speed matters more than org chart purity, the people building the product are also the people explaining it, positioning it, and optimizing its conversion.

There's a logic to this that goes beyond "we can't afford a marketing hire." The designer who built the onboarding flow understands user intent well enough to write the email that introduces new users to it. The developer who built checkout has the technical context to improve its conversion rate. The PM who defined the product strategy can write the SEO article explaining why the problem matters in the first place.

The product is the marketing now. How something works and how it's explained to the market used to be separate decisions made by separate people. That separation made sense when distribution channels were expensive to access. The tools changed. The expectations followed.

AI Is the Mechanism Behind the Shift

Most of what Figma documented has been accelerated by AI tooling.

A designer doing SEO work isn't a trained SEO specialist. They're someone with deep product context and AI tools that handle keyword research, content structuring, and optimization recommendations. The designer brings the knowledge of what the product does and who it's for. The AI covers the domain they never formally learned.

This is the specific mechanism: AI absorbs more of the specialized craft work within any discipline, which frees people to cover adjacent ground using knowledge they already have. A developer using Copilot has cognitive bandwidth left over for product decisions. A PM using AI writing tools can produce marketing copy without waiting on a content team.

The result is a team where everyone can reach further than their job title suggests. The report's data reflects this: product professionals are taking on tasks that would have required hiring a specialist five years ago.

Depth still matters. A senior engineer with deep systems knowledge is still the right person for hard technical problems. But for the broad range of tasks that product teams handle daily, AI has reduced the advantage that narrow specialization used to provide.

What This Means for Hiring and Team Structure

Most org charts were designed for a world where these 48 tasks were split across six or seven distinct departments.

The typical structure still separates design, engineering, and PM into distinct tracks with distinct hiring criteria. But Figma's data suggests the best-performing teams are the ones where those tracks are porous. Where designers contribute to technical decisions and developers review early design work instead of waiting for a finished spec. Where PMs are in the room for UX decisions, not reviewing outcomes after the fact.

If 48 tasks are flowing through your product team, and a significant portion sit at the intersection of design, development, content, and marketing, then hiring for one function and keeping people in their lane creates drag at the point where work needs to move fastest.

The practical shift for hiring: evaluate candidates on range, not only depth. A designer with strong product instincts who writes solid copy is worth more to a lean team than a more technically precise designer who won't work outside their defined scope. Same logic for developers, PMs, and every other function.

This isn't about lowering the bar. It's about moving it. The bar now includes the ability to operate across boundaries that used to be walls.

What This Means for Your Career

The 48 tasks in Figma's report aren't just a snapshot of what product teams do today. They're a signal about what will be expected next year and the year after.

Five years ago, being excellent at one narrow thing was a strong career position. That ceiling is lower now. Teams paying attention to this data are starting to hire for range alongside depth. They want the designer who can think about content strategy. The developer who can own a product spec. The PM who can run a research session when the dedicated researcher is unavailable.

The T-shaped professional used to be an aspiration. In 2025, it's the starting bar. The people growing fastest aren't going deeper into a single specialty. They're becoming genuinely capable across the adjacent tasks their team actually needs done.

That means making deliberate choices about what to build next. If you're a designer, it might mean developing enough SEO understanding to own it for your product area. If you're a developer, it might mean building enough product instinct to lead a sprint without a PM in the room. If you're a PM, it might mean writing copy well enough that you're not blocked waiting on a content person for every launch.

The 48 tasks are a map. You don't need to own all of them. But it's worth identifying which 10 beyond your core discipline you're already doing, and which 5 you should probably start.

---

• 70% of product development professionals regularly do work outside their core discipline
• The design-development boundary has dissolved on most modern teams
• Marketing tasks — SEO, landing pages, ad creation, lead gen funnels — are now product team responsibilities
• AI tools are the primary mechanism: they absorb craft-level specialty work, freeing people to cover more ground
• Career value in 2025 comes from range alongside depth — T-shaped is the starting bar, not the aspiration

The full Figma report: https://www.figma.com/reports/shifting-roles-product-teams-evolving/