Lessons learned from changing jobs in a difficult time
Skyler
Posted on December 16, 2020
Hello!
Glad to see you again in a new post - or welcome if it's your first time reading me! I thought I would write this column about my new job, how it went and how it is going.
Disclaimer: I'm still a DevOps Engineer, I just changed the company I worked for. The previous company was in Media, I now work in FinTech (tech for the financial industry). I have been working in this field for two years now.
#1: Remote
As the situation imposes it, the company is fully remote. In my own opinion, and just mine, this made joining a new company harder. I know many of you will want to go fully remote in the future and it is not my case - at least for now. A mix of office and WFH when "things go back to normal" (whatever that means) would suits me best.
Joining a company, learning new things, it can already be a difficult moment. Add on top of that, the situation, the tiredness of December, the "English is not my first language" and sprinkle some Imposter Syndrome and you have a great mix.
#2: I don't know sh*t
As I've mentioned in another post (Kubernetes : how to deploy as a beginner and by yourself), I had a lot of responsibilities when I was just a junior/graduate. I felt "good" on the moment about it - you need something with Kubernetes? Call SkylerDevops. You need Terraform? Call SkylerDevops. (Yes, this is a shameless promo).
Looking back on it, I'm not sure this was right.
I joined this new team, with people who all have more experience than me. And boy.
Oh boy.
It’s only Monday and I’m already tired of struggling at work
— Skyler (@skylerdevops) November 9, 2020
Help pic.twitter.com/xVQI1OVj8R
So I started my new job last week
— Skyler (@skylerdevops) November 5, 2020
And boy
Oh boy pic.twitter.com/rAd2pQ5Meh
This is me. A lot.
I'm currently learning how to use my stress in a good way and not let me turn into mush.
#3: Doubts
Related to the previous point, I found myself in a team that was better than at, well, everything. Initially, I struggled with this idea a lot.
"What am I supposed to add", "They must be so annoyed with me".
Well, let me tell you something. If you arrive in a company, with 2 years experience, and you know more than them, you need to ask some questions (I know, there are exceptions).
The idea when you start somewhere, especially at the beginning of your career is to learn. Let me repeat.
Learn.
It is not right to impose you to "figure it out" by yourself, with little to no mentoring. Believe me, I have been there. I used to think "I can do this, you see. I'm GOOD". I encourage you to read jesuisundev article about developer's ego, which retraces the story of many new devs with too many responsibilities. I will write my own story one of these days.
Within the first month of working at the company, I have written the best Powershell scripts I have ever written. I have been asked "why" and having to form a coherent answer, not just "she's devops, she knows".
You should learn to depend on your colleague and to not hesitate to send them "hey, I'm not quite sure about this, what do you think?".
I'm going to wrap up this blog post here, but I hope you got a few things from this. I would be curious to know other people's experience during these unprecedented times.
See you next time!
Posted on December 16, 2020
Join Our Newsletter. No Spam, Only the good stuff.
Sign up to receive the latest update from our blog.
Related
November 29, 2024