Customer Success Engineer (Founding)
Opsin · Time, IL · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections: headings using for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate.
We need to parse the posting.
Posting content:
← Careers Customer Success Engineer (Founding) The Role Opsin secures how enterprises adopt GenAI — Microsoft Copilot, Google Gemini, and custom agents — by finding and fixing the data access and oversharing risk underneath them. Our buyers are security teams and our deployments are technical. This is our first customer success hire, and it is a hybrid of implementation engineer and account manager. You will become the front face of Opsin across your accounts, own the full customer journey from onboarding through expansion, and help build the CS function from scratch. This is a senior, founding role working directly with the founders. Your Experience & Skills Must-haves 3–5+ years in a customer-facing post-sales role — Customer Success Engineer, Technical Account Manager, or Solutions/Implementation EngineerCybersecurity experience. You understand how security teams buy, deploy, and measure, and you can hold your own with a CISO or a security engineerStartup experience. You have operated at a startup, with minimal process and structureHands-on with automation and workflow tooling — Power Automate, Torq, Tines, and building skills in Claude or ChatGPTTrack record of owning enterprise accounts end to end — onboarding through renewal and expansion, not support ticketsCommercial instinct — can get into the technical weeds and then step back to see where an account should grow Preferred Data security, identity, or cloud security background — DSPM, DLP, IAM/IGA, permissions, SSPM, and adjacentExperience with Microsoft 365 / Entra ID, Copilot, or GenAI and agent platformsBased in the US, ideally in Central time Mindset & Fit Ownership — treats every account outcome as yours to drive, end to endHands-on — comfortable in the technical weeds with security, IAM, and IT teamsBuilder — energized by creating the playbooks and process that do not exist yetBias for action — thrives in a fast-paced startup with minimal structurePassionate about AI and cybersecurity Why Join Us? Early impact: Help shape a category-defining product in GenAI securityGrowth & ownership: Work directly with founders and tech leads to drive innovationCutting-edge tech: Build with LLMs, AI security, and enterprise AI adoption strategies About Opsin Opsin is a venture-backed GenAI security company, funded by top-tier investors including Race Capital. We empower enterprises to safely adopt GenAI solutions like Microsoft Copilot, Google Gemini, and other LLM-powered agents by monitoring and securing enterprise data access. Our platform ensures employees can leverage AI without exposing sensitive or over-permissioned information. Employment Type Full-Time Compensation Competitive salary, benefits, and equity Location Remote — US. Central time zone preferred. Excited to secure the future of GenAI? Join us! Apply At careers@opsinsecurity.com
We need to extract sections: About the role (the initial paragraph after The Role). Responsibilities (maybe the bullet list of duties). Requirements (must-haves). Qualifications (maybe preferred). Skills (maybe mindset & fit). Benefits (Why Join Us?). Pay (Compensation). Schedule (maybe location/remote? Not exactly schedule). The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include a section only when posting has real specific content for it. So we need to decide which sections have content.
Let's map:
- About the role: The paragraph after "The Role": "Opsin secures how enterprises adopt GenAI — Microsoft Copilot, Google Gemini, and custom agents — by finding and fixing the data access and oversharing risk underneath them. Our buyers are security teams and our deployments are technical. This is our first customer success hire, and it is a hybrid of implementation engineer and account manager. You will become the front face of Opsin across your accounts, own the full customer journey from onboarding through expansion, and help build the CS function from scratch. This is a senior, founding role working directly with the founders." That's substantive.
- Responsibilities: Could be derived from "own the full customer journey from onboarding through expansion, and help build the CS function from scratch." Also maybe "You will become the front face of Opsin across your accounts". Might be considered responsibilities. We could list bullet points: front face, own full customer journey, help build CS function, work directly with founders. That seems specific.
- Requirements: Must-haves list: 3–5+ years in a customer-facing post-sales role — Customer Success Engineer, Technical Account Manager, or Solutions/Implementation Engineer; Cybersecurity experience; Startup experience; Hands-on with automation and workflow tooling — Power Automate, Torq, Tines, and building skills in Claude or ChatGPT; Track record of owning enterprise accounts end to end — onboarding through renewal and expansion, not support tickets; Commercial instinct — can get into the technical weeds and then step back to see where an account should grow.
- Qualifications: Preferred: Data security, identity, or cloud security background — DSPM, DLP, IAM/IGA, permissions, SSPM, and adjacent; Experience with Microsoft 365 / Entra ID, Copilot, or GenAI and agent platforms; Based in the US, ideally in Central time.
- Skills: Mindset & Fit: Ownership — treats every account outcome as yours to drive, end to end; Hands-on — comfortable in the technical weeds with security, IAM, and IT teams; Builder — energized by creating the playbooks and process that do not exist yet; Bias for action — thrives in a fast-paced startup with minimal structure; Passionate about AI and cybersecurity.
- Benefits: Why Join Us? Early impact: Help shape a category-defining product in GenAI security; Growth & ownership: Work directly with founders and tech leads to drive innovation; Cutting-edge tech: Build with LLMs, AI security, and enterprise AI adoption strategies.
- Pay: Compensation Competitive salary, benefits, and equity.
- Schedule: Not explicitly given. Location Remote — US. Central time zone preferred. That's location, not schedule. Could we treat location as schedule? Probably not. The instruction says include Schedule section only if posting actually states them. It does not state schedule (like full-time hours, shift). It says Employment Type Full-Time. That's employment type, not schedule. Could we consider that as schedule? Might be considered schedule (full-time). But they said "Schedule" heading for schedule info like hours, shift, etc. The posting does not give schedule details beyond full-time. Might be considered schedule? I'd argue we can include Schedule with "Full-time". However they said "Prefer a few substantive sections over many thin ones." Might be okay to include Schedule with "Full-time". But we also have Employment Type Full-Time elsewhere. Could combine into Pay? Not ideal.
Better to include Schedule with "Full-time". It's specific.
We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must not repeat job title as heading. So no heading for Customer Success Engineer (Founding). Already not.
We must not put Job ID/requisition numbers as headings. None.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate.
We need to parse the posting.
Posting content:
← Careers Customer Success Engineer (Founding) The Role Opsin secures how enterprises adopt GenAI — Microsoft Copilot, Google Gemini, and custom agents — by finding and fixing the data access and oversharing risk underneath them. Our buyers are security teams and our deployments are technical. This is our first customer success hire, and it is a hybrid of implementation engineer and account manager. You will become the front face of Opsin across your accounts, own the full customer journey from onboarding through expansion, and help build the CS function from scratch. This is a senior, founding role working directly with the founders. Your Experience & Skills Must-haves 3–5+ years in a customer-facing post-sales role — Customer Success Engineer, Technical Account Manager, or Solutions/Implementation EngineerCybersecurity experience. You understand how security teams buy, deploy, and measure, and you can hold your own with a CISO or a security engineerStartup experience. You have operated at a startup, with minimal process and structureHands-on with automation and workflow tooling — Power Automate, Torq, Tines, and building skills in Claude or ChatGPTTrack record of owning enterprise accounts end to end — onboarding through renewal and expansion, not support ticketsCommercial instinct — can get into the technical weeds and then step back to see where an account should grow Preferred Data security, identity, or cloud security background — DSPM, DLP, IAM/IGA, permissions, SSPM, and adjacentExperience with Microsoft 365 / Entra ID, Copilot, or GenAI and agent platformsBased in the US, ideally in Central time Mindset & Fit Ownership — treats every account outcome as yours to drive, end to endHands-on — comfortable in the technical weeds with security, IAM, and IT teamsBuilder — energized by creating the playbooks and process that do not exist yetBias for action — thrives in a fast-paced startup with minimal structurePassionate about AI and cybersecurity Why Join Us? Early impact: Help shape a category-defining product in GenAI securityGrowth & ownership: Work directly with founders and tech leads to drive innovationCutting-edge tech: Build with LLMs, AI security, and enterprise AI adoption strategies About Opsin Opsin is a venture-backed GenAI security company, funded by top-tier investors including Race Capital. We empower enterprises to safely adopt GenAI solutions like Microsoft Copilot, Google Gemini, and other LLM-powered agents by monitoring and securing enterprise data access. Our platform ensures employees can leverage AI without exposing sensitive or over-permissioned information. Employment Type Full-Time Compensation Competitive salary, benefits, and equity Location Remote — US. Central time zone preferred. Excited to secure the future of GenAI? Join us! Apply At careers@opsinsecurity.com
We need to extract sections: About the role (the initial paragraph after The Role). Responsibilities (maybe the bullet list of duties). Requirements (must-haves). Qualifications (maybe preferred). Skills (maybe mindset & fit). Benefits (Why Join Us?). Pay (Compensation). Schedule (maybe location/remote? Not exactly schedule). The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include a section only when posting has real specific content for it. So we need to decide which sections have content.
Let's map:
- About the role: The paragraph after "The Role": "Opsin secures how enterprises adopt GenAI — Microsoft Copilot, Google Gemini, and custom agents — by finding and fixing the data access and oversharing risk underneath them. Our buyers are security teams and our deployments are technical. This is our first customer success hire, and it is a hybrid of implementation engineer and account manager. You will become the front face of Opsin across your accounts, own the full customer journey from onboarding through expansion, and help build the CS function from scratch. This is a senior, founding role working directly with the founders." That's substantive.
- Responsibilities: Could be derived from "own the full customer journey from onboarding through expansion, and help build the CS function from scratch." Also maybe "You will become the front face of Opsin across your accounts". Might be considered responsibilities. We could list bullet points: front face, own full customer journey, help build CS function, work directly with founders. That seems specific.
- Requirements: Must-haves list: 3–5+ years in a customer-facing post-sales role — Customer Success Engineer, Technical Account Manager, or Solutions/Implementation Engineer; Cybersecurity experience; Startup experience; Hands-on with automation and workflow tooling — Power Automate, Torq, Tines, and building skills in Claude or ChatGPT; Track record of owning enterprise accounts end to end — onboarding through renewal and expansion, not support tickets; Commercial instinct — can get into the technical weeds and then step back to see where an account should grow.
- Qualifications: Preferred: Data security, identity, or cloud security background — DSPM, DLP, IAM/IGA, permissions, SSPM, and adjacent; Experience with Microsoft 365 / Entra ID, Copilot, or GenAI and agent platforms; Based in the US, ideally in Central time.
- Skills: Mindset & Fit: Ownership — treats every account outcome as yours to drive, end to end; Hands-on — comfortable in the technical weeds with security, IAM, and IT teams; Builder — energized by creating the playbooks and process that do not exist yet; Bias for action — thrives in a fast-paced startup with minimal structure; Passionate about AI and cybersecurity.
- Benefits: Why Join Us? Early impact: Help shape a category-defining product in GenAI security; Growth & ownership: Work directly with founders and tech leads to drive innovation; Cutting-edge tech: Build with LLMs, AI security, and enterprise AI adoption strategies.
- Pay: Compensation Competitive salary, benefits, and equity.
- Schedule: Not explicitly given. Location Remote — US. Central time zone preferred. That's location, not schedule. Could we treat location as schedule? Probably not. The instruction says include Schedule section only if posting actually states them. It does not state schedule (like full-time hours, shift). It says Employment Type Full-Time. That's employment type, not schedule. Could we consider that as schedule? Might be considered schedule (full-time). But they said "Schedule" heading for schedule info like hours, shift, etc. The posting does not give schedule details beyond full-time. Might be considered schedule? I'd argue we can include Schedule with "Full-time". However they said "Prefer a few substantive sections over many thin ones." Might be okay to include Schedule with "Full-time". But we also have Employment Type Full-Time elsewhere. Could combine into Pay? Not ideal.
Better to include Schedule with "Full-time". It's specific.
We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must not repeat job title as heading. So no heading for Customer Success Engineer (Founding). Already not.
We must not put Job ID/requisition numbers as headings. None.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
Opsin secures how enterprises adopt GenAI — Microsoft Copilot, Google Gemini, and custom agents — by finding and fixing the data access and oversharing risk underneath them. Our buyers are security teams and our deployments are technical. This is our first customer success hire, and it is a hybrid of implementation engineer and account manager. You will become the front face of Opsin across your accounts, own the full customer journey from onboarding through expansion, and help build the CS function from scratch. This is a senior, founding role working directly with the founders.
Responsibilities
- Act as the front face of Opsin for assigned accounts.
- Own the full customer journey from onboarding through expansion.
- Help build the customer success function from scratch.
- Work directly with founders and technical leads.
Requirements
- 3–5+ years in a customer-facing post‑sales role (Customer Success Engineer, Technical Account Manager, or Solutions/Implementation Engineer).
- Cybersecurity experience — understanding how security teams buy, deploy, and measure, and ability to engage with CISOs or security engineers.
- Startup experience — operated at a startup with minimal process and structure.
- Hands‑on with automation and workflow tooling (Power Automate, Torq, Tines) and building skills in Claude or ChatGPT.
- Track record of owning enterprise accounts end to end — onboarding through renewal and expansion, not just support tickets.
- Commercial instinct — ability to dive into technical weeds and then step back to identify growth opportunities.
Qualifications
- Preferred background in data security, identity, or cloud security (DSPM, DLP, IAM/IGA, permissions, SSPM, adjacent areas).
- Experience with Microsoft 365 / Entra ID, Copilot, or GenAI and agent platforms.
- Based in the US, ideally in the Central time zone.
Skills
- Ownership — treats every account outcome as yours to drive, end to end.
- Hands‑on — comfortable in the technical weeds with security, IAM, and IT teams.
- Builder — energized by creating playbooks and processes that do not yet exist.
- Bias for action — thrives in a fast‑paced startup with minimal structure.
- Passionate about AI and cybersecurity.
Benefits
- Early impact: help shape a category‑defining product in GenAI security.
- Growth & ownership: work directly with founders and tech leads to drive innovation.
- Cutting‑edge tech: build with LLMs, AI security, and enterprise AI adoption strategies.
Pay
Competitive salary, benefits, and equity.
Schedule
Full‑time.
We need to ensure we didn't miss any substantive info: The location Remote — US. Central time zone preferred. We included that in Qualifications (Based in US, ideally Central time). Also we could add location as separate? But we already covered. We also have "Employment Type Full-Time" which we used in Schedule. We also have "Competitive salary, benefits, and equity" used in Pay. We also have "Excited to secure the future of GenAI? Join us! Apply At careers@opsinsecurity.com" - that's application instruction, which we must remove. So we omitted. We also have "About Opsin" paragraph: "Opsin is a venture-backed GenAI security company, funded by top-tier investors including Race Capital. We empower enterprises to safely adopt GenAI solutions like Microsoft Copilot, Google Gemini, and other LLM-powered agents by monitoring and securing enterprise data access. Our platform ensures employees can leverage AI without exposing sensitive or over-permissioned information." This is substantive; we haven't included it anywhere. Should we include it? Possibly under About the role or a separate section like "About Opsin". The instruction says use headings for section headings e.g.