Renaissance Learning North America
Software Engineer III
About this role
Renaissance is seeking a Software Engineer III to build discovery and search features across their education technology platform, serving teachers, admins, and students. This role involves full-stack development with a focus on adopting AI-driven multi-agent orchestration for feature development, working remotely across backend services and React frontends.
What you'll do
- Build discovery layer features including search/browse for teachers, curation tools for admins, and exploration interfaces for students
- Develop backend services using relational databases, non-relational datastores, message queuing, and cloud infrastructure with typed contracts
- Create frontend experiences in TypeScript and React with contract testing and accessibility as a core requirement
- Write comprehensive tests (unit, component, contract) and instrumentation including traces, metrics, and logs
- Work with high independence to scope problems and solutions appropriately
- Adopt and help pioneer Renaissance's S3 model of AI-driven multi-agent orchestration for software development
What they're looking for
- Full-stack web development (backend and frontend)
- TypeScript and React
- Relational and non-relational databases
- Cloud infrastructure and deployment
- Message queuing systems
- Testing (unit, component, contract testing)
- API design and typed contracts
- Observability and instrumentation
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Renaissance Learning North America
Renaissance Learning North America builds K-12 educational technology solutions delivered as scalable SaaS platforms. The company is hiring software engineers and DevOps professionals to develop backend services, frontend applications, and cloud infrastructure that support their platform-centric model.
View all jobs at Renaissance Learning North AmericaLikely interview questions
- Tell us about a production web application or service you've built from start to ship—what were the key technical decisions?
- How have you approached designing backend services to work against both relational and non-relational data stores?