Cyient embedded interview prep

Roles they hire for

• Aerospace embedded engineer
• Rail and medical embedded engineer

What they emphasise

• Aerospace, rail and medical embedded
• DO-178C and EN 50128
• Embedded Linux

Brush up on

DO-178CEN 50128ARINC 429 basicsTraceabilityEmbedded Linux

How the rounds usually run

A typical engineering services loop for embedded roles. Companies vary by team and seniority.

Online test

• Aptitude and reasoning
• C programming, electronics and OS basics

Example: What does sizeof return for a struct with a char, an int and a char, and why?

Technical 1: C and fundamentals

• Pointers, memory, data structures in C
• Your projects and the tools you used

Example: Reverse a singly linked list in place.

Technical 2: Domain for the project

• Depends on the project: AUTOSAR, Linux drivers, RTOS or protocols
• Scenario questions from real client work

Example: Explain how you'd add a new peripheral driver in the stack you know best.

Client interview (for project roles)

• The client's own technical screen for their programme
• Communication and ownership

Example: Explain your last module's design to someone who didn't build it.

HR

• Notice period, location and compensation

Example: Are you open to onsite assignments?

Practice questions

Original questions written for Cyient's focus areas, not leaked ones.

1. What does structural coverage (MC/DC) mean, and why does aerospace require it?
2. How does EN 50128 shape software for railway signalling?
3. Design a redundant sensor voting scheme for a safety function.
4. How do you maintain traceability when requirements change late?
5. Explain how you'd review code for a safety-critical module.

Your prep playlist

Design rounds to practise

Themes are inferred from Cyient's public product lines.