Employee mobility is one of the most sensitive issues for technology startups.

A startup may spend years training a software engineer, sales manager, product director or senior executive. During that period, the employee may gain access to highly valuable information, including:

• source code,
• algorithms,
• product architecture,
• customer lists,
• pricing policies,
• investor information,
• business plans,
• product roadmaps,
• artificial intelligence models,
• technical documentation,
• marketing strategies,
• sales pipelines,
• supplier conditions,
• and confidential commercial information.

The employee may then resign and receive an offer from a competing startup.

Founders frequently respond by pointing to a clause in the employment agreement:

“The employee may not work for any competing company for two years after termination.”

But is such a clause automatically valid under Turkish law?

The answer is no.

Turkish law permits post-employment non-compete obligations, but only under relatively strict conditions.

A startup cannot generally prevent every employee from working for every competitor simply because the employment contract contains a non-compete clause.

The principal rules are found in Articles 444 to 447 of the Turkish Code of Obligations No. 6098 (Türk Borçlar Kanunu – TBK).

Article 444 permits a legally capable employee to undertake in writing not to compete with the employer after termination. However, the clause is valid only where the employment relationship gave the employee access to the employer’s customer base, production secrets or information concerning the employer’s business, and the use of that information could cause the employer substantial damage.

Article 445 then requires the restriction to remain reasonable regarding:

• geographical area,
• duration,
• and type of activity.

Except in special circumstances, the duration cannot exceed two years, and courts may reduce an excessive restriction.

For startups, this means that a successful non-compete strategy should not be based on making the restriction as broad as possible.

The more effective approach is usually the opposite:

identify the startup’s legitimate interest and draft the restriction narrowly enough to protect that interest without unfairly preventing the employee from earning a living.

This article explains whether a startup employee non-compete agreement is valid in Turkey, when an employee can legally join a competitor, how long a non-compete may continue, what geographic restrictions are permitted, whether penalty clauses can be enforced and how startups can protect trade secrets without relying on excessively broad employment restrictions.

Non-Compete During Employment and After Employment Are Different

The first important distinction is between:

1. competition while the employment relationship continues; and
2. competition after the employment relationship ends.

These situations are governed differently.

Can an Employee Compete With the Startup While Still Employed?

Employees already owe a duty of loyalty during employment.

Article 396 of the Turkish Code of Obligations requires employees to perform their duties carefully and protect the employer’s legitimate interests.

It further provides that, while the employment relationship continues, employees cannot provide services to third parties in a manner contrary to their loyalty obligations and, in particular, cannot compete with their employer.

The same provision prohibits employees from using or disclosing information learned during employment, particularly production and business secrets, and continues confidentiality after termination to the extent necessary to protect the employer’s legitimate interests.

Consider the following example.

A developer works full-time for Startup A.

Without informing Startup A, the developer establishes Startup B and begins selling an almost identical competing product to Startup A’s customers while remaining employed.

Even if the employment agreement contains no separate post-employment non-compete clause, the employee’s actions may raise serious issues under the statutory duty of loyalty.

The legal position changes once employment ends.

After termination, an employee is generally free to continue their professional career unless a valid post-employment restriction applies.

What Is a Post-Employment Non-Compete Agreement?

A post-employment non-compete clause attempts to restrict certain competitive activities after the employment relationship ends.

Article 444 expressly contemplates restrictions preventing an employee from:

• establishing a competing business for their own account;
• working for another competing enterprise;
• or entering another type of interest relationship with a competing enterprise.

However, such restrictions require a valid written undertaking and must satisfy the substantive conditions established by the Code.

Therefore, a startup cannot simply state:

“Anyone who works here can never work for a competitor.”

The employer must have a legitimate and legally protectable reason for restricting the employee’s future professional activity.

Is a Written Non-Compete Clause Required?

Yes.

Article 444 requires the employee’s post-employment non-compete undertaking to be made in writing.

This is particularly important for startups, where employment relationships can sometimes develop informally.

A founder may tell a senior developer:

“You understand that you cannot work for our competitors if you leave.”

That oral statement should not be relied upon as a properly established TBK Article 444 non-compete undertaking.

The restriction should be documented in:

• the employment agreement;
• a written supplementary agreement;
• or another legally adequate written document.

However, written form alone is not enough.

A perfectly signed non-compete clause can still be invalid or subject to judicial limitation if the substantive requirements are not satisfied.

Not Every Startup Employee Can Be Subject to a Valid Non-Compete

This is one of the most important principles.

Article 444 does not permit employers to impose effective non-compete obligations automatically on every person appearing on the payroll.

The employment relationship must have given the employee access to:

• the customer environment;
• production secrets;
• or information concerning the employer’s activities;

and the use of that information must be capable of causing the employer significant damage.

This requires an employee-specific analysis.

Example: Senior CTO

A startup CTO knows:

• the entire source-code architecture;
• security weaknesses;
• unreleased product features;
• proprietary algorithms;
• engineering roadmap;
• investor plans;
• pricing strategy;
• and acquisition discussions.

If that CTO immediately joins the startup’s closest competitor in an essentially identical role, the startup may have a strong argument that access to confidential business information can create significant competitive harm.

A carefully drafted non-compete clause may therefore have a strong legal basis.

Example: Junior Administrative Employee

Now consider a junior administrative employee who:

• has no customer relationships;
• has no source-code access;
• does not know pricing strategy;
• has no access to trade secrets;
• and performs only routine administrative tasks.

The employment agreement nevertheless states:

“The employee may not work for any technology company in Turkey for two years.”

The startup may have considerable difficulty establishing why Article 444 should validly prevent that employee from continuing to work in the technology sector.

A non-compete should protect a legitimate commercial interest, not merely make employee departure difficult.

Access to Customers Can Justify a Restriction

Customer relationships can be particularly important for sales-driven startups.

Suppose a senior sales director personally manages:

• the startup’s largest 40 enterprise customers;
• renewal negotiations;
• customer discounts;
• pricing margins;
• procurement contacts;
• and pipeline information.

The director then resigns and joins the startup’s closest competitor.

If the director can use their detailed knowledge and relationships to move important customers to the competitor, the startup may have a legitimate interest in imposing a proportionate restriction.

However, merely having met some customers does not automatically justify a nationwide two-year ban.

The potential damage must still be sufficiently serious.

Trade Secrets Are Particularly Important for Technology Startups

Technology businesses frequently rely less on physical assets and more on confidential information.

Relevant information may include:

• proprietary source code;
• algorithms;
• model architecture;
• API design;
• security systems;
• technical vulnerabilities;
• unreleased software;
• product roadmap;
• confidential pricing;
• customer usage data;
• investment strategy;
• acquisition plans;
• database architecture;
• and internal performance metrics.

Where employees gain meaningful access to these materials, a legitimate non-compete interest may arise.

However, startups should distinguish between:

protectable confidential information

and

the employee’s general professional skills and experience.

A software developer does not lose the right to remain a software developer merely because they learned new programming techniques while working at a startup.

General Professional Knowledge Cannot Simply Be Locked Away

Employees inevitably become more experienced while working.

A developer may learn:

• Python;
• React;
• cloud architecture;
• DevOps;
• machine learning;
• sales techniques;
• management methods;
• or sector experience.

The employer generally cannot transform all accumulated professional knowledge into its private property.

The legitimate concern should instead be whether the employee can exploit information genuinely specific to the former employer.

For example:

General skill: knowing how to develop a SaaS platform.

Confidential information: knowing Startup A’s unreleased architecture, pricing algorithm and customer-specific vulnerabilities.

The distinction is essential.

A startup should protect the second category without trying to monopolise the first.

How Long Can a Startup Non-Compete Last?

Article 445 establishes a particularly important limitation.

A post-employment non-compete cannot contain inappropriate restrictions concerning:

• place;
• time;
• or type of work

that would unfairly endanger the employee’s economic future.

The statute further provides that the duration generally cannot exceed two years, except where special circumstances justify otherwise.

This does not mean:

“Every two-year non-compete is valid.”

Two years is generally the statutory maximum, not an automatic recommended duration.

A restriction of:

• three months;
• six months;
• one year;
• eighteen months;
• or two years

must still be justified by the specific circumstances.

A Six-Month Restriction May Be More Defensible Than a Two-Year Restriction

Suppose confidential technology becomes commercially obsolete within six months.

A two-year prohibition might be difficult to justify because the startup’s real competitive interest disappears much earlier.

Conversely, some highly sensitive information may retain competitive significance for longer.

The correct duration should therefore correspond to:

• how long confidential information remains commercially useful;
• customer renewal cycles;
• product development periods;
• and the employee’s specific access.

Startups should not automatically insert “24 months” into every employment agreement.

Geographic Scope Must Also Be Reasonable

A non-compete should define where the restriction applies.

Examples might include:

• Istanbul;
• Turkey;
• certain regions;
• specific countries;
• or a defined commercial market.

A clause stating:

“The employee may not compete anywhere in the world”

can be highly problematic unless the startup can demonstrate a genuine worldwide business interest and the restriction remains proportionate.

Article 445 expressly requires reasonable geographical limitation.

Digital Startups Create a Complicated Geographic Question

Traditional businesses may have obvious geographical markets.

A restaurant operating only in Istanbul may have difficulty justifying restrictions covering all of Europe.

But a SaaS startup may have customers in:

• Turkey;
• Germany;
• the United Kingdom;
• the United States;
• and the Gulf.

The fact that a company operates online can justify a broader geographical analysis in appropriate cases.

However, this does not mean every internet company can automatically impose a worldwide non-compete.

The restriction should still reflect the startup’s actual competitive activity.

For example, if 95% of customers and all active sales operations are located in Turkey, a global restriction may be much harder to justify than a Turkish-market restriction.

The Type of Prohibited Work Must Be Limited

A startup should also define which activities are prohibited.

This is frequently where badly drafted clauses fail.

Consider:

“The employee shall not work in the technology sector for two years.”

That clause could prevent a former cybersecurity engineer from working for:

• an e-commerce company;
• a telecommunications company;
• a gaming company;
• a software agency;
• an AI startup;
• or almost any modern employer.

The restriction may go far beyond protecting the former employer.

A better clause might target:

• specifically identified competing products;
• directly competing business models;
• specific customer segments;
• or activities substantially similar to those performed for the former employer.

The narrower the legitimate competitive concern is defined, the more defensible the clause may become.

Courts Can Reduce Excessive Non-Compete Restrictions

An excessively broad clause does not necessarily mean that the court must always choose between enforcing the entire clause or rejecting every part of it.

Article 445 expressly authorises the judge to limit an excessive non-compete regarding its scope or duration after considering all circumstances, including any counter-performance undertaken by the employer.

This creates a significant risk for employers drafting aggressive clauses.

A startup may write:

“Two years, worldwide, all technology businesses.”

But a court may conclude that the restriction is excessive and reduce its scope.

Startups should therefore draft for enforceability rather than intimidation.

Must the Employer Pay the Employee During the Non-Compete Period?

Turkish law does not establish a universal rule requiring every employer to pay salary throughout every post-employment non-compete period.

However, Article 445 expressly allows the court, when evaluating whether the restriction is excessive, to consider any counter-performance undertaken by the employer.

This means compensation can become relevant to proportionality.

For example, a startup demanding that a senior executive remain outside the relevant industry for a significant period may strengthen the fairness of the arrangement by providing agreed compensation.

Whether such a payment should be included depends on:

• the employee’s role;
• duration;
• geographic restriction;
• market conditions;
• and commercial importance of the information being protected.

Does a Non-Compete Prevent the Employee From Joining Any Competitor?

Not necessarily.

Even a valid clause applies only within its lawful scope.

Suppose a senior engineer worked for Startup A’s payment-processing product.

The employee then joins a large technology company that technically competes with Startup A in some areas but hires the employee exclusively to work on an unrelated cloud-storage product.

The mere fact that both companies are broadly “technology companies” may not automatically establish a prohibited competitive activity.

The actual roles and businesses should be compared.

Important questions include:

• Do the companies sell competing products?
• Do they target the same customers?
• Will the employee perform a similar role?
• Can confidential information realistically be used?
• Is the new activity within the contractually restricted field?

Labels alone should not determine the outcome.

Can a Startup Prevent an Employee From Establishing Their Own Competing Startup?

Potentially, yes.

Article 444 expressly recognises that a valid non-compete may restrict an employee from opening a competing business for their own account.

Consider:

A product manager learns all details of Startup A’s unreleased fintech platform.

The employee resigns.

One week later, the employee incorporates Startup B and launches an almost identical product targeting Startup A’s customers.

If a valid non-compete exists, this can form a strong basis for enforcement.

Even if the non-compete is ultimately disputed, separate issues may arise concerning:

• confidentiality;
• trade secrets;
• copyright;
• source code;
• customer solicitation;
• unfair competition;
• and misuse of company property.

Startup founders should therefore avoid treating the non-compete clause as their only protection.

Confidentiality Is Often More Important Than the Non-Compete

An employee’s confidentiality obligations can continue after termination where necessary to protect the employer’s legitimate interests.

Article 396 expressly provides that the employee must continue to preserve relevant secrets after termination to the extent required for protection of the employer’s legitimate interests.

This can be extremely important.

Suppose the non-compete clause is invalid because it is excessively broad.

That does not mean the former employee is entitled to:

• copy source code;
• disclose customer data;
• publish trade secrets;
• transfer confidential pricing;
• take internal investor decks;
• or use confidential technical documentation.

A good startup legal structure should therefore include strong confidentiality and information-security protection independent of the non-compete.

Non-Solicitation Can Be More Targeted Than a Complete Non-Compete

In some situations, the real commercial concern is not that an employee works for a competitor.

The concern is that the employee will:

• take customers;
• recruit the startup’s engineering team;
• or move key accounts.

Instead of preventing the employee from working in the industry entirely, a more targeted structure may restrict specific solicitation activities.

For example:

“For twelve months, the employee shall not actively solicit customers with whom the employee had material business contact during the final twelve months of employment.”

This may be more proportionate than:

“The employee may not work for any competitor.”

However, non-solicitation provisions should also be reviewed for proportionality and legitimate interest rather than assumed to be automatically enforceable.

Customer Non-Solicitation Should Be Narrowly Defined

A restriction concerning “all customers of the company” may still be too broad where the employee never had access to most of them.

A more defensible approach may focus on:

• customers managed by the employee;
• customers about whom the employee obtained material confidential information;
• or customers with whom the employee had direct contact.

This ties the restriction more closely to the employer’s legitimate interest.

Employee Non-Solicitation Requires Additional Caution

A startup may also want to prevent former managers from recruiting colleagues.

For example:

A CTO resigns and establishes another startup.

The CTO then attempts to hire the entire engineering team.

A carefully drafted employee non-solicitation arrangement may help protect organisational stability.

However, employers should distinguish agreements with their own employees from agreements made between competing companies not to hire each other’s workers.

The latter can create competition-law risks.

Employer-to-Employer “No-Poach” Agreements Are a Different Legal Issue

Suppose Startup A and Startup B privately agree:

“We will never hire each other’s employees.”

This is not the same thing as Startup A signing a reasonable Article 444 non-compete with its employee.

The Turkish Competition Authority adopted its Guidelines on Competition Infringements in Labour Markets on 21 November 2024.

The Authority expressly treats labour as a parameter of competition and examines agreements between employers that restrict employee mobility or coordinate employment conditions under Article 4 of Competition Law No. 4054.

The Competition Authority has also distinguished employer-employee restrictions under TBK Article 444 from arrangements between employers restricting competition for employees. The latter may fall within competition-law enforcement even though properly structured employee non-competes are separately recognised by the Code of Obligations.

Therefore, startups should not attempt to solve employee-retention problems by establishing informal “gentlemen’s agreements” with competitors.

Why No-Poach Agreements Are Particularly Relevant to Startup Ecosystems

Startup communities can be small.

Founders may know each other personally.

A conversation may occur:

“Don’t hire my engineers and I won’t hire yours.”

This may appear commercially convenient, but it can restrict:

• employee mobility;
• wage competition;
• hiring conditions;
• and competition for talent.

The Competition Authority’s labour-market enforcement framework means startups should be especially careful with such arrangements.

The safer solution is generally to protect legitimate company interests through:

• confidentiality;
• intellectual property protection;
• retention incentives;
• carefully drafted employee non-competes;
• and appropriate non-solicitation arrangements,

rather than agreements between competing employers.

What Happens If an Employee Breaches a Valid Non-Compete?

Article 446 regulates the consequences.

An employee violating a valid non-compete may be required to compensate the employer for resulting losses.

The startup may therefore seek damages if it can establish:

• a valid non-compete;
• breach;
• damage;
• and the necessary causal connection.

However, proving actual loss may sometimes be difficult.

For this reason, employment agreements frequently contain a contractual penalty.

Can a Startup Include a Penalty Clause?

Yes, but the structure matters.

Article 446 specifically contemplates a penalty clause attached to a non-compete.

Unless the contract provides otherwise, the employee may generally free themselves from the non-compete obligation by paying the agreed penalty, while remaining liable for any damage exceeding the penalty amount.

This consequence is often overlooked.

Founders sometimes assume:

“We included a EUR 50,000 penalty, so we can both collect EUR 50,000 and force the employee to leave the competitor.”

Not automatically.

The statutory structure requires more careful drafting.

Can the Startup Force the Employee to Stop Working for the Competitor?

Potentially, but this remedy is subject to additional requirements.

Article 446 provides that, in addition to seeking the penalty and additional damages, the employer may demand termination of the prohibited conduct only if:

• that right was expressly reserved in writing in the agreement;
• the importance of the employer’s infringed or threatened interest;
• and the employee’s conduct

justify such relief.

Therefore, a startup wanting the possibility of injunctive-type enforcement should address that issue expressly in the contract.

A damages clause alone does not automatically guarantee the ability to stop the employee from working elsewhere.

Excessive Penalties Can Create Additional Problems

A startup should also avoid using an obviously disproportionate penalty purely to frighten employees.

For example:

Employee annual salary: TRY 1 million.

Non-compete penalty: EUR 5 million.

A court may scrutinise such a contractual structure under applicable principles governing penalties and employee protection.

The amount should reflect:

• likely commercial damage;
• the employee’s role;
• confidentiality exposure;
• duration;
• and proportionality.

The purpose should be reasonable protection, not economic coercion.

When Does a Non-Compete Automatically End?

Article 447 contains very important termination rules.

First, the non-compete ends where it is established that the employer no longer has a genuine interest in maintaining the restriction.

Second, the non-compete ends if:

• the employer terminates the employment contract without a justified reason; or
• the employee terminates for a reason attributable to the employer.

These provisions are extremely important for startup layoffs.

Example: Startup Terminates Employee Without Just Cause

Suppose a startup is reducing costs after an unsuccessful investment round.

The company terminates a senior engineer even though the employee committed no misconduct.

The employment agreement contains a twelve-month non-compete.

The startup then tells the employee:

“We terminated you, but you still cannot work for any competitor for one year.”

Article 447 may prevent the employer from continuing to rely on the restriction where termination occurred without the legally relevant justified reason.

A company therefore cannot assume that every non-compete survives every termination.

Example: Employee Resigns Because of Employer Breach

Suppose the startup repeatedly fails to pay salary and the employee terminates the employment relationship for a reason attributable to the employer.

Again, Article 447 may terminate the non-compete obligation.

This rule prevents employers from causing termination through their own misconduct and simultaneously restricting the employee’s future livelihood.

What If the Employee Simply Resigns for a Better Offer?

The result may be different.

If the employee voluntarily resigns without a reason attributable to the employer and a valid non-compete exists, the restriction may continue according to its terms.

The startup would still need to establish:

• validity under Article 444;
• proportionality under Article 445;
• and the applicability of the restriction to the new activity.

What If the Employer No Longer Operates in That Market?

Article 447 also states that the restriction ends where the employer no longer has a genuine interest in maintaining it.

For example:

Startup A sells its entire fintech division.

It permanently exits the fintech market.

A former employee remains subject to a non-compete targeting fintech services.

The company may have difficulty establishing a genuine continuing interest in restricting that employee.

A non-compete exists to protect legitimate competition-sensitive interests, not merely to penalise a former employee.

What If the Employee Has Stock Options or Startup Shares?

Employee equity does not automatically make every non-compete valid.

Suppose an employee owns:

• 0.5% shares;
• vested options;
• or phantom stock.

That fact may affect the commercial relationship, but the employee’s employment-based post-termination restriction should still be analysed under the applicable legal framework.

If the employee is also a shareholder, separate contractual restrictions may exist under:

• the shareholders’ agreement;
• share-transfer documentation;
• investment documents;
• or an exit agreement.

Those restrictions should be analysed independently.

A founder selling a significant stake in a company may also face a different non-compete analysis from an ordinary employee.

Therefore, startups should not use one identical non-compete clause for:

• founders;
• employees;
• shareholders;
• consultants;
• and sellers of businesses.

The legal interests can differ substantially.

What About Freelancers and Consultants?

Articles 444–447 specifically concern employment/service relationships falling within the relevant statutory framework.

A freelancer or independent consultant may be subject to contractual non-compete provisions under general contract law, but the analysis can differ from the employee-protection regime.

Startups should therefore determine the real nature of the relationship.

Calling somebody a “consultant” does not necessarily determine their legal status if the factual relationship functions as employment.

Different agreements should be prepared for:

• employees;
• founders;
• freelancers;
• advisors;
• and corporate contractors.

Which Court Handles Post-Employment Non-Compete Cases?

This was historically controversial in Turkish practice.

However, the issue was resolved by the Yargıtay İçtihatları Birleştirme Büyük Genel Kurulu in its decision dated 13 June 2025, E. 2023/1, K. 2025/3.

The decision, published in the Official Gazette on 12 September 2025, held that disputes arising from breaches of post-employment non-compete obligations under TBK Articles 444–447 fall within the jurisdiction of the Commercial Courts of First Instance (Asliye Ticaret Mahkemeleri).

The distinction remains important because conduct occurring during employment may instead arise from the employee’s continuing duty of loyalty under Article 396.

For startups considering enforcement, correctly characterising the conduct therefore matters procedurally as well as substantively.

Startup Example: Validly Structured Non-Compete

Consider the following situation.

A Turkish fintech startup employs a Head of Enterprise Sales.

The employee:

• manages the company’s 25 largest clients;
• knows customer-specific pricing;
• knows renewal dates;
• has access to confidential margins;
• participates in strategic planning;
• and receives information concerning unreleased products.

The agreement provides that, for twelve months after termination, the employee will not work in substantially equivalent enterprise-sales activities for businesses directly competing with the startup’s identified fintech product in Turkey.

The restriction is:

• written;
• limited in duration;
• limited geographically;
• limited by activity;
• connected to genuine customer information;
• and connected to potentially substantial commercial damage.

Such a clause is substantially more defensible than a blanket prohibition covering all industries worldwide.

Startup Example: Excessively Broad Non-Compete

Now consider:

A junior UX designer works for a Turkish mobile application startup for five months.

The contract states:

“For two years after employment, the employee may not directly or indirectly work for, advise, invest in or cooperate with any technology, internet, software, advertising, e-commerce or digital company anywhere in the world.”

The employee had no:

• customer relationships;
• strategic information;
• access to source code;
• confidential pricing;
• or material trade secrets.

This clause raises serious validity and proportionality concerns.

It restricts almost the employee’s entire professional sector without an obvious connection to substantial damage to the startup.

Article 445 exists precisely to prevent restrictions that unfairly endanger the employee’s economic future.

How Should Startups Protect Themselves If Broad Non-Competes Are Risky?

The most effective protection is usually multi-layered.

A startup should not rely on one sentence stating:

“You cannot work for competitors.”

Instead, the legal framework can combine several mechanisms.

1. Confidentiality Agreement

Clearly identify confidential information.

2. Trade Secret Controls

Limit access according to employee roles.

3. Intellectual Property Assignment

Ensure company-created software and other IP are properly controlled.

4. Narrow Non-Compete

Use post-employment restrictions only where Article 444 requirements are realistically satisfied.

5. Customer Non-Solicitation

Protect customer relationships where justified.

6. Employee Non-Solicitation

Protect strategically important teams through proportionate restrictions.

7. Garden Leave or Notice Management

Where legally and commercially appropriate, manage sensitive transitions during the employment relationship.

8. Access Control

Employees should not automatically have access to all company information.

9. Offboarding Procedure

Immediately revoke:

• GitHub;
• cloud;
• CRM;
• email;
• server;
• and administrator access.

10. Return and Deletion Certification

Require return or deletion of company materials and credentials.

11. Security Logging

Maintain proportionate records showing downloads and transfers of sensitive information.

12. Retention Incentives

Use:

• stock options;
• vesting;
• bonuses;
• and career progression

to reduce unwanted turnover rather than relying exclusively on legal prohibition.

Why Access Control Is Better Than an Extremely Broad Non-Compete

Suppose every engineer can access:

• the entire production database;
• every customer contract;
• every investor file;
• all pricing information;
• and the complete code base.

The startup may later argue that every engineer possesses dangerous confidential information.

But that itself reflects poor governance.

A stronger structure applies need-to-know access.

This helps the startup prove that particular employees genuinely had access to specific sensitive information.

It also reduces the consequences of:

• resignation;
• cyberattacks;
• insider threats;
• and accidental disclosure.

Source-Code Access Should Be Carefully Managed

For software startups, offboarding should include:

• repository access removal;
• API key rotation;
• cloud credential changes;
• SSH key revocation;
• database access termination;
• removal from password managers;
• and review of recent downloads.

A non-compete cannot compensate for poor security architecture.

Should Every Startup Employee Sign the Same Non-Compete?

Generally, a role-based approach is more defensible.

For example:

Senior Executive

Potentially broader restriction because of extensive strategic knowledge.

CTO

Strong protection may be justified concerning proprietary technology and direct competitors.

Enterprise Sales Director

Customer-focused restriction may be particularly relevant.

Software Engineer

Restriction may be targeted at proprietary product areas rather than the entire technology industry.

Junior Employee

A full post-employment non-compete may not be justified at all.

The employer should identify why each category creates a genuine competitive risk.

Annual Review Can Be Useful

Startups change rapidly.

A restriction drafted when the company operates only in Istanbul may no longer reflect the business after expansion into ten countries.

Conversely, an employee’s role may change from:

junior developer

to

VP Engineering.

Employment documentation should therefore be reviewed when roles and business activities materially change.

Non-Compete Checklist for Turkish Startups

Before relying on a post-employment restriction, founders should ask:

1. Is the employee legally capable of entering the restriction?
2. Is the non-compete in writing?
3. Did the employee have access to customers?
4. Did the employee have access to production secrets?
5. Did the employee obtain significant confidential business information?
6. Could using that information cause substantial damage?
7. What specific interest is the startup protecting?
8. Does the employee actually work in a strategically sensitive position?
9. Is the restricted activity clearly defined?
10. Does the restriction cover only real competitors?
11. Is the geographic area justified?
12. Does the company actually operate in that territory?
13. How long does the confidential information remain valuable?
14. Is a two-year restriction really necessary?
15. Could six or twelve months be sufficient?
16. Does the restriction unfairly endanger the employee’s career?
17. Should compensation be paid during the restriction?
18. Is there a contractual penalty?
19. Is the penalty proportionate?
20. Does the contract expressly reserve the right to seek cessation of competitive activity where Article 446 requirements are met?
21. Is a confidentiality obligation included separately?
22. Is customer solicitation restricted where appropriate?
23. Is employee solicitation addressed where appropriate?
24. Are trade secrets technically protected?
25. Is repository access controlled?
26. Is there a formal offboarding procedure?
27. Why is the employment relationship ending?
28. Did the employer terminate without justified reason?
29. Is the employee terminating because of employer conduct?
30. Does the startup still have a genuine interest in the restriction?
31. Is the employee also a shareholder?
32. Are separate shareholder restrictions involved?
33. Has the startup made no-poach arrangements with other companies?
34. Could those arrangements create competition-law risk?
35. Can the startup prove all of these matters if enforcement becomes necessary?

If several of these questions cannot be answered, the non-compete may not provide the protection founders expect.

Frequently Asked Questions About Startup Employee Non-Competes in Turkey

Can a startup prevent an employee from joining a competitor?

Potentially yes, but only where a valid and proportionate post-employment non-compete exists under TBK Articles 444–447.

Is every non-compete clause in an employment contract valid?

No. The employee must have gained access to relevant customers, production secrets or business information whose use could cause substantial damage, and the restriction must remain proportionate.

Does the non-compete have to be written?

Yes. Article 444 requires a written undertaking.

How long can a non-compete last?

Except in special circumstances, Article 445 provides that it may not exceed two years. The restriction must nevertheless remain reasonable, and the judge can reduce an excessive term.

Can the startup prohibit the employee from working anywhere in the world?

Such a restriction would require a strong justification and must satisfy the geographical proportionality requirement. A worldwide restriction should not be assumed valid merely because the company operates online.

Can the employee still use professional experience acquired at the startup?

General professional skills and experience should be distinguished from the former employer’s confidential information, customer knowledge and trade secrets.

Does confidentiality continue after employment?

Potentially yes. Article 396 requires post-employment confidentiality to continue to the extent necessary to protect the employer’s legitimate interests.

Can the contract contain a penalty for breach?

Yes. Article 446 expressly recognises contractual penalties in non-compete arrangements, subject to the statutory structure and other applicable principles.

Can the startup force the former employee to leave the competitor?

Potentially, but Article 446 requires the right to demand cessation to be expressly reserved in writing, and the importance of the threatened interest and employee conduct must justify the remedy.

Does the non-compete continue if the startup fires the employee?

Not always. Article 447 provides that the restriction ends where the employer terminates without a justified reason or where the employee terminates for a reason attributable to the employer.

Can competing startups agree not to hire each other’s employees?

This is a separate competition-law issue and can create significant risk under Law No. 4054 and the Competition Authority’s labour-market guidance.

Which court hears disputes concerning post-employment non-competes?

Following the Yargıtay Grand General Assembly for the Unification of Judgments decision dated 13 June 2025, disputes concerning violations of post-employment non-compete obligations under TBK Articles 444–447 are heard by Commercial Courts of First Instance.

Conclusion: Are Non-Compete Clauses Preventing Startup Employees From Joining Other Companies Valid?

Turkish law does not establish a general rule allowing startups to prevent former employees from continuing their careers.

Nor does it prohibit every post-employment restriction.

Instead, the Turkish Code of Obligations attempts to balance two legitimate interests:

the startup’s right to protect commercially valuable information

and

the employee’s right to continue earning a livelihood and developing a professional career.

Article 444 permits written post-employment non-compete agreements but only where the employee gained access to customer relationships, production secrets or relevant business information and where use of that information could cause substantial damage to the employer.

Article 445 then requires proportionality.

A restriction cannot unfairly endanger the employee’s economic future through excessive limitations concerning:

• territory;
• duration;
• or type of activity.

Except in special circumstances, the restriction cannot exceed two years, and a judge may reduce an excessive clause.

For startups, this means clauses such as:

“The employee may not work for any technology company anywhere in the world for two years”

should not be treated as automatically enforceable simply because the employee signed the agreement.

A stronger non-compete might instead say, in substance:

“For a limited period following termination, the employee will not perform substantially equivalent activities for directly competing businesses in the defined market where the employee’s access to specified confidential information or customer relationships creates a material risk to the company.”

The exact drafting must, of course, reflect the employee and business concerned.

Startups should also distinguish non-compete protection from confidentiality.

Even if a former employee is legally free to join a competitor, that does not generally entitle the employee to:

• take source code;
• disclose customer lists;
• copy pricing models;
• transfer confidential roadmaps;
• expose security architecture;
• or misuse trade secrets.

Article 396 expressly recognises continuing confidentiality obligations where necessary to protect the employer’s legitimate interests.

This means the most effective startup protection strategy is rarely a single broad non-compete clause.

A more sustainable framework combines:

• role-specific non-competes;
• confidentiality;
• intellectual property provisions;
• customer non-solicitation;
• employee non-solicitation where appropriate;
• access controls;
• cybersecurity;
• offboarding procedures;
• retention incentives;
• and equity vesting.

Founders must also understand how employment termination affects enforceability.

Under Article 447, a startup that terminates an employee without the legally relevant justified reason may lose the benefit of the non-compete. The restriction can similarly end where the employee terminates because of reasons attributable to the employer.

Accordingly, every enforcement decision should begin by examining:

Why did the employment relationship end?

The remedy structure must also be carefully drafted.

Article 446 allows an employer to claim losses caused by breach and recognises contractual penalties. However, if the employer wants the ability to demand cessation of the competitive conduct in addition to financial remedies, that possibility must be expressly reserved in writing and must be justified by the seriousness of the threatened interest and the employee’s conduct.

Another major risk lies outside employment law entirely.

Startups sometimes try to preserve teams by agreeing informally with competitors:

“You don’t hire our developers; we won’t hire yours.”

This is fundamentally different from a valid employee non-compete.

The Turkish Competition Authority’s Labour Market Guidelines, adopted in November 2024, expressly recognise employee mobility and employment conditions as dimensions of competition and subject restrictive employer-to-employer arrangements to competition-law scrutiny.

Therefore, a startup should protect itself through its relationship with employees, confidential information and legitimate corporate interests—not through potentially anticompetitive agreements with other employers.

The procedural framework has also become clearer.

Following the 13 June 2025 binding Yargıtay unification decision, claims arising from breach of post-employment non-compete agreements under TBK Articles 444–447 fall within the jurisdiction of the Commercial Courts of First Instance.

For founders, the practical rule is therefore simple:

Do not ask how to stop employees from ever joining competitors.

Ask instead:

Which employees genuinely possess competitively sensitive information?

Which information could seriously harm the startup if used?

For how long does that information remain valuable?

Which competitors create the actual risk?

Which geographical market is truly relevant?

Can the same protection be achieved through confidentiality or non-solicitation rather than a complete work prohibition?

Why is the employee leaving?

Can the restriction survive judicial scrutiny without unfairly destroying the employee’s economic future?

A non-compete designed around these questions is far more likely to protect a startup effectively than a boilerplate clause copied into every employment agreement.

For Turkish startups, the objective should therefore be proportionate protection of legitimate business interests, not the elimination of employee mobility.

That approach is not only more consistent with Turkish law.

It is also usually better corporate governance for a startup seeking talented employees, venture capital investment and long-term growth.