@mrinalikamath That's good to hear! maybe some things have changed since I did my last interview rounds.
I'm with you on the onsite challenges, not problematic. Maybe a bit low signal but not a red flag
If you're looking to build a cool product demo, or get put together a show-reel for your site. Give Raylight a look. Diggin it thus far
https://t.co/9NqRvo8HRK
@dotmariusz Jealous of that. 100p
it's why Americans love European cities. Unfortunately the US infra is so messed up that it feels like they'll never get there. Have to drive everywhere for everything.
Cool! haven't tired this myself in Figma but you should be able to setup a MCP server with Claude.
https://t.co/QQBoiA4V7L
So claude could directly edit and generate designs in your figma. Might help with the whole "things getting lost" with the export and import steps you have to do currently.
I keep seeing posts from designers that goes like:
"AI doesn't have taste so I'm safe."
It's perhaps the weakest moat you can have.
Every designer now has the same easy access to libraries, that can make a half decent UI.
So what CAN you do?
Your portfolio will follow you throughout your career. You’ll give it heaps of attention while interviewing and will often abandon it when your day job is going well.
During those interview stages, designers (myself included) will spend too much time “making it just right.”
We’ll tell ourselves things:
”Just a few nicer mockups, then I would have got that offer.”
”They said they wanted to see more process, I should add some exposition.”
The way you can tell if your web portfolio is good enough is:
If you get your portfolio:
in front of another humans eyes,for a job you are qualified for,and they consistently move you on to the next interview round, it’s good enough.
(to be clear this would be the stage right before the phone screen round)
or other designers compliment you on your portfolio unprompted
Your web portfolio is just one step in the sales funnel. If you’re already acing that stage then your efforts could be better allocated toward improving other areas.
1. Be the one who thinks of every state.
AI tools describe and make empty, loading, error, undo states confidently but, then leave a quarter of them out in the implementation. Covering these states takes thinking and acting like a real user would.
@lazarframer Designers keep talking about taste as their moat. But the other thing that we have is fixing and anticipating error states.
I know it sounds small, but AI stinks at bailing out users from a failed flow.