Offered opportunities to learn new technologies. Good benefits and work environment.
On many occasions, long hours with tough schedules exist due to bad management.
First, a simple phone screen, with no much technical stuff. Then, an on-site interview, with maybe around 4-5 people. All questions will be technical, and most questions will relate to your resume. After that, you should hear the result in 2-3 wee
To start, a recruiter scheduled a telephonic interview with a hiring manager who was himself a Sr. Principal Engineer. The interview lasted for an hour. The interview was difficult, and it appeared the interviewer asked questions primarily based on
C: - Data structures - Embedded basics - State machines Questions on previous positions to understand knowledge depth. Challenging issues solved in previous jobs. Systems design questions. RTOS problems. Architectural system design questions.
First, a simple phone screen, with no much technical stuff. Then, an on-site interview, with maybe around 4-5 people. All questions will be technical, and most questions will relate to your resume. After that, you should hear the result in 2-3 wee
To start, a recruiter scheduled a telephonic interview with a hiring manager who was himself a Sr. Principal Engineer. The interview lasted for an hour. The interview was difficult, and it appeared the interviewer asked questions primarily based on
C: - Data structures - Embedded basics - State machines Questions on previous positions to understand knowledge depth. Challenging issues solved in previous jobs. Systems design questions. RTOS problems. Architectural system design questions.