Hire UI/UX Designers in Berlin: A Founder's Guide

[{"content":"Before looking for a designer, know exactly what you need one to do. 'UI/UX' is broad. Are you building a new product from scratch, iterating on an existing one, or fixing usability issues? Do you need someone focused on user research and information architecture, or more on visual design and interaction? Product Stage Matters:\n Early-stage startup (pre-product-market fit): You might need a generalist — someone who can handle user research, wireframing, prototyping, and visual design. This person often sets the initial design direction. They need to be comfortable with ambiguity and rapid iteration. Growth stage (post-product-market fit): You might need specialists. Perhaps a dedicated UX researcher, an interaction designer, or a UI designer focused on visual consistency and design systems. Key Questions to Answer Internally:\n1. What problem will this designer solve for us? (e.g., 'Our user onboarding drop-off is 70%,' or 'We need to build a new dashboard for enterprise clients.')\n2. What specific tasks will they perform daily/weekly? (e.g., 'Conducting user interviews,' 'Creating low-fidelity wireframes,' 'Designing high-fidelity mockups in Figma,' 'Building and maintaining a design system.')\n3. What outcomes do we expect? (e.g., 'Increase conversion rates by X%,' 'Improve user satisfaction scores,' 'Reduce support tickets related to product usage.')\n4. How will they collaborate with the existing team? (e.g., 'Work directly with one product manager and two engineers,' 'Report to the CTO.')\n5. What tools are essential? (e.g., Figma, Sketch, Adobe XD, Miro, Maze, Hotjar.) Being specific avoids mismatched expectations and saves time. If you don't know what you need, you won't recognize it when you see it. Your job description should reflect these specific needs, not general design platitudes. Clarify if you need someone to define the user experience strategy from the ground up, or if you need an executor to apply an existing design language. This distinction is critical for targeting the right candidates. Remember to also consider whether you need a full-time employee or project-based help from a contractor, which impacts how you define the scope and compensation. See our guide on how to hire a contract UX designer for more on this distinction. For a general understanding of product building, refer to our content on how to build a product.\n","heading":"1. Define Your Design Needs Precisely"},{"content":"Berlin has a competitive tech talent market. You need to know where designers look for jobs and how to stand out. Channels to Use:\n Job Boards: Local Berlin-focused: Berlin Startup Jobs, Gründerszene Jobbörse. These boards target individuals specifically looking for roles in Berlin's startup ecosystem. EU-wide/Specialized: Folks like Landing.jobs, Remote OK (if open to remote talent within Berlin), Product Hunt's job board (for product-focused roles). Design-specific: Dribbble Jobs, Behance Jobs (though often premium listings), AIGA Design Jobs. Professional Networks: LinkedIn: Standard for professional recruitment. Use targeted searches, reach out to individuals, and post jobs. Berlin has a strong LinkedIn presence for tech professionals. See our advice on how to use LinkedIn for sourcing tech talent. Xing (Germany-specific): Similar to LinkedIn but with a stronger local presence in DACH regions. Useful for German-speaking designers or those established in Germany.\n Referrals: Your existing network is often the best source. Ask your team, advisors, and other founders for recommendations. A referred candidate often comes with a level of pre-vetting.\n Local Meetups & Communities: Before COVID, meetups were a primary networking tool. Now, many have shifted online or to hybrid models. Look for groups like 'Berlin Product Tank,' 'UX Berlin,' 'Figma Berlin.' Participating in these communities, even passively, can expose you to talent and help you understand the local market. Consider sponsoring a meetup or giving a talk to raise your startup's profile. Design Agencies: If you're struggling to find a full-time hire or need immediate project-based help, consider engaging a specialized design agency in Berlin. They can provide senior talent fast, though at a higher cost. This is a good option for initial projects to define your core product, see our content on hiring a product agency.\n Freelance Platforms: For project-based or short-term needs, platforms like Upwork, Fiverr, or specific German freelance platforms can work. Be very clear about scope and deliverables. However, be cautious; quality varies wildly. See our guide on hiring remote freelance product designers. Crafting Your Job Post:\nYour job post needs to be clear, concise, and compelling. Avoid jargon where possible. State explicitly what the role entails, what skills are required, what your company does, and why someone should work for you. Be transparent about culture and expectations. If you need to hire specialists, our guide on hiring a product designer offers specific nuances.\n","heading":"2. Sourcing Talent in Berlin"},{"content":"The first filter for a UI/UX designer is their portfolio. This is more important than their resume. The resume tells you what they've done; the portfolio shows you how they think and what they produce. What to Look For in a Portfolio:\n Process, not just pretty pictures: A good portfolio demonstrates the designer's thought process. Do they explain the problem they were solving? What research did they conduct? What alternatives did they consider? How did they test their solutions? What were the outcomes and metrics? This is more important than visual polish alone. Look for detailed case studies. Understanding of User Needs: Can they articulate why they made certain design decisions, linking them back to user feedback or identified pain points? Problem-Solving Skills: Do their projects show an analytical approach to design challenges? Do they go beyond aesthetics to address usability and functionality? Variety (or focus): If you need a generalist, look for a range of projects (web, mobile, different industries). If you need a specialist, look for deep expertise in that area (e.g., complex data visualization, interaction design for specific devices). Clarity and Communication: Is the portfolio easy to navigate? Is the writing clear? A designer’s ability to explain their work is a proxy for their communication skills.\n Relevance: Do any of their projects relate to your industry or product type? While not strictly necessary, it can be a plus.\n Tools: Do they work with your preferred design tools (e.g., Figma)? Red Flags in a Portfolio:\n Only final mockups with no explanation of the process.\n Lack of measurable outcomes or data.\n A generic portfolio that doesn't feel personalized or thoughtful.\n Projects that are clearly academic exercises without real-world application. Resume Review:\n Look at their tenure at previous roles. Frequent job changes might indicate a lack of commitment, though startup careers often involve shorter stints. Check experience with specific industries or product types relevant to your business.\n Roles and responsibilities: Do they align with your needs? Did they lead projects or contribute as part of a team? Education and certifications. While not as important as practical experience, they can offer context. Filter ruthlessly at this stage. Only invite candidates for interviews who demonstrate a solid portfolio and a resume that aligns with your specific needs. This saves significant time later. Our resources on hiring a product manager also touch on portfolio assessment from a product perspective.\n","heading":"3. Initial Screening: Portfolio & Resume Review"},{"content":"The first real conversation should be a brief (20-30 minute) call. This isn't for deep technical assessment but to gauge communication skills, cultural fit, and align expectations. Objectives of the Initial Call:\n1. Verify Motivation: Why are they looking for a new role? Why your company specifically? Look for genuine interest, not just a job search.\n2. Clarify Expectations: Discuss salary range (be transparent), working model (remote/hybrid/on-site in Berlin), and basic role responsibilities. Ensure mutual alignment to avoid wasting time.\n3. Communication Skills: Can they articulate their experience clearly? Do they listen well? Can they explain complex design concepts simply? 4. Cultural Indicators: Do they seem enthusiastic? Do they ask thoughtful questions about your product, team, or challenges? Are they curious?\n5. Problem-Solving Mindset: Ask a brief, high-level question about a design challenge. 'Tell me about a time you had to compromise on a design vision. How did you handle it?' This tests their pragmatism. Questions to Ask (Examples):\n 'What attracted you to [Your Company Name] and this specific role?'\n 'Can you describe your ideal working environment?'\n 'Walk me through a project in your portfolio that you're most proud of, focusing on the problem you solved.'\n 'What are your salary expectations for a role in Berlin?' (Be prepared to state your range openly).\n 'What questions do you have for me about our product or team?' Your Role: Be prepared to concisely describe your company, product, team, and the specific challenges the designer would address. Sell your vision, but realistically. Be honest about where your product stands and the challenges ahead. This call is a two-way street; the candidate is also vetting you. Learn more about effective communication with candidates in our guide on how to improve candidate experience.\n","heading":"4. The Initial Call: Vetting for Fit"},{"content":"This interview (60-90 minutes) focuses on their practical abilities and design thinking. This is usually with a founder, product manager, or lead designer if you have one. Focus Area: Their Process and Problem Solving:\n Detailed Project Walkthrough: Ask them to walk you through 1-2 projects from their portfolio. Critically, ask 'why' at every step. 'Why did you choose this research method?' 'Why did you present these specific wireframes?' 'How did you gather feedback, and how did it influence your next steps?' 'What metrics did you track, and what was the impact?' 'What would you do differently if you had to do it again?'\n User Research Capabilities: Ask about their experience with user interviews, surveys, usability testing, and data analysis related to user behavior. How do they validate assumptions?\n Information Architecture & Wireframing: How do they structure content and user flows? Can they sketch ideas rapidly? Interaction Design: How do they think about user interactions? Do they consider states (empty, error, loading), animations, and micro-interactions?\n Visual Design (if applicable): If the role requires UI skills, assess their understanding of typography, color theory, layout, and visual hierarchy. Ask about their experience with design systems. Collaboration: How do they work with product managers, engineers, and other stakeholders? How do they handle disagreements or competing priorities? See our guide on cross-functional collaboration in product development.\n Tool Proficiency: Confirm their fluency in your team's primary design tools (e.g., Figma). Example Behavioral Questions:\n 'Tell me about a design that failed or didn't meet expectations. What did you learn?'\n 'Describe a time you had to advocate for a user-centered design decision against internal resistance.'\n 'How do you stay up-to-date with design trends and technologies?'\n 'How do you balance user needs with business goals and technical constraints?' Avoid generic questions. Dive deep into their specific project experiences. Look for someone who can articulate their rationale clearly and show adaptability. Our guide on recruiting good product people provides a broader context for these types of interviews.\n","heading":"5. The Technical Interview: Deep Dive into Process and Skills"},{"content":"A design challenge or take-home assignment can be a good way to see a candidate's actual design process in action. Be mindful of candidate time; keep it focused and purposeful, ideally requiring no more than 3-4 hours of work. When to Use a Design Challenge:\n Junior to Mid-level positions: Excellent for evaluating raw talent, methodological approach, and tool proficiency.\n Senior roles: Less common, but if used, it should be a strategic exercise rather than a tactical one (e.g., 'outline a design strategy for X feature' vs. 'design X feature'). For senior roles, a 'portfolio deep dive' with specific questions is often more suitable. Designing an Effective Challenge:\n1. Keep it relevant: Use a scenario close to your actual product or industry, but simplify it significantly. Avoid giving them your actual current problem, as this could feel exploitative.\n2. Define clear objectives: What specific skills are you testing? (e.g., 'Information architecture,' 'User flow,' 'Visual design consistency,' 'Problem definition').\n3. Set a reasonable time limit: State it explicitly (e.g., 'This challenge should take no more than 3 hours'). Respect their time. 4. Ask for process, not just output: Request sketches, wireframes, iteration notes, and a brief explanation of their choices, not just final mockups. The 'why' is more important than the 'what.'\n5. Provide clear submission guidelines: How should they deliver the work? (e.g., Figma file link, PDF). Example Challenge Scenario:\n'Design a feature for a mobile banking app that allows users to easily split a bill with friends. Focus on the user flow for initiating a split and inviting friends, as well as the visual presentation of tracking outstanding payments. You can assume basic authentication and contact access. Clearly state your assumptions and design process.' Evaluation:\n Judge the designer's approach, not just the aesthetic outcome. Did they ask clarifying questions? Did they consider edge cases? How well do they explain their decisions? Does their solution make sense from a user's perspective? Is it simple and intuitive?\n Assess their tool proficiency (e.g., clean Figma file, proper use of components). If you use a challenge, provide feedback to candidates who complete it, regardless of the outcome. This is professional courtesy and builds goodwill. Consider how this fits into your broader strategy of hiring for early stage startups.\n","heading":"6. The Design Challenge (Optional but Recommended for Junior/Mid-Level)"},{"content":"Reference checks are not optional. They provide an external perspective on a candidate's work habits, collaboration skills, and reliability. This is a critical step before making an offer. Whom to Contact:\n Aim for two professional references: a former manager and a peer or cross-functional colleague (e.g., a product manager, engineer). Preferably, references from their most recent relevant roles. Ask the candidate to provide references who are expecting your call. Questions to Ask (Examples):\n 'In what capacity did you work with [Candidate's Name]?'\n 'What were their primary responsibilities and biggest contributions?'\n 'Can you describe their strengths as a designer?'\n 'What areas do you think they could improve upon or develop further?' (Look for constructive feedback, not negatives).\n 'How did they collaborate with product managers/engineers/other designers?'\n 'How do they handle feedback or criticism on their work?'\n 'Can you give an example of a challenging situation they faced and how they handled it?'\n 'Would you hire them again, and why?'\n 'On a scale of 1-10, how would you rate their overall design ability/work ethic/teamwork?' Interpreting Feedback:\n Listen for consistency across references. Pay attention to specific examples, not just general praise. Look for any red flags, particularly regarding collaboration, communication, or handling pressure. Verify information the candidate provided during interviews (e.g., 'Did they really lead that project?'). Be direct but respectful. The goal is to gather honest insights. A positive reference typically offers balanced feedback, acknowledging strengths while identifying areas for growth. A reference that only gives generic praise might be less useful. This step helps confirm the picture you've built during interviews. It's an important part of validating your hiring decision, especially for core roles. Our guide on recruiting for product roles emphasizes the importance of thorough vetting.\n","heading":"7. Reference Checks"},{"content":"Berlin's tech salaries are competitive, though often slightly lower than London or Silicon Valley. You need to understand market rates for UI/UX designers to make a compelling offer. Key Factors Affecting Salary:\n1. Experience Level: Junior (1-3 years), Mid-level (3-6 years), Senior (6-10 years), Lead/Principal (10+ years).\n2. Specialization: A generalist may command a different rate than a highly specialized UX researcher or UI system designer.\n3. Company Stage: Early-stage startups often offer a base salary plus equity, while more established companies might offer higher cash compensation. 4. Benefits: Health insurance, public transport tickets (BVG), professional development budgets, gym memberships, flexible hours, remote work options. These add to the total compensation package. Current Market Estimates (Gross Annual Salary, Berlin, EUR - These are rough estimates and can fluctuate):\n\n Junior UI/UX Designer: €40,000 - €55,000\n Mid-level UI/UX Designer: €55,000 - €70,000\n Senior UI/UX Designer: €70,000 - €90,000\n Lead/Principal UI/UX Designer: €90,000 - €120,000+ (highly variable based on scope) Equity: For early-stage startups, equity is a significant component. Be prepared to explain your equity plan clearly (vesting schedule, strike price, valuation). It's a way to attract talent who believe in your vision and want to share in the potential upside. Consult our content on startup compensation. Crafting the Offer:\n Timeliness: Make the offer promptly after making your decision. Good candidates don't stay on the market long.\n Clear Terms: Detail base salary, equity (shares/options, vesting), start date, benefits (health insurance, vacation, public transport contributions), reporting structure. Personalization: Explain why you want them specifically. Refer back to their portfolio, interview performance, and how they fit your team's needs. Be Responsive: Be ready to answer questions and address concerns. Negotiation is common; be prepared for it within your defined budget.\n Berlin-Specific Perks: Highlight any benefits relevant to living in Berlin, such as support for relocation (if applicable), language courses, or professional networks. The city's quality of life and vibrant tech scene are selling points. Your offer isn't just about the numbers; it's about the full value proposition of working with your startup in Berlin. Understand the legal aspects of employment in Germany, such as standard probation periods (usually 6 months) and notice periods. Review content on product startup compensation for further insights. Consider the nuances of hiring a technical co-founder if your design needs are at the very executive level.\n","heading":"8. Compensation and Offer Strategy for Berlin"},{"content":"A well-structured onboarding process ensures your new UI/UX designer becomes productive quickly and feels integrated into your team and product. It’s not just about HR paperwork. Pre-Start Date:\n Welcome Pack: Send a personalized welcome email. Share company culture documents, product vision, and team structure.\n Equipment: Ensure their laptop, monitor, software licenses (Figma, etc.), and access credentials are ready on day one. Nothing frustrates a new hire more than waiting for basic tools.\n First Week Schedule: Create a clear schedule for their first week, including meetings with key team members, introduction to the product backlog, and initial tasks. First Week Priorities:\n Team Introductions: Introduce them to product managers, engineers, marketing, and leadership. Explain everyone's role and how they interact.\n Product Deep Dive: Provide access to product documentation, user research findings, analytics, and existing design files. Schedule dedicated sessions to walk them through the product's history, current state, and future vision. This is crucial for them to understand the context of their work. Our guide on product onboarding offers a broader view.\n Tool Setup & Access: Confirm access to all necessary tools – design tools, project management software (Jira, Asana), communication platforms (Slack), and version control systems. First Project/Task: Give them a tangible, manageable task they can complete within the first week or two. This allows them to contribute quickly and build confidence. It should allow them to familiarize themselves with your product's design system (if any) and work process.\n Mentor/Buddy System: Assign a colleague (not necessarily a designer if they are the first) to be their go-to person for informal questions. This helps them navigate the new environment. First Month and Beyond:\n Regular Check-ins: Schedule bi-weekly or weekly 1:1s to discuss progress, challenges, and integration. Feedback Loop: Establish a clear process for design critique and feedback. Encourage them to present their work early and often.\n Learning & Development: Discuss professional growth opportunities, conferences, or online courses. Berlin offers many design events and workshops. Culture Integration: Invite them to team lunches, social events, or informal gatherings. Help them understand the unwritten rules and social dynamics. Effective onboarding reduces time to productivity and improves retention. It demonstrates that you value their contribution beyond the hiring process. Think of onboarding as an extension of your hiring effort, a continued investment in their success. See our points on hiring the right people for your product to tie back to the broader hiring philosophy. Consider reviewing product manager responsibilities as the design role often overlaps heavily here.\n","heading":"9. Onboarding Your New Designer"},{"content":"Hiring a designer is only half the battle. How you integrate their work into your product development cycle determines their effectiveness and your product's quality. Design should not be an afterthought. Key Integration Points:\n Early Involvement: Designers should be involved from the earliest stages of product ideation and problem definition, not just when features are ready for 'beautification.' They should participate in discovery, user research, and defining product requirements alongside product managers and engineers. See our content on how to build a lean product to understand the importance of early integration.\n Design as a Partner: Treat design as an equal partner to product management and engineering. Design is not a service function; it’s a strategic one.\n Clear Handoffs (Handovers): Define a clear process for handing off designs to engineering. This often involves: Well-organized Figma files with components, specs, and states. Annotation tools or documentation explaining interactions and edge cases. Regular syncs between design and engineering during implementation. Our guide on product development cycle details how design fits in.\n Design System: Encourage the development and maintenance of a design system from early on. This creates consistency, speeds up design and development, and improves product quality. A design system is a 'single source of truth' for all UI elements and interactions.\n Feedback Loops: Establish structured design reviews and critique sessions. Create psychological safety for designers to share incomplete work and receive constructive criticism. Involve product, engineering, and even leadership. Content on how to get a job as a product manager and how to become a good product manager highlights the collaborative aspects.\n Quantitative and Qualitative Data: Designers should be involved in analyzing user data (analytics, usability testing results) to inform their decisions. Their work isn't just subjective; it's data-informed. See our notes on product strategy for startups and product validation.\n Advocacy for the User: Your designer is the voice of the user. Give them the platform to advocate for user needs and ensure the product remains user-centered. Without proper integration, even the best designer will struggle to make a lasting impact. Design needs a seat at the table throughout the entire product lifecycle. This also involves ensuring alignment with product market fit, as design significantly influences user adoption and retention. Review our articles on design thinking for product managers and B2B product management strategies.\n","heading":"10. Integrating Design into Your Product Process"},{"content":"The decision to hire a freelance designer or a full-time employee in Berlin depends on your current needs, budget, and long-term strategy. Freelance UI/UX Designers:\n Pros: Flexibility: Hire for specific projects, short-term needs, or to fill immediate skill gaps. No long-term commitment. Ideal for early validation phases or specific feature builds. See our guide on how to hire a freelance product designer and how to hire a contract product designer. Specialized Expertise: Access to senior designers with niche skills without the full-time salary associated. Many top-tier designers in Berlin choose to freelance. Speed: Often quicker to onboard and start working on a project. Cost-Effective (for short-term): Avoids overheads like benefits, office space, and long-term employment costs. Hourly or project rates can be higher, but you only pay for what you need.\n Cons: Less Product Deep Dive: Freelancers may not develop the same deep understanding of your product, users, or business context as a full-time employee. Availability: They might be working on other projects, leading to scheduling conflicts or slower response times. Cultural Fit: Harder to integrate into the core team culture and long-term vision. Knowledge Transfer: Documentation and knowledge transfer can be an issue once the project is complete. Full-Time UI/UX Designers:\n Pros: Deep Product Knowledge: They become embedded, developing a profound understanding of your product, users, and broader strategy over time. They help you achieve true product sense. Cultural Integration: Become a core part of your team, contributing to culture and values. Long-Term Vision: Can contribute to developing a consistent design language, strategy, and design system. They are invested in the company's long-term success. Read about building a product team. Dedicated Focus: Their entire focus is on your product. Mentorship/Leadership: Can grow into leadership roles, hiring experience product designers or building out a design team.\n Cons: Higher Cost: Salary, benefits, taxes, and overheads add up. This is a larger ongoing financial commitment. Our content on product management salaries can provide context for related roles. Less Flexibility: Hiring and firing in Germany have stricter labor laws, requiring more commitment. Slower to Hire: The recruitment process is typically longer and more resource-intensive. When to choose which:\n Freelance: For initial product validation, specific feature additions, quick clean-ups, or when budget is tight for a full-time role. Can also be a way to 'try before you buy' before offering a full-time contract.\n Full-Time: When you have a clear, ongoing need for design leadership, consistent strategic input, and a desire to build an in-house design culture. Essential when design is a core differentiator for your product. Check out how to identify an experienced product manager and similar roles. Carefully weigh these factors against your startup’s current stage and projected growth. Sometimes, a hybrid approach (e.g., a senior freelance designer for architectural guidance and a mid-level full-time designer for execution) makes sense. Learn more about product leadership and product management best practices which often involve in-house teams. Also, consider the specific challenges of hiring a product manager in Germany, which shares similar nuances to hiring designers.\n","heading":"11. Freelance vs. Full-Time in Berlin"},{"content":"Hiring in Germany, and Berlin specifically, involves adherence to German labor law. This is not optional and can be complex. Consulting a local legal expert is advisable. Key Areas to Consider:\n Employment Contracts (Arbeitsvertrag): Must be in writing. Details salary, working hours, vacation days, notice periods, and job description. Probation periods (Probezeit) are standard, typically 6 months.\n Visa and Work Permits: If hiring non-EU citizens, they will require a valid visa and work permit to legally work in Germany. The 'Blue Card' is a common route for skilled professionals. This process can be lengthy and requires support from your side. Seek advice on hiring international talent for the general approach.\n Social Security Contributions: Both employer and employee contribute to health insurance, pension, unemployment insurance, and long-term care insurance. These are mandated by law and take a significant chunk of gross salary.\n Health Insurance: Mandatory for all residents. Employees choose between public (Gesetzliche Krankenversicherung) and private (Private Krankenversicherung) insurance. Your contribution is usually half of the public rate or a fixed amount for private.\n Taxes: Income tax is progressive. You, as the employer, are responsible for deducting income tax (Lohnsteuer) and social security contributions and forwarding them to the relevant authorities.\n Payroll: You'll need a payroll service or an in-house expert familiar with German tax and social security regulations. Notice Periods (Kündigungsfristen): Legally defined and increase with tenure. During probation, it's usually 2 weeks. After probation, it starts at 4 weeks to the 15th or end of a month and can increase to several months after longer employment.\n Maternity/Paternity Leave: Germany has generous maternity (Mutterschutz) and parental leave (Elternzeit) policies. Be aware of these rights.\n Working Hours: Standard full-time is 40 hours per week. Overtime rules apply. Vacation: Minimum legal vacation is 20 days for a 5-day week, but many companies offer 25-30 days.\n Employee Data Protection (DSGVO/GDPR): Strict rules for handling employee personal data. For Freelancers (Freiberufler):\n Contract for Services (Werkvertrag/Dienstvertrag): Crucially, the freelancer must be genuinely self-employed to avoid 'false self-employment' (Scheinselbstständigkeit), which carries severe legal and financial penalties for the hiring company. Indicators of False Self-Employment: If the freelancer is fully integrated into your company structure, reports exclusively to you, uses your equipment, takes direction rather than delivering against a defined project, and works solely for you. Recommendations: Ensure the contract is precise about deliverables, not hours. The freelancer should ideally have multiple clients. They are responsible for their own taxes and social security. See our content on how to hire a freelance product manager for more on the specific distinction. This legal environment is serious. Do not guess. Hire a legal advisor specializing in German labor law before extending offers, especially your first hires. Missteps can be costly. For further context on general setup, refer to our guide on how to build a product from scratch which often touches upon these early operational activities.\n","heading":"12. Legal and Administrative Considerations for Hiring in Germany"}]