CV for tech jobs in Switzerland 2026: software, DevOps and data

Tech CVs in Switzerland occupy an interesting middle ground between the lean, metrics-driven format expected in Silicon Valley and the more structured European format common in Germany and France. Swiss tech employers, particularly international-facing firms, are comfortable with two-page CVs for senior candidates and expect GitHub or GitLab portfolio links for engineering roles. The most common failure in Swiss tech applications is a CV that lists technologies without context: tools named without projects, stacks listed without scale, certifications noted without the problems they helped solve.

Tech stack formatting: the four-tier structure

Unstructured technology lists are one of the weakest elements of many tech CVs. A flat list of twenty technologies provides no signal about depth of expertise, recency of use, or how the technologies relate to each other. The recommended structure for Swiss tech CVs organises skills into four tiers: programming languages (Python, Java, TypeScript), frameworks and libraries (React, FastAPI, Spring Boot), tools and platforms (Docker, Kubernetes, Terraform, Jenkins), and cloud providers (AWS, GCP, Azure) with specific service familiarity noted where relevant (AWS: Lambda, ECS, RDS).

Depth indicators, "primary", "proficient", "familiar", or years of active use alongside each entry add further signal. A recruiter or technical interviewer at Zühlke or Thoughtworks can quickly assess whether a candidate's Python expertise is production-grade or tutorial-level from the framing, without waiting for a technical screen to surface the gap.

GitHub and GitLab portfolio links

A GitHub or GitLab profile link should appear in the CV header alongside contact details for software engineering, DevOps, and data engineering roles. The profile itself must be maintained: repositories should have clear README files, recent commit history, and, for the most relevant projects, a brief description of the problem solved and the technical approach.

A GitHub profile with 200 contributions in the last year, several starred repositories, and clean code in the technologies relevant to the target role is a genuine differentiator at employers like Google Zurich, Thoughtworks and Roche Digital. A linked profile that is empty, contains only forked repositories with no original work, or has not been updated in two years is neutral at best and mildly negative at worst. Candidates should either invest in the profile or not link it.

Project descriptions with metrics

Each significant project or role in a tech CV should include at least one metric that conveys scale or impact. "Developed a microservices architecture for an e-commerce platform" is far weaker than "Designed and implemented a microservices migration for a platform serving 2.4M monthly active users, reducing deployment cycle from 3 weeks to 6 hours." The metric need not be large, what matters is that it conveys real-world context.

For infrastructure and DevOps roles, infrastructure cost reductions (CHF or USD), availability improvements (99.9% → 99.97% SLA), deployment frequency changes, and MTTR improvements are the appropriate metrics. For data engineering and analytics roles, data volume processed (TB per day), query performance improvements, and pipeline reliability metrics (uptime %) are the signals that hiring managers at UBS Tech and Novartis IT look for.

Cloud certifications: placement and currency

AWS, GCP and Azure certifications are widely valued in the Swiss market, particularly for cloud architecture, DevOps and data platform roles. These belong in a dedicated certifications section, typically positioned after the skills section and before the education block, with the certification name, issuing body, year obtained, and expiry date if applicable.

Outdated certifications (obtained more than three years ago and not renewed) should still be listed if the technology remains current in the candidate's practice, but the date makes their currency transparent. A GCP Professional Data Engineer certification obtained in 2022 and renewed in 2024 signals active engagement with the platform; one obtained in 2019 without renewal is a weaker signal for a cloud-native role in 2026. Candidates who have completed significant coursework without certification (e.g., extensive AWS training without sitting the exam) should note this with appropriate qualification rather than omitting it entirely.

ATS at large Swiss tech employers: Workday and Taleo

Large Swiss tech employers use ATS platforms that apply keyword screening before human review. Roche Digital and Novartis IT use Workday; UBS Tech has historically used both Workday and SAP SuccessFactors depending on the division; some legacy Swiss corporate setups retain Taleo. The implications for CV preparation are consistent across these platforms: exact terminology from the job posting should be mirrored in the CV where truthfully applicable.

A posting that specifies "Kubernetes experience" will not reliably match a CV that says "container orchestration with k8s". "Infrastructure as Code" is not guaranteed to match "Terraform automation". The safest approach for candidates applying to employers known to use Workday or Taleo is to read the job description line by line and ensure every required skill that applies to the candidate's background appears in the CV using the job posting's exact phrasing.

German language requirements: Google Zurich vs Swiss enterprise employers

German language requirements for tech roles in Switzerland are perhaps the most misunderstood aspect of the job market for international candidates. Google Zurich is genuinely English-first: the engineering organisation operates in English at all levels, German is not required for hiring, and the majority of the engineering workforce does not speak German to a professional standard. This is the exception, not the rule.

Zühlke Engineering, Adnovum, Ergon, and most Swiss enterprise consultancies work closely with Swiss-German clients and require German at B2 level minimum for any client-facing role. UBS Tech and the technology functions of Swiss banks operate largely in German internally, with English used for international projects. Roche Digital and Novartis IT are closer to the Google model, English-primary, but German is valued for cross-functional collaboration with Swiss teams. Candidates should state CEFR language levels for every language on their CV and should not apply to roles requiring German without at least B1, unless the posting explicitly states English-only is acceptable.

CV length: the two-page rule and its exceptions

The two-page maximum applies to Swiss tech CVs at all seniority levels for standard software engineering, DevOps, and data roles. A senior engineer with 15 years of experience should be able to present a compelling, metrics-rich two-page CV; forcing a recruiter through three or four pages is a negative signal about prioritisation ability.

The genuine exceptions are narrow. PhD holders applying for research-adjacent roles at Roche's computational biology teams, Novartis AI research units, or ETH Zurich spinouts may use a longer format that includes a publications appendix. Distinguished engineers or architects with a genuinely extensive portfolio of consequential projects may add a third page if, and only if, every line adds specific, differentiated signal. A third page padded with older roles restated in full, soft-skills summaries, or training certificates that add no incremental value will damage rather than strengthen the application.

---

Frequently asked questions

How important is a GitHub profile for Swiss tech applications?

For software engineering and DevOps roles, a well-maintained GitHub or GitLab profile is a meaningful positive signal at most Swiss tech employers. At Google Zurich and Thoughtworks it is close to expected; at Roche Digital and Novartis IT it is valued; at Swiss enterprise consultancies like Zühlke it is reviewed when present. The profile should contain original work with clear README documentation, recent commit history, and code that is representative of the candidate's current skill level. An empty or neglected profile is better left unlinked.

What is the best format for listing a tech stack on a Swiss CV?

Organise the tech stack into four explicit tiers: programming languages, frameworks and libraries, tools and platforms, and cloud providers. Within each tier, optionally indicate depth (primary, proficient, familiar) or years of active use. Avoid flat, undifferentiated lists of twenty technologies, they provide no signal about expertise depth and can trigger ATS mismatches when the phrasing differs from the job posting.

Where should AWS, GCP or Azure certifications be placed on the CV?

Cloud certifications belong in a dedicated certifications section, positioned after the skills section and before the education block. Each entry should include the full certification name, the issuing body, the year obtained, and the expiry or renewal date if applicable. Candidates who have allowed certifications to lapse but still work actively with the technology should list them with the original date and note the current practice level.

Is German required for tech roles in Zurich?

It depends on the employer. Google Zurich is English-only and does not require German for engineering roles. Swiss enterprise consultancies (Zühlke, Adnovum, Ergon) typically require German B2 minimum for client-facing work. UBS Tech and Swiss bank technology divisions operate largely in German internally. Roche Digital and Novartis IT are English-primary but value German for cross-functional collaboration. Candidates should state CEFR levels honestly and check individual job postings for explicit language requirements.