Skip to main content

Block

Software Engineer, Cash App Taxes

New York, NY, United States of AmericaFrom $270kmidAdded today

About this role

Build and own backend systems powering Cash App's tax filing platform, translating complex tax logic into scalable, reliable software. You'll work alongside tax experts and cross-functional teams to create accurate, user-friendly tax solutions for millions of customers.

What you'll do

  • Design and build high-quality backend features for tax filing, including form logic and e-file submission
  • Convert complex tax requirements into clean, maintainable, well-tested code with tax specialists
  • Create tools enabling non-technical contributors to make safe code changes while maintaining quality
  • Drive architectural and design decisions ensuring scalability, security, and maintainability
  • Collaborate cross-functionally with QA, product, design, and customer care teams
  • Identify and resolve issues around accuracy, reliability, and performance

What they're looking for

  • Backend development (Java/Kotlin)
  • System design and architecture
  • Object-oriented programming
  • SQL and relational databases (iBatis)
  • Cloud platforms (GCP/AWS)
  • Monitoring tools (Datadog, Splunk, New Relic)
  • API design (HTTP, JSON, gRPC, Protocol Buffers)
  • AI coding tools and AI-first development mindset
Apply on the employer's site

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

Block

Block builds financial infrastructure and lending platforms powering multiple brands including Cash App and Afterpay, along with bitcoin mining hardware through its Proto division. The company is hiring Software Engineers, Backend Infrastructure specialists, Product & Test Engineers, and Legal Systems Engineers to scale payments, lending systems, mining ASICs, and legal technology operations.

Website
block.xyz
View all jobs at Block

Likely interview questions

  • Tell us about a complex backend system you've designed—what were the key architectural decisions and tradeoffs?
  • How would you approach translating ambiguous or conflicting business requirements (like tax rules) into code?