-
-
Notifications
You must be signed in to change notification settings - Fork 124
First 90 days guide #1748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
nparker94
wants to merge
3
commits into
main
Choose a base branch
from
90-days
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
First 90 days guide #1748
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| --- | ||
| title: First 90 days | ||
| description: How to succeed in your first 90 days | ||
| emoji: 📔 | ||
| weight: 4 | ||
| --- | ||
|
|
||
| This guide will give you some suggestions on how to hit the ground running in your first 90 days of a tech job. | ||
|
|
||
| ## Your manager | ||
|
|
||
| You will likely want to set up a regular one to one meeting with your manager. This meeting is an opportunity for you to build your relationship with them. You can share any challenges you are facing and any successes with them to make sure they are aware of what a good job you are doing. It’s also a good place to ask for feedback as to how they think you are doing. Depending on the individuals, this meeting may be weekly, bi-weekly or monthly. Some managers may prefer for it to be ad hoc rather than on a fixed schedule, but if that is the case, we would advise setting a personal reminder to ask them for a meeting every month, in particular at the beginning when you are finding your feet. | ||
|
|
||
| This is a [sample list](https://www.unicorn-cto.com/1-1-questions/) of questions that your manager may ask you. | ||
|
|
||
| ## Your team | ||
|
|
||
| Your direct team are typically the people you interact with most and so building a good rapport with them is critical to your success and enjoyment. They will often be your first port of call if you are stuck with a technical issue or want advice. A good way to get to know someone is to suggest getting a coffee together or eating lunch and asking some questions to get to know them as a person beyond work. For example, what hobbies they have, what films and music they are into. Just bear in mind that some people will be more comfortable sharing their out-of-work self than others, and so if you are not reciprocating in their interest, it may be best to try with someone else. | ||
| If introductions to your direct team aren't set up, we suggest you take the initiative and book them in. | ||
|
|
||
| ## Meeting other people in the company | ||
|
|
||
| Sometimes in software jobs you may work very closely with your immediate team but not interact with many people outside of it. There are however other ways you can get to know people outside of your direct peers. Often there will be company socials that may be organised by the office manager or a voluntary social committee. There may also be team interest channels in Slack or Microsoft Teams, for example around music or pets. | ||
|
|
||
| It can be helpful to make friends in other teams and departments to better understand how the company works. If you are considering different career paths in tech this can also be a good way to get to know other job roles and what they really entail inside a company. | ||
|
|
||
| ## Learning and development | ||
|
|
||
| For more advice on lifelong learning see our [learning guide](../learning). In your first 90 days the amount of things to learn can be overwhelming, so it is useful to have a plan for what you want to focus on and discuss it with your manager. This will typically a combination of | ||
| - The parts of the system your team is responsible for | ||
| - What your team is working on right now | ||
| - Any upskilling in particular languages or technologies you need for your role | ||
|
|
||
| You should also not underestimate the value of learning about the wider context, what the company sells and its different products and business model as this will help you find the right solutions to problems you encounter. | ||
|
|
||
| It is also useful to keep a record of the skills you learn and any achievements. You can then use this when you want to go forward for a promotion, or when you are adding this experience to your CV for your next role. It can be easy to forget some of your wins when you are absorbed in the every day. | ||
|
|
||
| ## Asking for help | ||
|
|
||
| It’s normal to have to ask for help a lot to start with, even the most experienced tech professionals won’t know how that particular company works. It can feel like everyone knows more than you, but everyone expects you to ask questions as a new starter. However, it is important to strike the balance between trying to find the answer yourself and not wasting days on end stuck on the same thing. A rule of thumb is to try to work on a problem or blocker for 2 hours. If you still can't work it out, ask for help. If you are unsure, you can always ask for feedback after your first few problems as to whether you waited long enough before asking for help. Over time, you will also pick up where to ask different questions, as different people will have different expertise. | ||
|
|
||
| ## Quick wins | ||
|
|
||
| Look for tasks that you can quickly succeed at early on to demonstrate your value to the team. In an engineering role often the best way to understand how the system and processes work is to complete a very small change and follow it all the way through to production. You could also suggest an improvement to a team process or offer to help out with any other problem you see your team struggling with that you think you can help with. Being engaged and pro-active and showing you are a team player will help you to build positive relationships with your colleagues. | ||
|
|
||
| ## Feedback | ||
|
|
||
| Some companies will have a more feedback focused culture than others, and so you may receive feedback regularly as part of a regular process or you may not. After a couple of weeks, make sure you ask your manager and another team member you are working with closely how they think you are getting on. If there is anything they think you should be doing differently, it is better to know sooner rather than later and it also shows you are proactively engaged in your own development by asking. | ||
|
|
||
kfklein15 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| Finally, the first part of any job is usually quite intense and tiring as you get up to speed with how everything works, and then it calms down as you get more familiar, so don’t worry if you find it very full on to start with. No one is expecting you to understand everything in the first 90 days. But they expect you to be curious, interested and communicate with them. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.