Luminary
Software Engineer - Backend
About this role
Luminary seeks a Backend Software Engineer to own the tax and estate planning modeling engine that powers wealth transfer services for high-net-worth families. You'll build domain-specific logic for complex transfer tax computation, trust structures, and distribution modeling while working closely with legal and tax experts to ensure correctness.
What you'll do
- Own and evolve the transfer tax computation and distribution modeling engine
- Design flexible data models for complex trust and estate structures
- Work with JDs and CPAs to validate calculations against real-world tax code
- Expose modeling capabilities and hypothetical scenario tools to AI agents
- Ship production changes multiple times daily through continuous integration
- Partner with customers and subject matter experts to understand domain requirements
What they're looking for
- Backend software engineering (4+ years)
- Data modeling and schema design
- Complex business logic implementation
- Rigorous testing and correctness verification
- Working with domain experts and stakeholders
- Python or similar systems modeling language
- API design
- Familiarity with financial or tax systems (preferred)
Benefits
- Remote or hybrid work (NYC office near Bryant Park)
- Work on high-impact domain modeling problems
- Collaborate with JDs, CPAs, and subject matter experts
- Modern development tooling and practices
- Engineers own outcomes and talk directly with customers
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.
Luminary
Luminary builds AI-powered products and is seeking software engineers who combine technical expertise with a product-focused mindset to develop and enhance these solutions. The company values collaborative engineering teams and offers opportunities for engineers to directly influence product development.
View all jobs at LuminaryLikely interview questions
- Describe a time you modeled a complex real-world system in software—what were the tricky edge cases?
- How do you approach validation and testing for business logic you can't easily unit test?