Principal Engineer, Engineering Core Services

ForeFlight•Austin, TX

1d•$208,000 - $244,000•Hybrid

About The Position

Jeppesen ForeFlight is hiring a Principal Engineer to set technical direction across Engineering Core Services, a portfolio of shared platform capabilities used by its product organizations, including customer identity (CIAM), commerce, and other shared services. The role owns the long-term architecture and consolidation of customer identity, commerce, customer operations, and entitlement capabilities into a unified multi-product platform, where shared customer and account models support authentication, billing, entitlement decisions, and customer support. This is an individual contributor role with architecture ownership across the Core Services portfolio, responsibility for setting the technical bar for senior engineers, and influence across the broader engineering organization through architectural reviews and RFCs. The preferred work arrangement is hybrid in Austin, Houston, or Denver; virtual candidates may be considered. The Principal Engineer will establish the portfolio architecture and a two-to-three-year roadmap, lead shared identity and subscription/billing platform strategies, and set integration, privacy, security, and regulatory standards. The role involves direct collaboration with senior product, engineering, security, finance, legal, and customer-facing leaders, as well as engagement with major enterprise customers and partners on cross-product architecture questions. In the first year, success includes operating a modern shared identity foundation across product lines, establishing a long-term subscription and billing strategy with initial migrations underway, and creating Core Services patterns and architectural practices adopted by product engineering teams. The role is also expected to become a trusted technical voice for senior stakeholders on shared platform questions.

Requirements

12+ years of engineering experience, including at least 7 years as primary architect for a portfolio of shared services spanning multiple product organizations or business lines.
Track record architecting identity, commerce, entitlement, and customer operations around shared customer and account models as one platform at a multi-product company.
Deep production experience architecting and operating a CIAM platform at scale, with expert command of OAuth 2.0, OIDC, SAML 2.0, API security, and federation.
Deep production experience in at least one additional shared platform domain: commerce/billing, customer operations/CRM, or enterprise data integration.
Strong systems-integration judgment across heterogeneous environments and business models, including APIs, eventing, data modeling, and representation of contracts, entitlements, and catalogs across consumer subscriptions, enterprise contracts, per-seat and per-asset licensing, and reseller flows.
Cloud-native architecture experience with AWS, Kubernetes/EKS, service mesh, Terraform, observability, and secrets management, combined with experience operating in legacy enterprise environments such as ERP, SOAP/XML APIs, and longstanding catalogs, or strong evidence of ability to become productive across both.
Cross-functional leadership and comfort working as a peer with senior product, finance, security, legal, and customer-facing leaders, including direct engagement with major enterprise customers and partners on architecture.
Comfort coordinating across a recently combined company with divergent stacks and processes, in-flight unification, and associated organizational complexity.

Nice To Haves

Experience leading a migration from a legacy identity solution to a modern shared platform.
Experience integrating engineering platforms across two or more legacy stacks after an M&A.
Hands-on experience with commerce and subscription platforms such as Stripe Billing, Recurly, Zuora, or similar, in addition to homegrown commerce systems.
Experience taking a Platform Services organization from disconnected services to a coherent platform with shared standards and adoption across product teams.
Experience supporting subscription and billing platforms through audit readiness, financial-controls maturity, and revenue-recognition requirements.
Experience in aviation, regulated industries, or other domains with mission-critical customers and complex contract structures.
Privacy and regulatory experience with GDPR, SOC 2, aviation-relevant frameworks, and financial-controls frameworks relevant to subscription and billing platforms.
Background in security engineering or DevSecOps, with strong instincts for threat modeling authentication systems.
Experience contributing to or evaluating identity standards, such as IETF or OpenID Foundation standards.
Auth0 experience; other relevant major platforms include Okta CI, Entra ID, Ping, and ForgeRock.

Responsibilities

Own the architecture, two-to-three-year roadmap, and decision authority across the Engineering Core Services portfolio, including the platform-versus-product boundary.
Own CIAM platform architecture and consolidation onto a modern shared identity foundation across product lines, covering authentication, authorization, federation, and account lifecycle.
Lead the long-term subscription and billing platform strategy, including build-versus-buy-versus-hybrid evaluation and migration of legacy capabilities to modern shared platforms.
Drive simplification and standardization of contract, entitlement, and catalog models across product lines.
Define integration patterns and platform standards for product engineering teams consuming Core Services.
Mentor senior engineers, influence the broader engineering organization, and represent Engineering Core Services in forums with senior product, security, finance, and customer-facing leadership.
Engage directly with stakeholders on architecture questions that cross product boundaries.
Set the privacy, security, and regulatory posture for shared platform services, with particular ownership of identity compliance.
Establish Core Services patterns, standards, and architectural practices and support their adoption by product engineering teams.