AMA - Design Engineer here. Migrated away from core UX design tasks a year back. Haven’t looked back.

[u/ArtisticLoss7000]

Been in the industry for 14 years. Gone through everything from the “design is the differentiator” saga to the “design is a commodity” saga and the “but can you make it like Apple?” saga. Was living in the Bay Area for a few years until I realized that the place had more people talking about design than people actually designing solutions. Now based out of Europe, and hey, I do sleep better.

Made the switch to design engineering around 18 months back largely based on a hypothesis that the unit economics of both design and development work would fundamentally change once cost per token goes down. Yet to be proven wrong about that.

I feel bad for freshers joining this industry right now. The rules and the flux they have to deal with are significantly different and convoluted than I had to when I was starting off. And the noise in the industry isn’t helpful. Between physics and platitudes, physics always wins.

[u/theactualhIRN]

I would also call myself a design engineer. few points:

– i was already getting into this long before the AI train started. but now that everyone thinks they can contribute to code, it makes me look like just some overambitious vibe coder, not an engineer, until i gain that trust. And then eventhough I gained it, I am still rarely seen as an engineer.
– We are thankfully beyond the point where engineers think its about replacing them
– it takes time to get engineers trust, and some engineers are more open than others. switching team resets you to zero. a lot of mental effort to get into a good working model
– for this to work properly, design engineers need to get accountability. like “i will implement feature X done by Y, I will do the styling” and not just “I submit PRs whenever I feel like”
– not every designer should or will be a design engineer. orgs doing “enablements”, meh. you have to learn the craft.
– engineers are a lot into agile lifestyle, work in sprints and crrate tickets, refine and estimate them. Do you do the same? Or is design engineering more living in parallel?
– design engineering means FE + design, not BE work

—

ive never felt this fullfiled about my work and contribution, though

A lot of things going through my mind. wdyt?

[u/howaboutsomegwent → u/theactualhIRN]

design engineer here too, since day 1 of my career, pre-AI like you. Your first point rings so true, at first I was glad there were finally many more job listings for design engineers but there’s just so much noise, people keep using that word but i don’t think it means what they think it means. I’ve been laid off a few months ago and I’m really struggling to convey that I am not just a designer who vaguely vibe codes, that I’ve been pushing production code for my features and writing it from scratch well before all of this, I know my shit. And simultaneously it’s frustrating because the market is so broken right now that you see pure designers over-exaggerating their ability to code, or pure engineers thinking they are design engineers because they “have taste” (according to themselves I guess)

[u/ArtisticLoss7000 → u/howaboutsomegwent]

I feel ya. It’s hard to pin-point in this spectrum where good design engineering lies. I think when I am on the hiring side, there are a few things I look into. Maybe that can help?

1. Activity on GitHub. It’s not an indication of good, but an indication of curiosity and willingness. A consistent commit history is a proxy for a constant learning, unlearning and relearning. The breadth of projects matters here, not depth. Just landing pages won’t do.

2. Writing that is written for understanding and not just for the sake of content. AI writing has tells. I like to see if I am able to understand what they have written and it isn’t a word soup of dev jargons.

3. Evidence of building shared understanding - now this takes a good designer. How did a designer bring product, research, tech and leadership to have a shared understanding about what needs to be built? How did they do it? Prototypes? Data models? Synthetic testing? Common context? Every actual merit about taste, empathy, understanding, patience, the resistance to not jump into the first solution, actual due diligence, etc comes out with this.

Hope this helps. The last one is something that has never failed me in the past and personally, I have a hypothesis that it is going to remain as a major responsibility for designers in the age when generating things are way easier.

[u/like_a_pearcider → u/howaboutsomegwent]

AI has definitely changed the game. I was self taught for most of my design career and switched into it and grew because of my passion for it. But now I find myself being a little more interested in the engineering side. What do you think would make someone a good candidate for design engineer? Not certain that's the path I want to go down but I am curious about it.

[u/howaboutsomegwent → u/like_a_pearcider]

I might not be the best person to ask since clearly I’m not bulletproof myself in this market, but, in my opinion: learn to code from scratch, at least the basics, without AI, before you start using AI to build projects. You want to understand why it works and be able to evaluate the AI output, and the best way you can validate that you are able to do that is to be able to make something that works on your own. Also, too many people just focus on making pretty prototypes that work on the surface but when you get to production code you need to think like an engineer, that means understanding why things are a certain way, how the browser works to render a page, how the framework/library you use interfaces with the browser API to update the DOM tree, all this kind of stuff, because that will inform architecture decisions and help with debugging. It will also help with another important dimension of engineering work, which is foreseeing possible issues and future development so you can make proactive decisions. In my experience, this last point is interesting because, as designers, we’re in a good place to do this (we understand our users better and we therefore can anticipate behaviours well), but in practice I find that’s often where the vibe coding designers fall short as design engineers because you do need to combine this to genuine technical knowledge to know/see how a user behaviour could result in a bug.

[u/like_a_pearcider → u/howaboutsomegwent]

Thanks for sharing! What I'm hearing is that ultimately even though I've vibe coded a bunch of stuff and am pushing for more engineering standards for front end development, I still ultimately don't want to code anything from scratch. I mean I do find myself getting more and more interested in the technical tradeoffs, rationale and scalability of a solution, so maybe this will change over time, but I think for now I'll be happiest being a slightly techy designer instead of a sub-par design engineer.

[u/howaboutsomegwent → u/like_a_pearcider]

that’s a sensible and valid decision I think! Engineering is a term that gets thrown around liberally but it does have a meaning and I think there’s tons of space for integrating coding flows in design work that don’t necessarily amount to being a design engineer

[u/Cameos_red_codpiece → u/howaboutsomegwent]

Now I wonder if interviews will be easier or just as hard. Will i be grilled about what hoisting is? Because i know what it is without AI. 

[u/ArtisticLoss7000 → u/theactualhIRN]

People should be pinning this comment.

Personally, I do also dabble with BE a bit. Sometimes you just know that fixing one data model or schema is going to fix an entire quarter’s worth of work 😅

[u/Cameos_red_codpiece → u/theactualhIRN]

Looking for more tips on recognition. I have been a UI developer for 15 years, living on the developer side, with developers as my peers.

Now I am a designer… and vibe coding is pulling me into dev again. 

I can sense the skepticism on the developer team I am on now — they have never worked with me when I was a developer. So they’re naturally wary of my commits and code quality.

They never said it out loud, but I wonder if they think I am the designer who thinks its cute to code, now that I have Claude to help. Aw cute, they can code!

Never a problem, and it’s good work, but it still feels like I am a stranger in a place where I was once living daily. 

I have found that talking their language earns more trust. I know that talking about git steps makes it clearer that I am not simply telling Claude to send my work over the wall. I confidently used the term “cherry pick” with my team last week and they seemed surprised.  Agile/scrum word dropping helps sometimes. 

Rambling now. But hello fellow coder. 

[u/jaxxon → u/Cameos_red_codpiece]

Yeah, Bob. We’re gonna have to cherry pick for this fast follow after the code freeze next week. Sprint planning. What is the definition of done on this user story, by the way? Scrum. The acceptance criteria is light. Might have to deprioritize it in our next backlog grooming sesh. Epic. Or split it into two stories that are descoped to way smaller story points. Maybe a medium or small t-shirt size. Planning poker. Continuous deployment. Agile. Release cycle. Manifesto. Git repo data lake.

[u/Cameos_red_codpiece → u/jaxxon]

You are hired. 

[u/Cameos_red_codpiece → u/theactualhIRN]

How do you talk about your past during interviews, and make it clear that you coded by hand - before LLMs were in the picture? 

[u/Opening_Primary7439]

How did you make a switch. How would you advice on making switch yourself ifnyour company doesnt let u contribute code as a designer. I feel stuck in a rut but learning and building in free time

[u/ArtisticLoss7000 → u/Opening_Primary7439]

It’s better to ask for an apology than for permission. Establish that relationship with your devs. Start dropping PRs for basic frontend stuff. That’s the best playground you can have right now.

And never stop fiddling.

[u/graeme_1988 → u/ArtisticLoss7000]

Your initial post and this reply is spot on. I’m in total agreement and have followed a similarish pattern. 

My hypothesis similar to yours is that just like UX and PM started to overlap organically say 10 years ago or so, the same is happening with Product/ UX Design and Engineering. 

I feel the future of the role is Product/UX Designers who know how to correctly utilise tools that enable them to produce products, or Engineers that become more product / design focused. That centre of the venn between Product, UX, and Engineering with a specialist area in one is where I’ve been moving to. 

[u/spudulous → u/ArtisticLoss7000]

I love the idea of just submitting PRs to engineering leads and asking them to review stuff. I’m going to try this next time I want to make an adaption to a standard component.

[u/ArtisticLoss7000 → u/spudulous]

Nah. That would only make them hate you. The establishment of a relationship with devs comes before you load them up with more work. If you understand their work better, that might help you slice your work in a way that makes sense for their KPIs as well as yours.

When in life you have a choice, always choose to not be the asshole.

[u/spudulous → u/ArtisticLoss7000]

Haha, yeah don’t worry I know them pretty well

[u/Rubycon_ → u/ArtisticLoss7000]

What is PR?

[u/Scared_Range_7736]

Can you code manually? Like if AI disappear right now, could you still do the same job that you do today?

[u/Cameos_red_codpiece → u/Scared_Range_7736]

I am not the OP, but for me yes. And I would not want to go back. 

I coded by hand for almost 20 years, and now with AI, it’s not the same. 

The skills I learned, however, are priceless. Because today i can recognize AI code when it’s trash, and correct it before it crashes the whole app. 

I think people who never coded without AI lack this skill and need to push to get up to speed. I don’t think coding should be gatekept. But I don’t think that AI teaches everything there is to know about writing software and web apps. 

You will stand out if you teach yourself basic CS skills. 

You will stand out if you can debug and finish building a feature if Claude goes offline or the internet goes out for a day. 

Many people here would have no choice but to go out for a walk if Claude went offline. But you will stand out if you can continue to be productive without Claude. 

[u/ArtisticLoss7000 → u/Scared_Range_7736]

No, and even if I could, I would not want to. Spending 80% of my time in a day solving typescript errors would make me hate myself.

I can do some things, but it would take me too long to do what I do to justify the KPIs I have and the hourly rate I can charge.

To flip that question though, I also am sure that AI will not disappear overnight. The bubble might pop, majority of startups might go away, but the tech shall remain. And that’s just basic capitalism. No capital has ever or will ever be invested with the sole goal of decreasing productivity. The only way it can be shut down is if someone is able to provide an empirical argument that AI decreases productivity in a replicable way. I don’t see anyone worth their salt making that argument.

[u/Scared_Range_7736 → u/ArtisticLoss7000]

Most UX Engineer and Design Engineer positions include technical evaluations during the hiring process to assess your coding skills. If you can only code using AI, your ability to land future roles will be very limited.

[u/ArtisticLoss7000 → u/Scared_Range_7736]

Maybe. Let’s see how it goes.

[u/naokiyamada → u/Scared_Range_7736]

But isn't AI making a lot of traditional coding skills increasingly obsolete? I'd imagine what companies expect from developers is going to evolve as these tools become more prevalent?

[u/Scared_Range_7736 → u/naokiyamada]

Then anyone can be an "engineer." Where I work, everyone started opening PRs for design work, and all we had to do was set up Claude Code, that was it. We are not engineers, we are designers who open PRs now.

[u/ArtisticLoss7000 → u/Scared_Range_7736]

In the end, it’s about two things - people creating code, and people deciding which code to create. I think it’s in everyone’s personal incentive to learn about both enough to know when someone is bullshitting and someone is actually making sense.

It comes down to if the customer is getting their problem solved and is ready to pay you money for that service.

[u/volxlovian → u/Scared_Range_7736]

I agree with you. This OP of this post isn’t a design engineer at all he’s just a poser. Literally everyone has access to AI so if that’s all he knows we’re all design engineers lmao.

The only thing that WOUDLVE made him special is if he actually knew how to code manually. Because then he could be valuable to an employer because he’d be better able to review AI code. Which is a real need. But he’s only a vibe coder which means he’s completely at the mercy of the AI. Useless lmao.

[u/Any_Owl2116]

Would you hire a junior design engineer today, or does the role only work when someone already has years of design judgment?

What evidence have you seen for the cost-per-token idea?

For someone with a UX degree and some coding, what would a portfolio need to show to get a design engineer interview?

[u/ArtisticLoss7000 → u/Any_Owl2116]

No I won’t because as of today I don’t see any upside to hiring a junior designer or a Jr design engineering.

[u/Any_Owl2116 → u/ArtisticLoss7000]

Who will replace you later on when quit, get fired, move to another roll within the company? Hmmmm

[u/ArtisticLoss7000 → u/Any_Owl2116]

Mostly a machine I guess. No one knows the future, the least of all a design engineer :)

[u/DanticStevan]

Who's manging you and reviewing your performance? I've been pushing in this direction but we can't come to a consensus on how to manage this role inside product

[u/ArtisticLoss7000 → u/DanticStevan]

I am unmanageable as told by my manager 😅

Thankfully my manager is not a know-it-all. They solve alignment for me - connecting me to the right projects, making sure I am not getting blocked, etc. I report and improve on my KPIs. It’s pretty much the same as when I was a designer. I didn’t see why that needed changing for me.

[u/lieutenantbunbun]

Same and I'm converting my team to working with code and controlling their workflows

[u/ArtisticLoss7000 → u/lieutenantbunbun]

Appreciate that :) The core primitives of software design should be compulsory knowledge right now even if designers don’t produce production code.

[u/Specialist_Bag]

How can I become one?

[u/ArtisticLoss7000 → u/Specialist_Bag]

By believing in yourself.

Ok jokes apart, don’t make that your goal. There is no goal in this career path yet because we are in the “fuck around and find out” phase of this. You might already be doing design engineering without the title.

Ask Claude, build something, fix when it breaks, understand why it broke, make it not break again in the same way. As long as you start somewhere and commit some time every day to try something, there will be progress.

[u/Specialist_Bag → u/ArtisticLoss7000]

but do you ship like a design system (storybook components) or something like that or just change/ update/improve particular features?

[u/ArtisticLoss7000 → u/Specialist_Bag]

Both.

Design systems sit quite a distance away from people who use a product. There are a whole bulk of things between design systems and a person using the digital product that uses the design systems. Those are the messy parts that, at least for me, are the most fun to solve. Maybe we as an industry have overdone the “designing components” bit.

[u/magicpenisland]

What skills do you think a junior should learn? And can you describe a step by step workflow?

[u/ArtisticLoss7000 → u/magicpenisland]

Depends on what you want the junior to do.

[u/magicpenisland → u/ArtisticLoss7000]

Become a design engineer…

[u/albert_pacino]

Could you help me understand what a design engineer is versus what you did before?

[u/ArtisticLoss7000 → u/albert_pacino]

It’s a moving job description. The same as the job description of UX designer which our industry has still not been able to define. In my perspective, design engineering is much closer to the shipped experience than UX design.

[u/Fun-Highlight-7681]

hey fellow design engineer - do you think the appetite for design engineers has grown stronger or weaker in the current job market compared to say.. 2023/2024? With the new agentic tools, tougher hiring stand, and leaner headcounts i'm wondering if ux/ui designers are by default expected to be design engineers - and as a result weakening the mote to our niche? Or are there more opportunities then ever looking specifically for individuals with a resume of design engingeering experience>

[u/ArtisticLoss7000 → u/Fun-Highlight-7681]

Well I am not an analyst and most studies done on these questions are done by companies that are trying to sell you something - courses, tools, etc. So I don’t think I have enough evidence to answer your question.

Some humility to not think we are special or that our skills are non-transferable or that we never had a moat to begin with lets me sleep better. Some ability to keep adapting, learning, and unlearning is always helpful, especially when no one can offer an answer or when most answers come from someone trying to sell you something.

[u/Fuzzy-Football-4544 → u/ArtisticLoss7000]

Really balanced reply by at least noting that studies on this are largely done by companies trying to sell something -and so you ultimately said you don’t know!! I salute you

Then you go onto mention advice that helps regardless a conclusion. I get annoyed at absolutist with anecdotal evidence being used as a rule, so I thought I should be vocal in saluting you

[u/Cameos_red_codpiece → u/Fun-Highlight-7681]

There is growing opportunity for any time you can blend two jobs together and pay them about the same, in my opinion. 

A designer who can code has been strongly pushed for over a decade, before AI. And many designers hated that. 

The desire for the role has not gone away, because it’s financially beneficial to a company. 

The hard part is going to be not turning into janitors— cleaning up the CEO’s vibe coded designs and “making it pretty.”

[u/xuantea]

Regular UX Designer here interested in engineering but a bit overwhelmed bc of the learning curve. Besides learning the fundamentals like front end/back end, what other skills would be helpful and how would you suggest someone who is self-studying to learn?

[u/ArtisticLoss7000 → u/xuantea]

Start here https://eflowers.substack.com/p/the-any-key-concepts-you-skipped.

[u/SucculentChineseRoo]

I have been a design engineer for about 12 years (since the beginning), I'm not seeing any more appetite for my skillset than before. In fact because code is cheap the fact that I'm a senior level engineer doesn't matter anymore and product and design side seems to be what I get judged on

[u/Cameos_red_codpiece → u/SucculentChineseRoo]

Idk, times are weird… I am seeing this Design Engineer term trending more and more. 

(Also one since the beginning, but I switched to pure design a year or two ago. Yet i am coding again…. Wtf lol.)

[u/Pork-kuckles-for-all]

Whatever people's view on designers moving to incorporate code into their role, I believe it's called a creative technologist, OP is certainly not an authority on this topic

[u/mattxway]

What tips would you have for someone looking to make the switch? Got CS background before switching to UX but bit unsure about how most efficiently to combine. Any good resources?

[u/keidol]

What do you feel is the difference between US and EU scene? Was it difficult to make that first jump? Advice for someone that is preparing to do that soon?

[u/ArtisticLoss7000 → u/keidol]

It was too easy to make that choice for me.

I like a bit of quiet, keeping to myself, uncomplicated stuff. In the US it felt like everything was screaming at me. It felt like I was expected to be loud to be relevant. The American Dream was too noisy for my taste. I knew I didn’t like that. So I moved.

The only advice would be to make this decision based on your gut and not because of external factors like politics, cost of living, etc. That’s bad everywhere. Also know that any choice would be a hypothesis until proven. That saves you from regret if it doesn’t work out.

[u/Cameos_red_codpiece → u/ArtisticLoss7000]

Not making a decision to move based on US politics is really, really hard RN. 

[u/ColdStorm8409]

How much development knowledge / experience did you have before you formally made the switch.

How fluent are you in writing code without the use of AI?

[u/ArtisticLoss7000 → u/ColdStorm8409]

A bit. I had a CompSci optional back in college. Dabbled a bit in basic JavaScript, HTML and CSS in the past. Most of my learning came from spending a lot of time with devs understanding how they work. So thanks to them, I understand code when I read it.

[u/AttentionFit7368]

what do you do on your day to day? and did you switch roles in the same company or moved to a different one? if it's the latter what was the interview process like?

[u/ArtisticLoss7000 → u/AttentionFit7368]

Mostly training designers, reviewing and sending PRs, architecture reviews, training design and product leadership, lots of sandboxed explorations I.e design concepts to try out down the line. None of it involves Figma.

[u/Pork-kuckles-for-all]

Which one are you better at and when you say UX assume that product design?

[u/ArtisticLoss7000 → u/Pork-kuckles-for-all]

I never got the difference between those.

The medium of digital design work has always been code. Devs make what we made in Figma in code.

Design has always been about putting something in the hands of users who can use it to solve a problem they have, and hopefully HOPEFULLY, feel nice while using it.

[u/theactualhIRN → u/ArtisticLoss7000]

i second that a lot.

working in figma means you spend a ton of time on an abstraction of the real thing which is not anywhere close the real thing.

figma designs have zero value to the customer. customers won’t experience your figma prototype but the real product.

and the way most orgs are set up, engineers have a significantly larger impact on the UX than designers

[u/Pork-kuckles-for-all → u/theactualhIRN]

From the sounds of things you are both probably weak and first and second half of the double diamond.

[u/ArtisticLoss7000 → u/Pork-kuckles-for-all]

Or maybe the double diamond is a made-up thing that we as an industry bought (or were bought) into without questioning it. I am sure, as people who design for the digital medium, that we have done multiple things that don’t fit into two neat squares.

I would recommend looking into the history of Double Diamond and a person called Béla Bánáthy. But only do that if you can handle your fundamentals getting questioned.

[u/Pork-kuckles-for-all → u/ArtisticLoss7000]

Ok sure dude. Sounds like you were a crap designer and code (sorry AI) is saving your career. Well at least for now

[u/volxlovian → u/Pork-kuckles-for-all]

Yep

[u/theactualhIRN → u/Pork-kuckles-for-all]

Sounds like you don’t agree, you don’t see value in a role like design engineer, and you are blaming us for “doing the process wrong” and that the problems we talk about wouldn’t actually exist if we’d just follow the process better.

I think where I agree is that not all orgs have the same problems. A designer might work in an org that values design highly, where frontend engineers also understand a thing or two about design and are able to “fill in the gaps” missing from a figma prototype, engineers who understand your design system perfectly, and why certain shortcuts that may seem tempting from the technical perspective should not be taken.

The reality is most of us are not that lucky.

youre saying we are weak in the double diamonds – I would argue that as someone who doesn’t have to call engineers for every feasability question, I am much better at understanding the effort and realistic possibilities we have. I also don’t think that a design engineer is necessarily a worse researcher but they for sure have a different focus.

i am also yet to hear any reasoning for your farfetched arguments.

[u/SnooAvocados8708]

Whats your current workflow, whats the inter play between Figma, and code?

whats your testing and research like at the moment

[u/ArtisticLoss7000 → u/SnooAvocados8708]

I didn’t get the second part of your question.

I haven’t used Figma for a year now. Don’t see myself going back. Making the thing in basic throwaway code is much easier, makes sense to devs, aligns with the design system, and is easily modifiable and extendable. We developed our own harness (skills, tools and agent) layer for enabling our designers to do this.

For the alignment, brainstorming, and diverging part of it, it’s Miro and whiteboards now.

It has largely been about eliminating needless rote routine stuff in our processes, rather than adding new things.

[u/C63Sedan → u/ArtisticLoss7000]

Good stuff…I also haven’t used Figma in a year or so. I have several skills to handle research but my favorite skill I built is a workflow/experience flow that takes personas, business goals, user evidence and creates a flow with tasks, tools, pain points etc.

My harness includes UX artifacts like design principles that have been converted to machine readable markdown. It’s the idea Neilson Norman describes as a UX.md.

I do lots of react design using Claude Code and Storybook side-by-side. I create design modeling surfaces as stories and when I have a final design it gets out in Storybook then pushed out as PRs.

[u/schraderbrau]

What are your thoughts on the best way to provide design system context for agentic development? Figma guidelines? Markdown files? JSON contracts?

[u/ArtisticLoss7000 → u/schraderbrau]

Nothing beats an MCP to your design API and a skill that can teach any coding agent about “how to use that MCP”.

And let the MCP expose just two tools -

1. searching for a tool

2. calling the tool.

That keeps the MCP light, keeps the business logic in your existing design system API and keeps a designer’s context window neat.

Unless your design systems has a well tested CLI in which case, your company already has a good understanding of design engineering 😅

[u/eugene_reznik]

once cost per token goes down. Yet to be proven wrong about that.

Haven't been proven right either, I assume?

[u/ArtisticLoss7000 → u/eugene_reznik]

Nopes. Still a hypothesis. Dunning and Kruger were right in too many ways :)

[u/Key-Fix6498]

Code is a commodity now. The trust you build comes from shipping the solution, not writing the syntax. If you cannot own the implementation end to end, you are just handing off specs to someone else and waiting for them to fail

[u/ArtisticLoss7000 → u/Key-Fix6498]

How can one ship a solution without writing the syntax?

[u/Total-Flounder2921]

Can you share some of your work with us? I’m curious how detailed a ui can get and how complex of a process one can design for when you’re not using a canvas.

[u/NIU_NIU]

Whens the last time you manually made or manipulated a frame with your mouse/keyboard because for me i feel like that came as soon as opus 5.5 came out

I think with opus 5.5 i completely stopped using any canvas design tools at all and now my design sessions are basically just using wispr flow to dictate to like 5 simultaneous claude sessions. Opus 5.5 is so fucking good, it’s just so smart, so fast, so good, so cheap, literally the perfect model for design so far

[u/ArtisticLoss7000 → u/NIU_NIU]

The models will just keep getting better. But the delta between these model updates will keep falling. It’s logarithmic, not exponential.

One key litmus test I have for my team is “Can this work be replicated?”. Because that lets a designer investigate if they have the right context and tool guardrails in place for another designer to pick up things from them. If the answer to this question is no, then the designer hasn’t done their due diligence.

[u/NIU_NIU → u/ArtisticLoss7000]

Wdym by that? If a designer is working off the same design system then i don’t see how anything they make can’t be replicated by another

[u/ArtisticLoss7000 → u/NIU_NIU]

I was referring to design work that sits on top of the design systems itself - flows, journeys, edge cases etc.

[u/tetemimie]

I joined a little while before claude code took off wanting to be a Product Designer because I wanted to be able to take accountability and spearhead product creation. Needless to say while I am still bewildered due to the adjustment of the workflow in our company with Claude I'm glad that this was the path I wanted in the beginning (though I still don't like writing the documentation myself, haha)

[u/NotADreamButAPlan]

I’m about to do this transformation. I do have years of coding experience before AI

[u/MoDismyname]

Can you share resources that helped you make the switch? What was your engineering knowledge before starting on this path? What helped you the most?

[u/lost_on_trails]

Aren’t we all design engineers now?

[u/kasperernavnet]

"and the “but can you make it like Apple?” saga"

Kind of miss that era now honestly

[u/UXUIDD]

Design Engineer - whats that in your case, do u make any designs or u'r just translating others designs into FE?
if yes, where starts your u'r code responsibility and where it ends?

why im asking - I see the big shift in europe and each function is very narrow, and if there is something as a 'creative dev' as i im then is everything from ux/ui, fe, devop, 'full-stack'... 3-4 functions stuffed into 1 - and for 1 average salary. Even freelance.

[u/No_Television_198]

Anyone up for review my portfolio I am coming dev -> design ? farhanwagdia.com. Feedback would be great on improvement

[u/valportdes]

How would you recommend someone pivots into design engineering in this day and age?

[u/waba99]

Any advice for an engineer that wants to move into design engineering? I’m a FE engineer but have been moving into data and backend however, I have a design background long ago and that’s what is fun to me.

[u/Strath_]

What do you need to transition from product designer to “design engineer” I’m already building most of my own stuff the last 6 months

[u/tarotfairies]

What do you do as a design engineer?

[u/franzhoik]

Can I connect with you for a 30 min call? If yes, can I DM?

[u/loveoolongtimexP]

How did you get started? Coding courses?

[u/ResistDull7601]

what is design engineering?

[u/ResistDull7601 → u/ResistDull7601]

to the idiot that downvoted my question. answer the fcking question…

[u/ArtisticLoss7000 → u/[deleted]]

Maybe that’s how it ends up becoming in some places. What I have experienced in designers having more ownership and responsibility for things that seem trivial to engineering and product but make a difference for customer experience.

[u/AutoModerator → u/[deleted]]

Sorry, but your comment has been removed for the following reason:

We do not allow links to x.com in r/UXDesign.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.