Skip to main content

Wealth.com

Software Engineer

Hybrid, New York, Tempe, San Francisco (Remote)$140k–$175kfulltimemidAdded today

About this role

Wealth.com seeks a Software Engineer to design and scale backend systems powering its estate planning and AI-driven platform used by financial advisors. You'll own features end-to-end on a TypeScript stack, collaborating across product and engineering teams in a fast-paced startup environment.

What you'll do

  • Design and build backend services including APIs, data pipelines, and integrations with enterprise wealth management platforms
  • Own features from spec through implementation, testing, deployment, and post-launch monitoring
  • Write production-grade TypeScript with strong testing, observability, and operational discipline
  • Collaborate with product, design, and engineering teams to translate requirements into technical solutions
  • Contribute to system design decisions around scalability, reliability, security, and performance
  • Participate in code review, design discussions, and on-call rotations

What they're looking for

  • TypeScript backend development
  • API design (REST/gRPC)
  • Relational and NoSQL databases
  • Cloud infrastructure (AWS, GCP, or Azure)
  • Docker and Kubernetes
  • Event-driven systems and messaging
  • Logging, metrics, tracing, and observability
  • CI/CD workflows
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.

Wealth.com

Wealth.com builds an estate and tax planning platform designed to streamline financial planning processes. The company is hiring Software Engineers to develop scalable backend systems and GTM Engineers to build automation and integration solutions for revenue operations.

View all jobs at Wealth.com

Likely interview questions

  • Walk us through a backend system you designed and operated at scale—what were the key architectural decisions and trade-offs?
  • How do you approach writing production-grade TypeScript code, and what testing and observability practices do you prioritize?
Unlock all 7 questions free — and practice them live →