The front end is now at the heart of web development.
We are looking for a client-based front-end engineer (coder).

It has been 10 years since Monosus started specializing in the front end.
Until now, the role of the front-end (coder) has been the final step in web production, but it is now about to change dramatically.

Whether the user can use it easily (UI) and what kind of experience they are satisfied with (UX) have become the lifeblood of web services, and knowledge of the front-end, which controls the "appearance" and "movement", has become indispensable in determining specifications.

From the final production process to playing a central role in determining specifications.

If your role changes, so will the way you work. Rather than repeatedly sending emails and holding meetings in remote locations, as in the past, you might be able to be more directly involved by "creating something together" with the client at their site.

Therefore, we are now recruiting for a new client-based front-end engineer (coder).

The strength of the front-end is being able to put yourself in the user's shoes

It is becoming increasingly difficult to create highly usable websites using the traditional method of coders implementing content according to pre-defined specifications. The reason behind this is that the web has changed from a two-dimensional experience (looking at information) to a three-dimensional experience (experiencing the user's body).

As the areas of UI, UX, etc. expand, the number of projects for which the previously mainstream waterfall model (a method of progressing through the process in order from requirements definition → design → implementation) is no longer suitable is on the rise.
These are the words of Izumi Kojima , head of the Coding Factory Department.

Kojima, the leader of the new engineering team, says he "loves coding more than eating." He feels that the time has come to take advantage of the strengths of the front-end, which can see things from the user's perspective, in response to these changes.

Kojima
Even if there is a specification document filled with a mountain of UI and UX instructions, there are many cases where when you actually implement it, you find that it's "hard to use...". In that case, it's better not to decide on the specifications in advance, but to check them as you actually create it. At that time, only front-end engineers can think from the user's perspective and actually try and error.

The coder in charge of the front end works together with the designer and back end to create mockups and verify the movement and appearance. The final form is created by solidifying it little by little.

Kojima
This is a so-called "agile" development method, where all the engineers from previously separate processes (system design, design, coding, etc.) come together and work with the client to quickly create something. It feels like you're creating something on the fly, but there's no need to wait for the previous process to finish. To achieve this sense of speed, I think the most efficient way is to be stationed at the client's site for a certain period of time and work face-to-face.

From my previous position of "the person who implements the system at the end," I will now be "the person who helps create the system together" through trial and error. This is certainly a big change.

I want to be involved in the process of deciding specifications

Does this mean that the style of web production in the future will shift from the traditional waterfall model to an agile model?

Kojima
No, I want to keep the traditional way of doing things, but also try new ways of being involved. The production process of implementing everything all at once at the end will remain necessary, but I also want to be involved in the process of deciding the specifications.
The client has their own ideas, and we have the technology to make them a reality. In that case, working together is quicker, makes the client happy, and allows us to use new technologies to create cool websites (laughs).

Certainly, it is very rewarding as an engineer, but communication is also important in order to meet the needs of others. It seems that it is not enough to simply have technical skills.

Kojima
Of course, communication skills are necessary in addition to technical skills. But I think it's okay if you're currently working on a project and feel a certain sense of frustration. People who want to be more involved in the "let's do this" part, or people who want to try different kinds of projects. I think it's important to have the desire to jump out of your current position and step up as a creator.

"I want to hone my knowledge and skills as an engineer while working on new projects at various client sites. For such people, this way of working will be a great asset," says Kojima.

The peace of mind of knowing you have friends you can talk to

You will be stationed outside the company and handle one project after another. That sounds similar to being a freelancer, but what about your involvement within the company?

Kojima
It is not expected that they will be stationed at the same client's office forever, but rather they will come back after a few months, stay in the company, and then fly off again. The idea is that Monosus will be their home base.

Speaking from his own experience as a freelancer, he stresses that the biggest difference is the sense of security.

Kojima: When I was freelance, it was rewarding and fun, but it was really hard to have to do everything by myself. No matter how much I thought about it and tried to work efficiently, I only had one head and two hands. Then I got involved with Monosus and witnessed the teamwork of the coders. I joined Monosus because I was shocked by the way they helped each other out when they were in trouble (laughs). I think you can rest assured about that.

We offer advice when you are unsure, support when you are stuck on labor-hour adjustments, and sometimes we ask Yoyogi members to implement mockups. We plan to create a system for mutual support by participating in monthly coder meetings and holding knowledge sharing events.

Kojima
This way of working is possible because of the members of Yoyogi. By being with each other, we become a stronger production group. Even though we are outside the company, we are never alone, and I want to emphasize that.

I want you to experience the results of actually trying it out.

Yosuke Ito has actual experience in a resident project and will be in charge of training this time.

As Kojima's predecessor, he is a top engineer at Monosas who made a great contribution to dramatically improving the technology of the Coding Factory. Using his teaching skills, he was in charge of the coding course for both the first and second sessions of the "Kamiyama Monosas School". He is an education specialist with many "Ito children" within the company.

Ito, who was stationed at a client's site with multiple vendors early on, said, "The sense of teamwork is incredible." At the same time, he also seems to realize the importance of taking initiative.

Ito
Because we jump into the other person's home, the acceptance stance is completely different. It feels like we are really making it together. Like, "What should we do about this?" "Yeah, that's right" (laughs). There is little communication loss. We concentrate hard in meetings, and other than that, we work silently in our own areas. That switch is also very comfortable.
You have to take the initiative yourself, otherwise nothing will happen. You have been called in as a professional in that field, so you can't just wait for instructions.

If you don't go out of your way to get information, updates may be missed. It's a professional workplace that requires you to act independently. Although it's tough, it can also be fun, depending on how you get involved.

The front-end team takes the lead in driving the team

How is the position of the front end actually changing in the production field? It is said that even in projects involving systems where specifications were previously ordered from the back end to the front end, the reverse is increasingly happening.

Ito
Even in the current project, I'm the one who issues the order to the backend, and I'm also invited to design meetings. If the frontend doesn't take the lead, the project won't move forward quickly.
Originally, front-end is adjacent to both design and back-end, so it is easy to expand into both. If you understand design and servers, you are the best (laughs).

Using technology and knowledge to meet client needs is where an engineer's skills shine, but always providing optimal solutions seems like a big hurdle.

Ito
Of course, we also welcome high-level people who can do anything, but I think the important thing is whether you want to be that kind of engineer or not. Like, are you serious about making a living in the front-end?
There is always room for improvement in technology. I have expanded the scope of my abilities in that way. But the ability to properly talk to customers, understand them, and grasp what they are really looking for may be more important.

Ito says, "I'm an engineer because I like communication, and I'd be happy if someone like that came to work for us. We also have an educational system in place so that even people who come from a back-end background and have little experience in front-end can get by."

I will be teaching intensively in Yoyogi for about a month.

The training curriculum after joining the company will improve your basic HTML, CSS, JavaScript, and PHP skills to the required level. It will include courses based on coding guidelines , animation and back-end integration JavaScript, PHP function handling in WordPress, and other tools. Next, there will be a course on direction such as quality control, progress management, and budget management. Finally, as a practical part, you will learn about resident working style through role-playing.

Ito
The training period will be about one month, and will take place in the Yoyogi office. We will be hiring about 4-5 people this time, so the training will take place in a corner of the floor where everyone in the company is. During this period, we would like them to deepen their interactions with their Monosus colleagues, who will be their home base.
However, this is only the minimum setup. I hope that you will continue to learn new things in the field and improve your skills. There is no end to technology.

As you develop your skills, I have a feeling that in the future you will be required to work in a more upstream process, such as as a technical director or project manager.

Ito
That's one way to go, but on the other hand, you could aim to become a cutting-edge engineer, or there could be another path. I won't lay out any specific rails for you, but the environment is one that supports a variety of paths, so I hope you continue to pave the way.

We are looking for people who can help us create new ways of working.

Finally, we spoke with the company's representative, Mr. Hayashi.

Monosus has different origins and working styles in each of its locations - Yoyogi, Osaka, Kamiyama (Tokushima Prefecture), and Thailand. With regard to this recruitment, he says he is happy that there will be more options for working styles.

Hayashi
Osaka started with a single email, while Kamiyama was established by the head of the school and students who were in charge of vocational training. The cross-cultural team in Thailand has a lot of returning staff, and this spring the vice president will be moving to Suo-Oshima in Yamaguchi Prefecture (laughs).
Normally, company policies come first, but in our case, personal thoughts often take the starting point. My desire to value such aspects has not changed since I first started the company.

The company name Monosus was chosen with the idea that we should all have our own measuring stick. Let's stop relying on what other people give us in our lives.

Hayashi
To put it in a good way, this way of working is somewhere between a freelancer and a company employee. Since I've never done anything like this before, there are probably some aspects that are difficult to do, and not everything is set up like in a big company. Of course, I'm thinking about it properly as a business, but I think there are many parts that won't start unless I take action myself.

It's not a way of working that applies to everyone, but there's definitely fun in creating that sort of space. I'm sure there are engineers out there who aren't satisfied with just being given what they need, and want to think and act for themselves.

Hayashi
So, it's fine if you don't say things like "I love Monosus" or anything (laughs).
We hope to attract people who can respect the diversity of working styles and who are interested in trial and error while creating a new culture.