Important tips on bagging PPO during Internship and securing a Full-Time Role
4 December, 2022
11
11
0
Contributors
Background
Conversion Process
1.
Every Intern is assigned a project and a mentor (at Google we call them host) and a co-host. The project is usually a part of the product that the team is working on. The mentor is a senior engineer who will be your guide throughout the internship. You will be working with your mentor and other engineers on the team.
2.
There will be two evaluations during the internship. The first evaluation called Mid Evaluation happens after 5 weeks (since my internship period was 10 weeks) and the Final Evaluation happens in the last week of your internship. The Mid Evaluation is more of a check-in to see how you are doing and if you are on track. The Final Evaluation is more of a review of your work and the project. The host and co-host also get to give feedback on your performance and your project progress.
Technical Advice
1. Learn the basics
a. Version Control Systems
Git is one of the most popular version control system
b. Basic Commandline
cat
, grep
, sed
, awk
, etc. You can learn about these commands from the man pages. For example, to learn about the cat
command, you can run man cat
in your terminal.c. Data Structures and Algorithms
Note: You don't need to be an expert in these topics. You just need to be familiar with them. But most of these companies have DSA questions in their interviews. So, it is important that you are familiar with them.
2. Knowing the syntax of the language you will be using
3. Learn Design Patterns
23 Design Patterns
4. Write clean code
•
Keep it simple: When writing code, it's important to avoid unnecessary complexity. Simple, easy-to-understand code is usually easier to maintain and debug.
•
Use clear and descriptive names: Choosing clear and descriptive names for variables, functions, and other elements of the code can make it much easier to read and understand. Avoid using abbreviations or single-letter names, unless they are well-known and widely understood.
•
Use comments: Comments can be a helpful tool for explaining the purpose and functionality of different parts of the code. However, it's important to use comments sparingly and only when they are truly necessary, as too many comments can make the code harder to read.
•
Follow a consistent style: Consistency is key when it comes to writing clean code. Using a consistent style for indentation, spacing, and other elements of the code can make it easier to read and understand. It's also a good idea to follow established coding standards and guidelines, such as those provided by the programming language's community or the company you work for.
5. Learn testing
6. Know how to write a Design Doc
Non-Technical Advice
1. Be proactive
2. Keep your mentor (host and co-host) in the loop
3. Be open to feedback
4. Time management
5. Ask questions
Conclusion
internship
developer
develevate
toolstipstricks
developerlife