Selecting an offshore engineering vendor is usually treated as a sales process: presentations, reference calls, a rate comparison. That process tests how well a vendor sells, not how well it delivers. The questions that predict success are more specific and often uncomfortable. They concern who will actually do the work, who steers it, how results are accepted, how the contract holds up under German law, how your data is protected, and how you leave if it does not work. This guide lists 30 such questions in six groups, with notes on what a solid answer looks like.

Why selection carries more weight in 2026

The market for external engineering has grown, and so has the spread in quality. Nasscom's February 2026 strategic review puts the direct workforce of India's technology industry at 5.95 million in FY26, and a Nasscom and Zinnov report from May 2026 counts 2,117 global capability centres in the country. Vendors and in-house centres draw on the same pool of experienced engineers. A large pool does not guarantee that the people proposed to you are the people who will do the work.

Demand on the DACH side is shifting at the same time. Bitkom's 2026 AI survey finds that 57 percent of German companies with at least 20 employees use AI, up from 20 percent in 2024, and Bitkom's 2026 labour market study shows that 18 percent of companies rely more on external IT specialists to close gaps. More buyers, with more demanding technical requirements, are entering vendor selection. The questions below are designed to separate delivery capability from sales capability.

A. Team and leadership

  1. Who exactly will work on our engagement, by name and role? A solid answer names people and offers interviews before signature, not after.
  2. What share of the team are employees of your company, and are any subcontracted? Subcontracting affects quality control and IP chain.
  3. Who is our day-to-day counterpart, and what language level do they have in German and English?
  4. Who carries architectural and quality responsibility on your side? A named senior person, not a process.
  5. What happens if a team member leaves? What is the handover period, and who pays for onboarding the replacement?
  6. How many other clients does each named person serve? Shared senior people are common; you should know the allocation.

B. Delivery and acceptance

  1. How do you translate our requirements into a Leistungsbeschreibung with acceptance criteria?
  2. What does a sprint review and acceptance look like, and how is acceptance documented? Under a Werkvertrag, acceptance under BGB §640 has legal consequences.
  3. How do you report risk and slippage, and when? Ask for an anonymised example of an escalation.
  4. What is your definition of done, including tests and documentation?
  5. How do you work with our existing tools and repositories without your engineers being managed by our staff?
  6. How long from signature to first meaningful delivery, and what do you need from us to achieve that?

C. Contract structure and labour law

  1. Is the engagement structured as Werkvertrag (BGB §631) or Dienstvertrag (BGB §611), and why?
  2. Who gives instructions to individual engineers in practice? If the honest answer is your managers, the arrangement may in substance be Arbeitnehmerüberlassung under AÜG §1, with the consequences of §9 and §10 AÜG.
  3. How do you prevent drift into integration over time? A good vendor has a documented operating model, not only a contract clause.
  4. If you use individual freelancers, how do you assess Scheinselbständigkeit risk under SGB IV §7?
  5. For Austrian or Swiss entities in our group, have you adapted the structure? Switzerland prohibits leasing staff from abroad under Art. 12 Abs. 2 AVG.
  6. Which law governs the contract, and where are disputes resolved?

D. Security, data and IP

  1. Will your team access personal data? If so, will you sign a processing agreement under DSGVO Art. 28 and Standardvertragsklauseln under DSGVO Art. 46?
  2. Can you support our transfer impact assessment with concrete information on access controls and local law?
  3. How are devices, accounts and networks secured, including home office setups?
  4. How are access rights granted and removed, and how fast after someone leaves the project?
  5. How is IP assigned from your engineers to you, and from you to us? Ask to see the relevant clause in the employment contracts, redacted if necessary.
  6. What is your policy on AI coding tools with client code? Which tools, which settings, and is code used for model training?
  7. Is any part of our technology subject to export control, and have you dealt with Regulation (EU) 2021/821 before? Relevant for robotics, defence and dual-use work.

E. Commercials

  1. What exactly is included in the fee: leadership, quality assurance, tooling, travel?
  2. How are changes in scope priced, and how quickly can capacity go up or down?
  3. How is VAT handled? Services from a foreign vendor to a German business are generally subject to reverse charge under §13b UStG; invoices should reflect that.

F. Exit

  1. What are the notice periods and transition obligations, and what documentation do we receive on exit?
  2. Where does our code live throughout the engagement? The only good answer is: in repositories your organisation controls, from day one.

Red flags in the answers

Answer patternWhy it matters
"We will staff the team after signature"You are buying a promise, not a team
"Your team lead can manage our engineers directly"Convenient, but points toward integration and AÜG exposure
"Acceptance is informal, we just keep working"No legal or operational checkpoint for quality
"We host the code until final payment"Creates dependency and leverage against you
"Data protection is your responsibility"The vendor will not support your DSGVO obligations
Rate quoted before any scope discussionSelling capacity, not outcomes

A simple scoring model

Rate each answer on a three-point scale: 2 for a specific answer backed by a document or example, 1 for a plausible answer without evidence, 0 for an evasive or missing answer. Sum the scores per group and compare vendors group by group rather than by total alone. A vendor with a strong total but a weak score in group C (contract structure) or group F (exit) carries risks that a lower price will not offset.

How to run the process

Send the questions in writing before the first long meeting and ask for written answers. Then test the answers in conversation with the people who would actually lead your engagement, not only with sales staff. Score each group, and weight groups C and D heavily if you are in a regulated sector. A vendor that answers precisely and admits limits is usually a better partner than one that answers everything with yes.

Ask every shortlisted vendor to answer in writing, and score the written answers rather than the presentation. This guide is general information, not legal or tax advice.

Questions only help if the answers can be checked against something written down. niogod™ publishes its delivery steps on the protocol page and its compliance approach on the security page, and builds every pod around a German-speaking Projektleiter and Abnahme per sprint. If you are preparing a vendor selection for next year, you are welcome to run these 30 questions against that model.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights