误将公司doc输入外部AI导致HR约谈，要在开会前主动离职吗？

本人这次真的是心太大了。因为公司内部的AI工具实在太不好用了，十次有九次fail，前段时间我不小心把一份很长的公司Strategy Doc放进Gemini里概括总结问问题。结果立刻被Security和HR找上门，怀疑我有意泄露公司机密。

现状： 事情过去一个月后，HR突然在下周拉了一个包含我、我Manager以及HR的三方会议。HR强调这个case是Fully Confidential的。 说实话，我本来就一直想离职，目前也正在面试找新工作。但我现在不知道该如何应对下周的会议。

我的核心诉求：

• 绝对不能影响未来新公司的Background Check（背调）。
• 尽量不留负面记录，不想影响未来的Rehire Eligibility再次回到亚麻。

目前纠结的选项（求大家给建议）：

• 选项1：下周开会前直接提离职。 这种情况还能算作纯粹的Voluntary Resignation吗？能规避掉调查记录吗？
• 选项2：等到下周开会。 有没有可能是直接Termination，或者其实只给个Final Warning？如果被terminate，这时候还能拿到Severance package吗？

以及即使我在会议前主动辞职，HR系统中通常仍可能会标记为“Resigned under investigation”（在调查期间辞职）或不符合Rehire Eligibility？

这个公司好落后，这都不行？

这个诉求是你说了算吗？

匿名用户 发表于 2026-04-15 20:35:04
这个公司好落后，这都不行？

天了噜，公司内部的资料不允许放在公共access上呀，这都是公司的policy🤣

这种情况，离职了也一样记录，一样ineligible for rehire

提前辞职，重新面亚麻

你现在辞职背景调查也未必就不留负面记录，先看看公司怎么说吧，也许就是个warning

Don't resign before the meeting. Here's why:

Resigning before the meeting doesn't automatically make the investigation disappear - Amazon's HR system will almost certainly record the reason for the investigation, and the sequence of events (you resigned right before the meeting) looks suspicious, not clean. In many cases, "resigned while under investigation" gets flagged just like a termination.

Go to the meeting. Hear what they say. If this was genuinely accidental (and it sounds like it was - you used an external AI like many people do), you can explain it clearly. Companies often differentiate between malicious leaks and accidental/careless misuse. Given that you were using a commonly available AI tool and it was done without intent, the outcome might just be a formal warning.

Key things to do before the meeting:
- Write down exactly what happened (when, what doc, what you asked, what you got back)  
- Know if Gemini was on your personal or work device
- Don't discuss the meeting with coworkers

If they terminate you, at least you get severance. If you resign beforehand you likely get nothing and still have a complicated situation on your record.

The "Resigned under investigation" flag sounds scary but Amazon's internal system marks it regardless - quitting early doesn't usually scrub that, it just removes your leverage.

有那么不小心吗

你是无意的，不用太担心。这是公司系统层面应该防住的操作，相当于你帮it部门找到一个大bug。你要不是级别贼高，能接触到的文档机密级别也有限。以小代价找到大bug，你们公司赚了。你是帮公司省了大钱

而且既然你操作后立即被找上门，显然这些部门是有技术手段检测到的。既然能检测到，为什么不能在检测到的时候直接gate住你的上传操作，而要等上传完后再事后诸葛亮。是他们设计security流程的问题，还是priority不够没有resource来实现这个gating功能的问题？你或者帮他们找到了系统设计的漏洞，或者提供了支撑他们要resource的案例。会议的时候把在场的往同一条船上拉，“丧”事喜办就好

Good luck 🍀