Software Engineer

About OpenSesame

OpenSesame is the trusted partner for Workforce Reinvention in the age of AI. OpenSesame delivers integrated software, curated and customizable content, and expert services – embedded into existing learning, HR, and work systems – to help organizations expand their human+AI potential and thrive through change.

Learn more: www.opensesame.com/about

About the Team

The Core engineering team is a platform enablement team responsible for OpenSesame’s identity management and commerce domains. We build and maintain shared services that support product engineering teams across the company.

We operate in an agile, continuously improving, automation-oriented environment. We regularly inspect how we work, identify what’s slowing us down, and make deliberate changes to improve quality, reliability, and delivery.

About the Job

As a Software Engineer I on the Core team, you will design, build, and maintain production software for shared platform services in the domains we own. This role is for an engineer who is past entry level and ready to take ownership of well-defined work while continuing to grow technical judgment, system understanding, and independence.

You will work across a modern tech stack including TypeScript, Node.js, GitHub Actions, Terraform, AWS, SQL, and identity technologies such as SAML and OIDC. Experience with SSO platforms is a plus; we use Okta. You will also work in and around legacy systems and are expected to approach complex systems with curiosity and care.

You are expected to make meaningful contributions with increasing autonomy, take ownership of assigned work, and participate fully in team practices such as pairing, code reviews, on-call, and releases. You will continue learning by shipping real features, improving existing systems, and steadily expanding the scope of problems you can solve.

Performance Objectives

In your first 3 months:

Summary: Become an effective contributor by learning the Core team’s codebase, development practices, and operational expectations.

Team Collaboration: Build working relationships through pairing and teaming. Participate actively in standups, planning, retrospectives, and other required team meetings.

Code Contributions: Contribute small, well-scoped changes to Core services and tooling, following team standards.

Development Practices: Participate in code reviews and write appropriate unit tests and smoke tests for your changes.

System Familiarity: Develop a working mental model of at least one Core domain or service and how it fits into the broader platform.

Within 6 months:

Summary: Become an independent and reliable contributor, owning meaningful work and operational responsibilities.

Ownership: Own well-defined user stories or technical tasks from design through deployment with minimal oversight.

Codebase Proficiency: Confidently modify and maintain your team’s primary codebases. Begin developing a clear area of focus within Core.

Operational Readiness: Pa