Analyst II, Law Enforcement Response Team
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.
We need to decide which sections to include. The posting includes: ABOUT THE ROLE (prose), RESPONSIBILITIES (list), BASIC QUALIFICATIONS (list), PREFERRED SKILLS AND EXPERIENCE (list), COMPENSATION AND BENEFITS (prose describing benefits). Also ITAR REQUIREMENTS (legal requirement) maybe considered as a requirement? It's a requirement for eligibility. Could be part of Qualifications/Requirements. But we have to avoid legal boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. ITAR requirement is a legal requirement specific to the job, not boilerplate? It's a specific eligibility requirement. Might be considered substantive. However, it's a legal requirement; but not exactly EEO boilerplate. It's a specific condition. I'd include it perhaps under Requirements or Qualifications. But we have to decide sections.
We have sections: About the role (prose), Responsibilities (list), Qualifications (maybe combine Basic Qualifications and Preferred Skills and Experience? Could separate into Requirements and Skills). The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Pay or Schedule details besides mention of availability to work weekends, potential schedules including Tuesday–Saturday or Sunday–Thursday, potential for shifts to change as early as 6am or finish as late as 8pm, with notice. That's schedule info. So we could include a Schedule section. Also Compensation and Benefits section includes base salary etc. So we can include Benefits (maybe also Pay? The posting mentions base salary is just one part of total rewards package, but no specific numbers. So we should not create a Pay section if no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (medical, vision, dental, 401k, etc.) and schedule info. So we can have Benefits and Schedule sections. Pay section not needed because no specific salary.
Thus sections: About the role (h3), Responsibilities (h3), Requirements (maybe Basic Qualifications as Requirements), Skills (Preferred Skills and Experience), Benefits (h3), Schedule (h3). Also maybe include ITAR Requirements as part of Requirements.
We need to use
- for any list of duties/requirements/benefits. For prose use
. For Benefits we have a prose description; could also list items as
- . The benefits paragraph lists: equity, comprehensive medical, vision, and dental coverage, access to a 401(k) retirement plan, short & long-term disability insurance, life insurance, and various other discounts and perks. Could turn into list.
Schedule: we have prose about availability to work weekends, potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice. Could be list? Might be prose.
Now we must not repeat job title. No markdown fences. Just output HTML fragment.
Let's craft:
About the role
The Safety Team at SpaceXAI works to safeguard the user’s voice while balancing on- and off-platform safety risks through policy enforcement that promotes trust in SpaceXAI. As a member of the Law Enforcement Response Team within SpaceXAI Safety, you will focus on managing global information requests, ensuring efficient and accurate processing while supporting the team’s mission to protect user privacy and freedom of expression. This role requires a detail-oriented, collaborative, and adaptable individual who thrives in a dynamic environment and is passionate about delivering high-quality work.
Responsibilities
- Handle global information requests, including document intake, processing, and tracking, with a focus on accuracy and timeliness.
- Collaborate with Law Enforcement Response Team members in EMEA, and Singapore to prioritize requests and ensure consistency in operations.
- Continuously improve processes to enhance efficiency and consistency in handling legal requests.
- Participate in an on-call rotation, working closely with the Safety Team to provide timely responses to emergency requests from around the world.
- Identify anomalies or unusual patterns in requests and escalate ambiguous policy issues as needed.
- Maintain open, thorough, and regular communication with teammates and cross-functional teams to support team efficiency and deliverables.
- Deliver consistent, high-quality work on repetitive tasks while managing multiple priorities in a dynamic environment.
- Take ownership of projects, seeing them through from start to finish with a focus on detail and organization.
Requirements
- Fluency in written and spoken English.
- Exceptional communication and writing skills.
- Experience working with user information requests, legal documents, or a legal education.
- Strong attention to detail and organizational skills, with the ability to prioritize tasks in a dynamic work environment.
- Ability to handle repetitive tasks while maintaining high-quality output.
- Passion and enthusiasm for protecting user privacy and freedom of expression.
- Collaborative mindset with perseverance, determination, and a proactive approach to problem-solving.
- Comfortable navigating ambiguous policy escalations and making sound decisions.
- Availability to work weekends, with potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice.
- To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C. § 1157, or (iv) Asylee under 8 U.S.C. § 1158, or be eligible to obtain the required authorizations from the U.S. Department of State.
Skills
- 1+ years of experience in a Safety or Legal Operations role at a tech company, or as a paralegal, litigation support, or equivalent role.
- Bachelor’s degree or equivalent education/experience.
- Proven ability to spot anomalies or unusual patterns in data or requests.
- Strong sense of ownership, optimism, and enthusiasm for tackling complex challenges in a fast-paced environment.
Benefits
- Equity
- Comprehensive medical, vision, and dental coverage
- Access to a 401(k) retirement plan
- Short & long-term disability insurance
- Life insurance
- Various other discounts and perks
Schedule
Availability to work weekends, with potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice.
We have duplicated schedule info: we included it also in Requirements (availability to work weekends...). Might be duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we should avoid duplicating the same sentence in two places. The schedule info appears in BASIC QUALIFICATIONS (availability to work weekends...). It also appears maybe elsewhere? Not elsewhere. So we should include it only once. Where to place? Could be under Requirements (as part of qualifications) or under Schedule section. Since we have a Schedule section, we could place it there and not duplicate in Requirements. However, the BASIC QUALIFICATIONS includes that sentence; we need to preserve that info. If we move it to Schedule, we still preserve it, just not duplicated. That's okay. But we need to ensure we don't lose any other BASIC QUALIFICATIONS content. Let's list BASIC QUALIFICATIONS items:
- Fluency in written and spoken English.
- Exceptional communication and writing skills.
- Experience working with user information requests, legal documents, or a legal education.
- Strong attention to detail and organizational skills, with the ability to prioritize tasks in a dynamic work environment.
- Ability to handle repetitive tasks while maintaining high-quality output.
- Passion and enthusiasm for protecting user privacy and freedom of expression.
- Collaborative mindset with perseverance, determination, and a proactive approach to problem-solving.
- Comfortable navigating ambiguous policy escalations and making sound decisions.
- Availability to work weekends, with potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice.
We can keep all except the last one (schedule) for Requirements, and put schedule in Schedule section. That way we preserve all info, no duplication.
Now Requirements list will have 8 items (excluding schedule). Then Schedule section will have the schedule sentence.
Now also we have ITAR requirement; we need to include that somewhere. Could be under Requirements as an additional item. That's fine.
Now check for any other boilerplate: The posting includes "ITAR REQUIREMENTS: ..." and then "SpaceXAI is an equal opportunity employer. For details on data processing, view our Recruitment Privacy Notice." That's EEO boilerplate; we should remove that. So we will not include equal opportunity line.
Now check for any duplicated lines: The responsibilities list looks fine.
Now check for any placeholder text: none.
Now ensure we only include sections with real content. We have About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. All have content.
Now output HTML fragment only.
Let's craft final HTML.
Be careful to close tags properly.
We'll output:
About the role
...
Responsibilities
...
Requirements
...
Skills
...
Benefits
...
Schedule
...
Now write the content.
About the role prose: exactly as given.
Responsibilities list: exactly as given.
Requirements list: items from BASIC QUALIFICATIONS except schedule sentence, plus ITAR requirement.
Let's list them:
- Fluency in written and spoken English.
- Exceptional communication and writing skills.
- Experience working with user information requests, legal documents, or a legal education.
- Strong attention to detail and organizational skills, with the ability to prioritize tasks in a dynamic work environment.
- Ability to handle repetitive tasks while maintaining high-quality output.
- Passion and enthusiasm for protecting user privacy and freedom of
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. We need to decide which sections to include. The posting includes: ABOUT THE ROLE (prose), RESPONSIBILITIES (list), BASIC QUALIFICATIONS (list), PREFERRED SKILLS AND EXPERIENCE (list), COMPENSATION AND BENEFITS (prose describing benefits). Also ITAR REQUIREMENTS (legal requirement) maybe considered as a requirement? It's a requirement for eligibility. Could be part of Qualifications/Requirements. But we have to avoid legal boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. ITAR requirement is a legal requirement specific to the job, not boilerplate? It's a specific eligibility requirement. Might be considered substantive. However, it's a legal requirement; but not exactly EEO boilerplate. It's a specific condition. I'd include it perhaps under Requirements or Qualifications. But we have to decide sections. We have sections: About the role (prose), Responsibilities (list), Qualifications (maybe combine Basic Qualifications and Preferred Skills and Experience? Could separate into Requirements and Skills). The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Pay or Schedule details besides mention of availability to work weekends, potential schedules including Tuesday–Saturday or Sunday–Thursday, potential for shifts to change as early as 6am or finish as late as 8pm, with notice. That's schedule info. So we could include a Schedule section. Also Compensation and Benefits section includes base salary etc. So we can include Benefits (maybe also Pay? The posting mentions base salary is just one part of total rewards package, but no specific numbers. So we should not create a Pay section if no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (medical, vision, dental, 401k, etc.) and schedule info. So we can have Benefits and Schedule sections. Pay section not needed because no specific salary. Thus sections: About the role (h3), Responsibilities (h3), Requirements (maybe Basic Qualifications as Requirements), Skills (Preferred Skills and Experience), Benefits (h3), Schedule (h3). Also maybe include ITAR Requirements as part of Requirements. We need to use
- for any list of duties/requirements/benefits. For prose use
. For Benefits we have a prose description; could also list items as
- . The benefits paragraph lists: equity, comprehensive medical, vision, and dental coverage, access to a 401(k) retirement plan, short & long-term disability insurance, life insurance, and various other discounts and perks. Could turn into list.
Schedule: we have prose about availability to work weekends, potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice. Could be list? Might be prose.
Now we must not repeat job title. No markdown fences. Just output HTML fragment.
Let's craft:
About the role
The Safety Team at SpaceXAI works to safeguard the user’s voice while balancing on- and off-platform safety risks through policy enforcement that promotes trust in SpaceXAI. As a member of the Law Enforcement Response Team within SpaceXAI Safety, you will focus on managing global information requests, ensuring efficient and accurate processing while supporting the team’s mission to protect user privacy and freedom of expression. This role requires a detail-oriented, collaborative, and adaptable individual who thrives in a dynamic environment and is passionate about delivering high-quality work.
Responsibilities
- Handle global information requests, including document intake, processing, and tracking, with a focus on accuracy and timeliness.
- Collaborate with Law Enforcement Response Team members in EMEA, and Singapore to prioritize requests and ensure consistency in operations.
- Continuously improve processes to enhance efficiency and consistency in handling legal requests.
- Participate in an on-call rotation, working closely with the Safety Team to provide timely responses to emergency requests from around the world.
- Identify anomalies or unusual patterns in requests and escalate ambiguous policy issues as needed.
- Maintain open, thorough, and regular communication with teammates and cross-functional teams to support team efficiency and deliverables.
- Deliver consistent, high-quality work on repetitive tasks while managing multiple priorities in a dynamic environment.
- Take ownership of projects, seeing them through from start to finish with a focus on detail and organization.
Requirements
- Fluency in written and spoken English.
- Exceptional communication and writing skills.
- Experience working with user information requests, legal documents, or a legal education.
- Strong attention to detail and organizational skills, with the ability to prioritize tasks in a dynamic work environment.
- Ability to handle repetitive tasks while maintaining high-quality output.
- Passion and enthusiasm for protecting user privacy and freedom of expression.
- Collaborative mindset with perseverance, determination, and a proactive approach to problem-solving.
- Comfortable navigating ambiguous policy escalations and making sound decisions.
- Availability to work weekends, with potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice.
- To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C. § 1157, or (iv) Asylee under 8 U.S.C. § 1158, or be eligible to obtain the required authorizations from the U.S. Department of State.
Skills
- 1+ years of experience in a Safety or Legal Operations role at a tech company, or as a paralegal, litigation support, or equivalent role.
- Bachelor’s degree or equivalent education/experience.
- Proven ability to spot anomalies or unusual patterns in data or requests.
- Strong sense of ownership, optimism, and enthusiasm for tackling complex challenges in a fast-paced environment.
Benefits
- Equity
- Comprehensive medical, vision, and dental coverage
- Access to a 401(k) retirement plan
- Short & long-term disability insurance
- Life insurance
- Various other discounts and perks
Schedule
Availability to work weekends, with potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice.
We have duplicated schedule info: we included it also in Requirements (availability to work weekends...). Might be duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we should avoid duplicating the same sentence in two places. The schedule info appears in BASIC QUALIFICATIONS (availability to work weekends...). It also appears maybe elsewhere? Not elsewhere. So we should include it only once. Where to place? Could be under Requirements (as part of qualifications) or under Schedule section. Since we have a Schedule section, we could place it there and not duplicate in Requirements. However, the BASIC QUALIFICATIONS includes that sentence; we need to preserve that info. If we move it to Schedule, we still preserve it, just not duplicated. That's okay. But we need to ensure we don't lose any other BASIC QUALIFICATIONS content. Let's list BASIC QUALIFICATIONS items: - Fluency in written and spoken English. - Exceptional communication and writing skills. - Experience working with user information requests, legal documents, or a legal education. - Strong attention to detail and organizational skills, with the ability to prioritize tasks in a dynamic work environment. - Ability to handle repetitive tasks while maintaining high-quality output. - Passion and enthusiasm for protecting user privacy and freedom of expression. - Collaborative mindset with perseverance, determination, and a proactive approach to problem-solving. - Comfortable navigating ambiguous policy escalations and making sound decisions. - Availability to work weekends, with potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice. We can keep all except the last one (schedule) for Requirements, and put schedule in Schedule section. That way we preserve all info, no duplication. Now Requirements list will have 8 items (excluding schedule). Then Schedule section will have the schedule sentence. Now also we have ITAR requirement; we need to include that somewhere. Could be under Requirements as an additional item. That's fine. Now check for any other boilerplate: The posting includes "ITAR REQUIREMENTS: ..." and then "SpaceXAI is an equal opportunity employer. For details on data processing, view our Recruitment Privacy Notice." That's EEO boilerplate; we should remove that. So we will not include equal opportunity line. Now check for any duplicated lines: The responsibilities list looks fine. Now check for any placeholder text: none. Now ensure we only include sections with real content. We have About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. All have content. Now output HTML fragment only. Let's craft final HTML. Be careful to close tags properly. We'll output:About the role
...
Responsibilities
- ...
Requirements
- ...
Skills
- ...
Benefits
- ...
Schedule
...
Now write the content. About the role prose: exactly as given. Responsibilities list: exactly as given. Requirements list: items from BASIC QUALIFICATIONS except schedule sentence, plus ITAR requirement. Let's list them: - Fluency in written and spoken English. - Exceptional communication and writing skills. - Experience working with user information requests, legal documents, or a legal education. - Strong attention to detail and organizational skills, with the ability to prioritize tasks in a dynamic work environment. - Ability to handle repetitive tasks while maintaining high-quality output. - Passion and enthusiasm for protecting user privacy and freedom of
- . The benefits paragraph lists: equity, comprehensive medical, vision, and dental coverage, access to a 401(k) retirement plan, short & long-term disability insurance, life insurance, and various other discounts and perks. Could turn into list.
Schedule: we have prose about availability to work weekends, potential schedules including Tuesday–Saturday or Sunday–Thursday. Potential for shifts to change to as early as 6am or finish as late as 8pm, with notice. Could be list? Might be prose.
Now we must not repeat job title. No markdown fences. Just output HTML fragment.
Let's craft: