{"schemaVersion":"jobsearcher.job.v1","id":"bc9b7315d20aece66cd256db","url":"https://jobsearcher.com/jobs/bc9b7315d20aece66cd256db","canonicalUrl":"https://jobsearcher.com/jobs/bc9b7315d20aece66cd256db","title":"Staff Software Engineer","description":"Role Title: Staff Software Engineer\n\nPearson's PSG-CP (Pearson Software Group - Content Platform) team is looking for a forward deployed engineer who shows up where the work is happening, listens to a problem that nobody has fully written down yet, and leaves with software that addresses it. Not a deck, not a spec, not a Jira epic - running software.\n\nYou sit closer to the customer than a typical engineer and closer to the code than a typical solutions architect. The job is to compress the distance between \"we need something that does X\" and \"here, try this.\"\n\nYou will embed directly with our most strategic internal lines of business to drive AI adoption and ship working software against real problems. You will operate autonomously, thrive under ambiguity, and represent PSG-CP at the highest level inside the business. This is a significant responsibility — you'll play a key role in how AI shows up across Pearson.\n\nWhat you'd actually be doing\n\nGoing where the problem is. You will work directly with the internal stakeholders inside our different lines of business. Through real understanding of their pain points, their workflows, and the architecture of their current technical landscape, you'll design and build systems end to end for them. These are the people who will actually use what you build. You meet them on their ground, in their workflow, with their data.\n\nConducting real discovery. You're not waiting for a finished brief. You sit with users, watch them work, ask the questions, and translate what you hear into something buildable. The discovery is part of the engineering job, not a step that happens before it.\n\nBuilding during the conversation. The first version often exists before the meeting ends. People react to working software very differently than they react to wireframes — your job is to give them something to react to as fast as possible.\n\nWorking from messy inputs. Spreadsheets, PDFs, screenshots, recorded calls, half-written documents, contradictory emails from two stakeholders. You read all of it and turn it into something coherent. You don't ask people to clean up their inputs before you start.\n\nShipping production AI applications. Beyond prototypes, you build real applications on top of frontier LLMs, agents, MCP servers, evaluation harnesses, retrieval systems, custom skills — that run in production against real workflows. You know how to evaluate what you've built, not just demo it.\n\nIterating fast across many engagements. A typical engagement runs through many versions in a short window. Requirements shift every cycle. You don't get attached. You ship the next one.\n\nOwning the full stack. Frontend, backend, data, integrations, deployment, the URL you send the stakeholder, and the observability around it once it's live. There is usually no one else to hand pieces off to. If it isn't done, it's because you haven't done it yet.\n\nCodifying what works. When you find a pattern that ships across engagements — a prompt structure, an evaluation harness, an integration shim, an agent template — you push it back to the platform and engineering teams so the next FDE doesn't rebuild it. You make the rest of us better, not just yourself faster.\n\nOwning the relationship over time. The first prototype is the start, not the deliverable. You stay close to the line of business through the lifecycle of an engagement, identify new opportunities as they surface, and harden what graduates into production.\n\nWhat we're looking for\n\n8+ years of full-stack engineering experience, with meaningful time spent shipping production systems end to end. Background as a technical founder, FDE, or software engineer with consulting experience is all fair game.\n\nStrong CS fundamentals. Data structures, algorithms, system design. You can whiteboard a service architecture, talk through tradeoffs, and not flinch at a coding interview.\n\nFrontend depth. Modern React, TypeScript, real component architecture, state management you can defend, and the taste to build something that looks finished — not just functional.\n\nBackend depth in order of importance (Node.JS, Java, and Python). API design, data modeling, auth, error handling. Comfortable owning a service from request handler to schema.\n\nProduction LLM experience. Advanced prompt engineering, agent development, evaluation frameworks, retrieval, and deployment at scale. You've shipped at least one real LLM-backed application that someone other than you used.\n\nFluency with AI-assisted development tools and agentic coding. This is not a side note. The work moves at a pace that assumes you're using these tools efficiently, accurately, and rapidly. You should be able to demonstrate a clear process that delivers measurable results.\n\nData fluency. Databases at a real working level, comfort with Python data tooling.\n\nCloud and deployment fluency. AWS, GCP, or Azure — enough to put a service on a real URL behind real auth without filing a ticket. CI/CD, containers, observability.\n\nIntegration experience. You've built things that talk to systems you didn't write. SSO, OAuth, third-party APIs, internal platforms, legacy databases.\n\nHigh agency. You navigate ambiguity inside a complex organization without needing someone to clear your path. You make calls and own them.\n\nHigh cooperation, low ego. Pearson is 30,000+ people. Forward deployed work crosses team lines constantly.\n\nCommunication skills that work in both directions. You can sit in a room of executives and engineers, hold both threads at once, and not lose either audience. You can speak to end users about their problem and translate that into something other engineering teams can actually build against.\n\nCurrency on what's changing. You stay close to the frontier of LLM capabilities, agent patterns, and AI product stacks.\n\nEducation: Bachelor's degree in Computer Science or equivalent combination of education, training, and professional experience\n\nCompensation at Pearson is influenced by a wide array of factors including but not limited to skill set, level of experience, and specific location.\n\nThe full-time salary range is between $150,000 - $180,000. This position is eligible to participate in an annual incentive program, and information on benefits offered is here.\n\nApplications will be accepted through 30th September 2026. This window may be extended depending on business needs.\n\n#LI-EB1\n\nWho we are:\n\nAt Pearson, our purpose is simple: to help people realize the life they imagine through learning. We believe that every learning opportunity is a chance for a personal breakthrough. We are the world's lifelong learning company. For us, learning isn't just what we do. It's who we are. To learn more: We are Pearson.\n\nPearson is an Equal Opportunity Employer and a member of E-Verify. Employment decisions are based on qualifications, merit and business need. Qualified applicants will receive consideration for employment without regard to race, ethnicity, color, religion, sex, sexual orientation, gender identity, gender expression, age, national origin, protected veteran status, disability status or any other group protected by law. We actively seek qualified candidates who are protected veterans and individuals with disabilities as defined under VEVRAA and Section 503 of the Rehabilitation Act.\n\nIf you are an individual with a disability and are unable or limited in your ability to use or access our career site as a result of your disability, you may request reasonable accommodations by emailing TalentExperienceGlobalTeam@grp.pearson.com.\n\nJob: Engineering\n\nJob Family: TECHNOLOGY\n\nOrganization: Direct to Consumer\n\nSchedule: FULL_TIME\n\nWorkplace Type: Remote\n\nReq ID: 24663\n\n#LI-REMOTE","company":"Pearson","rawCompany":"pearson","city":"Myrtle Point","state":"OR","isRemote":false,"isActive":false,"createdAt":"2026-09-28T11:33:23.021Z","occupations":[{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"15-1299.08","title":"Computer Systems Engineers/Architects","slug":"computer-systems-engineers-architects"},{"code":"17-2199.00","title":"Engineers, All Other","slug":"engineers-all-other"}],"industries":[{"code":"513210","title":"Software Publishers","slug":"software-publishers"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Staff Software Engineer","description":"Role Title: Staff Software Engineer\n\nPearson's PSG-CP (Pearson Software Group - Content Platform) team is looking for a forward deployed engineer who shows up where the work is happening, listens to a problem that nobody has fully written down yet, and leaves with software that addresses it. Not a deck, not a spec, not a Jira epic - running software.\n\nYou sit closer to the customer than a typical engineer and closer to the code than a typical solutions architect. The job is to compress the distance between \"we need something that does X\" and \"here, try this.\"\n\nYou will embed directly with our most strategic internal lines of business to drive AI adoption and ship working software against real problems. You will operate autonomously, thrive under ambiguity, and represent PSG-CP at the highest level inside the business. This is a significant responsibility — you'll play a key role in how AI shows up across Pearson.\n\nWhat you'd actually be doing\n\nGoing where the problem is. You will work directly with the internal stakeholders inside our different lines of business. Through real understanding of their pain points, their workflows, and the architecture of their current technical landscape, you'll design and build systems end to end for them. These are the people who will actually use what you build. You meet them on their ground, in their workflow, with their data.\n\nConducting real discovery. You're not waiting for a finished brief. You sit with users, watch them work, ask the questions, and translate what you hear into something buildable. The discovery is part of the engineering job, not a step that happens before it.\n\nBuilding during the conversation. The first version often exists before the meeting ends. People react to working software very differently than they react to wireframes — your job is to give them something to react to as fast as possible.\n\nWorking from messy inputs. Spreadsheets, PDFs, screenshots, recorded calls, half-written documents, contradictory emails from two stakeholders. You read all of it and turn it into something coherent. You don't ask people to clean up their inputs before you start.\n\nShipping production AI applications. Beyond prototypes, you build real applications on top of frontier LLMs, agents, MCP servers, evaluation harnesses, retrieval systems, custom skills — that run in production against real workflows. You know how to evaluate what you've built, not just demo it.\n\nIterating fast across many engagements. A typical engagement runs through many versions in a short window. Requirements shift every cycle. You don't get attached. You ship the next one.\n\nOwning the full stack. Frontend, backend, data, integrations, deployment, the URL you send the stakeholder, and the observability around it once it's live. There is usually no one else to hand pieces off to. If it isn't done, it's because you haven't done it yet.\n\nCodifying what works. When you find a pattern that ships across engagements — a prompt structure, an evaluation harness, an integration shim, an agent template — you push it back to the platform and engineering teams so the next FDE doesn't rebuild it. You make the rest of us better, not just yourself faster.\n\nOwning the relationship over time. The first prototype is the start, not the deliverable. You stay close to the line of business through the lifecycle of an engagement, identify new opportunities as they surface, and harden what graduates into production.\n\nWhat we're looking for\n\n8+ years of full-stack engineering experience, with meaningful time spent shipping production systems end to end. Background as a technical founder, FDE, or software engineer with consulting experience is all fair game.\n\nStrong CS fundamentals. Data structures, algorithms, system design. You can whiteboard a service architecture, talk through tradeoffs, and not flinch at a coding interview.\n\nFrontend depth. Modern React, TypeScript, real component architecture, state management you can defend, and the taste to build something that looks finished — not just functional.\n\nBackend depth in order of importance (Node.JS, Java, and Python). API design, data modeling, auth, error handling. Comfortable owning a service from request handler to schema.\n\nProduction LLM experience. Advanced prompt engineering, agent development, evaluation frameworks, retrieval, and deployment at scale. You've shipped at least one real LLM-backed application that someone other than you used.\n\nFluency with AI-assisted development tools and agentic coding. This is not a side note. The work moves at a pace that assumes you're using these tools efficiently, accurately, and rapidly. You should be able to demonstrate a clear process that delivers measurable results.\n\nData fluency. Databases at a real working level, comfort with Python data tooling.\n\nCloud and deployment fluency. AWS, GCP, or Azure — enough to put a service on a real URL behind real auth without filing a ticket. CI/CD, containers, observability.\n\nIntegration experience. You've built things that talk to systems you didn't write. SSO, OAuth, third-party APIs, internal platforms, legacy databases.\n\nHigh agency. You navigate ambiguity inside a complex organization without needing someone to clear your path. You make calls and own them.\n\nHigh cooperation, low ego. Pearson is 30,000+ people. Forward deployed work crosses team lines constantly.\n\nCommunication skills that work in both directions. You can sit in a room of executives and engineers, hold both threads at once, and not lose either audience. You can speak to end users about their problem and translate that into something other engineering teams can actually build against.\n\nCurrency on what's changing. You stay close to the frontier of LLM capabilities, agent patterns, and AI product stacks.\n\nEducation: Bachelor's degree in Computer Science or equivalent combination of education, training, and professional experience\n\nCompensation at Pearson is influenced by a wide array of factors including but not limited to skill set, level of experience, and specific location.\n\nThe full-time salary range is between $150,000 - $180,000. This position is eligible to participate in an annual incentive program, and information on benefits offered is here.\n\nApplications will be accepted through 30th September 2026. This window may be extended depending on business needs.\n\n#LI-EB1\n\nWho we are:\n\nAt Pearson, our purpose is simple: to help people realize the life they imagine through learning. We believe that every learning opportunity is a chance for a personal breakthrough. We are the world's lifelong learning company. For us, learning isn't just what we do. It's who we are. To learn more: We are Pearson.\n\nPearson is an Equal Opportunity Employer and a member of E-Verify. Employment decisions are based on qualifications, merit and business need. Qualified applicants will receive consideration for employment without regard to race, ethnicity, color, religion, sex, sexual orientation, gender identity, gender expression, age, national origin, protected veteran status, disability status or any other group protected by law. We actively seek qualified candidates who are protected veterans and individuals with disabilities as defined under VEVRAA and Section 503 of the Rehabilitation Act.\n\nIf you are an individual with a disability and are unable or limited in your ability to use or access our career site as a result of your disability, you may request reasonable accommodations by emailing TalentExperienceGlobalTeam@grp.pearson.com.\n\nJob: Engineering\n\nJob Family: TECHNOLOGY\n\nOrganization: Direct to Consumer\n\nSchedule: FULL_TIME\n\nWorkplace Type: Remote\n\nReq ID: 24663\n\n#LI-REMOTE","datePosted":"2026-09-28T11:33:23.021Z","dateModified":"2026-09-28T11:33:23.021Z","hiringOrganization":{"@type":"Organization","name":"Pearson","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Myrtle Point","addressRegion":"OR","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"bc9b7315d20aece66cd256db"},"url":"https://jobsearcher.com/jobs/bc9b7315d20aece66cd256db"}}