A complete application in a minute
Tailored resume and cover letter, ready to send.
Prudential Japan seeks a Senior Software Engineer, Backend and Platform, to design, build, and operate digital products supporting customer journeys, policy administration, and business workflows across insurance value streams.
You will work in a product engineering organization, shaping engineering practices and standards while solving complex backend challenges across data models and integrations with external systems.
The Senior Software Engineer, Backend and Platform will help build Prudential Japan's next generation Product Engineering capabilities as part of the Japan Technology Transformation initiative.
This role is responsible for designing, building, and operating digital products and platforms that support customer journeys, sales journeys, policy administration experiences, and business workflows across Prudential Japan's end-to-end journey of life insurance value streams.
As part of a newly established Product Engineering organization, this role offers the opportunity not only to build products, but also to help establish engineering practices, standards, and ways of working that will shape the future of technology delivery at Prudential Japan.
We allocate after offer, across multiple domains. Policy administration, where contract truth must survive multiple years and a change to old insurance product must never silently break tens of thousands of live contracts. Customer communications, where essential customer communications reach every customer in one immovable window. CRM, where customer and agent information and interactions are managed consistently across products and channels.
New business and policy issuance, where an application must move accurately from initial submission through underwriting and approval to a legally effective insurance contract.
Integration, where the industry wide used services, banking and government systems meet our systems. And the compliance records, which are essential to maintain as an insurer.
Design, build and continuously improve backend services and data models for systems of record, where a change can alter an obligation the company owes a customer rather than only an applicationʼs behavior.
Create, maintain and enhance software capabilities and functionality across modern technology stacks, integrations and the full software lifecycle.
Own integrations with external parties you do not control, including government and banking systems, shared industry data services and print and delivery vendors.
Build and operate scheduled and batch processing that must finish inside a fixed window, including month end and year end cycles.
Build and extend the audit and evidence layer: what was shown, agreed, triggered and paid, retrievable for years.
Work closely with systems engineers, architects and business partners to ensure the quality and reliability of the product, and to deliver on business objectives.
Work alongside long-lived legacy systems and decide, case by case, what to wrap, what to replace and what to leave alone.
Engage with broader product considerations and planning across ideation, design, development, testing, business engagement and team leadership.
Carry on-call for what you own, and run incident reviews that look for causes rather than for someone to blame.
You do not need insurance experience. We will teach the domain.
Five or more years building and operating backend systems in production, including ownership of something that mattered when it broke.
Strong data modelling, especially temporal and bitemporal data modelling.
Transactional integrity, idempotency and reconciliation as daily practice rather than interview vocabulary.
Integrating with external organizations where the interface is theirs and will not change for you.
Real-time as well as batch processing at scale, with a working understanding of time windows and dependency chains.
Any high consequence or regulated domain is an advantage: payments, healthcare, logistics, energy, safety-critical systems.
Degree in relevant field or equivalent practical experience.
We run on AWS. We are not dogmatic about languages or frameworks and we do not screen on keyword matches: we care that you have gone deep in at least one stack and can pick up another. Depth in one column beats a shallow tick in all of them.
AI assisted development: Claude, Codex, Copilot or Cursor. Knowing how to build Agent skills is an advantage.
Java or Kotlin, Go, Python or TypeScript on Node.
PostgreSQL or Aurora as the default. Experience with schema evolution on live data matters more than any particular engine.
Integration: REST and event-driven patterns, plus the older shapes you will meet at the boundary, including scheduled file exchange and message queues.
Infrastructure as code and CI/CD: Terraform or CDK or Ansible, with pipelines you have owned rather than inherited.
Observability: Structured logging, metrics and tracing. CloudWatch, OpenTelemetry, Dynatrace, or Datadog
Nice to have: Kafka or Kinesis, and any experience bridging a mainframe or vendor package to modern services.
English: Fluent to Native
Japanese: Working level. JLPT N2 or native is an advantage.