Salary Transparency - Why We Stay Silent, and Who Benefits From It
Someone else sits at the desk next to you. You work on the same codebase, you have the same experience, you passed the same interviews. Your relationship is good, your work quality is similar. But you don't know what they earn. They don't know what you earn. Nobody asks, nobody tells.
This isn't a salary taboo. It's information asymmetry. And it works in one direction: against you.
The rule "don't talk about salary" doesn't protect you. It blinds you. This rule protects the company - and the company knows it very well.
Three Sources of Taboo: Culture, Contract, or Envy?
Why is talking about salary considered improper in Türkiye? The answer is cultural, legal, and psychological. But each has a different owner.
First is cultural heritage. Since Ottoman times, openly discussing income, despite the polite wish of blessing, has been considered impolite. Even today, if you ask a relative's salary, you might hear "how embarrassing." This inheritance lives on in the software sector too.
Second is contract language. Many companies insert into employment agreements, often spoken casually before day one, a clause against sharing salary with colleagues. Its legal validity is debatable. But developers don't know this, or fear the risk.
Third is a false excuse: envy. "If salaries are transparent, lower-paid staff will resent, people will be upset, the team will fracture." This reasoning comes entirely from the company, and blames you, not itself. The logic: "You'll be the resentful one."
Yet in 2024, 4,589 developers contributed data to getsalary.dev. Median salary 132,500 TL. Nobody filled that database driven by envy. They wanted to share knowledge.
The Real Power of Transparency: Negotiation Is Played on an Uneven Board
Why does transparency matter? Because salary negotiations happen at a table already tilted.
First is negotiating power. When you walk in for a raise, the company has already told you there is no budget, rated you below expectation, or said the market did not support it. Against all these claims, what do you hold? Nothing. You see no one else. You don't know what anyone else earns. The board is stacked against you.
From getsalary.dev data, you learn this: in the same role, same experience, same company, salaries can range from 80,000 to 160,000 TL. Knowing this lets you build your case on evidence.
Second is performance review evidence. When told "we rated you mid-level," the question is: what does mid-level pay in your role? Without data access, you are forced to accept the company's frame.
Anonymous, regional, role-based salary data puts you on the side of the table that speaks with evidence.
Third is regional wage awareness. In Türkiye's software market, there are wage differences between Istanbul, Ankara, Izmir, and Bursa. Remote work also introduced a second variable: experience and location affect every role, from accounting clerk to tech lead.
Without transparency, a company says "that's the market price." With it, you can ask why.
Türkiye's Legal Status: Is That Salary Confidentiality Clause Actually Valid?
Many developers think they have signed an employment agreement with a salary confidentiality clause. Or they remember being told "don't tell" on day one.
Briefly: Turkish law recognizes salary confidentiality clauses conditionally. The company's claim of "trade secret" holds in special cases, for example, if salary strategy leaking to a competitor creates real risk. But a regular developer telling a peer what they earn? Unlikely to cost them the job.
Of course, edge cases exist, management, commercial access, where confidentiality binds tighter. But the engineering team? By settled legal interpretation, salary confidentiality clauses stand only in narrow conditions.
Today's question isn't legal, it is social: even if you knew this, would you fear consequences anyway? If the company pressures you, what happens then?
Practical Transparency: Where to Start?
There are ways to begin learning through transparency.
First, anonymous platform contribution. getsalary.dev takes input from thousands yearly. No name, no email - you just add data to a secure repository. When hundreds contribute, thousands of developers gain insight. You can keep your own salary private - what matters is that by adding data, everyone at the table sees a clearer picture.
Second, team-level discussion, carefully. If your manager doesn't suppress salary talk, discussing with peer developers, especially trusted friends, becomes normal over time. Some teams have shifted their culture this way: open salaries improve team morale.
Third, mentor or advisor. If you have a former colleague or teacher you trust, asking "what would you have earned in this role" is fair game. Often, experienced perspective illuminates corners your own eyes cannot see.
Fourth, sector reports. Beyond getsalary.dev, institutions and firms publish salary data. Each has different assumptions, but together they sketch a regional and role-based frame.
The Art of Talking About It: Whom, How Much Detail, How to Frame?
Talking about salary means talking smart. Because information sharing and job security must move together.
Whom to tell? Not your manager - not first. Tell a peer or former colleague. If you talk to your manager, frame it as a negotiation opening, not as disclosure.
How much detail? Not just a number - context matters too. If you say "I make 150," add "3 years' experience, software architect, remote." That way your counterpart sees the number as tied to your situation, not a universal truth.
How to frame? Start with "When I switched companies, I did market research and..." or "getsalary.dev data showed..." This shifts the tone from discontent to understanding.
Why Contribute to getsalary.dev?
getsalary.dev was fed by 4,589 developers in 2024. It is Türkiye's largest salary database in software.
Contributing has two benefits.
First is collective. When you and 4,588 others share data, the sector's real salary distribution emerges. What is the median for a role? What is the range by region? How does it shift year to year? This knowledge strengthens thousands of future negotiators.
Second is personal. You see where your title-experience-location combination sits. Is 150,000 fair? 180,000? You will never know with certainty. But with 4,589 data points, you will see the median.
From there, it is your call.
Wage Transparency Is Part of Democratic Negotiation
"Don't talk about salary" doesn't protect developers. It protects the company. It blinds you.
If we stay silent, that silence won't cost the company productivity loss. Turnover accelerates, a departed good developer is replaced. Imbalance at the negotiation table lets the company quote you a lower number.
If we talk, anonymously or with care to keep conversations private, the picture shifts. The company cannot tell the next candidate "that is the market." The new hire knows the range. At performance review, they argue with data.
Information asymmetry is a one-directional weapon. Sharing information makes negotiations honest.
Your part: contribute to getsalary.dev once. In learning about yourself, you help the sector learn about itself.