This website uses cookies to ensure you get the best experience.

Coretura and our selected partners use cookies and similar technologies (together “cookies”) that are necessary to present this website, and to ensure you get the best experience of it. If you consent to it, we will also use cookies for analytics and marketing purposes.

See our Cookie Policy to read more about the cookies we set.

You can withdraw and manage your consent at any time, by clicking “Manage cookies” at the bottom of each website page.

Select which cookies you accept

On this site, we always set cookies that are strictly necessary, meaning they are necessary for the site to function properly.

If you consent to it, we will also set other types of cookies. You can provide or withdraw your consent to the different types of cookies using the toggles below. You can change or withdraw your consent at any time, by clicking the link “Manage Cookies”, which is always available at the bottom of the site.

To learn more about what the different types of cookies do, how your data is used when they are set etc, see our Cookie Policy.

These cookies are necessary to make the site work properly, and are always set when you visit the site.

Vendors Teamtailor

These cookies collect information to help us understand how the site is being used.

Vendors Teamtailor

These cookies are used to make advertising messages more relevant to you. In some cases, they also deliver additional functions on the site.

Vendors Vimeo
Skip to main content
Technology · Lindholmen

Power & Network Management Architecture

Own the power and network architecture across our vehicle platform

The Vision

We build the software platform that makes software-defined vehicles trustworthy, safety-critical middleware, connectivity, and software update capabilities running in commercial vehicles on public roads. The architecture decisions we make today will be in production for a decade, so getting them right from the start is a necessity, not a preference.

Why This Area Matters

Power and network management sit at the hardware/software boundary, and once a platform is in production these decisions are among the most expensive to change. A poor sleep/wake architecture means wasted energy, unreliable networks, and costly hardware respins; a good one is invisible. This is where great architecture has the highest leverage on the entire platform.

The Platform Context

Our platform consists of two HPCs and one Connectivity Unit, each HPC containing a SoC (running QNX, Linux, and Android via virtualisation) and an MCU (safety-critical real-time layer). Power and network management must coordinate sleep and wake across operating systems within a chip, across chips within an ECU, and across ECUs in the vehicle.

The Role

We are looking for an architect to own power and network management architecture across our platform, working directly with capability owners to provide the direction, patterns, and constraints they need. This is not a hands-off governance role, you will produce concrete artefacts that unblock engineering and shape decisions that cannot easily be revisited.

What You Will Deliver

  • Architecture Design Boundary and System Context, where power and network management begins and ends, and how it interfaces with the platform

  • Reference Architecture, a context-specific white book of directions, patterns, and design requirements for the domain

  • Design Constraints, domain, capability, and system-specific constraints feeding directly into development

  • Critical Architecture Decisions, identify and resolve the questions that must be settled before capability owners can proceed

  • Architecture Analysis Records, documented analysis of key choices, trade-offs, and rationale

The Concrete Problems You Will Solve

Active challenges on our platform today:

  • MCU network management, AUTOSAR Classic NM stack coordinating sleep/wake across multiple CAN channels, partial networking, and TC10 PHY sleep/wake for Ethernet, all with precise timing

  • SoC network management, QNX (NM master), Linux, and Android share a chip and must agree on network participation; the IPC between them and coordination with TC10 PHY needs end-to-end architecture

  • Graceful shutdown, defining "deep sleep" for MCU and SoC: what state is preserved or released, in what order, and how the system recovers cleanly on wake-up

  • Cross-ECU coordination, the two HPCs and the Connectivity Unit must coordinate network state so no ECU sleeps while another still depends on it

What We Are Looking For

You have a solid background in embedded automotive software architecture, with hands-on experience in AUTOSAR (Classic and/or Adaptive), vehicle network management, and E/E architecture, and you know the difference between designing for a lab and designing for a decade in the field.

Experience with partial networking, TC10, UdpNm, or multi-OS embedded environments is a strong advantage. On the power side, we particularly value cross-OS synchronisation for power management frameworks, suspend-to-RAM (S2R), a solid understanding of boot and sleep states and their safety impacts, and dynamic power management framework implementation.

Above all, you can take a complex, cross-cutting problem, define its boundaries, and produce architecture that engineers can actually build from, comfortable at the intersection of hardware constraints and software design, because that is where this role lives.


Apply Anonymously?

Many would like to know more before putting themselves out there. Generate and apply with your anonymized resume and hidden mail here. This means we will review your profile without knowing your identity, and keep the initial dialogue to an untraceable mail address.

Department
Technology
Role
Architecture
Locations
Lindholmen
Picture of Tobias Schött
Contact Tobias Schött Talent Acquisition Partner
Technology · Lindholmen

Power & Network Management Architecture

Own the power and network architecture across our vehicle platform

Loading application form

Applicant tracking system by Teamtailor