IT & Security Manager
FAR.AI · United States · 1 mo ago
RemoteRemoteInformation Technology$185k–$250k/yrFull-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.
We need to parse the posting.
We have "About Us" description: that's about the organization, not necessarily a section heading. The instruction: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
We have "About Us" description: that's about the organization, not necessarily a section heading. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can have sections: About the role (maybe from "The Role" paragraph), Responsibilities (Key Responsibilities), Requirements (maybe Must-Have Qualifications?), Qualifications (maybe Nice-to-Have?), Skills (maybe not explicit), Benefits (Benefits*), Pay (Compensation Range), Schedule (maybe not present). Also we could have "About Us" but not in list; but we could include as a section? The instruction says use those headings for sections; but we can include other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely we should stick to those. However we have "About Us" content that is substantive; maybe we can put it under "About the role"? Actually "About the role" is separate from "About Us". The posting includes "About Us" describing the organization. Could be considered "About the role"? Not exactly. But we could create a section "About the organization" but not in list; maybe we should include as a paragraph without heading? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could also use other headings if needed, but better to follow examples. However we have substantive content about the organization; we could put it under a heading "About the role"? That would be inaccurate. Perhaps we can include a heading "About Us" as even though not in list; but the instruction says use for section headings (e.g. ...). It doesn't say only those. So we can use for any section heading, but we should follow the pattern. I'd include sections: About Us, About the role, Responsibilities, Requirements (Must-Have Qualifications), Qualifications (Nice-to-Have), Benefits, Pay. Schedule not present, so omit.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements (Must-Have Qualifications) we need list. For Nice-to-Have Qualifications also list. For Benefits list.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About Us: The paragraph starting "FAR.AI is a non-profit AI research institute..." up to "...and supporting the community through targeted grants to technical researchers." That's the About Us.
We need to keep all details. We'll put that in
under
About Us
.
About the role: The paragraph starting "The Role We are hiring an IT & Security Manager..." up to "...You are the first person on this team, and you will shape what it becomes." Also includes "Why This Role / Why Now" paragraph? That could be part of About the role or separate. But we can include under About the role as well. However we might separate "Why This Role / Why Now" as its own section? Not in list. Probably include under About the role.
Responsibilities: The bullet list under "Key Responsibilities". Items:
- IT operations: Own our core internal systems end-to-end: accounts, devices, identity and access management, onboarding and offboarding, the FAR.Labs office network, and the daily support that keeps a growing team working.
- Security remediation: Work through our known security gaps, prioritized by risk. Access controls, endpoint hardening, data protection, data governance, and vendor and application risk are the near-term substance.
- Self-serve infrastructure: Reduce the amount of work that has to route through you. Partner with Business Operations and other teams to design systems and processes that reduce manual work.
- Cross-functional partnership: Work with team leads across Research, Operations, Futures (events), and Communications to understand how they actually work and help them build securely inside their own domains. You work cross-functionally to drive AI adoption.
- Building the team: Hire the in-person IT Coordinator, then manage and develop them. You get to define the role in accordance with the organization’s needs. Over time, this team may grow.
- Internal communication and change management: Roll out changes in a way people can live with. You communicate clearly about what is changing and why, and establish feedback loops to continue iterating post-deployment.
We need to preserve all details. We'll put each as - .
Requirements (Must-Have Qualifications): The list after "Must-Have Qualifications". Items:
- You have owned IT and security at a technical organization of roughly 30 to 150 people, ideally as the first or sole person to do so.
- You built the function yourself, without a team already in place around you.
- You are comfortable in a terminal and can code. You do not need to be an excellent engineer, but you are not afraid of it. You reach for automation before a manual process.
- You think about the people using what you build.
- You go after root causes instead of managing symptoms; you can point to a system you redesigned so that a whole class of requests stopped arriving, and you treat that as ongoing work rather than a one-time project.
- You have done hands-on security work driven by threat models. You can say who you were defending against and what you chose not to spend effort on, not just which frameworks you mapped to.
- You have implemented and owned core identity and device infrastructure, including MDM and SSO.
- You are fast and service-oriented. You read the support queue as information about the system, and the people you have supported would say you were reliable.
- You communicate clearly across technical and non-technical audiences.
- You can point to a time when you rolled out something that made someone's day harder, and you brought them along anyway.
- You use LLMs regularly in your own work and have an opinion on where they help and where they do not.
We need to keep all details.
Qualifications (Nice-to-Have Qualifications): list after "Nice-to-Have Qualifications". Items:
- You care about AI safety or security, or you are demonstrably curious about it. You understand why this work matters and you help assess the value of the risk we’re taking on.
- You have hired, managed, or mentored a junior teammate.
- You engage with security as a craft outside of work: your own compute build or a home lab, capture-the-flag competitions, side projects, or conferences like DEF CON or CCC.
- You have experience obtaining SOC 2 Type 2 and complying with GDPR. We are open to contracting out much of the work in obtaining certifications – our primary goal is to improve our actual security posture, not achieve certifications, but they may be a necessary step in certain engagements.
- You have experience in fast-paced environments. You've worked in startups, nimble nonprofits, or high-growth teams before and can adapt to change quickly.
- You have worked in a research organization, a deep-tech startup, or a similarly technical environment.
We need to keep all details.
Benefits: The list after "Benefits*". Items:
- 🩺 Health Insurance - 94% of Insurance premium paid by Organization commencing within 1 month after your start date
- 💰 Retirement - 401(k) plan with up to 2% match
- 🏝️ PTO - 25 days Paid Time Off per year, accrued weekly and up to 10 days of paid sick leave per year
- 🚼 Paid Leave - Paid Bereavement, Family, Medical and Pregnancy Disability Leave
- 🖥️ WFH Stipend & Equipment - Work computer and stipend provided for eligible employees
- 🍽️ Catered Meals (Berkeley Office Only) - Catered lunches and dinners on workdays at our office (Available only to full-time employees located in the US)
We need to keep all details. The emojis can stay as part of text.
Pay: Compensation Range: $185K - $250K. We'll put under
Pay
with .
Schedule: Not present, so omit.
We also need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Interview process", "References", "If you have any questions..." etc. Those are application instructions; we should remove them. Also "Compensation Range:" we keep as Pay.
We should also remove the "*Some candidates will have a short final conversation after that." etc. That's part of interview process; remove.
Also remove "Benefits*" footnote maybe keep but it's part of benefits heading; we can keep the asterisk? Probably remove the asterisk as it's just a footnote marker. We'll keep the benefits list as is.
Now construct HTML.
We'll start with
About Us
then ...
.
Then About the role
then ...
containing the role description plus why this role/why now.
We need to combine the role description and why this role/why now into one paragraph? Could be multiple paragraphs. We'll keep as maybe multiple
under same heading? The instruction: Use
for prose. So we can have multiple
elements.
Thus after heading, we can have
The Role ...
then Why This Role / Why Now ...
.
Then Responsibilities
then with - items.
Then
Requirements
then with Must-Have Qualifications items.
Then Qualifications
then with Nice-to-Have Qualifications items.
Then Benefits
then with benefits items.
Then Pay
then Compensation Range: $185K - $250K
.
Make sure to preserve all details exactly.
Check for any duplicated lines: The posting includes "About Us" repeated? Not really.
Check for any boilerplate like "EEO" etc: Not present.
Now produce HTML.
We need to be careful with special characters like & in "IT & Security Manager". Should we escape? In HTML, & should be &. So "IT & Security Manager" => "IT & Security Manager". Also "FAR.Labs" includes a dot; fine.
Also "FAR.Labs’ office network" includes a curly apostrophe ’; we can keep as is or replace with ’. Safer to keep as is; but HTML will treat as character; okay.
We'll output as plain text.
Let's craft.
About Us paragraph: copy exactly.
"FAR.AI is a non-profit AI research institute working to ensure advanced AI is safe and beneficial for everyone. Our mission is to facilitate breakthrough AI safety research, advance global understanding of AI risks and solutions, and foster a coordinated global response. We’re structured to support that work from early research through real-world adoption: Independent by design. We can pursue what's most impactful based on our theory of change and share what we find publicly
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely we should stick to those. However we have "About Us" content that is substantive; maybe we can put it under "About the role"? Actually "About the role" is separate from "About Us". The posting includes "About Us" describing the organization. Could be considered "About the role"? Not exactly. But we could create a section "About the organization" but not in list; maybe we should include as a paragraph without heading? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could also use other headings if needed, but better to follow examples. However we have substantive content about the organization; we could put it under a heading "About the role"? That would be inaccurate. Perhaps we can include a heading "About Us" as even though not in list; but the instruction says use for section headings (e.g. ...). It doesn't say only those. So we can use for any section heading, but we should follow the pattern. I'd include sections: About Us, About the role, Responsibilities, Requirements (Must-Have Qualifications), Qualifications (Nice-to-Have), Benefits, Pay. Schedule not present, so omit.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements (Must-Have Qualifications) we need list. For Nice-to-Have Qualifications also list. For Benefits list.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About Us: The paragraph starting "FAR.AI is a non-profit AI research institute..." up to "...and supporting the community through targeted grants to technical researchers." That's the About Us.
We need to keep all details. We'll put that in
under
About Us
.
About the role: The paragraph starting "The Role We are hiring an IT & Security Manager..." up to "...You are the first person on this team, and you will shape what it becomes." Also includes "Why This Role / Why Now" paragraph? That could be part of About the role or separate. But we can include under About the role as well. However we might separate "Why This Role / Why Now" as its own section? Not in list. Probably include under About the role.
Responsibilities: The bullet list under "Key Responsibilities". Items:
- IT operations: Own our core internal systems end-to-end: accounts, devices, identity and access management, onboarding and offboarding, the FAR.Labs office network, and the daily support that keeps a growing team working.
- Security remediation: Work through our known security gaps, prioritized by risk. Access controls, endpoint hardening, data protection, data governance, and vendor and application risk are the near-term substance.
- Self-serve infrastructure: Reduce the amount of work that has to route through you. Partner with Business Operations and other teams to design systems and processes that reduce manual work.
- Cross-functional partnership: Work with team leads across Research, Operations, Futures (events), and Communications to understand how they actually work and help them build securely inside their own domains. You work cross-functionally to drive AI adoption.
- Building the team: Hire the in-person IT Coordinator, then manage and develop them. You get to define the role in accordance with the organization’s needs. Over time, this team may grow.
- Internal communication and change management: Roll out changes in a way people can live with. You communicate clearly about what is changing and why, and establish feedback loops to continue iterating post-deployment.
We need to preserve all details. We'll put each as - .
Requirements (Must-Have Qualifications): The list after "Must-Have Qualifications". Items:
- You have owned IT and security at a technical organization of roughly 30 to 150 people, ideally as the first or sole person to do so.
- You built the function yourself, without a team already in place around you.
- You are comfortable in a terminal and can code. You do not need to be an excellent engineer, but you are not afraid of it. You reach for automation before a manual process.
- You think about the people using what you build.
- You go after root causes instead of managing symptoms; you can point to a system you redesigned so that a whole class of requests stopped arriving, and you treat that as ongoing work rather than a one-time project.
- You have done hands-on security work driven by threat models. You can say who you were defending against and what you chose not to spend effort on, not just which frameworks you mapped to.
- You have implemented and owned core identity and device infrastructure, including MDM and SSO.
- You are fast and service-oriented. You read the support queue as information about the system, and the people you have supported would say you were reliable.
- You communicate clearly across technical and non-technical audiences.
- You can point to a time when you rolled out something that made someone's day harder, and you brought them along anyway.
- You use LLMs regularly in your own work and have an opinion on where they help and where they do not.
We need to keep all details.
Qualifications (Nice-to-Have Qualifications): list after "Nice-to-Have Qualifications". Items:
- You care about AI safety or security, or you are demonstrably curious about it. You understand why this work matters and you help assess the value of the risk we’re taking on.
- You have hired, managed, or mentored a junior teammate.
- You engage with security as a craft outside of work: your own compute build or a home lab, capture-the-flag competitions, side projects, or conferences like DEF CON or CCC.
- You have experience obtaining SOC 2 Type 2 and complying with GDPR. We are open to contracting out much of the work in obtaining certifications – our primary goal is to improve our actual security posture, not achieve certifications, but they may be a necessary step in certain engagements.
- You have experience in fast-paced environments. You've worked in startups, nimble nonprofits, or high-growth teams before and can adapt to change quickly.
- You have worked in a research organization, a deep-tech startup, or a similarly technical environment.
We need to keep all details.
Benefits: The list after "Benefits*". Items:
- 🩺 Health Insurance - 94% of Insurance premium paid by Organization commencing within 1 month after your start date
- 💰 Retirement - 401(k) plan with up to 2% match
- 🏝️ PTO - 25 days Paid Time Off per year, accrued weekly and up to 10 days of paid sick leave per year
- 🚼 Paid Leave - Paid Bereavement, Family, Medical and Pregnancy Disability Leave
- 🖥️ WFH Stipend & Equipment - Work computer and stipend provided for eligible employees
- 🍽️ Catered Meals (Berkeley Office Only) - Catered lunches and dinners on workdays at our office (Available only to full-time employees located in the US)
We need to keep all details. The emojis can stay as part of text.
Pay: Compensation Range: $185K - $250K. We'll put under
Pay
with .
Schedule: Not present, so omit.
We also need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Interview process", "References", "If you have any questions..." etc. Those are application instructions; we should remove them. Also "Compensation Range:" we keep as Pay.
We should also remove the "*Some candidates will have a short final conversation after that." etc. That's part of interview process; remove.
Also remove "Benefits*" footnote maybe keep but it's part of benefits heading; we can keep the asterisk? Probably remove the asterisk as it's just a footnote marker. We'll keep the benefits list as is.
Now construct HTML.
We'll start with
About Us
then ...
.
Then About the role
then ...
containing the role description plus why this role/why now.
We need to combine the role description and why this role/why now into one paragraph? Could be multiple paragraphs. We'll keep as maybe multiple
under same heading? The instruction: Use
for prose. So we can have multiple
elements.
Thus after heading, we can have
The Role ...
then Why This Role / Why Now ...
.
Then Responsibilities
then with - items.
Then
Requirements
then with Must-Have Qualifications items.
Then Qualifications
then with Nice-to-Have Qualifications items.
Then Benefits
then with benefits items.
Then Pay
then Compensation Range: $185K - $250K
.
Make sure to preserve all details exactly.
Check for any duplicated lines: The posting includes "About Us" repeated? Not really.
Check for any boilerplate like "EEO" etc: Not present.
Now produce HTML.
We need to be careful with special characters like & in "IT & Security Manager". Should we escape? In HTML, & should be &. So "IT & Security Manager" => "IT & Security Manager". Also "FAR.Labs" includes a dot; fine.
Also "FAR.Labs’ office network" includes a curly apostrophe ’; we can keep as is or replace with ’. Safer to keep as is; but HTML will treat as character; okay.
We'll output as plain text.
Let's craft.
About Us paragraph: copy exactly.
"FAR.AI is a non-profit AI research institute working to ensure advanced AI is safe and beneficial for everyone. Our mission is to facilitate breakthrough AI safety research, advance global understanding of AI risks and solutions, and foster a coordinated global response. We’re structured to support that work from early research through real-world adoption: Independent by design. We can pursue what's most impactful based on our theory of change and share what we find publicly
even though not in list; but the instruction says use for section headings (e.g. ...). It doesn't say only those. So we can use for any section heading, but we should follow the pattern. I'd include sections: About Us, About the role, Responsibilities, Requirements (Must-Have Qualifications), Qualifications (Nice-to-Have), Benefits, Pay. Schedule not present, so omit.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements (Must-Have Qualifications) we need list. For Nice-to-Have Qualifications also list. For Benefits list.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About Us: The paragraph starting "FAR.AI is a non-profit AI research institute..." up to "...and supporting the community through targeted grants to technical researchers." That's the About Us.
We need to keep all details. We'll put that in
under
About Us
.
About the role: The paragraph starting "The Role We are hiring an IT & Security Manager..." up to "...You are the first person on this team, and you will shape what it becomes." Also includes "Why This Role / Why Now" paragraph? That could be part of About the role or separate. But we can include under About the role as well. However we might separate "Why This Role / Why Now" as its own section? Not in list. Probably include under About the role.
Responsibilities: The bullet list under "Key Responsibilities". Items:
- IT operations: Own our core internal systems end-to-end: accounts, devices, identity and access management, onboarding and offboarding, the FAR.Labs office network, and the daily support that keeps a growing team working.
- Security remediation: Work through our known security gaps, prioritized by risk. Access controls, endpoint hardening, data protection, data governance, and vendor and application risk are the near-term substance.
- Self-serve infrastructure: Reduce the amount of work that has to route through you. Partner with Business Operations and other teams to design systems and processes that reduce manual work.
- Cross-functional partnership: Work with team leads across Research, Operations, Futures (events), and Communications to understand how they actually work and help them build securely inside their own domains. You work cross-functionally to drive AI adoption.
- Building the team: Hire the in-person IT Coordinator, then manage and develop them. You get to define the role in accordance with the organization’s needs. Over time, this team may grow.
- Internal communication and change management: Roll out changes in a way people can live with. You communicate clearly about what is changing and why, and establish feedback loops to continue iterating post-deployment.
We need to preserve all details. We'll put each as - .
Requirements (Must-Have Qualifications): The list after "Must-Have Qualifications". Items:
- You have owned IT and security at a technical organization of roughly 30 to 150 people, ideally as the first or sole person to do so.
- You built the function yourself, without a team already in place around you.
- You are comfortable in a terminal and can code. You do not need to be an excellent engineer, but you are not afraid of it. You reach for automation before a manual process.
- You think about the people using what you build.
- You go after root causes instead of managing symptoms; you can point to a system you redesigned so that a whole class of requests stopped arriving, and you treat that as ongoing work rather than a one-time project.
- You have done hands-on security work driven by threat models. You can say who you were defending against and what you chose not to spend effort on, not just which frameworks you mapped to.
- You have implemented and owned core identity and device infrastructure, including MDM and SSO.
- You are fast and service-oriented. You read the support queue as information about the system, and the people you have supported would say you were reliable.
- You communicate clearly across technical and non-technical audiences.
- You can point to a time when you rolled out something that made someone's day harder, and you brought them along anyway.
- You use LLMs regularly in your own work and have an opinion on where they help and where they do not.
We need to keep all details.
Qualifications (Nice-to-Have Qualifications): list after "Nice-to-Have Qualifications". Items:
- You care about AI safety or security, or you are demonstrably curious about it. You understand why this work matters and you help assess the value of the risk we’re taking on.
- You have hired, managed, or mentored a junior teammate.
- You engage with security as a craft outside of work: your own compute build or a home lab, capture-the-flag competitions, side projects, or conferences like DEF CON or CCC.
- You have experience obtaining SOC 2 Type 2 and complying with GDPR. We are open to contracting out much of the work in obtaining certifications – our primary goal is to improve our actual security posture, not achieve certifications, but they may be a necessary step in certain engagements.
- You have experience in fast-paced environments. You've worked in startups, nimble nonprofits, or high-growth teams before and can adapt to change quickly.
- You have worked in a research organization, a deep-tech startup, or a similarly technical environment.
We need to keep all details.
Benefits: The list after "Benefits*". Items:
- 🩺 Health Insurance - 94% of Insurance premium paid by Organization commencing within 1 month after your start date
- 💰 Retirement - 401(k) plan with up to 2% match
- 🏝️ PTO - 25 days Paid Time Off per year, accrued weekly and up to 10 days of paid sick leave per year
- 🚼 Paid Leave - Paid Bereavement, Family, Medical and Pregnancy Disability Leave
- 🖥️ WFH Stipend & Equipment - Work computer and stipend provided for eligible employees
- 🍽️ Catered Meals (Berkeley Office Only) - Catered lunches and dinners on workdays at our office (Available only to full-time employees located in the US)
We need to keep all details. The emojis can stay as part of text.
Pay: Compensation Range: $185K - $250K. We'll put under
Pay
with .
Schedule: Not present, so omit.
We also need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Interview process", "References", "If you have any questions..." etc. Those are application instructions; we should remove them. Also "Compensation Range:" we keep as Pay.
We should also remove the "*Some candidates will have a short final conversation after that." etc. That's part of interview process; remove.
Also remove "Benefits*" footnote maybe keep but it's part of benefits heading; we can keep the asterisk? Probably remove the asterisk as it's just a footnote marker. We'll keep the benefits list as is.
Now construct HTML.
We'll start with
About Us
then ...
.
Then About the role
then ...
containing the role description plus why this role/why now.
We need to combine the role description and why this role/why now into one paragraph? Could be multiple paragraphs. We'll keep as maybe multiple
under same heading? The instruction: Use
for prose. So we can have multiple
elements.
Thus after heading, we can have
The Role ...
then Why This Role / Why Now ...
.
Then Responsibilities
then with - items.
Then
Requirements
then with Must-Have Qualifications items.
Then Qualifications
then with Nice-to-Have Qualifications items.
Then Benefits
then with benefits items.
Then Pay
then Compensation Range: $185K - $250K
.
Make sure to preserve all details exactly.
Check for any duplicated lines: The posting includes "About Us" repeated? Not really.
Check for any boilerplate like "EEO" etc: Not present.
Now produce HTML.
We need to be careful with special characters like & in "IT & Security Manager". Should we escape? In HTML, & should be &. So "IT & Security Manager" => "IT & Security Manager". Also "FAR.Labs" includes a dot; fine.
Also "FAR.Labs’ office network" includes a curly apostrophe ’; we can keep as is or replace with ’. Safer to keep as is; but HTML will treat as character; okay.
We'll output as plain text.
Let's craft.
About Us paragraph: copy exactly.
"FAR.AI is a non-profit AI research institute working to ensure advanced AI is safe and beneficial for everyone. Our mission is to facilitate breakthrough AI safety research, advance global understanding of AI risks and solutions, and foster a coordinated global response. We’re structured to support that work from early research through real-world adoption: Independent by design. We can pursue what's most impactful based on our theory of change and share what we find publicly
for any section heading, but we should follow the pattern. I'd include sections: About Us, About the role, Responsibilities, Requirements (Must-Have Qualifications), Qualifications (Nice-to-Have), Benefits, Pay. Schedule not present, so omit.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements (Must-Have Qualifications) we need list. For Nice-to-Have Qualifications also list. For Benefits list.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About Us: The paragraph starting "FAR.AI is a non-profit AI research institute..." up to "...and supporting the community through targeted grants to technical researchers." That's the About Us.
We need to keep all details. We'll put that in
under
About Us
.
About the role: The paragraph starting "The Role We are hiring an IT & Security Manager..." up to "...You are the first person on this team, and you will shape what it becomes." Also includes "Why This Role / Why Now" paragraph? That could be part of About the role or separate. But we can include under About the role as well. However we might separate "Why This Role / Why Now" as its own section? Not in list. Probably include under About the role.
Responsibilities: The bullet list under "Key Responsibilities". Items:
- IT operations: Own our core internal systems end-to-end: accounts, devices, identity and access management, onboarding and offboarding, the FAR.Labs office network, and the daily support that keeps a growing team working.
- Security remediation: Work through our known security gaps, prioritized by risk. Access controls, endpoint hardening, data protection, data governance, and vendor and application risk are the near-term substance.
- Self-serve infrastructure: Reduce the amount of work that has to route through you. Partner with Business Operations and other teams to design systems and processes that reduce manual work.
- Cross-functional partnership: Work with team leads across Research, Operations, Futures (events), and Communications to understand how they actually work and help them build securely inside their own domains. You work cross-functionally to drive AI adoption.
- Building the team: Hire the in-person IT Coordinator, then manage and develop them. You get to define the role in accordance with the organization’s needs. Over time, this team may grow.
- Internal communication and change management: Roll out changes in a way people can live with. You communicate clearly about what is changing and why, and establish feedback loops to continue iterating post-deployment.
We need to preserve all details. We'll put each as - .
Requirements (Must-Have Qualifications): The list after "Must-Have Qualifications". Items:
- You have owned IT and security at a technical organization of roughly 30 to 150 people, ideally as the first or sole person to do so.
- You built the function yourself, without a team already in place around you.
- You are comfortable in a terminal and can code. You do not need to be an excellent engineer, but you are not afraid of it. You reach for automation before a manual process.
- You think about the people using what you build.
- You go after root causes instead of managing symptoms; you can point to a system you redesigned so that a whole class of requests stopped arriving, and you treat that as ongoing work rather than a one-time project.
- You have done hands-on security work driven by threat models. You can say who you were defending against and what you chose not to spend effort on, not just which frameworks you mapped to.
- You have implemented and owned core identity and device infrastructure, including MDM and SSO.
- You are fast and service-oriented. You read the support queue as information about the system, and the people you have supported would say you were reliable.
- You communicate clearly across technical and non-technical audiences.
- You can point to a time when you rolled out something that made someone's day harder, and you brought them along anyway.
- You use LLMs regularly in your own work and have an opinion on where they help and where they do not.
We need to keep all details.
Qualifications (Nice-to-Have Qualifications): list after "Nice-to-Have Qualifications". Items:
- You care about AI safety or security, or you are demonstrably curious about it. You understand why this work matters and you help assess the value of the risk we’re taking on.
- You have hired, managed, or mentored a junior teammate.
- You engage with security as a craft outside of work: your own compute build or a home lab, capture-the-flag competitions, side projects, or conferences like DEF CON or CCC.
- You have experience obtaining SOC 2 Type 2 and complying with GDPR. We are open to contracting out much of the work in obtaining certifications – our primary goal is to improve our actual security posture, not achieve certifications, but they may be a necessary step in certain engagements.
- You have experience in fast-paced environments. You've worked in startups, nimble nonprofits, or high-growth teams before and can adapt to change quickly.
- You have worked in a research organization, a deep-tech startup, or a similarly technical environment.
We need to keep all details.
Benefits: The list after "Benefits*". Items:
- 🩺 Health Insurance - 94% of Insurance premium paid by Organization commencing within 1 month after your start date
- 💰 Retirement - 401(k) plan with up to 2% match
- 🏝️ PTO - 25 days Paid Time Off per year, accrued weekly and up to 10 days of paid sick leave per year
- 🚼 Paid Leave - Paid Bereavement, Family, Medical and Pregnancy Disability Leave
- 🖥️ WFH Stipend & Equipment - Work computer and stipend provided for eligible employees
- 🍽️ Catered Meals (Berkeley Office Only) - Catered lunches and dinners on workdays at our office (Available only to full-time employees located in the US)
We need to keep all details. The emojis can stay as part of text.
Pay: Compensation Range: $185K - $250K. We'll put under
Pay
with .
Schedule: Not present, so omit.
We also need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Interview process", "References", "If you have any questions..." etc. Those are application instructions; we should remove them. Also "Compensation Range:" we keep as Pay.
We should also remove the "*Some candidates will have a short final conversation after that." etc. That's part of interview process; remove.
Also remove "Benefits*" footnote maybe keep but it's part of benefits heading; we can keep the asterisk? Probably remove the asterisk as it's just a footnote marker. We'll keep the benefits list as is.
Now construct HTML.
We'll start with
About Us
then ...
.
Then About the role
then ...
containing the role description plus why this role/why now.
We need to combine the role description and why this role/why now into one paragraph? Could be multiple paragraphs. We'll keep as maybe multiple
under same heading? The instruction: Use
for prose. So we can have multiple
elements.
Thus after heading, we can have
The Role ...
then Why This Role / Why Now ...
.
Then Responsibilities
then with - items.
Then
Requirements
then with Must-Have Qualifications items.
Then Qualifications
then with Nice-to-Have Qualifications items.
Then Benefits
then with benefits items.
Then Pay
then Compensation Range: $185K - $250K
.
Make sure to preserve all details exactly.
Check for any duplicated lines: The posting includes "About Us" repeated? Not really.
Check for any boilerplate like "EEO" etc: Not present.
Now produce HTML.
We need to be careful with special characters like & in "IT & Security Manager". Should we escape? In HTML, & should be &. So "IT & Security Manager" => "IT & Security Manager". Also "FAR.Labs" includes a dot; fine.
Also "FAR.Labs’ office network" includes a curly apostrophe ’; we can keep as is or replace with ’. Safer to keep as is; but HTML will treat as character; okay.
We'll output as plain text.
Let's craft.
About Us paragraph: copy exactly.
"FAR.AI is a non-profit AI research institute working to ensure advanced AI is safe and beneficial for everyone. Our mission is to facilitate breakthrough AI safety research, advance global understanding of AI risks and solutions, and foster a coordinated global response. We’re structured to support that work from early research through real-world adoption: Independent by design. We can pursue what's most impactful based on our theory of change and share what we find publicly
under
About Us
. About the role: The paragraph starting "The Role We are hiring an IT & Security Manager..." up to "...You are the first person on this team, and you will shape what it becomes." Also includes "Why This Role / Why Now" paragraph? That could be part of About the role or separate. But we can include under About the role as well. However we might separate "Why This Role / Why Now" as its own section? Not in list. Probably include under About the role. Responsibilities: The bullet list under "Key Responsibilities". Items: - IT operations: Own our core internal systems end-to-end: accounts, devices, identity and access management, onboarding and offboarding, the FAR.Labs office network, and the daily support that keeps a growing team working. - Security remediation: Work through our known security gaps, prioritized by risk. Access controls, endpoint hardening, data protection, data governance, and vendor and application risk are the near-term substance. - Self-serve infrastructure: Reduce the amount of work that has to route through you. Partner with Business Operations and other teams to design systems and processes that reduce manual work. - Cross-functional partnership: Work with team leads across Research, Operations, Futures (events), and Communications to understand how they actually work and help them build securely inside their own domains. You work cross-functionally to drive AI adoption. - Building the team: Hire the in-person IT Coordinator, then manage and develop them. You get to define the role in accordance with the organization’s needs. Over time, this team may grow. - Internal communication and change management: Roll out changes in a way people can live with. You communicate clearly about what is changing and why, and establish feedback loops to continue iterating post-deployment. We need to preserve all details. We'll put each asPay
with. Schedule: Not present, so omit. We also need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Interview process", "References", "If you have any questions..." etc. Those are application instructions; we should remove them. Also "Compensation Range:" we keep as Pay. We should also remove the "*Some candidates will have a short final conversation after that." etc. That's part of interview process; remove. Also remove "Benefits*" footnote maybe keep but it's part of benefits heading; we can keep the asterisk? Probably remove the asterisk as it's just a footnote marker. We'll keep the benefits list as is. Now construct HTML. We'll start with
About Us
then...
. ThenAbout the role
then...
containing the role description plus why this role/why now. We need to combine the role description and why this role/why now into one paragraph? Could be multiple paragraphs. We'll keep asmaybe multiple
under same heading? The instruction: Use
for prose. So we can have multiple
elements. Thus after heading, we can have
The Role ...
thenWhy This Role / Why Now ...
. ThenResponsibilities
then- with
- items.
Then
Requirements
then- with Must-Have Qualifications items.
Then
Qualifications
then- with Nice-to-Have Qualifications items.
Then
Benefits
then- with benefits items.
Then
Pay
thenCompensation Range: $185K - $250K
. Make sure to preserve all details exactly. Check for any duplicated lines: The posting includes "About Us" repeated? Not really. Check for any boilerplate like "EEO" etc: Not present. Now produce HTML. We need to be careful with special characters like & in "IT & Security Manager". Should we escape? In HTML, & should be &. So "IT & Security Manager" => "IT & Security Manager". Also "FAR.Labs" includes a dot; fine. Also "FAR.Labs’ office network" includes a curly apostrophe ’; we can keep as is or replace with ’. Safer to keep as is; but HTML will treat as character; okay. We'll output as plain text. Let's craft. About Us paragraph: copy exactly. "FAR.AI is a non-profit AI research institute working to ensure advanced AI is safe and beneficial for everyone. Our mission is to facilitate breakthrough AI safety research, advance global understanding of AI risks and solutions, and foster a coordinated global response. We’re structured to support that work from early research through real-world adoption: Independent by design. We can pursue what's most impactful based on our theory of change and share what we find publicly