
Sass Experts in Stuttgart
to shape scalable interfaces with vetted, available freelancers matched by AIHire experts who structure maintainable stylesheets, build responsive design systems and integrate Sass with modern frontend workflows. FRATCH connects you with vetted, available freelancers through fast, precise AI matching.
Meet FRATCH Experts in Stuttgart, who have recently used Sass
Robert B.
Last position:
Digital fault reporting portal, custom ticketing system at Municipal client
Digital fault reporting portal, custom ticketing system
Project type: Web development / custom development / operational application software
Technology: Neos CMS, Flow Framework, MySQL, Dexie.js, PhpSpreadsheet
Status: Delivered
Background:
Faults in the client’s day-to-day operations and facilities had previously been reported by phone, on paper or by email and coordinated manually. There was no structured follow-up, clear assignment of responsibilities or complete documentation. A particularly critical issue was that field staff on site had no direct access to a central system – fault reports were created in isolation and information was lost.
Market research also showed that common helpdesk or ticketing systems did not adequately cover the specific requirements of municipal wastewater management – decentralized facilities, on-call duty coordination and integration with existing communication channels. Custom development was the only sensible solution.
Solution:
The client received a custom web-based fault reporting portal, developed from the ground up for the company’s exact operational processes. The system combines structured ticket creation, traceable status tracking, mobile field reporting and automated notifications in a single, low-maintenance platform.
Ticket lifecycle and audit trail:
Every fault report follows a clearly defined lifecycle:
- New
- In progress
- Under observation
- Completed
- Rejected
Every status change is logged immutably: who changed what, when – and why. The StateChange model ensures that the complete processing history can be traced at any time. In addition, staff can comment directly on tickets, ask questions and post status updates – keeping everyone on the same page without email chains.
Roles and permissions:
The portal has three user roles with fine-grained access rights:
- Admin – full system access, user management, department configuration
- Manager – processing and management of all reports within their area of responsibility
- Employee – creating and viewing their own and assigned reports
Department assignments automatically determine which tickets a user sees and which notifications are triggered.
Mobile tablet support with offline synchronization:
Employees report faults directly on site – at a manhole, in a machine room or outdoors. A dedicated tablet mode was developed for this purpose:
- Tablets are registered once and activated using a token-based process
- When there is no network connection, the system stores reports locally in the browser (IndexedDB via Dexie.js)
- As soon as a network connection is available, all reports created offline are synchronized automatically – no data loss and no manual reconciliation
- Photos can be uploaded directly from the tablet camera and linked to the ticket
This mechanism solves a key practical problem at wastewater treatment plants: reporting under difficult conditions, far from the office Wi-Fi.
Department-based notification system:
Each fault report is assigned to one or more of the twelve specialist departments.
As soon as a report is created, edited or moved to a new status, the responsible department contacts automatically receive an email. Notification settings can be configured individually for each user – no noise and no missed reports.
On-call duty management:
The portal integrates on-call duty management directly into the fault reporting process. On-call groups (RB1, RB2, RB3) are stored and managed in the system. Incoming faults can be assigned directly to the staff on duty – the on-call schedule and ticketing system are no longer separate worlds.
Cost tracking and Excel reporting:
Cost center codes and expenses can be recorded for each fault report – useful for internal cost allocation and budget control. The system allows all reports and cost data to be exported as an Excel file for monthly reports, analysis and transfer to other systems.
Technical implementation:
The portal was delivered as a custom solution based on Neos CMS / Flow Framework (PHP) – an enterprise framework with a clear MVC architecture, Doctrine ORM database abstraction and integrated access control. The MySQL database documents the continuous development of the data model since the project began in 2016 through more than 20 migration versions.
Dexie.js (an IndexedDB wrapper) provides offline functionality, using proven browser technology for robust client-side data persistence. The sync mechanism is implemented through a dedicated API endpoint and was carefully designed to be idempotent and conflict-free.
The core data model includes 13 entities (Report, Department, Location, Tablet, Cost, Image, Ondutygroup, Post, StateChange, among others), 11 controllers and over 25 configured API routes – complexity that a standard product could not provide without significant customization.
Benefits for the client:
- Fault reporting: phone, paper, email → structured web portal, including offline use
- Traceability: none → complete audit trail of all status changes
- Responsibilities: verbal and unclear → department assignment and role-based permissions
- Notifications: manual → automatic, configurable by department
- Field reporting: not possible → tablet app with offline sync and photo uploads
- On-call duty: managed separately → integrated into the fault reporting portal
- Reporting: compiled manually → Excel export at the click of a button
- Document history: none → complete, with timestamp and user
Result:
The company now has an operationally proven, fully custom ticketing system that accurately reflects the real processes of municipal wastewater management. Twelve specialist departments, three user roles, mobile field staff with offline capability, automated notifications and complete logging form a coherent system – with no breaks between media and no isolated solutions.
The decision to build a custom solution has paid off: a standard product would not have achieved this level of operational integration without significant customization – and would have become more expensive and less flexible in the long run.
Ivan G.
Last position:
Technical Lead at Porsche Digital GmbH
- Contributed to the design of the new financial services integration layer and moderated the architectural discussions
- Oversaw the security concept and approval of the application
- Prepared infrastructure setup and best practices for the Kotlin backend
Ronald F.
Last position:
Senior IT Consultant – Requirement Engineer at Deutsche Bank - Strivion
Methodology: Agile project management
Goal: Digitization and implementation of CCD2 requirements within the Consumer Finance systems.
Analysis, identification, and assessment of business requirements, as well as their transfer into technical implementation requirements. Coordination and status reporting of the various requirements. Documentation and process management using UML and BMPN. Cross-functional stakeholder management, UAT testing, data management, API architecture management.
Tools: Jira, Confluence, Visual Code, Sql Developer, Enterprise Architect, MsOffice, Bruno, ALM, Camunda, Figma
Achille C.
Last position:
Backend/Frontend Developer at ITZ-Bund
- Development of a microservice application for calculating account bookings
- Development of backend components with Java / JEE, Quarkus, Kafka, REST API
- Development of the test component with mocking frameworks (Mockito)
- Development of unit tests with JUnit / ArchUnit, integration test components
- Creation of OpenAPI specification format
- Configuration of CI/CD pipeline
- Development of frontend component with React
- Design, further development and optimization of system architectures
- Migration from MySQL to PostgreSQL
- Code reviews
- Java Corretto 21, JEE, Quarkus, Golang
- Reactive programming with Spring WebFlux, Project Reactor, Liquibase, Elasticsearch, Hibernate, HQL, JPA, SQL
- Git, Azure DevOps for CI/CD pipeline, YAML, JSON, Swagger UI, Postman, REST OpenAPI, Kafka Streams, Kafka Connect, Log4J, JUnit / ArchUnit
- Microservices, Jira, Confluence, MySQL, PostgreSQL, Docker, Kubernetes (deployment via Helm charts)
- Spring Security, OAuth 2, JWT, SonarQube
- IntelliJ, Maven, logging framework Splunk, Agile Scrum method, Nexus, Vaadin V24, build tool Vite
- React, React.JS, Node.js, JavaScript, Tailwind CSS, Agile Scrum method, BITV accessibility, Playwright
Robin S.
Last position:
Senior Cloud & Backend Engineer at Media-Saturn-Holding GmbH
- Implementing applications with Kotlin and Ktor as microservices
- Using MongoDB in the MongoDB Atlas cloud
- Asynchronous communication of services via Google Pub/Sub
- Using Kotest and MockK for unit tests
- Developing an administration frontend with TypeScript, React and Express.js
- Provisioning environments in GCP using Terraform
- Implementing CI/CD processes with GitHub Actions
- Operating scalable production and test environments in GCP with Kubernetes, Helm and Flux CD
- Monitoring environments with Prometheus and Grafana
- Providing BI data in the Google BigQuery data warehouse
Elizaveta G.
Last position:
BERNET Communication GmbH
- Technical support and further development of client websites on the WordPress CMS (hospitality industry)
- Further development of the company’s own partner website on the Kirby CMS
- Customization of the finished ZeroOne theme, with a particular focus on functionality such as booking systems, page filter plugins, and interactive animations
Waldemar W.
Last position:
Multipick Direct GmbH
Rebuilding the online shop, implementing a theme from the Shopware Store and customizing it, providing a custom design for the header and footer, implementing custom features, migrating data from the previous xt:Commerce shop, relaunching the shop, and optimizing performance using Cloudflare
Consulting, frontend development, project management, and leadership of a development team
Project management: Jira, MeisterTask, BugHerd
Team communication: Microsoft Teams, Google Meet, Zoom
Tools used: PHPStorm, BrowserStack
Discover over 15,000 top freelancers
Statistics of experts using Sass
Aggregated from the professional profiles of matched freelancers.
Experience
15 years (Germany: 17 years)

Position duration
4.6 years (Germany: 3 years)

Positions per freelancer
15 (Germany: 12)

Top business areas
Information Technology, Product Development, Project Management

Top industries
Information Technology, Government and Administration, Retail

Certification focus areas
Information Technology, Product Development, Project Management
Bachelor's degree or higher
100% (Germany: 87%)
Master's degree or higher
14% (Germany: 36%)

Certifications per freelancer
4 (Germany: 2)

Most common languages
German, English, French

Speak two or more languages
86% (Germany: 98%)
Based on our profile pool as of 18 Nov 2026.
Daily rate distribution
The chart shows how the daily rates of experts in this technology in Stuttgart are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows the share of experts charging within that range.
Average rates of experts in Stuttgart using Sass
Rates are based on recent contracts and do not include FRATCH margin.
The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.
The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.
Calculated based on our freelancers’ daily rates as of 18 Nov 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
Sass experts industry focus
See which industries our matched freelancers work in most often — every figure is calculated live from the freelancers on FRATCH.
- Information Technology (86%)
- Government and Administration (57%)
- Retail (57%)
- Tourism (57%)
- Automotive (43%)
- Banking and Finance (43%)
- Insurance (43%)
- Manufacturing (43%)
Please note that freelancers can work across multiple industries, so percentages overlap.
About the technology
What Sass does
Sass is a stylesheet language that extends CSS with variables, nesting, mixins, functions and reusable modules. Its SCSS syntax looks close to standard CSS, while the indented Sass syntax offers a more compact alternative. Sass files are compiled into browser-ready CSS and help teams manage large interface codebases.
Where it fits
Sass supports websites, web applications, design systems and responsive interfaces where styles need clear structure and consistent reuse. It works well for shared themes, component libraries and product interfaces with many states, breakpoints or brand variations. In Stuttgart, it often appears in digital products and industrial, automotive or service interfaces that require dependable visual consistency.
Ecosystem and tooling
Sass specialists commonly work across the full stylesheet toolchain:
- SCSS modules, partials and the Sass module system
- Variables, mixins, functions, maps and responsive breakpoints
- CSS custom properties and modern cascade features
- npm, Dart Sass, Vite, webpack and build pipelines
- Stylelint, source maps and automated checks
They also connect Sass output with component frameworks, design tokens and frontend testing practices.
When companies need help
Companies bring in freelance Sass expertise when a stylesheet system has become difficult to extend or when a redesign must preserve visual consistency across many screens. Specialists can establish naming conventions, split legacy files into modules, remove duplication and convert fragile rules into reusable patterns. They can also support a temporary delivery team during a migration from older Sass tooling or unstructured CSS.
What strong specialists deliver
Strong professionals understand CSS behavior rather than treating Sass as a simple preprocessing step. They control specificity, inheritance, cascade layers, responsive logic and generated CSS size. Their work includes readable architecture, documented conventions, stable build integration and output that remains accessible and maintainable for the wider frontend team.
Choosing the right fit
Look for a specialist who can show how they organized a real SCSS codebase and explain the trade-offs behind that structure. Ask how they handle component boundaries, shared tokens, responsive behavior, browser support and the gradual replacement of legacy styles. For remote collaboration or on-site work in Stuttgart, agree early on review practices, repository access, design-system ownership and the language used for documentation.
Frequently asked questions
Curious about Sass? Here are the answers that come up again and again.
Sass is used to organize and generate CSS for websites, web applications, component libraries and design systems. It adds variables, mixins, functions, nesting and modules before compiling styles into CSS that browsers can read.
Sass provides compile-time structure and reuse while keeping styles in a dedicated stylesheet workflow. Plain CSS now includes many comparable features, while CSS-in-JS places styling closer to components; the right choice depends on the application architecture, build process and team preferences.
Sass work benefits from strong CSS fundamentals, responsive design, accessibility, design tokens and component architecture. Familiarity with SCSS, Dart Sass, npm, Vite or webpack, Stylelint and frontend frameworks helps a specialist integrate styles into a complete delivery workflow.
Sass does not require a large standalone team, but complex codebases need a specialist who understands architecture, CSS behavior and build tooling. For a focused feature, a professional may mainly refine existing modules; a redesign or migration calls for deeper experience with conventions, dependencies and regression control.
Sass projects are well suited to remote collaboration because stylesheets, build configuration and reviews can be handled in a shared repository. Teams in Stuttgart should define feedback routines, design-system decisions and documentation expectations, along with whether German or English is used in day-to-day communication.
SCSS is often easier to introduce into an existing CSS codebase because its syntax closely resembles standard CSS. The indented Sass syntax can be concise, but teams should choose one format consistently and consider existing files, tooling and contributor familiarity.
Sass quality is visible in clear module boundaries, predictable naming, limited duplication and CSS output that remains manageable. Review the specialist’s approach to specificity, responsive rules, accessibility, source maps, linting and changes that affect several components at once.
Sass can complement CSS custom properties rather than replace them. Sass is useful for compile-time organization, calculations and reusable structure, while custom properties support values that can change at runtime, such as themes or component states.
The average hourly rate of freelancers in Stuttgart, Germany who have used Sass in their recent projects is 102 €, which corresponds to a daily rate of about 816 € based on an 8-hour working day.
Of the freelancers in Stuttgart, Germany who have used Sass in their recent projects, 100% hold at least a Bachelor's degree and 14% hold at least a Master's degree.
On average, freelancers in Stuttgart, Germany who have used Sass in their recent projects have 15 years of professional experience, with a single engagement typically lasting around 4.6 years.
The most common languages among freelancers in Stuttgart, Germany who have used Sass in their recent projects are German (100%), English (86%), and French (29%).
The most common industries among freelancers in Stuttgart, Germany who have used Sass in their recent projects are Information Technology (86%), Government and Administration (57%), and Retail (57%).
The most common business areas among freelancers in Stuttgart, Germany who have used Sass in their recent projects are Information Technology (100%), Product Development (100%), and Project Management (71%).
Main locations of FRATCH Experts, who have recently used Sass
Our freelancers and interim experts are at home across the DACH region — available on-site in the major business hubs or fully remote. Choose a location to discover matched specialists, local market insights and up-to-date availability.
Request a free demo
Get in touch with the FRATCH team and we will get back to you within 4 hours.
Would you rather directly get in touch?
We always have the time for a call or email!

Berlin
Hamburg
Munich
Cologne
Frankfurt