Responsibilities

The product platform is the layer other product teams build on. Today that means identity and access, including customer SSO, invitations, and sessions; the organization and tenancy model; the shared services, APIs, and schemas that carry customer data between products; and the developer experience, including the tooling and agent workflows engineers use to ship. The scope grows whenever product teams need a capability that should be built once. Role-based access control, email infrastructure, the production path for the models our products depend on, and likely data ingress are next in line. When this layer is right, product teams move faster and customers have a better experience.
This is a high-ownership, high-autonomy role on a team that is still defining itself. You'll have a direct say in how the platform, and the team, approach hard problems. We are still working out architecture, ownership boundaries, and integration patterns, so the right person operates without a playbook and brings strong technical judgment to ambiguous problems. You'll be a hands-on technical leader. You'll write production code, lead design reviews, and set the standards other engineers build to. The systems you own will be ones multiple teams depend on, and the engineers around you will get better and faster because you are there. Expect us to ask about a system you built: who used it, why they cared, and what you would have built differently had you understood that sooner.
Own the technical direction of the platform: Drive architectural decisions across identity and access, tenancy, shared services, developer experience, and each new platform area the company takes on. Set the standards the rest of the team builds to, and make ownership boundaries explicit where they are still fuzzy.
Stay hands-on: Write production code, lead design reviews, and take end-to-end ownership of the systems you drive, especially the ones multiple teams depend on.
Design for extension and reuse: Build composable abstractions and well-defined interfaces so product teams can extend the platform without forking it or waiting on you.
Design scalable, reliable system interactions: Make the architectural calls on system interactions and data flows that balance scalability, reliability, security, and performance as the platform evolves.
Translate ambiguity into executable plans: Partner with product and engineering leadership to turn loosely defined requirements into clear, well-scoped work with understood trade-offs.
Raise the engineering bar: Establish patterns and practices, through code, reviews, and direct collaboration, that improve quality, reliability, and maintainability across product teams, including how engineers use AI tooling well.
Mentor and grow engineers: Be a technical resource and thought partner for senior and mid-level engineers on the team and on the product teams you work with.

Staff Software Engineer (Platform Engineering) at Pivotal Health · LumiJobs

Staff Software Engineer (Platform Engineering)

Responsibilities

Qualification

Required

Benefits

Company

Pivotal Health

More roles at Pivotal Health