Principal Software Engineer (Location Services)
Principal Software Engineer (Location Services)
Posted 37 days ago
SENIORITY
Lead
About the role
- Technical Leadership & Architecture
- Own and evolve the architecture of core Location Services and geospatial capabilities
- Lead system design for highly scalable, low‐latency, and highly available location‐based services
- Define standards and best practices for geospatial data modeling, querying, and processing
- Evaluate and introduce new technologies, patterns, and frameworks where they provide material benefit
- Platform Ownership & Delivery
- Serve as technical owner for critical geospatial components and services
- Guide teams through complex technical initiatives spanning multiple services or domains
- Ensure solutions meet requirements for performance, accuracy, reliability, and security
- Actively influence roadmap direction through technical insight and risk assessment
- Cross‐Team Influence
- Partner with product, data, and infrastructure teams to align technical direction with business goals
- Provide technical insights to multiple engineering teams consuming Location Services
- Resolve cross‐cutting technical issues and reduce architectural fragmentation
- Operational Excellence
- Drive improvements in observability, resilience, and fault tolerance for geospatial systems
- Lead root‐cause analysis for significant production issues and ensure long‐term corrective action
- Champion automation, testing strategies, and reliability engineering practices
- Mentorship & Engineering Culture
- Mentor senior and mid‐level engineers, strengthening overall technical capability
- Set a high bar for engineering rigor, system design quality, and documentation
- Act as a role model for pragmatic decision‐making and long‐term systems thinking
- 10+ years of professional software engineering experience, with demonstrated senior technical leadership
- Deep experience designing and operating large‐scale distributed systems
- Strong expertise in geospatial concepts, such as: Spatial data models and indexing
- Geospatial queries, transformations, and projections
- Location accuracy, precision, and data quality considerations
- Proficiency in one or more backend programming languages (e.g., Java, C++, Python)
- Experience building and operating cloud‐native services (e.g., GCP, AWS, or Azure)
- Strong understanding of data storage technologies (relational, NoSQL, time‐series, or geospatial databases)
- Proven ability to influence technical direction across teams without direct authority
- Excellent communication skills, with the ability to articulate complex technical trade‐offs to diverse audiences
- Prior ownership of location‐based or geospatial platforms in production environments
- Experience with real‐time or near‐real‐time location processing pipelines
- Familiarity with geospatial tooling and standards
- Experience with containerization and orchestration (Docker, Kubernetes)
- Background in reliability engineering, performance tuning, and scalability testing
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
