NO JAPANESE REQUIRED: Backend Engineer in Japan
AI is moving beyond experimentation and into the systems companies depend on.
For backend engineers, that creates an interesting new challenge: how do you take technologies such as LLMs, AI agents, and intelligent document processing and turn them into reliable enterprise software?
That is exactly the problem engineers at a fast-growing Japanese AI accounting SaaS company are working on.
The company develops AI-powered cloud products that automate accounting and finance operations for large companies in Japan.
For backend engineers, that means building much more than APIs around an AI model.
You are designing the infrastructure, business logic, integrations, databases, and services that allow AI to become part of a real enterprise accounting workflow.
In this position explainer, we look at what this Backend Engineer role involves, the technology you would work with, and the type of engineer who could be a strong fit.
What Does the Company Do?
This company is a Japanese SaaS and AI business specializing in accounting automation.
It develops cloud-based solutions using technologies such as AI-OCR, machine learning, LLMs, and AI agents to reduce manual accounting work.
This next-generation accounting operations platform expands considerably beyond document recognition.
Instead of simply extracting information, the system is designed to support broader accounting operations such as:
Invoice processing and payment decisions
Expense management
Reconciliation
Lease accounting
Capital expenditure workflows
Enterprise accounting system integrations
This shift is important for engineers.
As the product becomes responsible for more of the accounting workflow, the backend needs to handle considerably more complex business logic, integrations, permissions, reliability requirements, and enterprise-scale workloads.
So What Does a Backend Engineer Actually Do Here?
The easiest way to understand the role is to think of the company's products as having two main layers:
| Area | What You Build | Main Engineering Focus |
|---|---|---|
| Platform / Foundation | Core systems that other applications run on | Scalability, reliability, permissions, integrations, and architecture |
| Application / Business Logic | Features supporting specific accounting workflows | Domain logic, customer workflows, and product functionality |
You can join either area depending on your experience and interests.
This makes the opportunity interesting if you want to continue as a backend engineer but have a preference between platform engineering problems and product/domain engineering problems.
Track 1: Platform and Foundation Development
The Platform and Foundation teams build the technical foundations supporting the company's next-generation accounting platform.
You work on areas such as:
User management
Authentication and authorization
Permissions
External system integrations
Core platform functionality
APIs and backend services
System resilience
Scalability
Performance
Architecture
Because the company serves large enterprise customers, these systems need to be reliable and secure while supporting increasingly complex workflows.
You are therefore not simply implementing individual product tickets.
You will be involved in questions such as:
How should the system scale as enterprise usage grows?
How should permissions work across complex organizations?
How should external accounting systems connect with the platform?
How should services be designed so that new accounting applications can be added efficiently?
If you enjoy architecture, distributed systems, APIs, infrastructure, and building reusable foundations for other engineers, this side of the organization could be particularly interesting.
Track 2: Application and Business Workflow Development
The Application Development teams are organized around particular accounting processes.
For example, there are teams working on areas such as:
Lease accounting
Reconciliation
Expense processing
Invoice payments
Capital expenditure
Here, the engineering challenge is slightly different.
You need to understand how accounting teams actually perform their work and translate those workflows into software.
That means working closely with Product Managers, frontend engineers, and other specialists to understand questions such as:
What happens after an invoice enters the system?
Who needs to review it?
What decisions can AI make automatically?
When should a human be involved?
What information needs to move between different systems?
Backend engineers then build the APIs, services, databases, and business logic that make those workflows possible.
This could appeal to you if you enjoy building products where understanding the business domain is just as important as writing technically strong code.
Where Does AI Fit Into the Role?
One of the most interesting aspects of this position is that AI is part of the production product, rather than an isolated research experiment.
The company has an internal research organization including Research Scientists working with technologies such as computer vision and LLMs.
Backend engineers collaborate with these specialists to integrate AI capabilities into the actual product.
That can include areas such as:
LLM integration
RAG systems
AI-powered workflow automation
AI agents
Document processing
Data pipelines
Model outputs within business applications
However, this is an important distinction:
You do not need to be an AI researcher to work in this position.
The backend team's job is often to take AI capabilities and turn them into dependable product functionality.
For example, an AI model might identify information contained in an invoice.
But a real enterprise product still needs to determine:
Where that data is stored
What business rules apply
Who can access it
Whether another system needs to receive it
What happens if the AI prediction is uncertain
How the workflow continues
How errors are handled
How the system remains reliable at scale
That is where backend engineering becomes essential.
What Technology Would You Work With?
The primary backend languages include:
Python / Golang / TypeScript
The specific language you use will depend on the team and system you work on.
Candidates are expected to have professional backend experience with at least one of these languages rather than all three.
You are also likely to encounter technologies and concepts including:
AWS and cloud infrastructure
APIs
Microservices
SQL databases
Docker
Kubernetes
Distributed systems
Agile and Scrum
Clean Architecture
Domain-Driven Design
AI development tools and coding agents
The engineering culture also puts emphasis on clean code, collaborative development, code reviews, and architecture discussions.
What Does the Development Environment Look Like?
The company uses Scrum-based product development, with engineers working alongside Product Managers, frontend engineers, research scientists, and other technical specialists.
Because the engineering organization is relatively compact, engineers can take ownership beyond individual implementation tasks.
You may contribute to:
Technical architecture
Feature design
Backend implementation
Database design
API design
Code reviews
Architecture discussions
System quality improvements
Development process improvements
The company also encourages engineers to share technical knowledge through activities such as Tech Talks, documentation, and internal study sessions.
That makes this less suitable for someone who simply wants requirements handed to them and prefers to code independently.
It is better suited to someone who wants to participate in how the system should be built, not only implement what has already been decided.
What Kind of Backend Engineer Are They Looking For?
The core requirement is at least three years of backend development experience using:
Python
Golang
or TypeScript
You should also have experience with areas such as:
Cloud-based web services
AWS or similar cloud platforms
API or microservice development
SQL databases
Database management
Code reviews
Technical design discussions
Working collaboratively within an engineering team
Experience with Docker, Kubernetes, enterprise SaaS, agile product development, OSS, DDD, or Clean Architecture would be an advantage.
However, the overall engineering mindset matters as well.
The company is looking for engineers who are curious about new technologies and willing to continuously improve both the product and the engineering organization.
This Role Could Be a Good Fit If You...
You may particularly enjoy this position if you:
Want to build AI-powered products without becoming an ML researcher
Enjoy backend architecture and system design
Want more ownership over technical decisions
Prefer product engineering over project-based development
Want to work closely with AI and research teams
Enjoy solving complex enterprise problems
Care about code quality rather than simply shipping features
Want exposure to both platform and application development
Enjoy working in an international engineering organization
Want to see the software you build used in real business operations
Do You Need Accounting Experience?
Not necessarily.
Accounting domain knowledge can certainly become valuable, particularly within the application teams, but it is not listed as a core requirement for the role.
You are more likely to need strong backend fundamentals and the willingness to learn the business domain.
In fact, this can be part of the appeal of the position.
You can apply your existing backend engineering experience while developing expertise in a highly specialized area involving enterprise SaaS, fintech/accounting workflows, and AI automation.
What Japanese and English Level Do You Need?
The role requires you to be able to participate in basic workplace communication and meetings in both Japanese and English.
The engineering organization includes members from a variety of international backgrounds, making it more globally oriented than many traditional Japanese enterprise software environments.
At the same time, because the product serves Japanese enterprise customers and deals with Japanese accounting workflows, some ability to communicate in Japanese remains important.
You therefore do not necessarily need to be a native Japanese speaker, but you should be comfortable communicating with colleagues in both languages.
What Is the Company Culture Like?
The organization is relatively flat and collaborative.
Its engineering team includes people from a range of national and professional backgrounds, with many employees having joined mid-career.
The company puts particular emphasis on:
Finding ways to make difficult things possible
Building trust with colleagues and customers
Working collaboratively
Bringing energy and ownership to your work
Moving quickly and continuously improving
For engineers, that translates into an environment where you are expected to contribute ideas, challenge decisions constructively, share knowledge, and take ownership.
Salary and Working Conditions
The expected annual salary range is:
¥7 million – ¥12 million
Final compensation depends on your experience, technical ability, and current salary.
The position is primarily office-based, so this is an important consideration if you are specifically looking for a fully remote engineering role.
Standard working hours are 9:30–18:30.
Why This Position Is Interesting
There are plenty of companies currently describing themselves as "AI companies."
The more interesting question for engineers is:
What role does AI actually play in the product?
At this company, AI is being incorporated into workflows that major companies use to run their accounting operations.
That creates engineering problems extending far beyond simply calling an LLM API.
You need architecture that scales.
You need secure enterprise integrations.
You need reliable APIs and databases.
You need complex business logic.
And you need to turn uncertain AI outputs into predictable software workflows that customers can actually depend on.
For a backend engineer, that combination of AI + enterprise SaaS + platform engineering + complex domain logic can provide a particularly interesting technical environment.
It is also a role where you can choose whether you want to move closer toward foundational platform engineering or deeper into product and domain development.
And because the engineering teams remain relatively small, you can have meaningful influence over how those systems are designed and built.
Quick Position Overview
| Position | Backend Engineer |
| Company Type | Japanese AI accounting SaaS company |
| Product Area | AI-powered enterprise accounting software |
| Salary | ¥7M–¥12M |
| Location | Minato-ku, Tokyo |
| Work Style | Primarily office-based |
| Core Languages | Python / Golang / TypeScript |
| Experience | 3+ years backend development |
| Cloud | AWS or equivalent experience |
| Architecture | APIs, microservices, databases |
| Japanese | Working communication required |
| English | Working communication required |
| AI Experience | Not mandatory |
| Key Areas | AI integration, enterprise SaaS, platform development, accounting workflows |
