When an Employee Lies About Work for Two Months: A Startup Nightmare
Imagine this: you sponsored an engineer to relocate internationally, trusted him with a critical product build, and received confident status updates for two full months — only to find out none of it was real. That is exactly the situation one startup manager recently shared in a letter to workplace advice columnist Alison Green of Ask a Manager. The story raises urgent questions about employee accountability, legal recourse, and the management practices that can prevent such costly deceptions in the first place.
The manager ran a small developer team at a startup building a new product. Their full-stack engineer — brought in from Peru with company sponsorship — had been delivering fake progress updates on a web portal for two months. The day the engineer announced he was leaving for a competitor, he casually admitted he had completed nothing. The manager openly acknowledged their own oversight: in a busy startup environment, they had never asked for a live demo or reviewed the actual codebase.
This scenario is every startup leader's worst fear, and it is more common than most people admit. Let's break down what happened, what options exist, and how to make sure it never happens to your team again.
Understanding What Actually Went Wrong
Before jumping to legal strategies or blame, it is worth examining the full picture. Both parties share some responsibility in how this situation unfolded, and understanding the breakdown clearly is the first step toward fixing the underlying systems.
The Employee's Misconduct
There is no softening this: consistently fabricating progress reports over two months is a serious act of professional dishonesty. The engineer did not simply fall behind and fail to communicate — he actively deceived his employer, accepted a sponsored relocation package, and collected a salary for work he knew he was not doing. That is not a gray area. It is a deliberate misrepresentation that caused real financial and operational harm to the startup.
The Manager's Blind Spot
The manager admits they dropped the ball by never checking a demo or reviewing actual deliverables. In a small startup with everyone stretched thin, it is understandable — but it is also a costly gap. Status updates without artifact reviews are essentially a trust system with no verification layer. That is a structural vulnerability, not just a one-time mistake.
Can You Take Legal Action Against an Employee Who Lied?
This is the question most managers in this position ask first, and the honest answer is: it depends, and it is complicated. Legal action is possible in some circumstances, but it is rarely straightforward and often not worth the cost or effort for a small startup.
Potential Legal Avenues
Depending on your jurisdiction and the specifics of your employment contract, there may be grounds to pursue the following claims against the employee.
- Breach of contract: If the employment agreement included clear deliverable milestones or performance obligations, failing to meet them while actively claiming otherwise could constitute a breach. Your legal team would need to assess whether the language is strong enough to support a claim.
- Fraudulent misrepresentation: Deliberately providing false status updates to induce continued employment and benefit (such as the relocation sponsorship) could, in some legal systems, be framed as a form of fraud. However, this is a high bar to clear and requires demonstrating intent and damages.
- Recovery of relocation costs: If the relocation sponsorship agreement included a clawback clause — many do — you may be able to reclaim those costs. This is one of the more practical legal options and is worth reviewing your contract for immediately.
- Unjust enrichment: In some jurisdictions, receiving payment for work not performed may support a civil claim for unjust enrichment, though these are difficult and expensive to litigate.
It is strongly advisable to consult an employment attorney in your jurisdiction before pursuing any of these routes. The cost of litigation for a small startup often outweighs the recovery, and many such cases settle or are dropped entirely once legal fees are factored in.
What You Likely Cannot Do
You cannot legally prevent the engineer from joining a new company. Employment law in most countries protects an individual's right to work, and absent a valid and enforceable non-compete agreement — which are increasingly unenforceable in many places — his career move is his own to make. You also cannot defame him publicly, even if you are furious. Stick to factual, documented statements if references come up.
Rebuilding After the Damage: Practical Next Steps
Whatever the legal outcome, the startup now has a product gap and a lost two months. Here is how to move forward with minimal additional damage.
Audit What Exists
Before bringing in a replacement, have another technical team member audit the codebase, repositories, and any documentation. You need a clear picture of ground zero before scoping new timelines. There may be fragments worth salvaging, or there may be nothing at all — either way, you need to know.
Revise Your Oversight Process
Going forward, implement short, regular demo cycles — even weekly fifteen-minute screen shares showing working code. Require access to version control repositories such as GitHub or GitLab so commit history is always visible. Progress is not what someone says; it is what exists in the codebase.
Update Employment Agreements
Work with a lawyer to add specific milestone language, relocation clawback clauses, and deliverable expectations to future employment contracts. These provisions do not prevent all misconduct, but they create contractual accountability and give you clearer legal footing if something goes wrong again.
The Broader Lesson for Startup Leaders
The painful truth this story illustrates is that trust without verification is not a management strategy — it is a vulnerability. In a startup environment where bandwidth is scarce and everyone is already stretched, it is tempting to take status updates at face value. But the cost of that shortcut, as this manager learned, can be enormous: lost months, wasted sponsorship funds, and a delayed product launch.
Building a culture of accountability does not mean micromanaging. It means creating visible, low-friction check-in systems where actual work is reviewed, not just reported. It means making it easy for team members to surface problems early before they compound. And it means catching the rare bad actor before they have two months to do damage.
Legal options may offer some partial recourse in a situation like this, but the real return on investment comes from the management and contractual changes that prevent it from happening in the first place. No startup can afford to lose two months of development time — and the good news is, with the right oversight structures, they do not have to.