A look into a real day in the life of someone working behind the scenes

Hello, this is Miyoshi, the recruiting manager.
It's still so hot, but the beginning of autumn has passed and it's autumn according to the calendar.
It feels like the seasons are changing when the wind blows.

Today, I'd like to introduce you to the daily routine of a backend engineer at our company. Our company has two development departments: contract development (System Development Department) and in-house development (Innovation Strategy Department). Today, I'll be talking about the work of a backend engineer in charge of contract development.

Engineer: What kind of person is Tamaki?

Name: Masakazu Tamaki
Occupation: Back-end engineer
Affiliation: System Development Department
Hobbies: Gaming

This marks Tamaki's third year since joining the company as a new graduate.
He has a calm demeanor, a unique perspective, and a sense of humor, and his intelligence and skillful choice of words are evident in every conversation. He is quick to notice the subtle nuances of things, and his ability to accurately grasp the other person's intentions and put them into words is often relied upon in daily interactions. He also gives the impression of being trusted within the company as an engineer who is kind to his juniors, offering solid support while offering advice.

Why did you become an engineer?

We asked Tamaki why he wanted to become an engineer!

Tamaki : Having been familiar with the internet since I was a child, I naturally became interested in programmers and the IT industry. That's when I came across Beyond, as I was looking for a company that was involved in both the web and IT.
At the time, they were using a unique selection method called " virtual interviews ," and I thought, "There's no other company doing something as interesting as this," so I decided to apply.
Through the training I received after joining the company, I felt that their style of making solid plans and working according to the man-hours suited me, and I'm currently working as a back-end engineer in the Systems Development Department.

---

Virtual interviews are a unique selection method that we have adopted as part of our recruitment methods. We are able to uncover the individuality and potential abilities of job-seekers that are difficult to convey through resumes and interviews alone, and many people apply through this selection process.
When people feel that "this sounds interesting!" and move forward with the selection process, it means that they empathize with our efforts and share similar sensibilities. We are very much looking forward to meeting such people.

Check out the complete summary of our unique recruitment efforts here!

Summary of Beyond's unique recruitment efforts - 2020-2025

Department introduction

The System Development Department to which Tamaki belongs is a department that undertakes contract development to meet customer requests for "we want this product made." The department is primarily responsible for the behind-the-scenes development of the systems used by customers, and is expected to contribute by utilizing its technical capabilities. Another key point is that there is no on-site work at client sites, and employees can work in-house, which makes it a department with a strong sense of unity.

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

TikTok: A Day in the Life of a Backend Engineer

A certain day's flow

I usually follow this routine at work.

① Checking inquiries/emails
② Organizing tasks and preparing for morning meetings
③ Dealing with clients (meetings and maintenance)
④ Checking specifications and design details
⑤ Sharing information through lunchtime meetings and morning meetings
⑥ Implementation work (coding and design)
⑦ Code reviews and sharing progress

Morning routine

Tamaki : When I arrive at the office, the first thing I do is check all my emails and chats. I read through inquiries from customers and within the company, prioritizing them based on urgency and content, and then organize my responses. I share any urgent issues with the relevant parties as soon as possible, and try to act on them as soon as possible.

After that, I check the progress of the tasks and internal projects I'm in charge of, and roughly plan my day's schedule. Depending on the project, we might have a morning meeting, so I prepare in advance by listing any points I want to discuss or confirm so that the conversation can go smoothly. I feel that this morning routine is an important time that not only contributes to my individual work, but also leads to cooperation across the entire team.

Morning work content

Tamaki : In the mornings, we mainly meet with clients. This is a valuable opportunity to hear directly about the background and nuances of their requests, so we make sure to carefully propose and confirm implementation policies. If we can get things in order here, the rest of the work will go more smoothly.

On days when there are no meetings, I often spend my time responding to inquiries and performing maintenance work, and even during these times I gain insights that can only be gained on-site. I also often check specifications and designs for new developments in the morning.

Before lunch, the whole team has a lunch meeting, and at morning meetings for each project, progress and issues are shared. By understanding the team's situation, it becomes easier to plan activities in the afternoon.

Afternoon work details

Tamaki : In the afternoons, I mainly focus on coding. I work on various implementations every day, developing new features and improving existing ones. I often check and adjust the design and specifications as I go along, and as I progress with development, I try to proactively review any areas where I feel like they could be improved.

When writing code, we are mindful of future ease of maintenance and take care to avoid any problems in the actual operating environment.
In particular, since Beyond operates its own servers, we strive to minimize the load on the server when it is running. For example, we utilize our knowledge of infrastructure in our development efforts, such as reviewing processes that tend to become heavy and improving implementation to reduce resource waste.

We have an evening meeting around 5pm, where we report on the day's progress and any issues we're having. By organizing the next day's work and priorities here, we can start work without hesitation the next day. The afternoon is mainly development work, but it's also a time to work while being mindful of not only the technical aspects but also cooperation with the team.

A message to our readers

Tamaki : There are a lot of interesting people here. I think it's an environment where you can really experience the joy of working in a team.

---

That concludes backend engineer Tamaki's daily blog!

Beyond is currently a one-day summer internship ! Through a basic engineering experience workshop, you can deepen your understanding of the work of an infrastructure engineer. We look forward to your application.

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

Well then

If you want to consult a development professional

At Beyond, we combine our rich track record, technology and know-how in system development that we have cultivated to date with OSS technology and cloud technologies such as AWS to create contract development of web systems with reliable quality and excellent cost performance.

We also work on server-side/backend development and linkage development of our own APIs, using the technology and know-how of the construction and operation of web system/app infrastructure for large-scale, highly loaded games, apps, and digital content.

If you are having trouble with development projects, please visit the website below.

● Web system development
● Server-side development (API/DB)