Skip to main content

FanDuel

Software Engineer

Atlanta, Georgia, United States$116k–$152.3kmidAdded 1 month ago

About this role

FanDuel seeks a software engineer to join their Payments Engineering team, building and maintaining deposit and withdrawal user journeys within their wallet platform. You'll work in multidisciplinary teams using AWS, Kubernetes, Terraform, Java, Python, and React to create scalable, secure systems serving millions of players.

What you'll do

  • Build and maintain payment-related user journeys for deposits and withdrawals
  • Write secure, testable, maintainable code following software engineering best practices
  • Participate in design discussions, code reviews, and team planning activities
  • Own parts of the product and codebase, striving to become a subject matter expert
  • Solve complex technical problems and improve existing systems
  • Collaborate with multidisciplinary teams to deliver high-quality solutions on schedule

What they're looking for

  • Java or similar backend programming languages
  • Distributed and scalable backend systems design
  • Data structures and algorithms
  • React and JavaScript for web applications
  • AWS and Kubernetes infrastructure
  • Software testing and quality engineering practices
  • Terraform or infrastructure-as-code tools
  • API development and debugging
Apply on the employer's site

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

FanDuel

FanDuel operates a sports betting and gaming platform, handling payments, wallet systems, and player experiences at scale. The company is hiring Security Operations Engineers for threat detection and incident response, as well as Security Engineers to embed security practices across its development lifecycle and address emerging AI/LLM risks.

View all jobs at FanDuel

Likely interview questions

  • Tell us about your experience building distributed, scalable backend systems. What challenges have you faced and how did you approach them?
  • Describe a time when you had to balance code quality with delivery velocity. How did you decide what trade-offs to make?