42 enriched SWE postings in 2026-W44. Share = postings mentioning the technology ÷ that number — postings still awaiting enrichment are excluded from the denominator, so a processing backlog cannot depress every share at once. The chart shows the top 15; the table in section 3 lists the top 30.
| Technology | Share | Change | Postings |
|---|---|---|---|
| linux | 26.2% | +11.4pp | 11 |
| aws | 26.2% | +2.3pp | 11 |
Nothing fell this week.
Change is in percentage points of share, not relative percent: a technology going from 1 to 3 postings would otherwise read as +200% and top the board. Boards consider every technology above the bar, not only the 30 the table below shows.
Premium compares the median advertised monthly salary of postings mentioning a technology against the overall median, over the trailing 90 days. Baseline: S$10500, the median of 391 postings advertising a monthly range — medians pin the unit so the figures are comparable. Separately, 100.0% of SWE postings state pay at all (391 of 391, in any unit); the rest hide it, and no figure here describes them. Entry-friendly is computed over the same 90-day window. Premium mixes seniority in (senior roles name more infrastructure); pick an experience band above to compare within one. Entry-friendly = the share of postings mentioning the technology that ask for at most 2 years' experience, or are Intern/Junior roles with no stated requirement. The table lists the top 30 technologies by postings.
| Technology | Kind | Postings | Share | Salary premium | Entry-friendly |
|---|---|---|---|---|---|
| aws | cloud | 11 | 26.2% | -7.1% | 0.0% |
| linux | tool | 11 | 26.2% | -7.1% | 0.0% |
| python | language | 8 | 19.0% | -7.1% | 0.0% |
| google-cloud | cloud | 7 | 16.7% | +0.0% | 0.0% |
| azure | cloud | 5 | 11.9% | +0.0% | 0.0% |
| java | language | 5 | 11.9% | +4.8% | 0.0% |
| kubernetes | tool | 4 | 9.5% | +0.0% | 0.0% |
| go | language | 3 | 7.1% | —(n=11) | 0.0% |
| shell | language | 3 | 7.1% | -7.1% | 0.0% |
| terraform | tool | 3 | 7.1% | —(n=12) | 0.0% |
| ansible | tool | 2 | 4.8% | —(n=19) | 0.0% |
| spring | framework | 2 | 4.8% | —(n=3) | 0.0% |
| sql | language | 2 | 4.8% | —(n=9) | 0.0% |
| docker | tool | 1 | 2.4% | —(n=11) | 0.0% |
| javascript | language | 1 | 2.4% | —(n=12) | 0.0% |
| kafka | tool | 1 | 2.4% | —(n=2) | 0.0% |
| kibana | tool | 1 | 2.4% | —(n=6) | 0.0% |
| mssql | database | 1 | 2.4% | —(n=2) | 0.0% |
| nodejs | language | 1 | 2.4% | —(n=3) | 0.0% |
| rust | language | 1 | 2.4% | —(n=2) | 0.0% |
| spark | framework | 1 | 2.4% | —(n=1) | 0.0% |
| typescript | language | 1 | 2.4% | —(n=3) | 0.0% |
These are MyCareersFuture's own skill tags — the competencies the employer filled in on the form, over the trailing 90 days (2026-08-08 → 2026-11-05) across 391 postings. They are not the technology ranking above: languages and frameworks appear only in the free-text description, which is why this system reads it separately. "Must-have" is the share of postings listing the tag that marked it essential rather than desirable — a tag that is everywhere but rarely essential is table stakes, one that is usually essential is a filter someone is applying.
| Skill | Postings | Share | Marked must-have |
|---|---|---|---|
| CISSP | 148 | 37.9% | 14.9% |
| Security Operations | 99 | 25.3% | 6.1% |
| Cybersecurity | 94 | 24.0% | 14.9% |
| Computer Science | 86 | 22.0% | 0.0% |
| Security Governance | 78 | 19.9% | 1.3% |
| Security Architecture | 74 | 18.9% | 12.2% |
| Enterprise Security Solutions | 72 | 18.4% | 12.5% |
| Risk Management | 72 | 18.4% | 0.0% |
| Threat Intelligence | 71 | 18.2% | 0.0% |
| Cybersecurity Engineering | 69 | 17.6% | 52.2% |
| Security Incident Response | 67 | 17.1% | 28.4% |
| Network Security | 64 | 16.4% | 14.1% |
| Cyberark | 62 | 15.9% | 56.5% |
| SIEM | 61 | 15.6% | 49.2% |
| Stakeholder Management | 54 | 13.8% | 0.0% |