Software Engineer Salaries in Colombia: 2025 Data for 2026 Hiring

GSC's weighted analysis of DANE's 2025 household survey puts median main-job cash pay for salaried software developers at COP 4.635 million per month. The middle half ran from COP 3.0 million to COP 8.0 million per month. These figures cover occupation 2512 and pay before deductions. Total compensation and employer cost sit outside the measure.

The 2025 Stack Overflow Developer Survey provides a separate benchmark: median reported annual compensation of US$39,874, with a middle half from US$14,681 to US$58,072. That measure may include salary, bonuses, and perks across different employment arrangements. Keep the two sources separate and test a live offer against current COP evidence for the defined role.

Colombia software engineer compensation at a glance

DANE and Stack Overflow answer different questions. DANE supplies weighted employee pay in local currency for one official occupation; Stack Overflow supplies self-reported annual compensation for selected developer roles.

The units are deliberately not normalized in this table. Annualizing DANE pay or converting Stack Overflow compensation to COP would make the values look more comparable without aligning their populations or compensation definitions.

DANE supplies a local employee-pay benchmark

GSC derived the national estimate from DANE's 2025 GEIH occupied-person microdata for occupation 2512 and salaried positions with positive P6500. That field records prior-month cash earnings from the main job before deductions, and the calculation applies DANE's official survey weight.

The derivation does not implement DANE's full complex-survey variance design, so it does not attach a confidence interval. Independent-worker income also sits outside this employee-pay distribution.

For a live search, use comparable COP offers, candidate expectations, current vacancies, and recruiter evidence. Record the role, level, location, pay measure, and source date for every benchmark.

Wider workforce, export, provider, and infrastructure context appears in the Colombia software industry data.

Stack Overflow compensation distribution

Stack Overflow converted responses reported in multiple currencies into one annual USD field. The table keeps that unit and shows the middle of the filtered distribution.

The quartiles mark the middle half of the filtered responses, while the mean and median describe only this survey slice. Compensation can move with responsibility, technical depth, experience, employer market, work arrangement, and package design, so a live offer still needs current evidence from the labor market being hired.

How to read the Stack Overflow benchmark

The source is the public Stack Overflow Developer Survey 2025 microdata. Stack Overflow fielded the survey from May 29 to June 23, 2025 and converted reported salaries to US dollars using exchange rates from June 25, 2025.

GSC limited the analysis to Colombia respondents in selected software-development roles with usable annual compensation after quality screening. The result is a self-selected, mixed-employment benchmark and does not represent national payroll.

ConvertedCompYearly is an annual US-dollar conversion of the respondent's reported compensation. The measure is broader than base salary. Stack Overflow asks for salary, bonuses, and perks before taxes and deductions.

Respondents used more than one currency and included both employees and independent workers. Read the result only as reported annual compensation among selected survey respondents.

The public sample becomes too thin once divided by role or experience, so this article does not publish subgroup medians or standardized career-level bands.

For an actual role, define the work before choosing a benchmark. A back-end engineer maintaining internal line-of-business services, a platform engineer handling a regulated production environment, and a technical lead owning customer-facing architecture can require different markets despite overlapping titles.

Use COP for offers and USD as a dated translation

Use Banco de la República's representative market exchange rate, or TRM, in effect when an offer or budget is approved. A later exchange rate can change the USD equivalent without changing the developer's contractual COP pay. Do not back-convert the Stack Overflow result with a newer rate and treat it as a local salary observation.

Use this normalization routine instead:

1. Keep contractual base salary and recurring payroll items in COP.

2. State whether each value is monthly or annual and how many payments it assumes.

3. Separate base pay, variable pay, statutory benefits, voluntary benefits, and equity.

4. Attach the Banco de la República TRM and effective date to every USD translation.

5. Model exchange-rate sensitivity for a USD budget rather than promising a fixed USD equivalent indefinitely.

6. Refresh the translation when the offer, budget, or contract is approved.

Two offers with the same headline USD equivalent can still differ in contractual COP, bonus probability, benefit value, review timing, and who carries exchange-rate risk.

Salary is not loaded employer cost

A direct employee creates obligations and operating costs beyond the salary line. Colombia's rules support a component-by-component build; one universal percentage uplift lacks support.

Colombia's pension and payroll-contribution authority, UGPP, shows why social-security and parafiscal calculations cannot be collapsed into one assumption: payment categories and payroll events can enter their contribution bases differently. Employment benefits and schedule premiums require separate calculations. Build those details into an employer-specific hiring-cost calculation instead of applying a percentage to survey compensation.

Applying a percentage to US$39,874 would therefore be misleading. The survey reports annual compensation in converted USD; a Colombian employment contract defines salary in COP. Employer cost changes with contribution bases, exemptions, risk class, schedule, and package design. Obtain a current payroll calculation and legal review for the real case; the cost to hire software developers in Colombia guide develops those employer obligations and route-specific costs.

Salary, EOR invoices, and provider rates answer different questions

Keep each commercial measure tied to the costs and responsibilities it actually includes.

In GSC's documented Colombia provider set, about 57% of profiles that disclose a rate publish a US$25–49 hourly directory band. That is public positioning. Signed contract rates, employee wages, loaded employer costs, and project budgets remain separate measures.

Don't multiply an hourly provider band by 2,080 and call the result equivalent salary. A provider may cover staffing, paid non-working time, delivery management, operating overhead, risk, and margin. State the exact coverage in the proposal and contract.

Begin by choosing a hiring model, then compare the responsibilities and costs included in each option. The software outsourcing cost guide supplies a commercial framework.

The Colombia page helps buyers examine Colombian software companies once the comparison moves from survey benchmarks to named providers, without confusing directory pricing with payroll data or employee compensation.

Build a defensible offer range

Use six steps to build and test a role-specific range.

1. Define the work

Write the expected outcomes, production risk, decision authority, and first-year success measures. “Senior” is not a complete specification.

A consistent map of software engineering levels can define decision scope before local market evidence is used to price the role.

2. Define the labor market

State whether the role is national remote, city-based, hybrid, or on-site. Add any foreign-hours, language, or on-call requirement.

Use the working-window tables and operating controls in nearshore software development in Colombia when foreign-hours coverage shapes the role.

3. Normalize every compensation source

Record each benchmark's population, geography, employment status, pay measure, period, and sample size, then note whether it includes bonus or benefits; reject sources that leave those fields undefined.

4. Set the COP package

Price monthly base salary separately from variable pay, statutory items, voluntary benefits, and any currency-protection term. Use current candidates and comparable offers to test the range.

5. Add employment or provider cost

Direct employment needs a current employer-specific payroll build. An EOR comparison should isolate employee cash, statutory pass-throughs, fees, foreign exchange, and exit terms. For staff augmentation, normalize hours, paid leave, management, and replacement.

6. Test the range in the market

Track qualified applicants, expected pay, assessment pass rate, and declined-offer reasons. Once the search is live, those results become more useful than a country median.

When a Colombia median is the wrong tool

City, seniority, and savings claims need role-specific evidence. The national benchmarks also cannot convert employee compensation into vendor pricing or resolve an undefined role.

Specialized, regulated, leadership, customer-facing, and nonstandard-hours positions require current evidence from the relevant labor market. If those COP results do not support the budget, a national survey benchmark should not override the market response.

Limitations

GEIH does not include a full survey-design confidence interval or independent-worker income. Stack Overflow is self-selected and becomes too thin for career-level bands. Both figures are historical planning inputs; current candidates and comparable offers should set the live range.