My industry has spotted a monster. Fast Company says design is about to be full of “Frankenjobs”: roles stitched together from parts of other roles. A little designer, a little engineer, a little PM, a little copywriter, sewn into one listing and sent shambling toward your inbox. And the word is doing exactly what it was built to do. It wants you to picture something unnatural. Parts that were never meant to share a body. A hiring manager on a hilltop, waiting for lightning.

I have one small problem with the panic. I’ve been a Frankenjob for twenty years. We just called it freelancing.

If you haven’t seen the listings yet, here’s the field guide. The titles are new and multiplying: design engineer, builder, design crafter, “product designer (technical).” Figma’s own survey says half of designers have now pushed AI-generated code to production, so the job descriptions are scrambling to catch up with what people already do. Read past the title, though, and every one of these listings wants the same four things.

NOW HIRING Design Engineer Builder Design Crafter Frankenjob
  • Design the interface
  • Build the interface
  • Ship it to production
  • Answer for what happens next
Fig. 01 Cycle the title. Watch the duties.

That’s the joke and the tell, all in one. The duties never move. The industry isn’t inventing a new kind of worker; it’s inventing new NAMES for a kind of worker that already exists, because the old org chart has no box to put them in.

I know this worker well, because I am one, and so is every freelancer who survived more than a couple of years. When a client hires me, they aren’t hiring a role. They’re hiring an outcome, and the outcome doesn’t care about my job title. Monday I’m building a brand system. Tuesday I’m in DNS records, because the site I designed has to actually resolve. Wednesday I’m writing the checkout emails, because the flow I built needs words in it, and the words are part of the design whether anyone admits it or not. Nobody ever called that a Frankenjob. They called it “while you’re in there, can you also…”

HEAD · CREATIVE ’06 ARM · VISUAL ’09 ARM · FRONT-END ’21 TORSO · PRODUCT ’16 LEG · COPY ’12 LEG · OPS ’24
Fig. 02 One hire, five donors. All parts tested separately.

Here’s the thing everybody gets wrong about the source material, and it matters. In the book, the monster isn’t the villain. The creature is assembled, sure, but it works. It’s strong, it’s fast, it learns languages by eavesdropping (relatable). The tragedy isn’t that the parts don’t function together. The tragedy is how everyone reacts to the stitches. And while we’re at it: Frankenstein is the doctor. The monster never gets a name. Hold that thought, because I’m coming back for the doctor.

So why does the stitched-together role suddenly work, when for decades companies swore it couldn’t? Specialization used to be the whole point. You hired a designer AND an engineer AND a copywriter because each craft took a career to get good at, and the seams between them were just the cost of doing business.

The seams were never free, though. A handoff is where the design intent leaks out. The mockup says one thing, the build says something 90% like it, the copy deck arrives late and doesn’t fit the layout, and every gap gets patched in a meeting. I’ve written before about what happens when building gets cheap: the expensive part of shipping was never the labor inside each box. It was the space between the boxes.

Stitch the roles into one person and the seams don’t vanish. They move inside, and inside is where they’re cheap. When the designer and the developer share a skull, the handoff is a thought. The layout question that would’ve been a ticket, a wait, and a compromise becomes a two-minute nudge, done while the coffee’s still hot. That’s the entire economic argument for the Frankenjob, and AI is what made it viable at scale: the floor rose under every individual craft, so one person with real judgment can now hold limbs that used to require whole departments. I didn’t get more talented in the last two years. My reach got longer.

DESIGN BUILD SHIP −Δ −Δ THREE WEEKS Relay · intent leaks at every gap
DESIGN BUILD SHIP SEAMS INTERNAL SAME AFTERNOON Stitched · seams move inside
Fig. 03 The seams don't disappear. They move somewhere cheaper.

Now, the doctor.

Because there are two ways to build this creature, and only one of them deserves the defense I just wrote. The real Frankenjob is built around ownership: one person holding the whole arc from idea to shipped, with the seams internal, answerable for the outcome. The counterfeit is built around coverage: three salaries stapled into one hire, three backlogs feeding one calendar, same expectations on every front and a third of the time for each. That one’s not a monster. That’s a budget line wearing a monster costume, and it will burn a good person down to the bolts.

You can tell them apart in the listing, if you know where to look. The real one talks about outcomes: own this product, ship this flow, answer for what happens next. The counterfeit talks about tasks: support three teams, maintain the design system, “help out with” front-end. If the duties read like a relay schedule instead of a body, someone’s trying to get the parts without paying for the stitching… and the stitching is the job.

So no, I’m not scared of the Frankenjob. I’ve watched this exact shape of work, one person spanning the seams, do things a relay of specialists couldn’t touch. The creature is fine. The creature has been quietly running half the internet’s small studios for decades.

It’s the doctor you have to watch. The monster just does what it was built to do.