Dataiku is hiring a German-speaking BDR to run vertical campaigns into DACH banking, insurance, retail and utilities, and the new VP of Field Marketing is told to localize with AI. But every industry page on the German site (/de/solutions/banking, insurance, manufacturing and eight more) is English text under a German menu, tagged lang="de" and canonicalized to the English page, so it cannot rank in German. The Japanese versions of the same pages are fully translated. A DACH prospect who clicks "Lösungen" gets English.
First action
Translate /de/solutions/banking and /de/solutions/insurance this week with a native reviewer.
How to measure it
DACH demo requests from German pages
- Now
- –
- Target
- +30%
- By
- 2 quarters
Steps
Confirm the scope
The 11 /de/solutions pages and their use-case cards.
Web team lead 1 day
Translate with AI
Draft German for each page, keeping product names in English.
Digital & Growth lead 3 days
Native review
A German-speaking seller or partner checks tone and terms.
Business Development Representative DACH 3 days
Fix the tags
Self-canonical and hreflang de/en/ja on each page.
Web team lead 1 day
Add German proof
One German-language story each for banking, insurance and manufacturing.
VP of Global Field Marketing 3 weeks
Point campaigns at them
BDR sequences and event follow-up link to the German pages.
Business Development Representative DACH 1 week
Measure
German organic entrances and demo requests by page.
Digital & Growth lead monthly
Why it works
Translate the 11 /de/solutions pages and their use-case cards, give each its own canonical and hreflang, and add one German-language customer story per priority industry (banking, insurance, manufacturing). Use AI translation with a native reviewer, as the VP post expects, then build the BDR's German sequences and German event follow-up around those pages.
German-language buyers search and read in German, and an industry page in their language is the asset a BDR's vertical campaign needs. Japan already shows the pattern works: the localized site carries its own press and customer news.
Ready to use
ChecklistGerman industry page launch list
[ ] Translate all 11 /de/solutions pages and use-case cards [ ] Native reviewer sign-off per page [ ] Self-canonical on each German page [ ] hreflang de / en / ja / x-default [ ] German meta titles and descriptions [ ] One German customer story per priority industry [ ] German demo form confirmation and follow-up email [ ] BDR DACH sequences link to the German pages [ ] Track German organic entrances and demo requests
Risks and how to handle them
Machine translation sounds foreign
Native review of every page before it goes live.
Pages drift from the English versions
Add the German pages to the same release checklist.
Evidence
- Your websiteLocalization check (October 21, 2026): the sitemap's 1,085 URLs carry 231 Japanese alternates but only 91 German ones. All 11 industry and function pages under /de/solutions/ (banking, insurance, healthcare, life sciences, manufacturing, public sector, retail & CPG, utilities & energy, supply chain & logistics, finance & audit, marketing) show English text under the German menu, with lang="de" and a canonical tag pointing to the English page. The Japanese versions, such as /ja/solutions/banking ("銀行業向けAI"), are fully translated with their own canonical; German product pages such as /de/product/mlops are translated too.Source
- HiringBusiness Development Representative DACH (German-speaking, London; open on the board, updated September 1, 2026): "Manage a large volume of daily inbound and outbound leads", "design, research and execute outbound vertical and/or geographical markets campaigns" in a dedicated territory, for industries "such as e-commerce, retail, banking, insurance, utilities, and transport"; "Business Level German" required.Source
- HiringVP of Global Field Marketing (New York, posted October 16, 2026): owns field marketing across AMER, EMEA and APJ, partner marketing and the events portfolio ("Dataiku Succeed, regional Summits and Exchanges", plus Snowflake Summit, Databricks Data + AI Summit and AWS re:Invent), leading "a team of 25 accountable for a material share of company pipeline". Rules in the post: "No program launches without a named sales owner, a follow-up motion and a pipeline number"; "Use AI to localize campaigns and tailor account-level content without adding proportional headcount or agency spend"; "fast, AI-personalized follow-up on every event"; "Rationalize the portfolio continuously on ROI data".Source
- Your websiteGerman customers page is translated ("Lernen Sie einige der über 600 Unternehmen weltweit kennen"), but the stories it links to are English, for example /de/blog/novo-nordisk (English text, canonical to the English post). The Japanese site has its own press releases, such as Japanese localization, the Tokyo SaaS region, and Murata Manufacturing and JAL adopting Dataiku.Source