Principal Software Engineer

Company: Pearson

Location: United States

Salary: $150K – $170K a year

Work arrangement: On-site

Employment type: Full-time

Experience: 10+ years

Education: bachelor degree

Posted: 2026-11-03

Responsibilities

You will lead the modernization of the content platform by designing target systems and managing large-scale migrations of content and data. Additionally, you will establish shared technical standards, mentor engineers, and act as the primary technical point of contact for critical system incidents.

Requirements

Candidates must have 12+ years of experience in software engineering, including at least 4 years at a staff or principal level. Proficiency in the full-stack core of Java, Spring Boot, Node.js, TypeScript, and React, along with extensive AWS experience, is required.

Skills

  • Java
  • Spring Boot
  • Node.js
  • TypeScript
  • React
  • AWS
  • System design
  • Cloud infrastructure
  • Software architecture
  • API development
  • Technical leadership
  • Mentoring
  • Terraform
  • CI/CD
  • Observability
  • Data migration

Benefits

  • Annual incentive program
  • Health insurance
  • Retirement benefits

About this role

We are modernizing Pearson's content platform into a set of shared platform
services. You will be one of the principal engineers leading that work hands-on.
You design the target systems and move content and users onto them safely. Full
stack here goes beyond front end and back end: the work spans user interfaces,
workflow orchestration, AI, backend services, and cloud infrastructure. You will
stay deep in design and implementation while raising the technical judgment and
execution of the engineers around you.

What you will own

* The technical plan and delivery for several technology tracks, such as
consolidations, migrations, and other large-scale initiatives, from target
design through launch.

* Migrations of large volumes of content and data, such as assessment items or
media assets, with verification that nothing is lost or broken for downstream
products.

* Shared capabilities that should be built once and used everywhere, like media
handling, search, rendering, or AI content services, exposed through clean
APIs.

* An honest, costed view of the technical debt in your systems and what to fix
first.

* Escalated incidents on your systems: you are the technical point of contact
when one has business impact, and you stay on it through root cause and the
fix that prevents a repeat.

* Security and stability for the applications you own. That covers runtime and
framework upgrades, vulnerability and penetration test remediation, secure
data handling, and disaster recovery plans that are documented, exercised,
and audit ready.

* Shared standards across teams for design patterns, tooling, reliability,
observability, performance, and evaluation, including how AI-powered
workflows are measured, tested, and kept safe.

* The long-term technical roadmap for your area, and the subject-matter
expertise that comes with it.

How you will work

This is a hands-on engineering role, not an architecture role. You will not be
embedded in a single team; you will work across the platform on initiatives and
technical problems that matter most to leadership. You own the designs, the code
on the critical path, and the engineering calls that decide whether an
initiative succeeds. You should enjoy defining the problem as much as solving
it.

* Write production code where the risk is highest and review the hardest
changes from other engineers.

* Unblock hard technical problems that span systems, teams, or domains.

* Work with engineering managers, product managers, architects, and quality
engineering. When long-term initiatives and current delivery compete for the
same people or code, make the tradeoff visible and help decide it.

* Work directly with the people who use the platform across Pearson's lines of
business, and separate the foundational problems from the incremental ones
before the team commits.

* Spot opportunities that cut across team and product boundaries, bring
stakeholders to a shared direction, and carry the work from exploration
through launch and iteration.

* Make high-consequence technical decisions under ambiguity, balancing speed
and learning against scalability, simplicity, and long-term maintainability.
Hold views grounded in evidence, and change them when the evidence changes.

* Evaluate frameworks, tools, and vendors, and pilot practices like contract
testing, automated regression, and zero-downtime migration before teams adopt
them.

* Run technical feasibility reviews for new AI capabilities, and work with
internal teams and external partners to assess and co-develop them.

* Use AI coding tools daily, particularly for large upgrades and refactors, and
help teams adopt them with sound review habits.

* Act as a technical multiplier: review critical designs, mentor engineers, and
improve engineering practices. Success includes the senior engineers around
you becoming owners of these systems too.

Minimum qualifications

* 12+ years building and operating production software, including 4+ years at
staff or principal level, or as technical lead across several teams or a
large multi-service system.

* Led a re-platforming or legacy migration of a production system with active
users and data, through to switching off the old system.

* Led the design and delivery of technically complex, user-facing systems.

* Upgraded or migrated production systems off an end-of-life runtime or
framework.

* Full-stack depth in our core stack: Java and Spring Boot, Node.js and
TypeScript, and React, with MongoDB and event-driven services (SQS, SNS,
Kafka) behind APIs with many consumers.

* Production experience on AWS, especially ECS Fargate, Lambda, S3, and API
Gateway, with observability (New Relic, CloudWatch), CI/CD (GitHub Actions),
and infrastructure as code (Terraform).

* Writes clear design documents and migration plans, explains tradeoffs to
engineering, product, and executive audiences, and influences without
authority, especially when the decision carries real uncertainty. We will ask
you to walk us through a document you wrote.

* Bachelor's degree in Computer Science or an equivalent combination of
education and experience.

Preferred qualifications

* Content platform experience: authoring and content management, digital asset
management, content transformation pipelines, content delivery, or assessment
systems.

* Content and learning standards such as EPUB, XML/XSLT, QTI, or LTI.

* Built or operated an LLM-backed feature in production, using Python and
services such as AWS Bedrock or Azure OpenAI, and understands the problems AI
brings: nondeterminism, evaluation, latency, and safety.

* Moved a product off a commercial platform, such as a DAM or CMS, onto
in-house services.

* Search and caching with OpenSearch or Solr and Redis.

* Worked with distributed teams and delivery partners across US and India t...

About Pearson

Education · 10,001+ employees · headquartered in London

See all my matches — 2 min, free

More Software Engineer Jobs

316 new Software Engineer jobs were posted this week in United States.

All Remote Software Engineer Jobs →

Get new Software Engineer jobs by email — start free

Before you apply, check your resume against ATS filters for free.