54 lines
2.5 KiB
Markdown
54 lines
2.5 KiB
Markdown
|
## To do the online coding assessment:
|
||
|
|
|
||
|
|
it may be helpful to watch these videos as well.
|
||
|
|
-[ first tip:](obsidian://open?vault=Coding%20Tips&file=Tip%201.) don't panic
|
||
|
|
- very easy to get overwhelmed by big wall of text and make sure to read entire problem and all cases before writing the code
|
||
|
|
- write down notes and keywords
|
||
|
|
- [second tip](obsidian://open?vault=Coding%20Tips&file=Tip%202): don't worry about writing bad code at first
|
||
|
|
- they know it will take iterations
|
||
|
|
- you can always submit multiple times!
|
||
|
|
- run the stub code first and see if there are any sample test cases
|
||
|
|
- [third tip:](obsidian://open?vault=Coding%20Tips&file=Tip%203) submit your own test cases
|
||
|
|
- generating your own test cases shows that you are understanding the question fully before coding
|
||
|
|
- [fourth tip:](obsidian://open?vault=Coding%20Tips&file=Tip%204) use language reference materials
|
||
|
|
- important when you forget how to list comprehension in python
|
||
|
|
- you are always free to look up docs
|
||
|
|
- [fifth tip](obsidian://open?vault=Coding%20Tips&file=Tip%205): do the easy questions first!!
|
||
|
|
- you won't feel as stressed out
|
||
|
|
- [sixth tip](obsidian://open?vault=Coding%20Tips&file=Tip%206): start doing the easiest solution first even if it is not the most optimized solution, at least having that answer at all maybe
|
||
|
|
-[ seventh tip:](obsidian://open?vault=Coding%20Tips&file=Tip%207) TAKE the sample test!!
|
||
|
|
|
||
|
|
|
||
|
|
---
|
||
|
|
## Techniques while coding:
|
||
|
|
|
||
|
|
What you should be focusing on is the techniques and approaches. A lot of times, these techniques can be applied in other problems as well.
|
||
|
|
|
||
|
|
Some important techniques to focus on:
|
||
|
|
|
||
|
|
- rabbit and tortoise 2 pointer approach
|
||
|
|
- level order traversal using a queue
|
||
|
|
- backtracking
|
||
|
|
- drawing a recursion tree
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
|
||
|
|
### Signs that you are not ready for a programming job.
|
||
|
|
|
||
|
|
1. You are not able to code in front of other people
|
||
|
|
a. if you are not able to code on the spot, work with other people work in software development
|
||
|
|
b. also just record yoursef while coding
|
||
|
|
2. You should be able to explain how data flows through that application on a high level
|
||
|
|
3. You don't have any substantial portfolio projects
|
||
|
|
- companies are going to want to see that you are able
|
||
|
|
4. Unable to debug applications.
|
||
|
|
- being a programmer means you are constantly going to fix
|
||
|
|
5. Not doing any coding challenges.
|
||
|
|
- have to get good at coding under pressure on platforms like hackerrank or leetcode.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
[Amazon common topics](https://www.educative.io/blog/crack-amazon-coding-interview-questions#questions)
|
||
|
|
|