Senior Software Engineer - Payments & Treasury

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "Your Role", "Who You Are (Must-Haves)", "Who You Might Be (Nice-to-Haves)", "How We Take Care of You". We need to use headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content accordingly. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Who We Are: description of company. Could be "About the role"? Actually "About the role" is about the job, but we have "Your Role" describing responsibilities. So we could have sections: About the role (maybe summarizing the role description), Responsibilities (list of duties), Requirements (must-haves), Qualifications (maybe nice-to-haves?), Skills (maybe list of technical skills), Benefits (How We Take Care of You includes Competitive Salary & Stock Options, Health Benefits, New Hire Home-Office Setup, Monthly Stipend). Pay: we have Competitive Salary & Stock Options (salary mentioned but not specific number). Should we include Pay section? The posting mentions Competitive Salary & Stock Options but no specific number. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Competitive Salary & Stock Options, which is a statement about pay (though not a number). So we could include a Pay section with that statement. Benefits: we have Health Benefits, New Hire Home-Office Setup, Monthly Stipend. So Benefits section. Schedule: not mentioned, so omit. We need to avoid filler like "commensurate with experience". Not present. We need to use

  for each section heading. We need to use

  • for any list of duties/requirements/benefits. We need to use

    for prose. We need to preserve all substantive information. We need to remove boilerplate like "Alpaca is proud to be an equal opportunity workplace..." and "Recruitment Privacy Policy". Also remove duplicated lines. Let's extract substantive content: Who We Are: - Alpaca is a US-headquartered, global leader in agent-first brokerage infrastructure for stocks, ETFs, options, crypto, fixed income, 24/5 trading, and more. - Amongst our subsidiaries, Alpaca is a licensed financial services company, serving hundreds of financial institutions across 40 countries with our institutional-grade APIs. - This includes broker-dealers, investment advisors, wealth managers, hedge funds, and crypto exchanges, totalling over 10 million brokerage accounts. - Our global team is a diverse group of experienced engineers, traders, and brokerage professionals who are working to achieve our mission of opening financial services to everyone on the planet. - We're deeply committed to open-source contributions and fostering a vibrant community, continuously enhancing our award-winning, developer-friendly API and the robust infrastructure behind it. - Alpaca is proudly backed by $400 million in funding from top-tier global investors including Portage Ventures, Spark Capital, Tribe Capital, Social Leverage, Horizons Ventures, Opera Tech Ventures, SBI Group, Derayah Financial, Unbound, Peak XV, Elefund, and Y Combinator. - Our Team Members: We're a dynamic team of 400+ globally distributed members who thrive working from our favorite places around the world, with teammates spanning the USA, Canada, Japan, Hungary, Nigeria, Brazil, the UK, and beyond! - We're searching for passionate individuals eager to contribute to Alpaca's rapid growth. - If you align with our core values—Stay Curious, Have Empathy, and Be Accountable—and are ready to make a significant impact, we encourage you to apply. Your Role (Responsibilities): - As a senior software engineer, you will help build and scale the systems and services that form the foundation of Alpaca and empower millions of users that are trading billions of dollars worth of assets daily. - The payments team is responsible for building and maintaining a modern global payments and treasury platform. - Operating in an industry in which money movement is a critical component, we adopt a modern technology focused approach with highly scalable, event-driven systems. - Resilient engineering, technical and operational scalability, and system integrity are crucial to our success. - We have ambitious plans to build a seamlessly integrated comprehensive treasury platform into an industry leading end-to-end financial infrastructure on a global scale. - Alpaca has and will continue to prove ourselves as an innovative market leader and this team is a core component of our growth across global markets and asset classes. - We are looking for senior engineers who are keen on providing quality solutions, have great fundamentals, proven experience building and architecting at scale, and not afraid of challenging conventions or voicing their opinions. - In this role, you will have the autonomy to design and implement solutions to achieve defined goals while actively participating in defining those goals. - An understanding of cloud-based modern architecture, infrastructure, and orchestration practices are also great assets we actively look for. Who You Are (Must-Haves): - Strong problem-solving skills paired with a proactive mindset - Excellent communication and collaboration skills - The ability to work independently and as part of a team - A preference for simple and elegant solutions - At least 3 years of experience working on systems at scale - Proven experience in building and maintaining microservices - Experience with client facing APIs - Strong coding skills, preferably in Go - Ability to write clean, well tested, and maintainable code - Experience with domain driven design and event driven design - Ability to debug issues or better yet, foresee problems and avoid them entirely - Familiarity with containerization and orchestration technologies, especially Kubernetes - Experience with cloud platforms, preferably Google Cloud Platform - Experience with messaging queues and message brokers - Experience with relational databases, preferably PostgreSQL - Experience with distributed systems design - Previous experience with or understanding of payment rails and the payment lifecycle - Experience with double entry accounting and financial ledgers Who You Might Be (Nice-to-Haves): - Previous experience in the financial industry or knowledge of payments initiations - Experience with financial reconciliation systems - Experience with or understanding of ISO20022 financial standard - Experience working remotely - Experience working at a startup, exchange, brokerage, market maker, or hedge fund - DevOps mindset is an asset How We Take Care of You (Benefits): - Competitive Salary & Stock Options - Health Benefits - New Hire Home-Office Setup: One-time USD $500 - Monthly Stipend: USD $150 per month via a Brex Card We need to decide sections. Potential sections: - About the role (maybe combine Who We Are and Your Role? But "About the role" is about the job, not company. Could use "About the role" for the role description (Your Role). And maybe "About the company" not a standard heading; but we could put company info under "About the role"? Might be odd. However instructions say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. Thus: - About the role: maybe a brief description of the role (the role overview). Could be the first paragraph of Your Role: "As a senior software engineer, you will help build and scale the systems and services that form the foundation of Alpaca and empower millions of users that are trading billions of dollars worth of assets daily." plus maybe the payments team description. We'll put that as prose. - Responsibilities: list of duties (maybe bullet list). Could include building and scaling systems, payments team responsibilities, resilient engineering, ambitious plans, autonomy to design, etc. - Requirements: Must-haves list. - Qualifications: Nice-to-haves list (or could be Qualifications). We'll treat Nice-to-haves as Qualifications. - Skills: maybe list of specific technical skills (Go, Kubernetes, GCP, PostgreSQL, etc). But we already have them in Must-haves; could split but risk duplication. Better to keep Must-haves as Requirements, and maybe Skills as a subset? However we need to avoid thin sections. Perhaps combine Requirements and Skills into one? But instructions: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (including must-haves and nice-to-haves?), Benefits, Pay. But we need to follow heading names exactly? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all of them, just that if we use a heading it should be one of those. So we can choose a subset. Thus we could have:

    About the role

    (prose)

    Responsibilities

    (ul)

    Requirements

    (ul) for must-haves

    Qualifications

    (ul) for nice-to-haves

    Benefits

    (ul) for benefits

    Pay

    (p) for Competitive Salary & Stock Options We should not include Schedule. We need to preserve all substantive information. Ensure we don't lose any details. Let's extract each piece. About the role: Could be a short paragraph summarizing the role: "As a senior software engineer, you will help build and scale the systems and services that form the foundation of Alpaca and empower millions of users that are trading billions of dollars worth of assets daily. The payments team is responsible for building and maintaining a modern global payments and treasury platform. Operating in an industry in which money movement is a critical component, we adopt a modern technology focused approach with highly scalable, event-driven systems. Resilient engineering, technical and operational scalability, and system integrity are crucial to our success. We have ambitious plans to build a seamlessly integrated comprehensive treasury platform into an industry leading end-to-end financial infrastructure on a global scale. Alpaca has and will continue to prove ourselves as an innovative market leader and this team is a core component of our growth across global markets and asset classes. We are looking for senior engineers who are keen on providing quality solutions, have great fundamentals, proven experience building and architecting at scale, and not afraid of challenging conventions or voicing their opinions. In this role, you will have the autonomy to design and implement solutions to achieve defined goals while actively participating in defining those goals. An understanding of cloud-based modern architecture, infrastructure, and orchestration practices are also great assets we actively look for." That seems to capture the role description. Responsibilities: Could be a list of duties: maybe bullet points: "Help build and scale the systems and services that form the foundation of Alpaca", "Build and maintain a modern global payments and treasury platform", "Adopt a modern technology focused approach with highly scalable