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

Hello, I'm Miyoshi, the recruitment manager

Today, I would like to introduce
the daily work of our infrastructure engineers I am ashamed to say that I had never even heard 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
Job: Infrastructure Engineer
Affiliation: 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 the work is enjoyable and the relationships are good,
and that even though he had no experience, he was able to grow as a person by receiving help from senior engineers
!

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 : At first, I was vaguely attracted to the IT industry, which offers more flexible working styles than an engineering job. I graduated from the Faculty of Letters and had no connection to the IT industry, but when I learned that there were many liberal arts graduates who were active as engineers, I thought maybe I could become an engineer too, and gradually became interested. 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 Yoshida belongs responsible for everything from server construction to operation and maintenance . Taking advantage of the geography and time differences of overseas bases, the cloud server is kept in stable operation with manned monitoring 24 hours a day, 365 days a year.

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: [Close up on a new graduate!] What happens when an engineer who joined the company with no experience grows a year later? [Infrastructure engineer]

The flow of a certain day

① Identifying tasks
② Team or whole-group lunch meeting
③ Creating work procedures
④ Customer service
⑤ Regular meetings and meetings

This is what a typical day looks like when I'm not on duty (a day when my main focus is responding to alerts and customer inquiries).
Sometimes I'm able to quietly work on my own tasks, and other days I'm responding to alerts all day.

Morning Routine

Yoshida : All communication with customers and alert notifications are done via chat. Hundreds of messages accumulate in a day, so when I arrive at work, I first go through them all, mark them as read, and deal with important messages and messages addressed to me in order. After that, I identify the tasks for the day, clarify their priorities, and create a schedule.

Morning work

Yoshida : The work varies, but whenever I carry out a task, I always need a procedure manual, so I create one each time. Whenever I receive an inquiry, I investigate (check logs and middleware settings) and report accordingly. I also belong to the SSL team that manages SSL certificates, so I handle any SSL certificate or domain-related matters that require contact with customers. In the mornings, there is relatively more preliminary work, such as research and document preparation, compared to the afternoons. Incidentally, on this day, I used Google Meet to carry out the update work with members working remotely.

Afternoon work

Yoshida : Regular SSL meetings, meetings to improve alerts, and internal project meetings are scheduled from time to time. 1-on-1s and mentor interviews are often scheduled on F (days when I'm not on duty). Other than that, I review procedure manuals and carry out tasks that have been pre-arranged. I also sometimes work on tasks for internal projects (Organizational Culture Committee: a team that stimulates communication between employees) and hold 1-on-1s. On this day, I held a 1-on-1 with a new graduate member of the team!

Duty day

Yoshida : We have three shifts: E (8:00-17:00), L (14:00-23:00), and N (23:00-8:00). Each shift has a member in charge, and when a member changes, a handover (a time when any updates to the response methods or changes in the customer's environment are shared with the next person on duty). N (23:00-8:00) is handled by members from our Canada office.
To respond to alerts (receive notifications when an abnormality occurs in the system or server, investigate the cause, and take the necessary action), we need to be aware of the current situation, so a handover takes place whenever a member changes.

After that, my main duties throughout the day are basically responding to alerts and customer inquiries.
For example, if a problem occurs, such as "the server is overloaded and the website cannot be displayed," "communication becomes unstable," or "an abnormality is detected in the system," an alert (notification) will be sent immediately. When I receive an alert, I immediately check the situation, investigate the cause, take recovery measures, and report to the customer.

In addition to alerts, we also respond quickly to actions from customers, such as work requests, sharing maintenance schedules, and notifications about changes to the environment, and share information with on-duty team members as necessary.
Ideally, nothing will happen, but we have a system in place that allows us to respond immediately in the unlikely event that something does happen.

A message to our readers

Yoshida : The IT world is limitless, so being an infrastructure engineer is an interesting job because you can learn something new every day. I'm sure you have a lot of worries, but do your best to do what you can only do now!

---

That concludes Infrastructure Engineer Yoshida's daily blog!

Our 3-day summer internship for 2027 graduates will 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 be able to learn about the work of an infrastructure engineer while also gaining practical experience in building a game server.

offer a one-day online summer internship for those who live far away or find it difficult to attend for three days

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~