Senior Software Engineer, Shared Platform Services

About The Team

We build and run the shared platform services that the rest of JLL's technology organisation is built on: identity and access management, document storage, managed event streaming, etc. These are multi-tenant services, consumed by teams right across JLL and all around the world. Because so much of the firm's technology is built on top of them, reliability, security and careful change management sit at the centre of how we work.

The team is small and distributed, with members in APAC and the Americas. This role is based in Tel Aviv and collaborates across those regions daily, which calls for strong written communication, structured handovers and a high degree of independence.

About The Role

This is a senior individual contributor role with breadth across several of our platform services rather than ownership of a single codebase. You will take technical ownership of the services you work on, from design and implementation through to their behaviour in production, and you will have real influence over the architectural decisions that determine how they evolve as more of the firm comes to depend on them.

Enablement is a substantial part of the role. Shared services only create value once other teams are running on them successfully, so you will work directly with consuming teams to understand their requirements, shape the integration and support them into production, while continuously improving the platform so that each subsequent team needs less of your involvement than the last.

The breadth is intentional. The role spans backend services, administrative interfaces, identity and access design, storage, event streaming and the infrastructure underneath them, and you will decide for yourself where your effort is best spent.

What You'll Do

Design and build JLL's Shared Services

• Own what you build end to end: requirements from multiple stakeholders, design, implementation, and how it behaves once it is live
• Scale the services this team owns, which applications and people right across JLL rely on every day
• Design APIs that many applications call at once, where correctness, latency and backwards compatibility all have to hold together
• Tackle the harder problems: storage that spans multiple clouds, change-data-capture into our enterprise data platform, bulk operations at scale
  
  

• Be the senior technical counterpart for teams integrating with us, from the first conversation to their first weeks live
• Design the provisioning model behind an integration: service accounts, storage configuration, permissions, roles, directory groups
• Keep the documentation and runbooks worth trusting, including secret and certificate rotation
• Build the self-service tooling that means teams stop needing to ask
• Go looking for the manual work that quietly eats the team's week, and engineer it out of existence
  
  

• Be accountable for availability, performance and security, not merely present on the on-call rotation
• Take incidents to root cause and fix the cause, not the symptom
• Raise the bar on observability, alerting and hardening before the next incident forces it
• Keep the services secure and audit-ready, from vulnerability remediation to compliance evidence
  
  

• 5+ years building and operating production backend services, with deep expertise in at least one modern backend language and ecosystem
• Hands-on experience with at least one major public cloud, to a depth that includes running and debugging production workloads on it
• Practical experience with both relational and non-relational databases under high production traffic
• Experience with event-driven architecture
• Demonstrable ownership of services in production: on-call, incident response, root cause analysis
• Excellent English communication, written and spoken
  
  

• Experience building or operating a shared, multi-tenant internal platform
• Container orchestration and container-based deployment pipelines
• Infrastructure as code
• Modern front-end work, particularly for internal admin and self-service tooling
• Observability tooling and the discipline of alerting that people actually trust
• Exposure to audit and compliance requirements in an enterprise environment
  
  

• A distributed team with limited timezone overlap, and the asynchronous habits that requires
• High test coverage expectations on changed code
• Being interrupted by production and by other teams, and still shipping
• Small team, broad surface area, direct ownership