Job Description Template: Backend Developer

This template helps Swiss employers write a clear backend developer job description. It includes role overview, day-to-day responsibilities, technical must-haves and nice-to-haves, and a realistic compensation section. Adapt the Pensum percentage, canton, and tech stack to your needs.

Also available inDeutschFrançaisItaliano

A well-written job description attracts qualified backend developers and sets expectations before the interview. This template is designed for Swiss SMEs hiring without an HR department.

Customize the Pensum (part-time or full-time percentage), location (specify canton and city), and technology stack. Include language requirements where relevant—most Swiss backend roles list German, French, or English as essential.

About the Role & Responsibilities

Start by describing what the backend developer will actually build or maintain. Name your tech stack (e.g., Python, Node.js, Go) and key systems they'll touch.

Keep responsibilities concrete and measurable. Avoid lists longer than six items—focus on the three to four things that matter most to your business.

  • Design, build, and maintain server-side applications and APIs
  • Write clean, testable code and participate in code reviews
  • Troubleshoot production issues and optimize system performance
  • Collaborate with frontend developers and product teams on requirements
  • Document code and contribute to technical architecture decisions
  • Support deployment and monitoring of applications

Requirements: Must-Have & Nice-to-Have

Must-haves are skills or experience your candidates genuinely need on day one. Be honest: listing too many scares off strong applicants.

Nice-to-haves acknowledge that perfect candidates are rare. Separate them clearly so a developer with 80% of what you want still applies.

  • Must-have: 3+ years backend development in production environments
  • Must-have: Strong command of [your primary language: Python/Node.js/Go/Java/etc.]
  • Must-have: Experience with relational databases (PostgreSQL, MySQL) or similar
  • Nice-to-have: Familiarity with cloud platforms (AWS, Google Cloud, Azure)
  • Nice-to-have: Experience with Docker, Kubernetes, or container orchestration
  • Nice-to-have: Knowledge of microservices architecture or event-driven systems

What We Offer

Be specific about Pensum (e.g., 80–100%), location (e.g., Zurich, Bern), and employment type (permanent, contract length if fixed-term).

Include base salary range or a single figure in CHF, mention 13th monthly salary if applicable, insurance contributions, and any benefits. Transparency attracts the right candidates.

  • Pensum: [80–100% / your percentage], permanent position based in [canton and city]
  • Salary: CHF [lower range]–[upper range] per month, depending on experience and qualifications
  • 13th monthly salary (one-month bonus) in December
  • Group insurance (health, accident, disability) according to [name of GAV if applicable, or 'standard market terms']
  • Flexible working arrangements: [e.g., '2 days home office per week' or '4-day week option']
  • Professional development budget: CHF [amount] annually for courses and conferences

Frequently asked questions

Should I list salary as a range or a fixed amount?
A range (e.g., CHF 120,000–150,000 annually) is clearer and invites more applicants. If you prefer a single figure, add 'depending on experience' to signal flexibility. Transparency reduces back-and-forth negotiation later.
Where do I mention language requirements?
Add language requirements to the must-haves section. Example: 'Fluent German (written and spoken); English an advantage.' In Romandy or Ticino, adapt accordingly. If remote, clarify time-zone expectations.
How specific should the tech stack be?
Name the languages and frameworks your team actually uses (e.g., 'Python and Django' or 'Node.js and Express'). Avoid listing 10 technologies—candidates stop reading. Add 'willingness to learn new tools' if you value growth mindset.

General information for Swiss employers, not legal advice. Have a lawyer confirm anything with legal consequences.

Related