I see it as a different skillset. You possess skills to cut maintainable code, work through issues (technical and people), and whatever other traits the organisation sees you doing well in, or have the potential to. That is quite different from interviewing, which is often just about impressing people enough to let you in the door. I say this having gone through the same process. If you’re that worried, study the code as you’re already doing, grind leetcode, or my preference - pick up harder problems and run with them. You’ll learn some new stuff, maybe build something cool and feel a bit less like an imposter.
I see it as a different skillset. You possess skills to cut maintainable code, work through issues (technical and people), and whatever other traits the organisation sees you doing well in, or have the potential to. That is quite different from interviewing, which is often just about impressing people enough to let you in the door. I say this having gone through the same process. If you’re that worried, study the code as you’re already doing, grind leetcode, or my preference - pick up harder problems and run with them. You’ll learn some new stuff, maybe build something cool and feel a bit less like an imposter.