Joining Google as an L3 next week. Any helpful tips for me to succeed.
I have 5 yoe and got downleveled. I am joining a team where all tech stack including the programming language will be new to me. This is not too important though as I am pretty sure I can pick things up quick.
I got downleveled by HC, my goal is to succeed in this role and get to L4 ASAP.
Any tips for me to succeed in this role. I will be in Android org, productivity engineering.
Thanks in advance.
TC 205
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
I have onsite in a month and can use help with the following qs
1. How many leetcode had you solved n breakdown?
2. Can you share your interview experience?
3. Why do you think you got downleveled?
4. Can you dm me? Im out of credits :(
Thanks!
I apologize. I’m usually nice 😇
That said, I've never heard of OP's company.
Give yourself some time to ramp up - Google is a Tech Island meaning that it uses very little tooling, libraries, or frameworks that are generally available to the rest of the industry. You will need time to learn and your manager knows this - so focus intensely initially on learning and small initial tasks. Even basic things like how to commit code will be new.
After that focus on being autonomous. You should be able to take larger, less well defined pieces of work, flesh it out, and complete it without overly relying on others. Senior devs are expected to be able to carry fairly abstract tasks to the finish line, resolving ambiguities and holes as needed. You should also be in the habit of proactively seeking work within the mission of your team - if you see something that should be a project but isn't yet, pitch it. Creating one's own work is also part of the expectation for senior engineers.
This comment was deleted by original commenter.