TL;DR:
I share my journey from working as an ALT (Assistant Language Teacher) in Japan to becoming a self-taught web developer. I retell of the challenges I faced navigating the tech job market here—especially the pitfalls of SES/SIer companies—and offer advice for those looking to break into IT. If you're starting out, this post highlights what I wish I’d known before diving in.
I wanted to write about the tech landscape for those looking to start out as a self-taught web developer in Japan. From my own experience, I’ve noticed there aren’t many detailed articles covering this topic—aside from a few Reddit discussions. There are a lot of things that aren’t talked about enough, including the challenges and traps that newcomers might face.
So, I want to share my journey—how I got started as a web developer in Japan and what I’ve learned along the way. I’ll also go over things to be aware of when looking for your first company, so you can avoid potential missteps and make better decisions.
A bit about myself
I came to Japan in 2018 as an ALT (Assistant Language Teacher). It was an experience I genuinely enjoyed—getting to explore Japan’s countryside, immersing myself in the culture, and engaging with students in a meaningful way. One of the best parts was feeling like I was making a difference in their learning.
Of course, being an ALT also came with a fair amount of downtime between lessons. I used that time to study for the JLPT (Japanese Language Proficiency Test), first passing N2 and then eventually N1. Once I had finished my language studies, I found myself wanting to learn something new.
That’s when I got interested in web development. Seeing how websites and web apps worked—and being able to build something interactive from scratch—seemed really cool to me. I’d always had an interest in tech since I was a kid, but I never pursued it seriously (mostly because I thought math would be a big part of it, and calculus was not my thing). To my relief, I quickly realized that advanced math isn’t really necessary for web development.
I took an online course for six months, covering the basics—HTML, CSS, JavaScript, Git, GitHub, and all the essential tools needed to start building projects. I used every resource I could find: Udemy, The Odin Project, YouTube tutorials... anything that could help me learn.
Near the end of my course, I had built enough projects to get comfortable with web development. I enjoyed working with React, so most of my projects were based on it. I also found myself really enjoying the styling and design aspects—it was fun making things look good while keeping them functional.
My First Programming(?) Job After Being an ALT
Oooh boy. The few months leading up to the end of my ALT contract were brutal. I was firing off applications left and right to every developer job listing I could find online. But most postings—especially on LinkedIn—were looking for mid to senior-level developers with at least 3+ years of experience.
It was tough. Really tough.
There were barely any entry-level English speaking dev jobs, and the only entry-level ones that existed were mostly at Japanese companies listed on recruitment sites like En Tenshoku, Doda, and Type. Unfortunately though, Japanese is required in these type of companies.
At first, I was amazed by how many “entry-level” programming jobs there seemed to be. Japan must really need a lot of developers! But despite the sheer number of listings, I struggled to secure an actual job offer. I got plenty of interviews, though, which at least meant my resume was good enough to catch attention.
Falling Into the SES/SIer Trap
Eventually, I landed a job at a small startup IT company and was excited to finally begin my Frontend development journey! Or so I thought.
At the time, I had no idea how most local Japanese IT companies actually worked. What I had signed up for was an SES (System Engineering Service) / SIer (System Integrator) company.
Quick explainer: These companies don’t actually do development work in-house. Instead, they hire engineers and “rent” them out to client companies as temporary workers. So instead of being assigned to internal projects, you're basically a contractor, waiting for a client to pick you up.
My First Day
On my first day, I arrived at the office expecting to be assigned to a front-end project. Instead, I was asked to:
- Get my picture taken
- Record a self-introduction video
- Fill out a skill sheet
I was confused. Wait, I thought I'll be assigned to a project straight away? Am I job searching again?
Turns out, I had to go through another round of interviews—this time with potential client companies. These were arranged by my account manager, who basically acted as a middleman trying to “sell” me to clients.
A bit odd… but I figured as long as I can land a Frontend development project, I’d be fine.
My “Programming” Assignments (Or Lack Thereof)
I was on standby for almost a month, using the time to polish my skills while waiting for an interview. And then…
My first assignment? Updating POS registers at a supermarket chain.
- Job description: Follow a manual and install new software on registers.
- Schedule: Graveyard shift. Twice a week.
- Programming involved? None.
Not exactly what I imagined for my first “dev job.”
Still, I figured it was just the start. I put up with it for two months before being placed on standby again.
Next assignment? Working at a PC recycling company, wiping and refurbishing old business/consumer PCs.
I started asking my account manager when I’d actually be assigned to a Frontend development role. His response? “There just aren’t any frontend projects available right now unfortunately.”
Then, to make things even worse, they tried to assign me to:
- Another kitting job
- A call center role
- A project management position
That was it. I had enough.
Escaping the SES Cycle
At this point, I realized I was wasting my time and immediately started job hunting again. Eventually, I landed a position at another Japanese startup—this time, as a real Frontend Developer.
It wasn’t exactly smooth sailing (I’ll write another post about that), but at least I was finally in the field I had worked so hard to break into.
Final Thoughts & Advice
I'll be honest—I was naive. I didn’t do proper research on SES companies before joining one, and looking back, I wish I had been more informed. After leaving, I started digging deeper into how these companies operate, watching YouTube videos, reading reviews, and hearing others’ experiences. Many SES companies can be sketchy, and I should have been more cautious. But at the time, I was desperate for a job and needed a way to stay in Japan.
So, if you're looking to start your IT career in Japan, here’s what I’ve learned:
- Prioritize international companies (called Gaishikei (外資系). They generally offer better salaries, work-life balance, and career growth opportunities.
- Get your JLPT N2 or N1. This is very important as your personal projects on Github alone won't make you stand out without the language skills for workplace communication.
- Look for 自社開発 (jisha kaihatsu) in job listings. This means the company works on its own internal projects, rather than dispatching employees to clients.
However as a disclaimer, not ALL of Japanese companies are terrible, as well as not ALL of international companies are perfect. You just need to use your intuition and look up the companies in detail as much as you can.
If You’re Considering an SES Company… Be Careful
If you’re set on joining an SES company, do your homework. Here’s what to watch out for:
During the interview, ask how likely you are to be placed in a project that matches your skills and the guaranteed chance of getting it. If they dodge the question or give some vague answer, that’s a red flag.
Pay attention to the vibe of the people interviewing you. If the recruiter, CEO, or engineers seem uninterested, unprofessional, or just gives off bad vibes, it may not be the place you want to work at. My interviewer looked grumpy and he didn't exactly make the interview comfortable—should’ve taken that as a sign.
Research the company on review sites:
転職会議 (Highly recommended)
OpenWork
enひょうばん
Use Google Translate if needed, and take note of recurring negative reviews. I know some reviews can be very exaggerated but there is always a grain of truth in them.
Check the company size and number of employees. A small size company could mean a lot of pressure and low quality jobs (hence lower chance of ending up with the type of project that you want to belong in)
Look at their overtime policy. In Japan, overtime is unfortunately mostly unavoidable, so avoid companies that list 30+ hours per month.
I hope my experience gives you some insight into the IT job market in Japan and helps you navigate it more smoothly. My goal with this blog is simply to share what I’ve learned and offer a fair bit of caution for those starting out. If this helps even one person avoid the traps I faced, then it’s worth it.
Top comments (0)