英文しかない場合： 本ポジションは日本語JDの用意がありません。
Software Engineer (Site Reliability) - Mercari Crossborder
- Employment Status: Full-time
- Work Hours: Full Flextime (no core time)
For more details, see the Overview of Our Positions section on our Careers site.
About Mercari
Circulate all forms of value to unleash the potential in all people
"What can I do to help society thrive with the finite resources we have?" The Mercari marketplace app was born in 2013 out of this thought by our founder Shintaro Yamada as he traveled the world. We believe that by circulating all forms of value, not just physical things and money, we can create opportunities for anyone to realize their dreams and contribute to society and the people around them. Mercari aims to use technology to connect people all over the world and create a world where anyone can unleash their potential. For more information about Mercari Group’s mission, see Mercari’s Culture Doc
Organization/Team Mission
Mercari Engineering Principles
Mercari Engineering Principles are a shared understanding that serves as the foundation of engineering beliefs and behavior at Mercari. The Engineering Principles are designed to complement the organizational identity (Mercari’s mission, values, and culture) from an engineering viewpoint.
These principles ultimately help us achieve Mercari’s mission by defining the ideal state we seek to realize in the long term.
- Passion For The Product
- Grow Together
- Solve Through Mechanisms
- Collaborate Openly
For more details, please see the following link:
Mercari has operated localised marketplaces in Japan and the United States for years. We, the Cross Border team, recently launched a new global app — already live in Hong Kong, Taiwan, and the United States — with the ambition to expand into over 100 countries in the coming years. Behind that expansion is a single engineering goal: build a global app platform that lets existing and future product services run consistently across every region, without the fragmentation (see more on our tech blog) that comes from excessive localisation.
The cross-border nature of the business means reliability is never a purely technical problem. You will work alongside product engineers, operations teams, and third-party logistics and vendor partners to ensure the platform holds up under the real-world pressures of multi-region, multi-currency, and multi-regulatory commerce. Speed and stability are both requirements — the team is expected to make deliberate trade-offs and move forward with a clear long-term foundation in mind.
See here for more information about our mission and values.
Work Responsibilities
You will be joining the SRE & Enabling team for the global app platform — responsible for two equally important things: keeping the platform stable as the business grows across more regions and more products, and enabling every engineer on the platform to develop, ship, and operate software faster and more safely. A separate platform engineering team builds the underlying foundation; this team is its reliability and developer-experience counterpart.
In practice, you will own both the operational side — observability, incident response, on-call, SLOs — and the enabling side: the CI/CD pipelines, developer tooling, onboarding experience, and AI-powered workflows/automation that reduce friction for engineers building on the platform. The two are closely connected: better tooling means faster delivery with fewer incidents; better observability means engineers can debug their own services without waiting for SRE. Candidates who thrive here care about both dimensions equally, are self-directing, and are motivated by making an entire engineering organisation more effective.
- Platform Reliability
- Own the SRE function for the global app platform as it expands into new regions — defining SLIs/SLOs, leading production readiness reviews, and ensuring reliability is built in from design through to launch.
- Operate the platform reliably across multiple time zones: roll out and run services with each region’s traffic patterns in mind to meet the reliability requirements of a global, always-on service.
- Scale databases and infrastructure as the user base grows, and evolve the architecture from today’s single-region setup toward a multi-region configuration.
- Track and improve reliability metrics (change fail rate, incident frequency, time to detect and resolve) to guide trade-off decisions between delivery speed and platform stability.
- Observability & Incident Management
- Build and own the observability stack — metrics, distributed tracing, structured logging — and continuously improve production debugging so on-call engineers can resolve issues independently at any hour.
- Lead incident response: rapid detection, mitigation, resolution, and blameless post-mortems; participate in on-call rotation with a long-term goal of reducing alert volume through AI-assisted automation.
- Developer Enabling
- Own the developer-facing side of the platform: CI/CD pipelines, deployment tooling, development environments, and the systems that determine how fast and safely engineers can go from code to production.
- Lift the productivity and development experience of every engineer building the global app so the team can ship a global product more efficiently, increasingly by leveraging AI to accelerate the entire development workflow.
- Identify and eliminate friction in the engineering workflow — through automation, self-service tooling, AI-assisted workflows, and platform improvements — so engineers spend more time building and less time waiting or debugging.
- Cross-functional Collaboration
- Partner with platform engineering, product engineering, and operations to bridge the gap between infrastructure health and product-level reliability — working across time zones with teams in Japan, APAC, and beyond.
- Collaborate with operations teams and third-party vendor partners on reliability requirements that extend into logistics and external integrations; share learnings across engineering teams to raise the collective bar.
Unique Challenges
- Global scale: you are building the reliability foundation for a platform targeting 100+ countries, where a single time zone no longer bounds the problem.
- Multi-region evolution: growing the user base means scaling data and infrastructure and moving from today’s single-region service toward a globally distributed, multi-region architecture.
- SRE meets enabling: you will directly shape how the entire engineering team develops, ships, and operates software.
- AI-native approach: working at the frontline of AI-driven development velocity and the operational strengthening it demands — you will help shape the SRE culture that emerges as engineers and autonomous agents share the work.
- Business context: you will work directly with product, engineering, operations, and business stakeholders across regions, connecting reliability engineering to real commercial outcomes, not just uptime numbers.
Qualifications
- Required Experience/Skills
- Hands-on experience operating production services on cloud infrastructure, particularly GCP and Kubernetes.
- Experience defining reliability indicators such as SLIs/SLOs and continuously improving service reliability based on them, including on-call rotations and blameless post-mortem processes.
- Operational experience with databases and a solid understanding of database fundamentals.
- Hands-on experience applying AI/LLMs to improve engineering productivity, and/or experience building and providing tooling to developers.
- A proactive mindset toward incident response and troubleshooting, and a willingness to embed directly into product teams when the service requires it — improving reliability at the product level, not only the infrastructure level.
- Demonstrated experience learning from incidents and working cross-functionally to design and implement preventive measures and automation.
- Foundational knowledge of web services architecture.
- Preferred Experience/Skills
- Experience setting SLIs/SLOs not only within engineering but by communicating and aligning with business and product leaders.
- Experience in product development within a team environment.
- Experience developing AI agents.
- Language
- Japanese: Independent (CEFR – C1)
- OR English: Independent (CEFR – C1)
For details about CEFR, see here.
Learn More About Mercari Group
Recruiting at Mercari
At Mercari Group, we value empathizing with and embodying the mission and values of the Group and each company. To promote the creation of an organization that maximizes the total amount of value exhibited by all members, we would like to understand the experience and skills of each candidate as accurately as possible.
Recruiting cycle at Mercari Group
- Application screening
- Skill assessment: For engineering positions, you will be asked to complete a skill assessment on HackerRank or GitHub. For non-engineering positions, you may be asked to complete an assessment depending on the position. (The timing of the assessment may coincide with the interview process.)
- Interview: The number of interviews may vary depending on the position.
- Reference check: We will ask for online references around the timing of the final interview.
- Offer: Offers will be determined carefully in consideration of the final interview and the reference check.
Learn more about our recruiting process here.
Equal Opportunity Hiring
Here at Mercari, we work to realize a world in which no one’s potential is limited by their background and everyone has the opportunity to freely create value. We also firmly believe that a mindset of Inclusion & Diversity is essential for us to achieve our mission.
This, of course, extends to our hiring practices as well. Mercari is committed to eliminating discrimination based on age, gender, sexual orientation, race, religion, physical disability, and other such factors so that anyone who shares our mission and values can join us, regardless of their background. For more details, please read our I&D statement.
Please read and acknowledge our Privacy Policy prior to submitting your application.