> Markdown version of [/jobs/ext/3586058-cybersecurity-engineer](https://www.wearedevelopers.com/jobs/ext/3586058-cybersecurity-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # cybersecurity engineer - **Company:** coera robotics - **Location:** Berlin, Germany - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, C++ (Programming Language), Cloud Computing Security, Cyber Security, Linux on Embedded Systems, Firmware, Public Key Infrastructure, Reverse Engineering, Software Engineering, Cloud Platform System, Production Code, Vulnerability Analysis - **Published:** October 5, 2026 - **Apply:** https://www.adzuna.de/details/5893001333 ## About the Role * At least five years in product or platform security, with hands-on software engineering fluency. Production code in C and C++. * Hardening embedded Linux and firmware, including secure boot chains. * IEC 62443-4-1 and -4-2 and ISO/IEC 27001, with working literacy in CRA Annex I and TARA methodology. * Cloud security fluency. * Cryptographic primitives and PKI operated in production. Strong signals * Prior work on a safety-certified or functionally safe product. The single most valuable signal for coera because it means you already treat security and safety as one property. * Published vulnerability research, CVEs, or speaking record at Black Hat, DEF CON, Pwn2Own, OffensiveCon, CCC, or Troopers. * Cyber-physical attack surfaces and hardware-level threats: anti-tamper, reverse engineering. * CRA, NIS2, or Machinery Regulation 2023/1230 fluency demonstrated in shipped product. * AI and ML system security literacy: model weight protection, model supply chain, adversarial inputs. ## Description A robotic agent that can be compromised is a robotic agent that cannot be trusted. Security is the shadow half of coera's safety guarantee. The EU Cyber Resilience Act is in force, reporting obligations start September 2026, and full application follows in December 2027. You will own the security architecture, the threat model, and the evidence base that lets coera pass every customer security review and every regulator briefing. what you will own * Design the end-to-end security architecture of coera's platform: supply chain, build pipeline, deployed runtime, update channel. * Deliver CRA (Regulation (EU) 2024/2847) Annex I conformance and the IEC 62443-4-1 and -4-2 evidence base for the first customer deployment. * Run threat modelling (TARA) on every integration and turn findings into shipped mitigations. * Own incident-response readiness, penetration-testing relationships, and the security artefacts that pass customer review. * Work closely with the safety engineer to keep safety and security as one property. * Set the bar for secure engineering practice across the team.