Senior Software Engineer, Frontend (Web)

Okta•Toronto, ON

2d•Hybrid

About The Position

We are seeking a Senior Software Engineer to build and evolve Okta’s web platform using React and Next.js. In this role, you will bring deep frontend expertise to solve complex engineering problems autonomously from designing scalable page systems and optimizing performance to integrating CMS APIs and refining developer workflows. You work independently on ambiguous problems but thrive in collaboration with designers, content architects, and fellow engineers. AI-assisted development tools are part of how this team works, and you leverage them fluently to move faster while maintaining high standards. This is a hands-on IC role with significant autonomy and real ownership, ideal for an engineer who combines deep technical understanding with strong collaborative instincts.

Requirements

5–8 years of professional frontend or full-stack engineering experience shipping production web applications.
Deep working knowledge of Next.js, including App Router patterns, server/client components, data-fetching strategies, caching, and API routes. You understand the trade-offs between rendering approaches and can choose the right one for a given problem.
Consistently produce high-fidelity, polished UI from Figma comps.
Strong CSS skills including responsive design, Grid, Flexbox, and CSS-in-JS (styled-components, Emotion, or similar).
Experience with animation and interaction patterns using Framer Motion, GSAP, or CSS transitions.
Solid experience connecting Next.js to headless CMS platforms (Contentful, AEM, Sanity, or similar). You understand content models deeply and have built template systems that map structured data to rich frontend experiences.
Fluent with AI-assisted programming tools (Claude Code, Copilot, Cursor). You use them to move faster while critically evaluating output understanding when to trust, when to reject, and how to prompt effectively.
Strong understanding of Core Web Vitals, bundle optimization, and rendering strategy trade-offs.
Solid command of WCAG standards, SEO best practices (structured data, metadata, SSR/ISR), and how to build them into your work from the start rather than bolt them on.
Deep HTML, CSS, and TypeScript fundamentals.
Comfortable with Git workflows and CI/CD pipelines.
You communicate clearly, collaborate well across disciplines, and can work through ambiguity without needing constant direction.

Nice To Haves

Experience with Adobe Experience Manager (AEM) or similar enterprise CMS authoring platforms.
Experience with Three.js, WebGL, or advanced interactive web experiences.
Contributions to design systems or component libraries.

Responsibilities

Build and maintain reusable page templates, features, and component systems in Next.js using TypeScript and React.
Design scalable data-fetching patterns from headless CMS APIs (GraphQL and REST), transforming structured content into polished frontend experiences.
Collaborate on content model design with content architects, ensuring CMS data maps cleanly to frontend templates.
Implement responsive, accessible, high-performance UI following established design system patterns and propose improvements when existing patterns fall short.
Work closely with the design system team to assemble pages and experiences from the internal component library.
Identify gaps where new patterns or variants are needed, articulate requirements clearly, and collaborate on solutions whether that means contributing to the design system directly or building well-scoped custom components when the system doesn’t yet cover a specific need.
Leverage AI-assisted development tools (Claude Code, GitHub Copilot, Cursor) fluently in your daily workflow to accelerate delivery.
Critically evaluate AI-generated output and share effective patterns with teammates.
Help the team develop good habits around AI tooling through collaboration and example, not mandate.
Write thorough unit and integration tests to prevent regressions.
Participate actively in code reviews giving thoughtful, constructive feedback and receiving it openly.
Collaborate across disciplines with content architects, designers, and the design system team to deeply understand content models, component APIs, and how they fit together in page assembly.
Communicate technical trade-offs clearly to non-technical stakeholders.
Take ownership of frontend performance Core Web Vitals, bundle optimization, and rendering strategy choices (SSR/ISR/static).
Investigate and resolve complex production bugs independently.
Contribute to operational improvements like monitoring, documentation, and internal tooling that benefit the broader team.