Software Developer - Front-end Foundations
Jane
- Location
- Canada
- Job Type
- full-time
- Salary
- $95,100 to $142,600
- Posted
- September 21, 2025
Job Description
The Impact You Could Have
- Contribute to core platform work like Module Federation and Burrito (Jane’s design system) through well-scoped tasks with support from the team
- Improve developer experience by maintaining front-end tooling, writing automation scripts, and enhancing CI checks
- Support other developers by answering questions in Slack, participating in office hours, and improving documentation
- Help evolve our frontend systems and standards by giving feedback, implementing patterns, and raising thoughtful questions
- Collaborate closely with design partners to build accessible, reusable components and model good design–engineering handoffs
- Assist with maintaining internal packages and libraries used across Jane’s front-end ecosystem
- Share knowledge via short docs, demos, and pairing sessions
- Explore responsible AI tools to accelerate local workflows and reduce toil
- Contribute to our developer community with curiosity, humility, and a collaborative mindset
- Engage in and embody Jane’s people-centered culture
The Experience We're Looking For
- 2 - 4 years of front-end web development experience,
- Solid proficiency with JavaScript or TypeScript, React, and styling fundamentals
- Some hands-on exposure to platform-adjacent work such as adding a build step, writing a CI config, or publishing/maintaining an npm package
- Demonstrated ability to deliver well-scoped tasks independently, ask good questions, and seek feedback
- Commitment to code quality, testing basics, and maintainable patterns
- Adaptability and growth mindset with a strong desire to learn new tools and domains
Experience That Is Nice-to-have
- Exposure to design systems or microfrontend architectures
- Familiarity with bundlers or build tools such as Webpack, Vite, or Rollup
- Experience authoring or maintaining an npm package
- Comfort with automated testing fundamentals
- Interest in accessibility and inclusive design practices
- Experience collaborating with designers on component implementation
- Notes about the role
- The Frontend Foundation team is a platform team. We build and maintain systems every Jane developer depends on, including Module Federation, Burrito (our design system), and the surrounding tooling and workflows
- L2 engineers contribute to these systems through guided, well-defined work, participate in the on-call rotation with mentorship, and grow responsibility over time
How You'll Be Supported In This Role
- Clear scopes, pairing, and regular feedback from more senior teammates
- Mentorship and opportunities to grow depth in dev tooling, CI/CD, package maintenance, accessibility, and responsible use of AI
- Gradual increases in autonomy, with sensible guardrails
π― Who is this job for?
This role is ideal for a Mid-level front-end developer with 2–4 years of experience. Candidates should be skilled in JavaScript or TypeScript, React, and front-end tooling, and have familiarity with CI/CD, internal packages, and design systems. It's a great fit for someone who thrives in collaborative environments, values clean, scalable code, and is comfortable working on platform-level tools used by other developers.
π¬ Potential Interview Questions
-
How would you structure and govern Module Federation across multiple apps?
Expose only stable, versioned entry points; declareshared
singletons for React/React-DOM with strict semver; enforce a platform lockfile and CI contract tests to prevent breaking changes and duplicate bundles. -
What makes a design-system component (e.g., in Burrito) both accessible and themeable?
Start with semantic HTML and ARIA where needed, keyboard/focus management, and WCAG-compliant contrast. Use design tokens as CSS variables for theming, prefer composition over prop bloat, and keep SSR/hydration safe. -
How do you keep bundles small and avoid duplication in a federated setup?
Tree-shakeable ESM builds,sideEffects:false
, strict import paths (noindex.ts
barrel traps), dynamicimport()
for routes/heavy widgets, and shared vendor deps pinned via federation to avoid multiple copies. -
What’s your approach to publishing/maintaining internal npm packages?
Use Changesets/semantic-release for semver and changelogs, define correctpeerDependencies
, ship ESM + types (and CJS if needed), run pre-publish checks (type/lint/test/size), and add API docs via Storybook/TS docgen. -
How would you design CI checks that improve developer experience without slowing teams down?
Parallelize type/lint/unit/component tests, add bundle-size and a11y budgets, spin up PR previews, and run slower E2E/visual tests on main or nightly; fail fast with actionable messages and cached dependencies. -
How do you implement reliable component tests for platform primitives?
Use React Testing Library with accessible queries, test behavior/state transitions (not implementation details), mock network/time safely, and add Storybook interaction tests for common scenarios. -
How do you integrate microfrontends with routing and auth safely?
Keep an app shell owning router/auth/session; pass capabilities via typed context/adapters; remotes render inside slots and avoid global state. Version contracts and validate at runtime with zod/io-ts. -
How do you approach CSS architecture for a large federated codebase?
Token-driven theming via CSS variables, layered styles (reset → base → components → utilities), scoped styles (CSS Modules/emotion) to prevent leakage, and deterministic class names for stable visual tests. -
What guardrails help maintain accessibility at scale?
Automated checks (axe/Playwright a11y), lint rules for alt/aria, focus-visible and skip-links baked into the shell, and a DS checklist (roles, labels, keyboard paths) required before component publish. -
How can responsible AI tools speed up platform work without risking quality/security?
Use them for scaffolding, docs, and test boilerplate—not for unchecked core logic; never share secrets/proprietary code externally; require human review, run linters/tests, and track suggestions against coding standards.
π Job Summary
Jane is hiring a remote Frontend Software Developer (Canada only) to help evolve its core platform, including design systems and developer tooling. You’ll work with React, TypeScript, and CI/CD to improve frontend architecture, build reusable components, and support the dev community. With salaries ranging from \$95K–\$142K CAD and strong mentorship, Jane offers a people-centered culture, flexible work, and meaningful projects that support healthcare professionals across North America. Join a team that values curiosity, inclusivity, and impact.