There's a moment at every networking event, every family gathering, and with every new LinkedIn connection where someone asks the question: "So… what do you do exactly?"
"Senior Creative Development Manager," also known as SCDM.
And let's be real, it sounds like three different jobs had a meeting and couldn't agree on a name. Nobody knows what it means, recruiters don't know how to classify it, job boards don't have a dropdown for it, and ATS systems have no idea what it is… so it dumps resumes like mine and moves on.
You can attempt to simplify the role though... "I'm a designer!" Well, that's not right… because I also write production code every week. "I'm a developer!" But that's not right either, because I also lead design strategy and build design systems. "I'm a manager!" But that makes it sound like I sit in meetings all day, and it completely undersells the fact that I'm still building things every day when I'm not stuck in said meetings.
I've come to terms that the title means absolutely nothing in isolation, but everything in practice. And for what it's worth, I wouldn't have it any other way.
Every day of my week looks very different.
The easiest way to explain what this role actually is would be to just walk through what the work looks like.
Some days I'm writing front-end code, including component builds, debugging issues, and shipping features. I typically have my hands on a keyboard working in VS Code, terminal is hooked in and running, and a collection of half drank drinks i cycle through.
Some days I'm in Figma wireframing, prototyping, and working on components for design systems. I'm thinking through user flows, visual hierarchy, and how a real person would navigate from point A to point B without getting confused or frustrated (or wanting to write a nasty review about how "stupid" a feature or experience is).
Some days I'm leading projects… sometimes I'm the design lead, sometimes I'm the development lead. At this point, I've learned that the project doesn't care what your title says, it only cares about whether someone is driving it forward and making the call when creative/technical direction is needed.
Some days I'm the product manager. I'm sitting with the problem and defining requirements, prioritizing features and roadmaps, and negotiating scope with stakeholders who all want different things. Nobody handed me this responsibility in the original job description, but the project needed someone to step up… and given my comfortability working between design and development, I gladly stepped in.
Some days I'm the marketing strategist thinking about positioning, conversion, and user psychology. How do we move someone from "I'm curious" to "I'm convinced"? What story are we telling and does the experience actually deliver on it?
And some days, I'm all of these things before lunch rolls around.
The point isn't that the role is chaotic per se... the point is that real problems don't respect the lines we draw between disciplines. They usually don't arrive neatly labeled "this is a design problem" or "this is a development problem" or "this one's for marketing." They just arrive, and somebody has to figure out what the problem actually is before anyone can decide how to solve it. That somebody is usually me.
Why this role exists.
Companies usually build org structures around disciplines: a design team, a dev team, a marketing team, a product team, etc. That makes sense for scale since ideally you need specialists across all these disciplines. However, typically the more specialists you bring in the more likely you are to find gaps in processes and comprehension… and it all builds tension about who's responsible for what, where does work start and stop, and what happens when a problem arises: is it the design team's fault? Did the development team screw up? Did the marketing team overpromise stuff again?
The handoff between design and development is where things tend to break the most though... the translation between marketing strategy and product experience is where meaning can easily get lost as well. Hybrid roles tend to flourish in the gray area between these teams since they might be able to translate between design and development, communicate features and benefits marketing can work with, and much more.
Most people specialize… and that's typically the smart thing to do. You're able to build deep, respected expertise when you niche down. There has to be someone that can translate between the specialties though... who's capable of speaking designer to the designers, developer to the developers, and business to the stakeholders? And the same person that understands all three languages instead of repeating buzzwords between meetings?
That's the SCDM role in a nutshell. And what I just described above can easily come across as generalist… but this role has been far from being generalist. A generalist usually knows a little about everything. This role requires someone who goes deep into multiple disciplines and can operate at a high level in each one respectively. There's a big difference between "I've heard of React" and "I built the component library from scratch." There's also a difference between "I appreciate good design" and "I can open Figma and design the entire experience myself."
The hybrid isn't usually someone who dabbles… they're someone who decided that being excellent at one thing wasn't enough for the kind of work they wanted to deliver.
The dropdown problem.
Here's the funny part about having a role like this: the professional world was not built for you.
Job boards usually force you to pick one discipline. Design, Engineering, Marketing, or Management. Pick one. The form doesn't allow for "D: All of the above."
We know at this point ATS systems pattern-match against known titles… "Senior Creative Development Manager" doesn't match "UX Designer," it doesn't match "Front-End Developer," it doesn't match "Creative Director," so what is the system supposed to do with you? Your resume could be a perfect fit for the role and the algorithm will never show it because the title doesn't look like what it's been trained to recognize.
Recruiters see the title and don't know which bucket to put it in. "Is this a design hire? An engineering hire? A management hire? Who are you?" Yes. Yes to all of it.
I get it though… most places want specialists that can hone in on their craft. However, it only takes a quick look through multiple job listings to see the fine print… where they start asking for these other tasks and responsibilities in a wraparound way.
The hybrid is the superpower.
Every career advisor says "specialize." Pick a lane, own your niche, and stay in your zone. And for most people, that's generally good advice.
But the person who can design the experience, build it, lead the team shipping it, and tie the whole thing back to the business strategy? That person doesn't wait for handoffs… they don't need a three-week alignment process between design and development because they ARE the alignment. They don't need someone to translate the business goal into technical requirements because they're capable of reading both languages natively.
There's a real speed advantage to having hybrids on a team. When you can go from whiteboard sketch to Figma prototype to working code without switching desks or waiting for another team's sprint capacity, the business starts realizing those efficiencies… and it translates to money, and time, saved. Work that might take three teams coordinating over multiple sprint cycles can now take one hybrid with a solid team a few days. The process of waiting gets eliminated, the handoffs, the miscommunication, and the meetings about the meetings are lessened because there's now a person that can translate the message in real-time.
The team also realizes an improvement in quality. When the same person who designed the component is also capable of building it, the gap between design intent and what actually ships starts to disappear. What you designed is what gets built, so there's less of those "that's not quite what I meant" conversations. The vision and the execution start to live in the same brain, and that's a skill that's hard to replicate.
Does this scale infinitely? Absolutely not… one person can't be the designer, developer, strategist, and leader for a fifty-person team. But for focused, high-impact projects? Products that need to move fast without sacrificing quality? For teams that need someone who can flex into whatever the moment demands? The hybrid becomes the most valuable person in the room… and there aren't many of them.
I wouldn't have it any other way.
I could simplify my role if I wanted to... I could pick "designer" and lean into that, I could also just call myself a "front-end developer." I could throw all of that aside and go with "creative director" and let people assume whatever they want to assume.
But none of those titles capture the actual work I do... And at the end of the day, I'd rather flex between roles than sit in a lane and wait for an opportunity to arrive. The ability to walk into any room and adapt to whatever the project needs… that's 15 years of deliberately choosing to build a range instead of building a box.
My title confuses people, but my work doesn't. And I've found that when someone finally sees the full picture between the code, the design, the strategy, the leadership, and the systems thinking all coming from the same person… they stop asking what my title means and simply ask when I can start.
Have a title that doesn't play nicely in your field? Don't be too worried about it, maybe you've just outgrown the form and have become your own version of a unicorn. And the last time I checked, people think unicorns are pretty awesome.