I think the most difficult part on the technical interview is beating the nerves, I've been around for some time now, done quite a few interviews already (lost count of how many I "failed", and passed some too 😜), but I still get nervous when performing a coding challenge.
So, I'd suggest you keep doing challenges, google the common interview questions, check this repo with some common asked ones, and keep doing challenges. There are some platforms like HackerRank where you can practice if that's what you prefer for studying. Otherwise, you can also read some OSS projects, play around manipulating string and array; learning about data structures, etc.
Examples:
get only the odd numbers in an array
reverse a a string
check if a string is a palindrome
etc.
All these questions have plenty of solutions on the internet and even tutorials.
In a nutshell, stay calm.
"Failing" is normal for everybody, just keep learning.
Good luck! 👍
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think the most difficult part on the technical interview is beating the nerves, I've been around for some time now, done quite a few interviews already (lost count of how many I "failed", and passed some too 😜), but I still get nervous when performing a coding challenge.
So, I'd suggest you keep doing challenges, google the common interview questions, check this repo with some common asked ones, and keep doing challenges. There are some platforms like HackerRank where you can practice if that's what you prefer for studying. Otherwise, you can also read some OSS projects, play around manipulating
stringandarray; learning about data structures, etc.Examples:
All these questions have plenty of solutions on the internet and even tutorials.
In a nutshell, stay calm.
"Failing" is normal for everybody, just keep learning.
Good luck! 👍