Skip to main content

Valon

Software Engineer II

New York$170k–$200kfulltimemidAdded 2 days ago

About this role

Valon seeks a Software Engineer II to build and scale AI-native mortgage servicing infrastructure on their modern platform. You'll tackle complex regulatory requirements, collaborate cross-functionally, and work with Python, React, Kubernetes, and GCP to transform a legacy industry.

What you'll do

  • Design and build robust infrastructure to handle evolving federal, state, and agency regulations
  • Learn new technologies quickly and apply them to challenging financial systems problems
  • Develop scalable systems that handle billions of dollars at scale
  • Collaborate with Product and Design teams to define optimal customer experiences
  • Work cross-functionally to balance product and technical requirements
  • Dive deep into mortgage servicing domain complexity

What they're looking for

  • Python
  • React
  • Docker
  • Kubernetes
  • Google Cloud Platform
  • Distributed systems design
  • Web or mobile application development
  • Infrastructure management

Benefits

  • Competitive salary with equity stake in Series C company
  • Comprehensive medical, dental, and vision coverage
  • Pre-tax commuter benefits for transit and parking
  • Flexible PTO, sick days, and 11 company holidays
  • 12 weeks fully paid parental leave for all parents
  • Learning & development opportunities with 360-degree feedback
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.

Valon

Valon builds an AI-native operating system for mortgage servicing and regulated finance. The company is hiring AI deployment engineers, software engineers, and sales engineers to develop internal tools, scalable infrastructure, and drive enterprise customer adoption of their platform.

Website
valon.com
View all jobs at Valon

Likely interview questions

  • Describe a time you built a scalable system from scratch under tight timelines—what was your approach?
  • How would you approach learning a highly regulated domain like mortgage servicing quickly?