Here is the link.
Strong hire signal - bias on not hiring-wrong-one
Humanity to accept the help
Ask around to get help
Show friendly professionalism
Get to know better
Subconscious help you out
Team work spirit
Not preparing - Two technical things
Team work, behavior
Through 4 hours, 4 stories to refer to
Any story - two hours - prepare stories before hand.
How did you define API?
How to use the ...
First 10 minutes -
Spending all the time on one problem - that is not the question for you, follow up question and second
Plow through the question
Make sure that you work fast, and you can pack in as much time as you can
Remember to write the code
Mix some really code with pseudo code
Take picture - credit you can get as you should be ...
Resume - write a feedback, interviewer will take resume as help to write feedback
Interviewer ...
Not focus on analysis enough - college does not teach you enough - time and space analysis
What you are even writing - even it is working
Didn't we talk about the analysis
Bonus tip:
Enjoy the lunch
Prepare technical before the interview
Notes taken by one viewer:
1. Not get a referral
2. Discouraged by refusal and stop applying. Should keep applying
3. Focus only on the tech. Should also show your friendly professionalism and that you're nice to work with
4. Not preparing. Should prepare 2 technical things + 2 personal stories to show your teamwork/leadership/communication capabilities, behavior, personalities
5. Spend time on one problem. Plow through all the question
6. Should write the code down to explain, not just hand waving. Use your resume as a reference when talking.
7. Not focus on analysis enough
No comments:
Post a Comment