Senior Software Engineer - Clearing

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "Your Role", "Things You Get To Do", "Who You Are (Must-Haves)", "Who You Might Be (Nice-to-Haves)", "How We Take Care of You". Also maybe "About the company". The instruction: 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. The posting includes: - Who We Are (company description) - Your Role (description of responsibilities) - Things You Get To Do (list of duties) - Who You Are (Must-Haves) (requirements/qualifications) - Who You Might Be (Nice-to-Haves) (nice-to-haves) - 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 also have mention of "Competitive Salary & Stock Options" which is pay info. So we could have a Pay section? The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Competitive Salary & Stock Options, Health Benefits, etc. So we could have a Benefits section (maybe combine Pay and Benefits). The instruction gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings. We need to avoid filler. So we should include sections for: - About the company (maybe "About Alpaca" or "Who We Are") but they said use headings like About the role, Responsibilities, etc. However they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It's examples, not strict list. So we can use headings like "About Alpaca", "Role Overview", "Responsibilities", "Requirements", "Nice-to-Have Skills", "Benefits". Ensure we don't create empty sections. We must preserve all substantive information. So we need to include all details from each section. We need to convert lists to

  • . For prose, use

    . We need to remove boilerplate: "Alpaca is proud to be an equal opportunity workplace dedicated to pursuing and hiring a diverse workforce. Recruitment Privacy Policy" - remove. Also remove duplicated lines? Not seeing duplicates. We need to ensure we don't include application instructions (none present). Also remove any "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So remove the equal opportunity line. Now structure: We could have:

    About Alpaca

    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.

    But note: The instruction says 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. The "Who We Are" includes some recruiting language; we can keep. Now "Your Role": Could be a section "Role Overview" or "About the role". Use

    About the role

    then prose. Then "Things You Get To Do": Could be "Responsibilities" with
    • . Then "Who You Are (Must-Haves)": Could be "Requirements" with
      • . Then "Who You Might Be (Nice-to-Haves)": Could be "Nice-to-Have Skills" with
        • . Then "How We Take Care of You": Could be "Benefits" with
          • . Also includes Competitive Salary & Stock Options (pay). Could also have a Pay section but we can include salary in Benefits. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Competitive Salary & Stock Options, Health Benefits, New Hire Home-Office Setup, Monthly Stipend. So we can have Benefits section. We need to ensure we don't create empty sections. Now we need to preserve all substantive information. Let's extract each piece. From 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. We can keep all that. Now Your Role: - As a Senior Software Engineer on the Clearing team you’ll work on what happens after the trade is made. - Most of the work we do is not user facing (although we have some user facing systems as well) but is very much essential to the day to day operations of a Broker Dealer company. - During the past couple years we’ve become self-clearing in US equities, US options, and this is the team at the heart of those achievements. - We’re not stopping there: there are always new (not yet announced) integrations to build, and new product offerings to enable through those integrations. - Beyond core clearing, we also work on securities finance related functions and building the infrastructure that allows us to launch new product offerings, like Fully Paid Securities Lending. - There may also be additional exciting initiatives currently in development. Now Things You Get To Do (list): - Work in a team where we value quality of thinking, excellence in execution, practical solution and willingness to take responsibility, instead of tenure, hierarchy, or arguing about the theoretical benefits of things that don’t matter - Own projects from ideation to deployment, cutting through ambiguity to build what’s necessary, not just what’s asked for. - Design and build new systems that let us enable new products for the company or unlock more revenue - Refine our existing systems. They’re not perfect and will never be, but we believe in improving them as long as the outcome is meaningful and tangible - Learn about things you never knew existed but are instrumental in keeping the financial markets healthy and functioning - Learn what it takes to build a company like Alpaca, see behind the curtains, and cooperate with great people from other teams. You also get to influence what we do and how we do it! - Participate in our on-call rotation to ensure our systems are in tip-top shape. We value our free time as much as you do, so we prioritize eliminating issues that cause friction for the team. Now Who You Are (Must-Haves) (list): - You understand that we’re working on systems people entrust with their hard earned money and you take that very seriously - You are deeply interested in how traditional financial markets work - You (have taken and) can take the lead on a project: we’ll describe what we’re trying to fix or build, who to reach out to if you need help, and you’ll handle the rest - You take responsibility for the work you do personally, and also collectively, as a team. If there’s an issue and you’re the only one around, then you roll up your sleeves instead of saying you didn’t write the code. - You understand which design choices matter and which ones can be easily adjusted once we learn more about how the world truly works - You know when you don’t know something and you seek out that information instead of faking, guessing, or having an LLM do the thinking for you - You don’t cling to your ideas: if new information surfaces then you can let things go and focus on what truly matters - You want to see the long-term impact of your decisions and take on larger and larger efforts, leveraging the expertise you’ve gained along the way. We value people who stick around to see their systems scale and evolve over time. - You have experience working at startups and know that not everything is perfect and you’re the one who helps us trend towards that goal. You also understand that we have a business to run and priorities can shift based on market needs. - You’re willing to push back in a civilized and productive way, and can accept when the decision ultimately differs from what you think would be the best course of action. We