Member of Trading Operations
Anchorage Digital · United States · 4 wk ago
RemoteRemoteManufacturingFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the posting.
Key content:
- Intro about company: maybe "About the role"? Actually the posting includes description of company, but we can put under "About the role" or maybe "About Anchorage Digital"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly.
We have:
- Role description: "As a Member of Trading Operations, you are responsible for supporting our clients in their daily activities. You will play a crucial role in supporting the post-trade life-cycle of the activity of various digital assets, ensuring timely settlements, reconciliations, and implementing strong risk mitigation strategies. This position requires a deep understanding of cryptocurrencies, blockchain technology, financial operations, and risk management. The ideal candidate will possess strong technical skills, the ability to handle complex tasks, organizational knowledge, and effective communication and influence capabilities. You have a full understanding of the settlement operations, as well as the regulatory and operational considerations of each step. You support client interactions across multiple teams and work closely with trading to ensure processes and procedures are developed and continuously refined."
That's responsibilities.
- Then "We have created the Factors of Growth & Impact to help Villagers better measure impact..." then list of bullet points under categories: Technical Skills, Complexity and Impact of Work, Organizational Knowledge, Communication and Influence. Those are like skills/requirements.
- Then "You may be a fit for this role if you have: 3+ years experience supporting the settlement activities of institutional clients in both traditional asset classes and crypto assets. Have experience with and understanding of crypto-native institutions. Demonstrated problem-solving skills and agility, to identify emerging risks quickly, brainstorm solutions, and pivot when goals change. Able to work rotational weekend and holiday coverage". That's qualifications/requirements.
- Then "Although not a requirement, bonus points if: Experience in Python, SQL, low-code platforms is a plus. A passion for building early-stage startups. You were emotionally moved by the soundtrack to Hamilton, which chronicles the founding of a new financial system. :)". That's maybe "Skills" or "Preferred qualifications".
- Then "About Anchorage Digital: Who we are ..." That's company description; could be "About the role"? Actually "About the role" is more about role; "About Anchorage Digital" is company overview. Could be placed under "About the role"? But instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" containing role description and maybe company overview? Might be okay.
We need to avoid boilerplate: EEO, legal, privacy, AI tools, etc. Remove those.
Also remove duplicated lines.
We need to preserve all substantive info: include details about settlement activities, technical skills list, complexity, organizational knowledge, communication, experience requirements, bonus points, company description (maybe under About the role). Also mention security policy about in-person onboarding? That's part of company culture; maybe include under About the role? It's substantive: "With the evolving landscape of digital threats... we have a security policy mandating all new hires complete an in-person onboarding process - no exceptions." That's relevant to role; could be included in About the role or Responsibilities? Probably under About the role as part of company expectations.
Also mention "Security is our foundation and we prioritize physical identity verification and secure IT setup." etc.
Also mention "While our security and IT logistics require physical presence to protect our infrastructure from sophisticated global threats, this move is equally about our Village culture. We believe that a laptop can be shipped, but our culture cannot."
Also mention offices locations? Might be considered substantive but maybe not needed for role? Could be included under About the role.
We need to decide sections.
Potential sections:
- About the role (includes company overview, security policy, culture, location, mission)
- Responsibilities (duties)
- Requirements (mandatory qualifications)
- Skills (technical skills, maybe also preferred)
- Qualifications (maybe same as Requirements? Could combine)
But we need to avoid duplication.
Better: Use sections: About the role, Responsibilities, Requirements, Skills.
We can put Requirements: 3+ years experience, crypto-native institutions, problem-solving, rotational weekend/holiday coverage.
Skills: Technical Skills list (from Factors of Growth & Impact) plus bonus points (Python, SQL, low-code, passion for startups, Hamilton soundtrack). Also maybe include Organizational Knowledge, Communication and Influence as part of Skills? Could separate but we have limited headings.
We could also have "Qualifications" for education? Not present.
We could have "Responsibilities" as the bullet list of duties (settlement, monitoring, etc.)
We need to use