No label in tech hiring is used more, and verified less, than "full-stack." On a strong candidate it means genuine range: someone who can carry a feature from database schema to deployed frontend and own the result. On a weak CV it means a tutorial in each layer. Because full-stack is the highest-volume developer market in Germany, the recruiting problem is not scarcity, it is signal-to-noise: the candidates exist, but so do hundreds of near-identical CVs, and standard screening cannot tell them apart. This guide is about how to.
What "full-stack" actually means, and what it hides
The honest definition: a developer who can take a feature from data model to API to interface to deployment, and be trusted with the result. In practice nearly every full-stack developer is deeper on one side, which is fine and normal; the failure is when a brief doesn't say which side must be deep, or when a CV claims uniform depth that doesn't exist.
| Claim on the CV | What it often means | What to check |
|---|---|---|
| Full-stack, frontend-leaning | Strong React/Vue, competent API work, thin infrastructure | Can they design a schema and debug a slow query? |
| Full-stack, backend-leaning | Strong services/data, functional but plain UI work | Can they build a usable interface without a component library holding their hand? |
| Full-stack, genuinely balanced | Rarer: has shipped complete products, often in small teams or startups | The deployment story: who put it live, and who fixed it at 2 a.m.? |
| Full-stack as keyword stuffing | One tutorial per layer, no ownership of anything end to end | Ask for one feature they carried alone, watch the detail collapse |
The German market: volume, not scarcity, and what that changes
Full-stack is the broadest developer market in Germany: startups hire them as founding engineers, agencies staff projects with them, and Mittelstand companies want them for small internal product teams. Honestly framed, the top of this market is competitive but not scarce the way ML engineers or cloud architects are; the difficulty is filtering. That changes recruiting strategy: process speed still wins offers, but vetting quality is what protects you. Ranges below are market observation and vary with stack, region, and company stage.
| Level | Permanent (gross annual salary) | Freelance (day rate) |
|---|---|---|
| Junior (0-2 yrs) | ~€42-55k | Rarely freelance at this level |
| Mid-level (2-5 yrs) | ~€50-70k | ~€500-750 |
| Senior (5+ yrs, end-to-end ownership) | ~€70-95k | ~€600-950 |
| Lead / founding engineer profile | ~€85-115k | ~€800-1,100 |
Vetting: separating depth from buzzword
Because keyword lists are identical across genuine and shallow candidates, the CV screen is nearly worthless here. Everything useful comes from work evidence, and one hour of the right conversation beats ten CV reviews.
| Signal | What it tells you | How to verify |
|---|---|---|
| A feature shipped alone, end to end | Real range, real ownership | Deep walkthrough: schema, API, UI, deployment, and what broke |
| Debugging across layers | Can locate a fault in DB, API, or browser without guessing | Give a realistic bug scenario and follow their search path |
| Deployment literacy | "Done" means live and monitored, not merged | Ask how their last project reached production and who ran it |
| Judgment on trade-offs | Knows when good enough beats elegant | Ask about a shortcut they took deliberately and how they contained it |
| Sensible AI-tool usage | Uses assistants for speed without losing understanding | Have them review AI-generated code and find the planted flaw |
Where recruitment goes wrong for this role
| Failure mode | Why it happens | What it costs |
|---|---|---|
| Keyword screening in a keyword-saturated market | Highest CV volume of any dev role | Interview pipelines full of tutorial-level candidates |
| Expecting uniform depth | The label promises everything | Rejecting strong T-shaped candidates for honest gaps |
| Framework-of-the-month filters | "Must have 3 years of X" | Screens out adaptable seniors, selects for narrow matching |
| Whiteboard algorithms as the bar | Habit borrowed from big tech | Selects prep over product sense in a product-sense role |
| Ignoring the AI-tools shift | Output volume still read as skill | Hires who generate code fast but can't debug what they generated |
Permanent vs. freelance, and how a specialized network changes the filter
Full-stack developers are the classic flexible resource: freelancers carry MVPs, project peaks, and agency work, while permanent hires anchor product teams. Because the market's problem is noise rather than scarcity, the biggest value a specialized network adds here is the filter itself: every profile has already produced work evidence, not just a keyword list. Aiporate applies the same evidence-based vetting to full-stack profiles as to specialist roles, with a vetted shortlist within 72 hours of a completed brief across permanent, freelance, and embedded models.
| Dimension | Permanent hire | Freelance / embedded |
|---|---|---|
| Best for | Product teams, long-lived codebases, growing juniors | MVPs, project peaks, parental-leave cover, agency-style delivery |
| Availability | Good by tech standards; strong seniors still move fast | Deep, mature freelance market; starts within days |
| Cost shape | ~€70-95k senior salary + employer costs + fee (market observation) | ~€600-950/day (market observation) |
| Risk profile | Mis-hires hide longer in team settings | Output visible within the first sprint |
| Where a network helps most | Pre-vetted depth instead of CV volume | Same filter, plus speed on short-notice starts |
