{"id":111,"date":"2024-02-14T15:13:44","date_gmt":"2024-02-14T15:13:44","guid":{"rendered":"https:\/\/zephrcf.leaddev.com\/leaddev-new-york-2024\/?page_id=111"},"modified":"2026-05-12T13:42:52","modified_gmt":"2026-05-12T13:42:52","slug":"leaddev-berlin","status":"publish","type":"page","link":"https:\/\/zephrcf.leaddev.com\/leaddev-berlin\/","title":{"rendered":"LeadDev Berlin 2026"},"content":{"rendered":"\n
\"LeadDev<\/span>
\n

Berlin \u2022 November 9\u201310, 2026<\/p>\n\n\n\n

 The pressure is real. <\/strong>
 Find what works.<\/strong> <\/mark><\/h1>\n<\/div><\/div>\n\n\n\n
\n
\n
\n

For engineering leaders<\/mark> when the job is changing faster than the playbook<\/h2>\n<\/div>\n\n\n\n
<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n

You’re expected to deliver results from AI<\/strong>, keep your team from burning out<\/strong>, and close the gap between what leadership expects and what’s actually possible<\/strong>. And do all of it without a clear engineering leadership playbook.<\/p>\n\n\n\n

LeadDev Berlin<\/strong> is where that changes.<\/p>\n<\/div>\n\n\n\n

\n