[full remote ok/flat hierarchy] Backend Software Engineer | Distributed Systems | (Japan) | Java / Go

If you enjoy building reliable backend systems that operate under real production load, this opportunity puts you at the center of a high-traffic consumer platform used by millions across Japan.
We’re looking for a Backend Software Engineer to help evolve a large-scale, in-house platform where architectural decisions, system performance, and long-term maintainability are taken seriously.
This is a hands-on engineering role with meaningful ownership and direct product influence.
What You’ll Be Responsible For

• Architecting and implementing backend services in Java or Go
• Delivering features end-to-end — from technical design to deployment
• Strengthening system reliability, scalability, and operational visibility
• Optimizing data flows across relational and NoSQL databases
• Participating in system design reviews and technical roadmap discussions
• Continuously improving platform health and reducing structural complexity

What You’ll Need

• 3–5+ years of backend development experience in production systems
• Strong experience with Java, Go, Kotlin
• Experience designing APIs and working with both SQL and NoSQL databases
• Understanding of distributed systems and performance optimization
• Collaborative mindset and comfort working in agile teams
• Business level Japanese (intermediate or more) and English

Preferred Experience

• Microservices-based architectures
• Spring ecosystem, gRPC, or GraphQL
• CI/CD pipelines and cloud-native development
• Experience contributing to system refactoring or modernization efforts

Why Engineers Join

• Fully remote-friendly team within Japan
• Exposure to high-throughput, production-grade systems
• Balance of stability and speed — established product with active evolution
• Real technical ownership and influence over architectural direction
• Opportunity to deepen expertise in large-scale backend engineering

If you’re looking for a backend role where scale, engineering quality, and long-term system design truly matter — this is worth exploring.