VP, Forward Deployed Lead
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we should map content to appropriate headings. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings if they match content. But we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings when applicable. We need to include a section only when posting has real specific content for it. So we need to decide which sections we have content for.
We have:
- About the role: Could be "Who You Are" and "What You’ll Do". That's role description. Could map to "About the role". Provide description.
- Responsibilities: "What You’ll Do" list.
- Requirements/Qualifications/Skills: "What We’re Looking For" and "Bonus Points". Could combine into Requirements and Qualifications.
- Benefits: "What We Offer" includes benefits.
- Pay: base salary range.
- Schedule: maybe hybrid/flexible working arrangements.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: EEO, accommodation, etc. Also remove "Apply now and join us..." maybe considered application instructions? It says remove application instructions. So we should drop the "Apply now and join us as we grow the economy that runs on code." line.
Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content:
Who We Are: description of Galaxy Digital Inc. (global leader...). This is company overview; maybe not needed as a section? Could be part of About the role? But we could include as a brief intro paragraph before sections. The instruction: "Prefer a few substantive sections over many thin ones." We could include a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings when applicable. We need to include a section only when posting has real specific content for it. So we need to decide which sections we have content for. We have: - About the role: Could be "Who You Are" and "What You’ll Do". That's role description. Could map to "About the role". Provide description. - Responsibilities: "What You’ll Do" list. - Requirements/Qualifications/Skills: "What We’re Looking For" and "Bonus Points". Could combine into Requirements and Qualifications. - Benefits: "What We Offer" includes benefits. - Pay: base salary range. - Schedule: maybe hybrid/flexible working arrangements. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, accommodation, etc. Also remove "Apply now and join us..." maybe considered application instructions? It says remove application instructions. So we should drop the "Apply now and join us as we grow the economy that runs on code." line. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: Who We Are: description of Galaxy Digital Inc. (global leader...). This is company overview; maybe not needed as a section? Could be part of About the role? But we could include as a brief intro paragraph before sections. The instruction: "Prefer a few substantive sections over many thin ones." We could include a
for company overview before headings. What We Value: culture values list. Could be part of About the role or maybe a separate section like "Culture". But not in prescribed headings. Might be better to incorporate into About the role paragraph. Who You Are: description of role (Member of Technical Staff, Forward Deployed Lead). This is role overview. What You’ll Do: responsibilities list. What We’re Looking For: requirements. Bonus Points: additional nice-to-have. What We Offer: benefits. Base Salary Range: pay. Hybrid/Flexible Working Arrangements: schedule. Flexible Time Off (paid) etc are benefits. We need to use
- for any list of duties/requirements/benefits.
We need to use
for prose. We must not create sections with filler like "commensurate with experience". The Pay section: we have base salary range $215,000 - $285,000 USD. That's specific, so we can include Pay section. Schedule: we have hybrid/flexible working arrangements, willingness to travel 25-40%, flexible time off. That's schedule info. Benefits: list of benefits: competitive base salary and discretionary bonus (but that's pay), hybrid/flexible working arrangements (maybe schedule), flexible time off (paid), 3% 401(k) company contribution, company-paid health and protective benefits for employees, partners, and other dependents, generous paid parental leave, competitive family planning benefits for US employees, opportunities to learn about the Crypto industry, smart entrepreneurial colleagues, free daily snacks and weekly breakfasts/lunches, employee resource groups, free coaching and counseling sessions through Headspace. We should separate benefits from pay and schedule. Thus sections: - About the role (prose: combine Who We Are, What We Value, Who You Are maybe). Could be a paragraph. - Responsibilities (
Responsibilities
with- of duties from What You’ll Do).
- Requirements (
Requirements
with- from What We’re Looking For).
- Qualifications (
Qualifications
maybe from Bonus Points? Or combine with Requirements. But we need to avoid thin sections. Could combine Requirements and Qualifications into one section? But instruction says use headings like Requirements, Qualifications, Skills. Could have Requirements and Qualifications separate if we have content. Bonus Points could be Qualifications. - Benefits (Benefits
with- of benefits).
- Pay (
Pay
withbase salary range). - Schedule (
Schedule
withhybrid/flexible, travel 25-40%, flexible time off). We must not include sections with filler. All have content. Now we need to ensure we don't repeat job title as heading. Not using. We must not include Job ID etc. Now produce HTML. Let's craft content. About the role paragraph: combine Who We Are, What We Value, Who You Are. Who We Are: "Galaxy Digital Inc. (Nasdaq: GLXY) is a global leader in digital assets and data center infrastructure, growing the economy that runs on code. Galaxy delivers the onchain infrastructure that connects institutions to digital assets, including trading, advisory, asset management, staking, self-custody, and tokenization. Galaxy also develops and operates data center infrastructure to power AI and HPC workloads. Anchored by its Helios campus in Texas, Galaxy is building a multi-gigawatt pipeline of more than 5.7 GW of potential capacity, positioning it among the largest and fastest-growing data center developers in North America. The Company is headquartered in New York City, with offices across North America, Europe, the Middle East, and Asia." What We Value: "We are a diverse team of free thinkers, and fast movers united to help investors and creators energize the global economy. We are looking for individuals who thrive in a culture of builders and overachievers and embrace high performance, transparent feedback, and a mission-first approach. Our culture shapes our way of working and gets us where we want to be. Seek Excellence. Be Selective To Be Effective. Be Highly Aligned, Loosely Coupled. Disagree Transparently. Encourage Independent Decision-Making. Build Dream Teams." Who You Are: "The Member of Technical Staff, Forward Deployed Lead is the de facto CEO of their pod within Galaxy Edge — a small, senior team focused on one client engagement or one innovation bet. In this role, you will own product direction, technical standards, client relationships, and account growth, working alongside a dedicated Delivery Lead who handles timelines and execution. You will rotate between our two verticals — Forward Deployed Product & Engineering and R&D & Innovation — carrying hard-won market and technical context across the boundary. You will partner closely with Tier-1 financial institution stakeholders from engineers to C-suite executives, translating their needs in custody, settlement, tokenization, and trading into buildable roadmaps. This is a deliberately hybrid role requiring a hands-on startup CTO mindset combined with the commercial instinct to grow accounts and turn delivered trust into the next engagement." We can combine into a few paragraphs. Now Responsibilities: list from What You’ll Do: - Own product and technical direction: translate institutional needs — custody, settlement, tokenization, trading, and regulatory context — into a buildable roadmap; set the technical bar, make hard design calls, and stay in the code when it matters - Drive commercial and account growth: run your account like a business, identify expansion opportunities, advise senior client stakeholders (CTO, COO, Head of Digital Assets), and convert delivered trust into the next engagement - Lead client and executive relationships: run discovery from engineers to the C-suite, define success in their terms (adoption, risk, cost, time-to-value), and navigate complex regulated organizations to alignment - Rotate into R&D and Innovation: lead 0-to-1 product creation on frontier blockchain and AI, and codify learnings into reusable components and playbooks that feed back into client delivery - Serve as the voice of the customer back into Galaxy’s product organization, translating delivered insights into what the firm builds next - Embrace and champion the thoughtful adoption of AI to improve team performance and business outcomes. - Leverage AI tools (e.g., generative AI, automation platforms, data copilots) to improve productivity, decision-making, and output quality in your day-to-day work. Now Requirements: from What We’re Looking For: - Proven track record of owning outcomes end to end in ambiguous, high-stakes settings - Real technical depth — you’ve shipped production software and can lead engineers credibly - Commercial instinct — you’ve turned delivered work into expanded scope or revenue - Executive presence — fluent from a whiteboard to a C-suite briefing - Founder-grade agency and low ego — you find a path when none is obvious and care about the outcome, not the credit - Typically 6+ years across forward-deployed/solutions engineering, technical PM, and client-facing delivery; shape of ownership matters more than years - Willingness to travel approximately 25–40% of the time Now Qualifications (Bonus Points): - Experience in digital assets or blockchain infrastructure - Prior delivery experience into Tier-1 financial institutions - Hands-on production LLM or AI agent experience - Technical founder or quota-carrying solutions architect background - Fluency in custody, settlement, payments rails, tokenization, or trading systems Now Benefits: from What We Offer (excluding base salary and discretionary bonus maybe separate pay). But we can include all benefits except base salary (pay) and schedule items. Benefits list: - Hybrid/Flexible Working Arrangements (but that's schedule) - Flexible Time Off (paid) - 3% 401(k) company contribution - Company-paid health and protective benefits for employees, partners, and other dependents - Generous paid Parental Leave - Competitive family planning benefits for US employees - Opportunities to learn about the Crypto industry - Smart, entrepreneurial, and fun colleagues - Free daily snacks and weekly breakfasts/lunches - Employee Resource Groups - Free coaching and counseling sessions through Headspace We might also include discretionary bonus as part of pay. Now Pay: base salary range $215,000 - $285,000 USD. Also mention discretionary bonus? Could include in Pay section: "Competitive base salary and discretionary bonus". But we have base salary range. We'll include both. Now Schedule: hybrid/flexible working arrangements, willingness to travel approximately 25–40% of the time, flexible time off (paid). Could also mention flexible time off as benefit but okay. We must not create sections with filler like "commensurate with experience". We have specific base salary range, good. Now output HTML. Structure:
Company overview paragraph...
Culture paragraph...
Role overview paragraph...
ThenResponsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine. Let's craft paragraphs. Paragraph 1 (Who We Are): combine. Paragraph 2 (What We