Skip to main content

IXL Learning

Software Engineer

San Mateo, CAmidAdded 1 month ago

About this role

IXL Learning, a leading EdTech company serving millions of learners, seeks a Software Engineer to develop and enhance educational products. You'll collaborate with skilled engineers on full-stack development while working on features that impact education globally.

What you'll do

  • Develop back-end systems, application logic, and user interfaces for educational products
  • Lead the complete development lifecycle including design, coding, testing, and debugging
  • Work on both new projects and existing codebases alongside talented engineering teams
  • Provide technical estimates, evaluate new technologies, and assess implementation feasibility
  • Communicate and coordinate across multiple development teams on product releases

What they're looking for

  • Java or object-oriented programming languages
  • Back-end development
  • Full-stack software development
  • Software testing and debugging
  • Technical communication and collaboration
  • Code documentation
  • Platform and technology evaluation

Benefits

  • Competitive salary: $116,000–$150,000
  • Equity compensation
  • Health and benefits package
  • Work on products impacting millions of learners
  • Collaborative, values-driven company culture
  • On-site role in San Mateo, CA headquarters
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

IXL Learning

IXL Learning builds personalized educational technology products and platforms used by millions of students, teachers, and parents worldwide. The company is hiring software engineers for full-stack development roles across backend systems, frontend applications, mobile platforms, and APIs.

Website
ixl.com
View all jobs at IXL Learning

Likely interview questions

  • Tell us about your experience with Java or object-oriented programming. Can you walk us through a complex project where you used these skills?
  • Describe your experience working on both greenfield projects and legacy codebases. How do you approach each differently?