sbt Experts in Germany
matched in minutes by AIHire experts who manage Scala builds, multi-project repositories, dependency resolution and automated release pipelines with sbt, while working smoothly with your existing engineering and delivery teams. FRATCH connects you with vetted, available freelancers through fast, precise AI matching.
Meet FRATCH Experts in Germany, who have recently used sbt
Santhosh K.
Last position:
Freelance Software Engineer at Zalando SE
- Drive migration of enterprise authorization platform from Styra DAS to open-source OPA via Skipper (Zalando's Golang-based ingress proxy) integration
- Optimise k8s resources and integrate native Prometheus metrics with OPA
- Migrate from internal monitoring solution to Prometheus CRs + Dash0
Tech Stack: Java/Kotlin, Golang, Python, Spring Boot, AWS, Kubernetes, Docker, OpenTofu, Prometheus, Grafana
Nikunjkumar P.
Last position:
Senior Java Backend Developer at Questax Professionals GmbH
- Provide the Price Listing Service team with prices for all cars and vans in different markets
- Adapt market-specific requirements such as taxes, government subsidies, campaigns
- Import and synchronize new prices for all new and existing cars and store them in the Redis datastore
- Support our product and on-call duty
- Daily business, development of new features, bug fixing
- Pair programming, code review, mob programming
- Develop POCs for new ideas
- Maintain and extend the backend
- DevOps tasks
- Run Kubernetes updates
- Adjust and further develop Kubernetes resources
- Develop and adapt Helm charts
- Adapt and update ArgoCD
- Maintain, adapt, and improve CI/CD
Thomas P.
Last position:
Freelance Software Architect at Self-employed
Qaiser A.
Last position:
Freelance Lead DevOps Engineer at Schwarz Gruppe Produktion
Bootstrapping a CloudOps team and building a multi-cloud provider backend for a low-code Internal Developer Platform (IDP) with env zero
Introducing user story mapping, ADRs, milestones, and backlog management
Designing and developing core APIs, setting up CI/CD pipelines, OpenTofu/Terraform scripts
Representing and communicating the team with third-party stakeholders (e.g. env zero)
(Cross-)team coaching on DevOps, software design, Terraform, Golang, and agile practices
Stephan S.
Last position:
Senior Data/ML Consultant & Technical Lead at Jolin.io
Role: Software Engineer & Applied Mathematician (Mathematical optimization for scheduling; duration: 1 months; team setting: Team of 2, remote; technologies: JuMP, Julia, Pluto, Svelte, JavaScript, TypeScript, JetBrains Space, Terraform, Nomad)
Role: Software & Cloud & Web Engineer (Building scalable data science compute cluster from scratch; duration: 11 months; team setting: Team of 1, on-site; technologies: Terraform, Kubernetes, k8s ingress, k8s services, k8s RBAC, k8s networking, k3s, etcd, S3, DNS, certificates, Julia, Pluto, JavaScript, Tailwind, Astro, npm, Parcel, Preact, MUI, JWT, AWS SQS, AWS RDS, Python, GitLab, GitHub)
Role: AI & Web Engineer (Custom ChatGPT service; duration: 1 months; team setting: Team of 2, remote; technologies: Python, Poetry, LangChain, Tailwind, ChatGPT API, Flask, FastAPI)
Role: Architect & Data Engineer (Central datalake setup and ingestion; duration: 9 months; team setting: Team of 5, remote; technologies: Infrastructure-as-code, AWS CDK, Python, Boto3, PySpark, AWS Glue, IAM, S3, ECS, Fargate, Lambda, Apache Hudi, DeltaLake, Databricks, GitHub, Jira, Miro)
Role: Software Engineer (PoC Julia migration of scikit-decide; duration: 1 months; team setting: Team of 2, remote; technologies: Python, Julia, GitHub)
Ritika S.
Last position:
AWmOpsRtKekEX(CPEliRenIEtN: CInEfoSrs.yDs,aHtaitAarcchhiiEtencetr(gAyW) S)
Global marketing analytics for Hitachi Energy as part of a global data modernization initiative aiming to enhance data retention, historical data availability and provide Eloqua's 2-year retention for remote interaction reporting and analytics.
Analyzed Eloqua's default retention policy and identified risk of data loss for records older than two years.
Designed and implemented historical data preservation strategy by creating transformed tables in the target data platform to archive older data while ensuring data quality dashboards.
Collaborated with the Power BI team to re-point dashboards from raw Eloqua imports to the newly created archival layer.
Leveraged Jira to track and manage data engineering tasks, bugs, and feature requests across Agile sprints; coordinated backlog prioritization and task assignment to align data pipeline development with business needs.
Power BI dashboard optimization:
Worked closely with business stakeholders to assess and understand reporting needs for reverse customer data.
Designed and implemented incremental refresh in Power BI to ensure daily updates without full data reloads.
Collaborated with Azure data engineers to optimize data processing and publication pipelines.
Stakeholder communication & data modeling:
Acted as liaison between Group Data Office and Technology Office to align data modelling standards.
Gathered requirements from data engineering team and participated in weekly status meetings to provide implementation updates and resolve blockers across teams in Germany, Poland, and India.
Documentation & quality assurance:
Prepared end-to-end technical design documentation, data flow diagrams, and Power BI audit guides for future reference.
Participated in UAT sessions with business users to validate data outputs and report accuracy.
Henning P.
Last position:
Backend Systems Development at Deutsche Bank/DWS/Morgenfund
- Developed backend systems for the DWS Investment App, a white-label investment solution (robo-advisor), and an investment solution for institutional clients.
- Java 8-17, Kotlin, Spring Boot, Spring MVC, OpenAPI 3.0, JPA, JDBI, Oracle, Hazelcast, JXLS, Apache POI, Apache PDFBox, Apache Kafka & Avro, Active MQ, Elasticsearch, React Native, Spock Test, IntelliJ IDEA, Kubernetes, Helm, Microservices/Netflix-Stack, TeamCity, Splunk.
- Kanban team, continuous integration.
- Migrated existing applications from Deutsche Bank's private cloud environment to Azure as part of a carve-out.
Jens G.
Last position:
Shijou GmbH
- Software architecture and backend development for a marketplace solution / eCommerce retail
- Used Scala, Python, http4s, Next.js, Elasticsearch, PostgreSQL, AWS
Frank W.
Last position:
Fullstack Software Developer at Goodright GmbH
- Built backend APIs using Quarkus, Kotlin, MongoDB, Docker Compose and NGINX
- Developed frontend with React, TypeScript and Ant Design
Discover over 15,000 top freelancers
Statistics of experts using sbt
Aggregated from the professional profiles of matched freelancers.
Experience
21 years
Position duration
2.2 years
Positions per freelancer
12
Top business areas
Information Technology, Business Intelligence, Product Development
Top industries
Information Technology, Retail, Automotive
Certification focus areas
Information Technology, Business Intelligence, Product Development
Bachelor's degree or higher
100%
Master's degree or higher
63%
Doctorate
13%
Certifications per freelancer
2
Most common languages
German, English, Spanish
Speak two or more languages
100%
Based on our profile pool as of 19 Sep 2026.
Daily rate distribution
The chart shows how the daily rates of freelancers in this technology in Germany are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows how many freelancers charge within that range.
Average rates of experts in Germany using sbt
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 19 Sep 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
sbt 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 (100%)
- Retail (67%)
- Automotive (44%)
- Education (44%)
- Banking and Finance (44%)
- Insurance (44%)
- Fashion (33%)
- Professional Services (33%)
Please note that freelancers can work across multiple industries, so percentages overlap.
About the technology
Scala build foundation
sbt, short for Scala Build Tool, is the standard build system for many Scala applications and libraries. It defines project settings, resolves dependencies, compiles source code, runs tests and packages deliverables. Its interactive shell and incremental execution make repeated local builds efficient.
Projects and deliverables
Companies use sbt for backend services, data-processing applications, shared Scala libraries and Akka-based systems. It supports multi-project builds, so related modules can share settings while remaining independently testable. Typical deliverables include deployable artifacts, published libraries, test reports and reproducible build definitions.
- Configure Scala and Java compilation
- Create multi-project build structures
- Publish artifacts to internal repositories
- Connect builds to continuous integration
Ecosystem and tooling
Strong sbt specialists work across the Scala ecosystem rather than treating the build file in isolation. They understand Scala versions, dependency graphs, Maven-compatible repositories, plugins, scripted tasks and configuration in build.sbt files. They may also connect sbt to ScalaTest, MUnit, Akka, Play Framework, Docker workflows and cloud delivery pipelines.
When expertise matters
Freelance expertise is useful when a build has become slow, fragile or difficult to understand. It also helps during a migration from another build approach, a Scala version change, repository consolidation or the separation of a large codebase into modules. In Germany, specialists may support distributed teams remotely or join on-site delivery work where German and English collaboration are both needed.
- Diagnose dependency conflicts and eviction warnings
- Improve incremental compilation and build performance
- Modernize plugins and shared build conventions
- Stabilize release and publishing workflows
Reliable delivery practices
A capable professional keeps build logic readable, versioned and consistent across local machines and continuous integration. They make dependency updates deliberate, isolate custom plugins and ensure that clean builds produce the same result as developer builds. They also document commands, release steps and the reason behind non-obvious settings.
Choosing the right specialist
Look for evidence of hands-on work with the Scala Build Tool in repositories similar to yours. Ask how the specialist would inspect a slow build, trace a dependency conflict or structure shared settings across modules. Quality shows in small, reversible changes, clear diagnostics and tests that prove the build remains dependable after maintenance or migration.
Frequently asked questions
Before you brief your next project: the most common questions about sbt.
sbt is the Scala Build Tool used to compile Scala and Java code, resolve dependencies, run tests and package applications or libraries. It is especially useful for multi-project repositories and services that need repeatable builds in local development and continuous integration.
sbt is closely aligned with Scala’s ecosystem and offers an interactive shell, incremental execution and flexible build definitions. Maven favors convention and XML-based configuration, while Gradle uses a broader general-purpose build model; the right choice depends on the existing codebase, team skills and plugin requirements.
A strong sbt specialist usually understands Scala compilation, JVM dependency management, repository publishing and continuous integration. Experience with ScalaTest or MUnit, Akka, Play Framework, Docker and cloud delivery can also be important when the build is part of a production service.
The required depth depends on the assignment. A focused dependency update may need familiarity with standard build files, while a multi-project migration or custom plugin requires proven experience diagnosing build graphs, compiler settings and release automation.
sbt is well suited to remote collaboration because build definitions, commands and dependency settings can be reviewed in version control. A freelancer should document local setup, use reproducible continuous integration builds and communicate clearly in the team’s working language, whether that is English, German or both.
Bring in an sbt freelancer when builds are slow, dependency conflicts keep returning, releases are hard to repeat or a Scala migration is blocked. External expertise can also help establish shared conventions before a growing repository becomes difficult to maintain.
Ask the specialist to explain how they would inspect an unexpected dependency, isolate a failing task or improve a slow multi-project build. Good answers include measurable diagnostics, small changes, test coverage and documentation rather than a blind rewrite of build.sbt.
A complete sbt assignment should leave behind working build definitions, tested dependency and plugin settings, and a clear path for local and continuous integration execution. Depending on scope, the deliverables may also include publishing configuration, release documentation and recommendations for future maintenance.
The average hourly rate of freelancers in Germany who have used sbt in their recent projects is 101 €, which corresponds to a daily rate of about 806 € based on an 8-hour working day.
Of the freelancers in Germany who have used sbt in their recent projects, 100% hold at least a Bachelor's degree, 63% hold at least a Master's degree, and 13% hold a doctorate.
On average, freelancers in Germany who have used sbt in their recent projects have 21 years of professional experience, with a single engagement typically lasting around 2.2 years.
The most common languages among freelancers in Germany who have used sbt in their recent projects are German (100%), English (100%), and Spanish (22%).
The most common industries among freelancers in Germany who have used sbt in their recent projects are Information Technology (100%), Retail (67%), and Automotive (44%).
The most common business areas among freelancers in Germany who have used sbt in their recent projects are Information Technology (100%), Business Intelligence (89%), and Product Development (89%).
Main locations of FRATCH Experts, who have recently used sbt
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.
Berlin Hamburg Munich Cologne Frankfurt Stuttgart Dusseldorf Leipzig Dortmund Essen Bremen Dresden Hanover Nuremberg 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!
Philipp Thomaschewski
FRATCH CEO
