Methodology

Transparency builds trust. This page explains (at a practical level) how we compute, label, and update our data and tools.

Last updated: 2025-12-27 By Ivo Pereira (IT Jobs List).

General principles

We try to build a site people can use for decisions (jobs, offers, contracting) without inflating certainty. When information is ambiguous, we label it. When rules change, we version pages.

  • We optimize for usefulness and trust.
  • Romania-heavy fiscal tools are versioned by tax year and effective date.
  • We publish limitations and assumptions so readers can judge the output.

Salary Insights

Salary Insights are derived from aggregated job listing data (salary ranges when available). Different companies report compensation differently, so we focus on trends and distributions.

  • We use only listings with explicit salary ranges for salary charts.
  • We may exclude outliers and incomplete entries to reduce noise.
  • Where relevant, we show sample size signals (counts) to avoid false certainty.

Layoffs

Layoff data can be sensitive and sometimes incomplete. We aim to present a useful tracker without amplifying rumors or personal data.

  • We prefer primary sources and reputable publications where available.
  • We remove personal data from submissions.
  • We label status clearly (e.g., confirmed vs unconfirmed) when possible.

Tech Radar

Tech Radar is a signal derived from aggregated job listings (demand signals, trend direction). It is not a guarantee of hiring outcomes.

  • Signals can be affected by seasonality and posting volume.
  • We focus on directionality and relative comparisons rather than absolute numbers.
  • We update the radar periodically and adjust the methodology when needed.

Tools & calculators

Our tools are built for practical decision-making. For Romania-heavy fiscal tools we version by tax year and effective date.

  • Assumptions are displayed clearly and are editable where rules vary.
  • Outputs are meant for estimation and planning; confirm details with an accountant/lawyer if needed.
  • We add “common mistakes” and examples to reduce misuse and improve accuracy.

Updates and corrections

If something is outdated or incorrect, we want to know. For changes that affect money or legal decisions, we prioritize quick fixes and clear changelogs (when relevant).

  • Send the page URL and what should change.
  • If you can, include a source (official doc, payroll statement, or reputable publication).
  • We avoid publishing personal data in corrections or public notes.

Want to report an issue?

If you notice a mistake or outdated assumption, contact us with the page URL and what should change.