> Markdown version of [/jobs/ext/2692990-senior-software-engineer](https://www.wearedevelopers.com/jobs/ext/2692990-senior-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer - **Company:** Pearson - **Location:** Austin, TX, United States (Remote available) - **Experience:** Expert - **Salary:** $100,000.0 - $169,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Learning Management Systems, Data Migration, Software Debugging, OAuth, OpenID, Security Assertion Markup Language (SAML), Sharable Content Object Reference Model, Software Engineering, Web Content Accessibility Guidelines, Web Standards, Event Driven Architecture, HR Software, Graphql, Webhooks - **Published:** September 3, 2026 - **Apply:** https://dejobs.org/x/x/96045D92944B449CB50774FBCC440B53/job/ ## About the Role * 7+ years of software engineering with genuine full-stack range, and a track record of building products from scratch - as a founder, founding engineer, or member of a labs, incubation, or new-products team. * Integration depth: designing and consuming APIs (REST, GraphQL), auth and identity flows, eventing, and moving data between systems that were never designed to talk to each other. * Systems thinking: you can hold a complex enterprise environment in your head, find the load-bearing constraints, and design something that works within them. * Pragmatic engineering judgment: you optimize for learning speed early and reliability later, and you can explain exactly where and why you drew that line. * Comfort with modern AI-assisted development, and informed opinions about when AI belongs in a product and when it doesn't. * Strong communication with technical and non-technical audiences - including client-facing conversations where you're the engineering voice in the room., * Direct experience with learning technology standards and platforms: LTI, SCORM, xAPI, QTI, Caliper, the 1EdTech ecosystem, and LMS/LXP integration work. * Web standards depth (W3C, WHATWG) and practical accessibility knowledge (WCAG) - accessibility is a floor for everything we ship. * Standards-body, committee, or working-group participation. * Experience turning research - user or technical - into build decisions. Who thrives on this team * Flexible. Bets change, priorities shift, and fidelity ranges from napkin sketch to production. You move fluidly between them. * Not precious. Some of what we build will be thrown away - that's the process working, not failing. You hold your work loosely and your standards tightly. * Comfortable in parallel. You'll usually carry more than one workstream at a time, and you can context-switch without dropping threads. * A systems thinker. You can understand complex systems - technical, organizational, or both - and figure out how to work effectively within them. * A genuine problem-solver. You start from the problem, not from your job title or your favorite solution. * Good with people. You build trust quickly across teams, disciplines, and levels - inside Pearson and with clients. * Principled and pragmatic. You follow the rules that matter - ethics, privacy, security, and accessibility are non-negotiable - and you know how to flex in and out of heavyweight structures when a small, fast-moving team calls for it. * A clear communicator. You make your thinking legible in writing, diagrams, demos, and rooms full of executives or engineers. * Ego-free about execution. Everyone on this team is willing to write ALL the code or NONE of the code, depending on what the bet needs. * Comfortable in discomfort. Ambiguity, unfamiliar domains, and half-formed ideas are the raw material of this job. * An independent thinker. You form your own view, argue for it well, and update it quickly when the evidence says you should. ## Description You're a generalist builder who turns ambiguous problems into working software. As the Senior Product Engineer on this team, you'll architect and build new products end to end - front end, back end, data, and infrastructure - with a particular love for the part many engineers avoid: integrations. Everything this team ships connects to something: other Pearson products, client learning platforms, HR systems, identity providers. Your job is to make those connections real, reliable, and fast to stand up. This is a senior individual contributor role. There are no direct reports; your influence comes from what you build and how you reason about it. What you'll do * Take new product concepts from architecture sketch to working software - prototypes, pilots, and MVPs - across the full stack. * Own integrations end to end: composing other Pearson products' APIs and platforms, and connecting into client-side systems - auth and identity (OAuth 2.0, OIDC, SAML), provisioning (SCIM), events and webhooks, and learning standards (LTI, SCORM, xAPI) where they apply. * Right-size the engineering to the stage of the bet: gloriously disposable code for a one-week concept test, production-grade foundations for products that graduate. Knowing which is which is the core skill. * Work directly with client technical teams during pilots - discovery, scoping, deployment, and debugging inside their environments. * Instrument everything for learning: telemetry, evaluation, and the data the team needs to make honest kill-or-scale decisions. * Use AI as a force multiplier - in your own development workflow, and, where a bet calls for it, as a capability inside the products themselves. * Contribute well beyond the code: shaping concepts, joining research sessions, and pressure-testing feasibility before anyone falls in love with an idea. * Partner with Pearson's platform, security, and architecture teams so that graduating products land well inside the wider organization. ## Related Videos - [Keeping applications secure by evolving OAuth 2.0 and OpenID Connect](https://www.wearedevelopers.com/videos/100152-keeping-applications-secure-by-evolving-oauth-2-0-and-openid-connect) - [Putting the Graph In GraphQL With The Neo4j GraphQL Library](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library) - [Making Teaching Code Less Academic and More Market-Ready - Peter Ruppel](https://www.wearedevelopers.com/videos/1911-making-teaching-code-less-academic-and-more-market-ready-peter-ruppel) - [Get started with securing your cloud-native Java microservices applications](https://www.wearedevelopers.com/videos/123-get-started-with-securing-your-cloud-native-java-microservices-applications) - [GraphQL + Apollo + Next.js: A Lovely Trio](https://www.wearedevelopers.com/videos/311-graphql-apollo-next-js-a-lovely-trio) - [Delegating the chores of authenticating users to Keycloak](https://www.wearedevelopers.com/videos/1558-delegating-the-chores-of-authenticating-users-to-keycloak) ## Related Articles - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Is Software Engineering Hard?](https://www.wearedevelopers.com/magazine/448-is-software-engineering-hard) - [How to Answer the Interview Question: “Why Do You Want to Be a Software Engineer?”](https://www.wearedevelopers.com/magazine/392-how-to-answer-the-interview-question-why-do-you-want-to-be-a-software-engineer) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers)