Onejay
Software engineer based in Japan. I have been working in the industry since 2018, building practical and maintainable services across backend development, cloud operations, and developer workflows.
- GitHub: jay2u8809
- Blog Archive: Onejay Lab
- Location: Japan
- Languages: Korean, Japanese, English
Profile
I currently work on a mobile app service in the location-based services domain. My main responsibilities include backend development with NestJS in a serverless architecture, as well as cloud operations across AWS and GCP.
Since starting my career in 2018, I have focused on building production-ready systems rather than prototypes. I value clear architecture, operational stability, and maintainable code that supports long-term product growth.
I am especially interested in:
- Building reliable backend systems for real services
- Designing maintainable serverless architectures
- Improving engineering productivity with better tooling and documentation
- Operating cloud infrastructure in multilingual and cross-functional environments
Experience Highlights
- Working as a backend engineer for a location-based mobile app service
- Building and operating serverless backend services with NestJS
- Managing cloud infrastructure and operations on AWS and GCP
- Using TypeScript, Terraform, and Serverless Framework in day-to-day development
- Organizing technical knowledge and improving developer workflows
Current Role
- Location-based mobile app service
- Backend Engineer
- NestJS serverless backend, AWS/GCP operations
Key Projects
Skills
- Languages: TypeScript, JavaScript, HTML, CSS
- Frontend: React, modern web UI development
- Backend: NestJS, Node.js, API-oriented service development
- Infrastructure: AWS, GCP, Terraform, Serverless Framework
- Documentation: technical writing, multilingual documentation structure
Strengths
- Strong ownership from implementation to operations
- Preference for simple, durable, and production-ready solutions
- Clear technical communication
- Comfortable working across backend, infrastructure, and documentation concerns
If you would like to collaborate or get in touch, please reach out through GitHub: