Transitioning into tech can feel like jumping into the deep end of a pool. The pace is fast, the learning curve is steep, and the responsibilities come quickly. But don't let that deter you. This article will equip you with the strategies to navigate it.
How to chart your own learning journey and take charge?
How to embrace early responsibilities and iterate?
Taking Charge of the Learning Curve
In tech, the expectation is that you'll quickly become self-sufficient. This doesn't mean you're alone, but you'll need to take initiative in your learning and growth. Here is another homage to adopting a “growth mindset”. Remember how your friends might ask questions that you can get by just Googling it? In tech, you will want to absorb resources independently by leveraging internal documents and WiKis.
Tips for Success
Set clear expectations with your manager for your first week, month, and 90 days
Big tech has established a structure where your manager will likely set up first 30/60/90 day goals for you. Earlier stage companies may not have that in place yet. It’s your responsibility to discuss expectations clearly with your manager in your first week.
Take ownership of relationship building in your own hands! It’s a good idea to have a “ways of working” session so you two can learn more about each others’ styles.
Be prepared to invest extra time in learning, even outside work hours
This tip might raise some eyebrows, but hear me out. In the fast-paced tech world, sometimes personal time investment can accelerate your progress significantly.
Below is an old IG story of mine from October 15, 2020, with a caption that was part complaint, part humble brag. I joined ByteDance on October 12, 2020. No one asked me to burn the midnight oil that night. I was eager to be finish the initial learning phase ASAP and start contributing immediately. So I used my personal time for it. No regrets. 2 weeks later, I started leading my first initiative.
Pro Tip: If you do choose to put in extra hours, make sure it's strategic. In those crucial early days, this extra effort can pay dividends. It's about investing in yourself and your career trajectory.
Leverage internal documentation and resources
There’s only so many meetings you can have with your manager to learn about strategies, projects and next steps.
Don’t be shy asking for additional resources you can learn from in your own time. I onboarded into my current role by refreshing the one-pager on the status quo of how we onboarding and ensuring success for new restaurants. This frame allowed me to laser focus on reading up related wikis articles and asking followup questions with my cross-functional partners.
Don't hesitate to ask questions, but research first
I agree there is no stupid question, especially in your first 30 days on a new gig. As discussed in my previous article, “How I learnt to be scrappy in Big Tech”. An underlying assumption is that you will come to meetings with suggestions and answers.
That also applies here. Being in tech means you have the ownership to look up something before asking about it or asking to verify if your source is still up-to-date.
Network with colleagues early to build your support system
You should meet with all key stakeholders and collaborators within your first 30 days and get to know them.
If you are not 100% sure who they are, discuss it with your manager
Learn to Swim with Early Responsibility
“Launch quickly, gather feedback, and iterate” has been the motto for many tech companies. Gone are the days where we could take 2 weeks build a deck an then a month to ensure internal alignment on it.
Be prepared to handle important tasks within your first few weeks and potentially lead projects before you feel 100% ready. If you don’t enjoy learning how to swim by getting thrown in the water, you will feel very uncomfortable. This sort of ownership will accelerate your growth and integration into the team.
Tips for Success
Embrace the challenge as a sign of trust from your manager and team
This ties into the importance of having a “ways of working” conversation early on as discussed above. It’s in everyone’s best interest for you to start independently run projects without your manager’s hand-holding.
This can be daunting but leverage it as an opportunity to demonstrate your capabilities and build confidence from here.
Don’t hold off on your questions. Communicate blockers & progress early, and, often
Always lean on the side of over communicating, especially early on. Your manager is also your mentor, ally and first layer of defense for any blockers you can’t resolve
This can include but not limited to
Clarify the ask from your manager
Confirm the deadline of an ask or project
Ask for more time to take on an ask
Discuss the priority of tasks
Analyze cross functional alignment and blockers with your manager
Embrace internal data and own it
Data-driven evidence can be your best friend. Use it to distill insights and uncover new opportunities.
In my first 3 months at DoorDash, I learnt about new restaurant success metrics and SQL queries inside out so I could speak confidently when we reviewed 2023 performance and brainstormed 2024 strategies.
Don't be afraid to ship projects quickly and iterate based on feedback
During my first project at DoorDash, I embraced the iterative approach. After completing it, I hosted an online feedback session with cross-functional partners involved in the project, where I collected first hand information on what went well, what could be improved and what could be added.
Using these valuable inputs, I soon developed a new and improved process after incorporating the feedback. This approach not only improved the project outcomes but also demonstrated my adaptability and commitment to continuous improvement.
Share this post