What does an infrastructure engineer do? I gave a rough answer

Hello, I'm Miyoshi, the recruitment manager

Today,the typical tasks our infrastructure engineers performI'd like to introduce you to
To my embarrassment, I wasn't even aware of the existence of infrastructure engineers until I entered this industry...

When you hear the words "servers" and "networks," many people probably have the impression that they are somehow difficult and specialized

In this article, we will focus on a typical day in the life of an infrastructure engineer, who can be described as the "unsung hero" of the industry, and hope that it will give you a sense of familiarity with the type of work they do and how they work

We hope this article will be of some help to those who want to learn more about the IT industry and infrastructure field, or those who have heard of the job title of infrastructure engineer but don't know much about the actual work involved

《Click here to find out more about a day in the life of our web development engineers》

A day in the life of an in-house development engineer! What kind of work do you usually do?

Engineer: What kind of person is Yoshida?

Name: Yoshida
Occupation: Infrastructure Engineer
Department: System Solutions Department, Maintenance Team
Hobbies: Dancing

Yoshida joined the company as a new graduate in 2012. He studied literature as a student and became an engineer with no prior experience

Looking back at when he first joined the company, he said he thought, "I still want to be a student!" and "Can I really become an engineer since I have no connection to IT?" However, now his attitude has changed, and he thinks, "Being a working adult is fun because it has different appeal from being a student," and "You can become an engineer even if you have no experience."

The main reasons for this
that they enjoy their work, have great relationships with their colleagues
, and are able to grow as an engineer with the help of senior engineers, even though they have no prior experience
!

I often ask Yoshida for various requests and assistance with recruitment-related matters, and I feel reassured knowing that "I can trust this person!"

Why did you become an engineer?

Yoshida: Initially, I was vaguely drawn to the IT industry because it offered more flexible working arrangements than the typical engineering profession. I majored in literature and had no prior experience in the IT industry, but I learned that there are many people with liberal arts backgrounds who are successful engineers, and I started to wonder if I could become an engineer too. I gradually became interested in it. After that, I was fortunate enough to join Beyond, and after a training period, I became an infrastructure engineer!

---

Like Yoshida, I was also attracted to the IT industry because of its flexible working style. I joined the company mid-career, and although my job title was already decided, my industry choice started out vague. However, after arriving at Beyond, I became a fan of the company and decided on my direction!

It's okay to have a vague starting point, so first research various companies and job types, and once you find one that appeals to you from various aspects, I think you'll be able to determine the path you want to take!

What is the System Solutions Department?

The System Solutions Department, to which Mr. Yoshida belongs,responsible for everything from server construction to operation and maintenance. Utilizing the geography and time differences of overseas locations, they ensure the stable operation of cloud servers with 24/7 manned monitoring.

If you're curious about what it's like working in the System Solutions Department, be sure to check out the video below!

TikTok:A Day in the Life of an Infrastructure Engineer (Short Version)
YouTube:[Following a New Graduate!] What Happens When an Engineer Joins the Company with No Prior Experience and Has Become a Year Old...? [Infrastructure Engineer]

The flow of a certain day

① Identifying tasks
② Daily team and company-wide meetings
③ Creating work procedure manuals
④ Customer service
⑤ Regular meetings and conferences

On days when I'm not on duty (a day where my main responsibilities are responding to alerts and customer inquiries), my daily routine is as follows:
Sometimes I can quietly work on my own tasks, and other times I spend the entire day responding to alerts.

Morning Routine

Yoshida: We handle all communication with customers and alert notifications via chat. Hundreds of messages pile up every day, so when I come to the office, I first quickly read through them and mark them as read, then I deal with the important ones and those addressed to me in order. After that, I identify the tasks for the day, clarify their priorities, and create a schedule.

Morning work

Yoshida: My work involves a variety of tasks, but I always need a procedure manual when performing any work, so I create one each time. If I receive an inquiry, I investigate it according to the content (checking logs and middleware settings) and report back. Also, as I belong to the SSL team that manages SSL certificates, I handle matters that require contact with customers regarding SSL certificates and domains. In the mornings, I tend to do more preliminary work such as investigations and document creation compared to the afternoons. By the way, on this particular day, I used Google Meet to work on updates with members working remotely.

Afternoon work

Yoshida: We have regular SSL meetings, alert improvement meetings, and internal project meetings as needed. I often schedule 1-on-1s and mentor meetings on my F-days (days when I'm not on duty). In addition, I review procedure manuals and carry out tasks that have been pre-arranged. I also sometimes complete tasks for internal projects (Organizational Culture Committee: a team that revitalizes communication among employees) and conduct 1-on-1s. On this particular day, I conducted a 1-on-1 with a new graduate member of the team!

Duty day

Yoshida: We have three shifts for on-call duty: E (8:00-17:00), L (14:00-23:00), and N (23:00-8:00). Each shift has a designated member, and a handover(a time to share any updates to response procedures or changes in the customer's environment with the next person on duty) takes place each time a member changes shift. The N shift (23:00-8:00) is handled by members from the Canada office.
To handle alerts(receiving notifications when an anomaly occurs in the system or server, investigating the cause, and taking necessary actions), it's necessary to understand the current situation, so we conduct a handover every time a member changes shifts.

After that, the main tasks throughout the day are basically responding to alerts and customer inquiries.
For example, if problems occur such as "the server is overloaded and the website is not displayed," "the communication becomes unstable," or "an anomaly is detected in the system," an alert (notification) will be sent immediately. Upon receiving an alert, you will immediately check the situation, investigate the cause, take measures to restore functionality, and report to the customer.

In addition to alerts, we also respond quickly to customer actions such as work requests, maintenance schedule sharing, and notifications regarding environmental changes, and share information with on-duty team members as needed.
Ideally, nothing will happen, but we have a system in place to respond immediately in case of any unforeseen circumstances.

A message to our readers

Yoshida: The IT world is limitless, so the job of an infrastructure engineer, where you can learn new things every day, is fascinating. I know you'll have a lot of anxieties, but do your best to make the most of what you can only do now!

---

That concludes Infrastructure Engineer Yoshida's daily blog!

Our3-day summer internship for 2027 graduateswill include a web application workshop where participants will build a multiplayer game server using AWS and actually play the game. Through this experience, participants will learn about the work of an infrastructure engineer while gaining practical experience in building a game server.

for those who live far away or are unable to attend the full 3-day programa 1-day online summer internshipwe offer

We look forward to receiving your application!

[Recruitment event for 2027 graduates] Summer internship (3 days) will be held

[Recruitment event for 2027 graduates] Summer internship (1 day) will be held

 

Well then~