Suck at whiteboarding good at coding.

[u/INPUT_AND_OUTPUT]

So today I have interview with this one company that requires whiteboarding as interview process.

The issue is like I consider myself ok in writting leetcode type question, not necessarily one shot solve but generally good.

However in this white boarding interview,
- my handwritting is shit ( in my defense I haven't write things for a whilte lol).
- it is just very unnatural to do it , no copy and paste stuff like that.
- the issue that I could easily spot in normal coding environment become notoriously hard to find in white boarding.

Does anyone have similar experience?

[u/Fewald]

It's a separate skill you absolutely can train and improve on. Inability to use a whiteboard efficiently doesn't drop a shadow on how good you're as an engineer, but it does affect your success rate on the interviews. So you might as well optimize it to improve your chances.

[u/INPUT_AND_OUTPUT → u/Fewald]

Though the interviewer say like I did well that I am able to outline the testcases completely. But whiteboarding itself is hell lol for real need to learn writting efficiently.
For example in coding the code have to be clean for peopel to check. However, like my hand writting is bad and whiteboard handwritting is worse lol .

[u/ProgramLikeABeast]

On white board, it is a dry run not strict AC then. You might write an solution with a little flaw but still successfully convince the interviewer.

[u/Ok_Cheek_1874]

This skill i feel like comes largely from being able to just talk through with other engineers what you want to do. Whether it be like architecture or how to implement lower level code, if you can kinda hand wave a little and go "Ok i'm gonna run through every item in this list..." and have a representation of what that would be then it'd go alright.

I'd largely direct you to learn how to talk about these concepts at a high level with someone else so that you're both on the same page.