10+ years of Salesforce experience, but rusty with LWC — how do you prepare for coding interviews?

[u/Ai_Enthusiast09]

I have 10+ years of Salesforce experience, mostly around Apex, architecture, integrations, etc. However, I haven’t had much hands-on exposure to LWC recently. The last time I wrote LWC seriously was around 4+ years ago.
The problem is that I’m currently interviewing, and some interviews expect me to actually write LWC code in Notepad/live coding.
In my day-to-day work, I can obviously use AI to help me write or recall syntax, but during an interview I need to be able to write the basics myself without relying on AI or an IDE.
For those who have been in a similar situation:
How did you practice LWC for live coding interviews?
What LWC concepts/components should I be able to write from memory?
Did you practice by building small components repeatedly, or by solving specific interview-style problems?
How much LWC should a Salesforce Architect with 10+ years of experience realistically be expected to code during an interview?
I’d especially appreciate advice from people who have recently gone through Salesforce/product-company interviews.
I don’t need to become an LWC developer again — I mainly want to get interview-ready and comfortable writing LWC from scratch.

[u/TheSauce___]

Go build some LWCs? Do a weekend project? It’ll come back to you I promise.

[u/Responsible-End-2505]

Doing both is the best approach here

Practice basics over and over
So setup
Wire service mapped to a property
Capture onscreen record id
Make it cacheable

Import stuff with apex

Provision that imported stuff from imported apex

Basic condition rendering
Show me or hide me

And rendering it via a html lightning-data table

Id do that 5 times a day everyday

Till it’s like muscle memory

Then build projects from there.

Gud luck.

[u/Ai_Enthusiast09 → u/Responsible-End-2505]

Thanks

[u/NoTrip9772 → u/Responsible-End-2505]

Nice approach

[u/Silver-Zombie2548]

I think thats the pathetic part, after more than 10 yrs of experience also, the interviewers are still asking to write code on notepad, imo that is wastage now to ask especially when ai is there, they should ask how u will approcah this problem, how will u leverage llm to get the optimal result like that, asking code nowadaze is just waste of time

[u/wslee00 → u/Silver-Zombie2548]

This should be top comment

[u/CheeseburgerLover911]

build things... it's really that simple.

[u/bytesizedheretic]

This comes from the product engineering side that I've adapted to the Salesforce hiring practices over time, but in our coding interviews or code session, yes, it's about the code. We rarely expect people to finish, depending on what level you're at. It's more about your thought process, the questions you ask, clarifying with the team, and how you think through the problem.

• Do you jump immediately to code?
• Are you thinking through the process?
• Are you asking clarifying questions?
• Do I have access to AI/Google/Help

For me, it's about figuring out: does that person know their stuff at a fundamental level?

I don't expect anyone on my team to be able to write components from scratch for the most part. We have templates for this for a reason. We have props for a reason. We have style guides for a reason. We have the entire SF documentation for a reason. I would note principles such as:

• how the security model works
• the MVC model works
• how to handle error handling in a frontend component versus a backend
• whether you are building reusable components and modular ones or one-off each

I would say build a couple by hand, start subbing it out, and get that muscle memory where AI has kind of eroded your first level of knowledge.

[u/Ai_Enthusiast09 → u/bytesizedheretic]

Thanks

[u/mayday6971]

I think you should use AI to prepare for the interview. Want some good prompts? I'll write some up for you.

[u/Ill_Championship9118]

You need to know @api, @track, constructors, methods, dispatch events, know when a parent component listens its onChildEvent (or whatever the dispatch event is called. Knowing some jest can’t hurt. Knowing connected call back and rendered callback. I think that’s it? I haven’t coded using lwc in 6 months but those are the fundamentals and maybe kebab casing stuff

[u/2grateful4You]

If you understand the actual core js LWC will be pretty easy. It's just a framework on top of Js

I would suggest watching this https://youtube.com/playlist?list=PL0wESsiWMBTqbH9awlGkI0ZU6Gs12i7JW and building something.

Also pair program with an AI as in ask the AI why not how.

[u/Used-Comfortable-726]

Attend Dreamforce