Software Engineer, Access Bay Area, CA,

It all started with an idea at Block in 2013. Initially built to take the pain out of peer-to-peer payments, Cash App has gone from a simple product with a single purpose to a dynamic ecosystem, developing unique financial products, including Afterpay/Clearpay, to provide a better way to send, spend, invest, borrow and save to our 50+ million monthly active customers.

We want to redefine the world's relationship with money to make it more relatable, instantly available, and universally accessible.

Today, Cash App has thousands of employees working globally across office and remote locations, with a culture geared toward innovation, collaboration and impact. We've been a distributed team since day one, and many of our roles can be done remotely from the countries where Cash App operates. No matter the location, we tailor our experience to ensure our employees are creative, productive, and happy.

We're the Access team, and we're building the next generation of authentication and permissions infrastructure for Block. Behind every login and every account there's a platform that needs to be both rock-solid and remarkably flexible.

This isn't about maintaining legacy systems, it's about building the foundation that will enable Cash App and Block's ecosystem to scale while serving increasingly diverse customer needs.

As Block accelerates product innovation, we're seeing an explosion of new use cases: different account capabilities, different authentication requirements, different customer cohorts with different needs. We're building a platform that lets product teams move fast while we maintain the trust and security that our customers depend on.

You'll be joining at an inflection point. The decisions we make now about architecture, about APIs, about how we enable other teams—will define how Block scales for years to come. This is foundational work with massive leverage.

• Design and build the APIs and services that power Authentication & Permissions across Cash App and Block's ecosystem, the systems that determine who can access what, and how they prove they are who they say they are. The work is varied and impactful. You might:
  • Build fine-grained permissions systems that enable different roles and capabilities across various account configurations
  • Build secure authentication experiences that protect customers while maintaining seamless access to their accounts
  • Improve account recovery success rates, helping legitimate customers regain access while keeping bad actors out
  • Consolidate authentication platforms
    , migrating critical flows into scalable, composable services
  • Design authorization primitives that product teams across Block can use to build secure, flexible experiences
• How you'll work: You'll navigate complexity with pragmatism. You'll balance immediate business needs with long-term platform goals. You'll ship iteratively while keeping the big picture in mind. You'll collaborate across product, design, security, and engineering teams. You'll think critically about priorities. You'll adapt and thrive in an environment where priorities shift and requirements evolve. The common thread: you'll be solving complex technical problems that directly impact both customer trust and product velocity.
  
  You'll need to balance pragmatism with technical excellence—shipping iteratively while building toward a coherent platform vision.

• 5+ years building and operating production systems with demonstrated impact and technical ownership
• Ability to think critically and analyze complex problems, weigh trade-offs, and make pragmatic decisions that balance competing priorities
• A bias toward iterative delivery. You know how to break big problems into shippable pieces and maintain momentum through ambiguity
• Comfort with complexity. Whether it's large codebases, distributed systems, or evolving requirements, you don't get overwhelmed; you get strategic
• Excellent communication skills. You can explain technical concepts clearly, build alignment across teams, and adapt your style to different audiences
• Customer empathy. You understand that behind every API call is a person trying to…