Third Party Risk Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings. The posting doesn't have explicit headings but we can infer sections: About the role (intro), Responsibilities (list of duties), Requirements (hard requirements), Qualifications? maybe not separate. Skills? maybe not. Benefits (what we offer). Pay (compensation range). Schedule? Not present. So we should include sections only if real content.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive info, not invent or summarize away detail. So we need to include details like inventory reconciliation, onboarding, due diligence, audit oversight, SME reviews, BCDR, fourth party DDQ, SLA, issues, reverse due diligence, first 90 days breakdown, who will thrive traits, hard requirements list, pay transparency sentence, benefits list.
We must use - for any list of duties/requirements/benefits, and
for prose.
We must not include filler like "commensurate with experience". Not present.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: annual US base salary range $150,000-$250,000 + equity. Benefits are stated: relocation support, visa support, latest Apple gear, lunch benefit, gym benefit, beautiful office, 4x on-/offsites per year, annual development budget, plus localized benefits: comprehensive medical, dental, vision insurance and 401(k). So we can have Benefits section.
We should not include EEO statement.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
... intro paragraph describing Augustus and role overview.
Then Responsibilities: list of duties.
Then Who Will Thrive At Augustus? maybe as "Who will thrive" but we can use Who will thrive
or maybe "Qualifications"? But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. "Who will thrive" could be under Qualifications or Skills? It's more about traits. Could be under Qualifications. But we can also create a section "Who will thrive" if not matching allowed headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list, but we should prefer those. However we can still use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. So we need to map:
- About the role: intro.
- Responsibilities: list of duties.
- Requirements: hard requirements.
- Qualifications: maybe "Who will thrive" traits? Or we could put "Who will thrive" under Qualifications.
- Skills: maybe not needed.
- Benefits: perks.
- Pay: compensation range.
- Schedule: not present, so omit.
We should not create empty sections.
Thus:
About the role
Few people get to build a bank from scratch... (the introductory paragraph up to "Now, we are building the US team from the ground up, while continuing to grow rapidly in Europe.") That's substantive.
Then Responsibilities: list of duties bullet points.
Then Requirements: hard requirements bullet list.
Then Qualifications: who will thrive traits bullet list.
Then Benefits: what we offer bullet list.
Then Pay: compensation range paragraph.
We must not include duplicated lines. Ensure we preserve all details.
Let's extract the intro paragraph: "Few people get to build a bank from scratch. Even fewer get to build one at a moment when banking itself is being reinvented. The Dollar is the best product in the history of the world - there is infinite global demand. But International Fintechs and non-US banks are left with two unsatisfying options to access it: Either they build on legacy clearing banks that are slow and unreliable, or they interface with middleware providers that don’t move and hold the dollars directly, but themselves rely on underlying legacy banks. Augustus collapses this stack by combining two things: A real, national bank charter (in organization), and Marble, our proprietary core banking system, built around intelligence, made of code. We are a group of operators, unicorn early employees, ex-founders and people who walked away from degrees because they believe this is an industry and career defining opportunity. We are backed with more than $200M from Peter Thiel's Valar Ventures, Tiger Global, Hummingbird, QED, Creandum, and the founders of Nubank, Ramp, Deel, Circle, Fluidstack, Fuse, and n8n. We are regulated in Europe and live with Euro and Stablecoin clearing today. Now, we are building the US team from the ground up, while continuing to grow rapidly in Europe."
That's the intro.
Then "The Role" heading: we can incorporate into Responsibilities? Actually "The Role You own the mechanics..." That's a paragraph describing role. Could be part of About the role or separate. But we already used About the role for company intro. Maybe we should put role description under About the role as well. But we need to avoid duplication. Could combine.
Better: About the role includes company overview and role overview. Then Responsibilities list.
Let's craft About the role paragraph: combine company overview and role overview: "Few people get to build a bank from scratch... Now, we are building the US team from the ground up, while continuing to grow rapidly in Europe. The Role You own the mechanics that make the TPRM program run day to day. You are the person who keeps the vendor and partner inventory reconciled, moves relationships through onboarding and due diligence, coordinates SME reviews across every function that touches third-party risk, tracks BCDR posture on every critical vendor, and keeps the TPRM issues pipeline current." That's a bit long but okay.
Then Responsibilities: list of duties bullet points from "You own:" list.
We need to preserve all bullet items: Inventory, Onboarding, Initial & Ongoing Due Diligence, Audit Oversight, SME Reviews, BCDR, Fourth Party Due Diligence, Vendor DDQ & Partner DDQ, SLA, Issues, Reverse Due Diligence.
We should format each as
- with the description.
Then "Your first 90 days" could be part of Responsibilities? But it's a timeline. Could be its own section maybe under Responsibilities or Qualifications? But we have no heading for timeline. Could include as a paragraph under Responsibilities? But instruction says use
- for any list of duties/requirements/benefits. The first 90 days is a list of time-bound milestones; could be a list. We could treat as a list under a heading "First 90 days" but not in allowed headings. However we could incorporate into Responsibilities as a list? Might be okay to add a section "First 90 days" as
First 90 days
though not in examples but maybe allowed. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says prefer those. To be safe, we could embed the first 90 days as a paragraph under Responsibilities? But it's a list; we could make a under Responsibilities with sub-items? Might be messy.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine first 90 days into Responsibilities as a paragraph describing the ramp-up. But we need to preserve all substantive information; we can summarize but not invent or summarize away detail. Summarizing might be okay if we keep details? The instruction says do NOT invent or summarize away detail. So we must keep the detail, not summarize away. So we need to keep the weeks breakdown.
Thus we need a section for first 90 days. Could use heading "First 90 days". Even if not in examples, it's still a section heading. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, just gives examples. So we can use First 90 days
.
Similarly "Who Will Thrive At Augustus" could be under Qualifications or Skills. But we can also make a heading "Who will thrive". However we already have Qualifications heading; we could put the traits there.
Let's decide sections:
- About the role (company + role overview)
- Responsibilities (list of duties)
- First 90 days (list of weeks)
- Who will thrive (traits) maybe under Qualifications
- Requirements (hard requirements)
- Benefits (perks)
- Pay (compensation)
We need to avoid duplicate content.
Let's extract "Who Will Thrive At Augustus" bullet traits: Relentless, Set The Bar, Shape The Game, Systems First, plus bullet list of "This role is for you if:" and "This is not for you if:" We need to preserve all.
We can put that under Qualifications as a list.
Now Requirements: hard requirements bullet list.
Now Benefits: "What we offer" bullet list plus "Additional to the global benefits above, we offer localized benefits such as comprehensive medical, dental, and vision insurance and a 401(k) retirement plan for our US team." Also maybe include "Perks & Benefits:" list.
Now Pay: "Pay transparency Compensation packages at Augustus include base salary, equity, and benefits. New hire offers are made based on a candidate's experience, expertise, and geographic location. The annual US base salary range for this role is $150,000-$250,000 + equity." Also later "Compensation Range: $150K - $250K". We'll keep the detailed paragraph.
Now ensure we don't include EEO statement.
Now produce HTML.
Let's craft.
We'll need to escape any HTML special characters like & but fine.
Let's write:
About the role
Few people get to build a bank from scratch. Even fewer get to build one at a moment when banking itself is being reinvented. The Dollar is the best product in the history of the world - there is infinite global demand. But International Fintechs and non-US banks are left with two unsatisfying options to access it: Either they build on legacy clearing banks that are slow and unreliable, or they interface with middleware providers that don’t move and hold the dollars directly, but themselves rely on underlying legacy banks. Augustus collapses this stack by combining two things: A real, national bank charter (in organization), and Marble, our proprietary core banking system, built around intelligence, made of code.
for prose. We must not include filler like "commensurate with experience". Not present. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: annual US base salary range $150,000-$250,000 + equity. Benefits are stated: relocation support, visa support, latest Apple gear, lunch benefit, gym benefit, beautiful office, 4x on-/offsites per year, annual development budget, plus localized benefits: comprehensive medical, dental, vision insurance and 401(k). So we can have Benefits section. We should not include EEO statement. We need to output only HTML fragment, no /, no markdown fences. Let's craft:
About the role
... intro paragraph describing Augustus and role overview.
Then Responsibilities: list of duties. Then Who Will Thrive At Augustus? maybe as "Who will thrive" but we can useWho will thrive
or maybe "Qualifications"? But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. "Who will thrive" could be under Qualifications or Skills? It's more about traits. Could be under Qualifications. But we can also create a section "Who will thrive" if not matching allowed headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list, but we should prefer those. However we can still use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. So we need to map:
- About the role: intro.
- Responsibilities: list of duties.
- Requirements: hard requirements.
- Qualifications: maybe "Who will thrive" traits? Or we could put "Who will thrive" under Qualifications.
- Skills: maybe not needed.
- Benefits: perks.
- Pay: compensation range.
- Schedule: not present, so omit.
We should not create empty sections.
Thus:
About the role
About the role
Few people get to build a bank from scratch... (the introductory paragraph up to "Now, we are building the US team from the ground up, while continuing to grow rapidly in Europe.") That's substantive. Then Responsibilities: list of duties bullet points. Then Requirements: hard requirements bullet list. Then Qualifications: who will thrive traits bullet list. Then Benefits: what we offer bullet list. Then Pay: compensation range paragraph. We must not include duplicated lines. Ensure we preserve all details. Let's extract the intro paragraph: "Few people get to build a bank from scratch. Even fewer get to build one at a moment when banking itself is being reinvented. The Dollar is the best product in the history of the world - there is infinite global demand. But International Fintechs and non-US banks are left with two unsatisfying options to access it: Either they build on legacy clearing banks that are slow and unreliable, or they interface with middleware providers that don’t move and hold the dollars directly, but themselves rely on underlying legacy banks. Augustus collapses this stack by combining two things: A real, national bank charter (in organization), and Marble, our proprietary core banking system, built around intelligence, made of code. We are a group of operators, unicorn early employees, ex-founders and people who walked away from degrees because they believe this is an industry and career defining opportunity. We are backed with more than $200M from Peter Thiel's Valar Ventures, Tiger Global, Hummingbird, QED, Creandum, and the founders of Nubank, Ramp, Deel, Circle, Fluidstack, Fuse, and n8n. We are regulated in Europe and live with Euro and Stablecoin clearing today. Now, we are building the US team from the ground up, while continuing to grow rapidly in Europe." That's the intro. Then "The Role" heading: we can incorporate into Responsibilities? Actually "The Role You own the mechanics..." That's a paragraph describing role. Could be part of About the role or separate. But we already used About the role for company intro. Maybe we should put role description under About the role as well. But we need to avoid duplication. Could combine. Better: About the role includes company overview and role overview. Then Responsibilities list. Let's craft About the role paragraph: combine company overview and role overview: "Few people get to build a bank from scratch... Now, we are building the US team from the ground up, while continuing to grow rapidly in Europe. The Role You own the mechanics that make the TPRM program run day to day. You are the person who keeps the vendor and partner inventory reconciled, moves relationships through onboarding and due diligence, coordinates SME reviews across every function that touches third-party risk, tracks BCDR posture on every critical vendor, and keeps the TPRM issues pipeline current." That's a bit long but okay. Then Responsibilities: list of duties bullet points from "You own:" list. We need to preserve all bullet items: Inventory, Onboarding, Initial & Ongoing Due Diligence, Audit Oversight, SME Reviews, BCDR, Fourth Party Due Diligence, Vendor DDQ & Partner DDQ, SLA, Issues, Reverse Due Diligence. We should format each as
- for any list of duties/requirements/benefits. The first 90 days is a list of time-bound milestones; could be a list. We could treat as a list under a heading "First 90 days" but not in allowed headings. However we could incorporate into Responsibilities as a list? Might be okay to add a section "First 90 days" as
First 90 days
though not in examples but maybe allowed. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says prefer those. To be safe, we could embed the first 90 days as a paragraph under Responsibilities? But it's a list; we could make a
- under Responsibilities with sub-items? Might be messy.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine first 90 days into Responsibilities as a paragraph describing the ramp-up. But we need to preserve all substantive information; we can summarize but not invent or summarize away detail. Summarizing might be okay if we keep details? The instruction says do NOT invent or summarize away detail. So we must keep the detail, not summarize away. So we need to keep the weeks breakdown.
Thus we need a section for first 90 days. Could use heading "First 90 days". Even if not in examples, it's still a section heading. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, just gives examples. So we can use
First 90 days
. Similarly "Who Will Thrive At Augustus" could be under Qualifications or Skills. But we can also make a heading "Who will thrive". However we already have Qualifications heading; we could put the traits there. Let's decide sections: - About the role (company + role overview) - Responsibilities (list of duties) - First 90 days (list of weeks) - Who will thrive (traits) maybe under Qualifications - Requirements (hard requirements) - Benefits (perks) - Pay (compensation) We need to avoid duplicate content. Let's extract "Who Will Thrive At Augustus" bullet traits: Relentless, Set The Bar, Shape The Game, Systems First, plus bullet list of "This role is for you if:" and "This is not for you if:" We need to preserve all. We can put that under Qualifications as a list. Now Requirements: hard requirements bullet list. Now Benefits: "What we offer" bullet list plus "Additional to the global benefits above, we offer localized benefits such as comprehensive medical, dental, and vision insurance and a 401(k) retirement plan for our US team." Also maybe include "Perks & Benefits:" list. Now Pay: "Pay transparency Compensation packages at Augustus include base salary, equity, and benefits. New hire offers are made based on a candidate's experience, expertise, and geographic location. The annual US base salary range for this role is $150,000-$250,000 + equity." Also later "Compensation Range: $150K - $250K". We'll keep the detailed paragraph. Now ensure we don't include EEO statement. Now produce HTML. Let's craft. We'll need to escape any HTML special characters like & but fine. Let's write:About the role
Few people get to build a bank from scratch. Even fewer get to build one at a moment when banking itself is being reinvented. The Dollar is the best product in the history of the world - there is infinite global demand. But International Fintechs and non-US banks are left with two unsatisfying options to access it: Either they build on legacy clearing banks that are slow and unreliable, or they interface with middleware providers that don’t move and hold the dollars directly, but themselves rely on underlying legacy banks. Augustus collapses this stack by combining two things: A real, national bank charter (in organization), and Marble, our proprietary core banking system, built around intelligence, made of code.