Translated from 日本語 • View original Nice to meet you! This is Mochizuki, who joined the company mid-career as a team MSP member in November 2021. Currently, I live in Fukuoka, so I basically work remotely, but I come to the office once a month.
Today, I would like to introduce how I joined Colorkrew and the atmosphere of the team.
How he joined the company and what made him decide
My previous job was a Japanese SIer, and I was an on-premise network engineer. As for the job description, I listened to the requirements of customers, created detailed designs, and carried out construction and implementation work.
I started studying AWS as a personal initiative in addition to my work, which led me to be attracted to cloud infrastructure and wanted to work with it.
At that time, I was looking at a job on OpenWork (a company review site) that deals with cloud infrastructure, and found Colorkrew. I thought it was an interesting company, such as hiring a bari flat and opening up various information within the company, so I liked the job offer, but I received a scouting message from Mr. Akakawa, the MSP project leader, and after a casual interview and an interview, I received a job offer.
The interview and interview did not have the atmosphere of a formal recruitment interview at all, and I was able to talk in a relaxed atmosphere as if I were having a conversation. Also, it was good that I had the opportunity to meet with Mr. Suzuki of the operation team before the interview, so I was able to understand the atmosphere and work style within the team in detail. (I prepared too many questions, and it was like I was interviewing.) laughs)
I was told that I could ask anything, so I asked a lot of questions in interviews and interviews, but there were no questions that were NG. If you are considering applying in the future, I would like to recommend that you actively ask questions about anything.
There are four main factors that led me to join Colorkrew.
- Evaluate information dissemination/challenges
- Opportunities to work with Azure/AWS/GCP and IaC can be expected to improve technical skills
- You have the opportunity to be involved not only in contract work but also in your own products.
- The team atmosphere is like working remotely with peace of mind.
Since my previous job, I had been writing articles at Qiita and publishing AWS-related books, and I was appreciated for my efforts to disseminate information and do new things.
In addition, the wide range of technical areas used in internal and external projects allows you to develop your skills, and you can also develop your skills in Goalous and Mamoru BizIt was also attractive that it was possible to contribute to our own products.
Onboarding
On the first day of joining the company, I introduced myself in both Japanese and English at the company-wide morning meeting, and then I was explained about the internal system and set up my PC. We also had the experience of using the company's social media platform Goalous to set goals for onboarding and post activities.
From the second day, I received explanations about each project and had one-on-one conversations with team members to deepen my understanding of the company. In the first week, first month, and third month of employment, there will be interviews with human resources managers to report on current status, consult with each problem, and communicate improvements in onboarding.
By the way, Colorkrew's work style is mainly remote work, but in fact, I went to the office every day for the first week. I received an offer from the company because I thought it would be smoother to switch to remote after I had a certain level of relationship than to suddenly start working online. I also felt that it would bring me closer, so I decided to spend less than a week at a business hotel near my company. (The company will cover transportation and accommodation expenses when you come to work.)
As a result, I was able to meet various people every day regardless of the project in the office, so I'm glad I went. I was especially happy to be able to hold a welcome party at the exchange space called Joyful Studio after work. Thanks to being able to talk directly with many people, I was able to get used to the team at an early stage.
In addition, there is a lunch system in the company, so when I come to work, I try to actively communicate with this system under the pretext of this system. I am very grateful that there is a system that promotes employee interaction.
Lack of communication that was anxious
I currently work primarily in the MSP operations team, where I monitor the operation of customers' cloud infrastructure and propose improvements.
There are many different people on the team, but I think they are "nosy" people in a good way. They share the information they have within the team, support them when they are in trouble, and they are very reliable because they work with us on our concerns.
The team holds morning meetings every morning from 10 a.m. to share project status and internal information. I have the opportunity to talk to members every day, so I don't feel lonely even when working remotely. In addition, each member posts a branch report on Teams, an internal communication tool, so you can see who is doing what.
So far, I haven't felt a lack of communication because someone responds to me when I write a little problem or consults with me on the phone. I think Team MSP is a great environment for "nosy" people who actively share what they know or give advice on what others are doing.
There is no shortage of communication across the company as well. There is a company-wide morning meeting every Monday, a small talk in English/Japanese twice a week, and on Fridays, I have the opportunity to talk with the representative, Keishi Keishi.
Participation is voluntary except for the morning meeting, but you can communicate a lot with people outside the team depending on yourself. I often participate in the above, so I had many opportunities to talk with various people.
Since I was working from a rural area, I was worried about the lack of communication with the company and team, but I was not worried about that at all.
What's Coming
In the future, I would like to actively challenge myself in technical fields that I have no experience in. Early after joining the company, I used Terraform, which manages infrastructure with code, to build a verification environment and change the settings of the customer environment, but I still have only a touch of it, so I would like to deepen my understanding.
There are many other technologies used in the customer environment that are unknown, so we will do our best to catch up quickly. In the future, I would like to apply the skills I learned in this way to my own products.
I also hope to be able to disseminate the technical knowledge I have learned not only within the company but also outside the company. Recently, I was involved as a writer on an AWS-related book (released on January 19, 2022) supervised by Kohei Kurokawa, who runs the AWS learning service.
Information dissemination is recommended within the company, and I think it is an opportunity to appeal what I am interested in, so I would like to actively implement it in the future.