In Japan, it is not uncommon for projects to fail or for engineers to bear the brunt of issues in the large-scale chain of outsourced software development.

To address the communication overhead that grows in such situations, “designers who cannot program” or “programmers who merely act as coordinators” are often introduced into various processes.
However, separating designers, implementers, and managers entirely often leads to conflicts, which is unfortunate for everyone involved.
Just as a person who cannot cook should not write recipes, and a chef who only gives orders cannot create delicious dishes, the same applies to software development.

Output-Oriented Development

In all aspects of our work, including hiring and organizational structuring, we adhere to a policy of prioritizing source code and output.

Rather than dividing tasks by process, a single engineer is responsible for everything until a feature is complete. This approach clarifies accountability and provides a sense of accomplishment.

We also conduct code reviews using GitHub. These reviews are valued for two reasons: ensuring quality assurance and fostering growth as a technician.

Output-Oriented Hiring

In hiring, we evaluate what you have made public and what you have created out of personal interest.
We look at your GitHub code, contributions to open-source projects, personal tools or scripts you’ve created, unfinished “dog food” projects, blogs, and social media, rather than focusing on which university you graduated from, what qualifications you hold, or which projects you participated in at previous companies.

This is because we are interested in the value you have personally created, rather than the organizations you have belonged to (though, of course, we also value those who have contributed within companies).

Additionally, publicly sharing something you’ve created demonstrates the courage to put yourself out there for evaluation, no matter how small the project. This is a commendable quality.

Confucius once said, “One who knows is no match for one who likes. One who likes is no match for one who enjoys.”
This means that those who enjoy something surpass those who merely love it, and those who love it surpass those who merely know it.
Your personal output reflects what you love and enjoy.
Tell us what you’ve thought about and created.
Let’s pursue what we love together and enjoy engineering.