JA

Why don't Japanese SIers use coding tests or technical interviews? The upsides and downsides of hiring for teamwork

Here is what this post covers:

Introduction

In IT work, the knowledge you need for design and the ability to understand something you have never seen before feed directly into how good the finished system is. That is why technical skill and reading comprehension matter so much on the job. I think companies would be better off testing for those abilities when they hire, too.

Many Japanese companies, though, spend their interview time and money not on technical or coding ability but on things like teamwork and personality, which have little to do with the actual work. As a result, mismatches after joining are common. The company wastes money and time, the employee’s career takes damage, and the employee may end up resenting the company.

In this post I look at why Japanese companies, and SIers in particular, don’t test technical skill and instead spend their time on personality assessments and checking for teamwork. (An SIer, or system integrator, is a Japanese IT services company that builds and runs systems for client businesses, usually under contract.) I also look at whether hiring for teamwork really lowers the quality of the people a company gets, and what risks come with the spread of generative AI.

Note: This post is based on general claims from career-change media and personal blogs. SIers differ a lot from one another, and some have recently shifted toward hiring on technical skill.

1. Why there is no technical test

Hiring is for generalist roles, based on potential

When SIers hire new graduates or people a few years out of school, they are not looking for engineers who can already write code. A motivation like “I want to write code” can even be read as a sign that the candidate is better suited to a web company building its own product.

Interviews focus on soft skills

In Japanese interviews, new graduates are judged mostly on teamwork and enthusiasm, and mid-career hires on how their past experience would apply to projects. Some point out that almost no companies measure ability directly, the way a coding test does.

Division of labor through layers of subcontracting

Prime contractors and second-tier contractors handle client negotiation, requirements definition, high-level design, and project management, and they hand implementation off to subcontractors. So the closer a company sits to the prime contractor, the fewer chances its junior staff get to write code.

Documentation and management come first

On large projects, the job tends to center on project management and writing documents, so programming ability rarely becomes a hiring requirement.

Mostly mature technology

Maintaining and operating existing systems is the main source of revenue, and Java and COBOL are widely used. Deep knowledge of the latest technology is rarely required.

The plan is to train people after they join

Basic training of about three months followed by on-the-job training is typical. At large companies, new hires go through group training run by a training company, moving from business skills to IT fundamentals to development training.

Exceptions

Forward-leaning companies such as Mercari and LINE do use coding tests. Web companies building their own products also use take-home tests with a deadline and live coding over a shared screen. Across Japan as a whole, though, they are still a minority.

2. Does hiring only for teamwork fill a company with incompetent people?

My answer is that the worry is half right. Hiring for teamwork does not automatically mean a company fills up with incompetent people, but the structure does make differences in technical ability hard to see.

Where the worry is right

  • The brand hides real ability: People who leave large SIers are sometimes described as disappointing after they change jobs. Technical people who handle code and design work alongside management people who only manage and negotiate, and a job title alone doesn’t tell you which is which.
  • Technical skill may not grow, depending on assignment: Depending on which phase of the work you are assigned to, you may rarely touch technology and have a hard time building skills.
  • Training shows a company’s attitude: A company whose training is mostly business etiquette, with only a few days of technical training, probably doesn’t value technology much. A company that spends months on development exercises means to grow you as an engineer.
  • Mismatches are a problem across all hiring: In a survey of 604 hiring staff at product companies and SIers, 85.9% had experienced a mismatch. The most common reason, at 48.4%, was “capable, but couldn’t deliver results as part of a team,” followed by “technical skills didn’t match their years of experience” at 38.9%. Hiring for teamwork and hiring for technical skill each have their own ways of failing.

Why you can’t flatly say incompetent people gather there

  • Companies evaluate client handling and proposal skills, not only teamwork.
  • Technical skill is meant to be built after joining, and there are training and on-the-job training programs for that.
  • Certifications such as the Fundamental Information Technology Engineer Examination act as a minimum filter on knowledge.
  • Management and upstream work also require technical understanding.

3. The risk ahead: generative AI

Generative AI has started to take over a large share of code generation, and the assumption that you are safe as long as you do upstream work is starting to break down. Some analyses say the gap in pay and career prospects between people who can use AI well to offer value and those who can’t is widening quickly. This is the point where the cost of hiring without looking at technical skill is likely to start showing.

4. Wrapping up

  • There are reasonable explanations for why SIers don’t run technical tests: the nature of the roles, the division of labor, and the plan to train people after hiring.
  • The real problem is less that incompetent people get hired and more that capable people have a hard time standing out on technical skill, so evaluation and pay tend to get flattened.
  • If you want to compete on technical skill, apply for a development role through role-specific hiring, or pick a company that tests technical skill.

References

All of these are in Japanese.