Skip to main content

Leland

Software Engineer

  • Confirmed live in the last 24 hours
  • No salary listed
  • Mid level
  • Full-time
  • On-site · Leland HQ - Lehi, UT
  • Added 1 month ago

About this role

Leland is seeking an experienced Software Engineer to build and maintain core platform features connecting users with coaching and career development resources. You'll work cross-functionally with product and design to develop high-quality, performant code while owning quality through testing and code reviews in a fast-growing, well-funded AI-native startup.

What you'll do

  • Collaborate with product, design, and engineering teams to build platform features for coaching and community connectivity
  • Build and maintain foundational infrastructure components
  • Write high-quality, performant code and propose innovative product ideas
  • Ensure product quality through comprehensive testing and rigorous code reviews
  • Take ownership of code quality without dedicated QA support
  • Foster an inclusive, collaborative team culture

What they're looking for

  • Full-stack or specialized frontend/backend development
  • React and TypeScript
  • Next.js
  • Java
  • GraphQL
  • Testing and code review practices
  • Self-directed problem-solving
  • Cross-functional communication

Benefits

  • Work on a mission helping people achieve career and educational goals
  • Direct impact in a collaborative, high-energy environment
  • Opportunity to shape product strategy alongside leadership
  • Fast-paced, AI-native startup culture
  • Well-funded company ($19M raised)
Apply with Autofill

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.

Leland

Industry
Technology & Software
View all jobs at Leland

Likely interview questions

  • Can you walk us through a time when you owned the quality of a feature from development through production without a dedicated QA team?
  • Tell us about your experience working across frontend, backend, or full-stack domains—how do you approach learning new technology stacks?