Here's a thread of advice 👇🏻
1) Behavioral interview questions such as: "What are your career goals"
2) Technical questions like: "Pretend I know nothing about React, explain it to me from 0" or "What is a float in CSS"
4) Takehome code challenges, where you're given a task to solve asynchronously
5) Pair programming challenges where you're working with one of the company's engineers to solve a problem.
First, to learn more about what data structures and algorithms are out there and what they're for...
Blog posts: medium.com/basecs
Podcasts: codenewbie.org/basecs
Videos: dev.to/vaidehijoshi/l…
While I was reading resources like these, I took my own notes and put them in a GitHub repository I could come back to:
github.com/aspittel/codin…
I love codewars.com and @hackerrank for beginner - intermediate levels.
projecteuler.net is great for super mathematical problems.
and #AdventOfCode adventofcode.com.
Explain your thought process, draw diagrams, write out the intermediary code, explain pitfalls in your approach, etc!
Be vocal, and ask clarifying questions.
That's part of being a good developer after all!
Don't lie and say you know something you don't -- it will be easy for them to figure out you're being dishonest.
But show a growth mindset -- "I don't know that yet, but I'd love to learn it --
Also, interviews go both ways. If you have to jump through a million hoops that might be a red flag for what it's like to work at the company.
Hope this thread helps!!