Real, anonymous reports from people who interviewed for Software Engineer at OPmobility, newest first and distilled into what to expect across the loop.
Get your personalized OPmobility Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I started with an online interview, and the timeline felt pretty fast from the recruiter side. Soon after, I went through an on-site sequence that included a floor tour, and then I had a follow-up discussion with the production manager. The team I interacted with seemed focused on moving things along, and scheduling was fairly flexible, which helped me keep momentum.
The most technical part of the process landed in a manager technical round where I had to talk through my background and then explain details from studies/projects I’d worked on. I was asked about section studies and also about plastic-related topics like common defects and guidelines, and then I got into fixation strategy. Before that, the interview had the usual “tell me about yourself” opener and a prompt to walk through relevant experience in a structured way. Overall, I walked away with the impression they wanted clear, domain-specific answers quickly, and I couldn’t tell whether my fit was judged as much by clarity and depth as by the content itself.
> 1 year
Average Positive Anderson, SC
My process started with an HR screening, and after that I moved into two more interviews with managers. The first HR step leaned into background and how I’d handled work situations, and I remember the HR conversation including scenario-based questions about how I’d react in different circumstances. The overall tone felt a little judgmental at moments, especially when it came to how I’d frame my experience.
Once I got past that step, the rest shifted into a more technical and role-focused direction. I sat down with one manager and the conversation stayed anchored in how things worked within the company and how my past industry experience translated to the work they were doing. There were also follow-up questions about my employment history, including gaps, where I had to explain clearly rather than just list dates. Afterward, I had another interview with managers from other branches to confirm the fit.
> 1 year
Average Neutral France
My journey started with a call with talent acquisition, and then the process moved straight into a manager conversation shortly after. The feel was th…
> 1 year
Average Negative Genk
I went through a two-step process that started with HR and moved into a technical interview. The first part felt relatively basic, while the second st…
> 1 year
Easy Negative Iaşi
I first took an exam, and then the follow-up interview centered directly on that assessment. The interviewer moved from discussing the exam into a lot…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Timeline & Structure
The interview process is generally fast-paced, starting with an HR screening followed by technical discussions with managers. Candidates noted a structured flow, often moving quickly from one step to the next without much delay.
TimelineStructureFast-paced
Technical Assessment Focus
Candidates experienced a strong emphasis on technical knowledge, particularly in areas relevant to the role, such as battery pack design and programming languages like C and C++. The technical interviews often involved discussing past projects and applying knowledge to specific scenarios.
TechnicalC/C++Battery design
Behavioral Screening
The initial HR screening included scenario-based behavioral questions aimed at understanding how candidates handled past work situations. This part of the process was described as somewhat judgmental, impacting the overall candidate experience.
BehavioralHR ScreeningScenario-based
Interviewer Dynamics
Candidates reported mixed experiences with interviewers, ranging from cordial and engaging to challenging and dismissive, particularly during technical discussions. The quality of interaction significantly influenced candidates' perceptions of the evaluation process.
Interviewer dynamicsEngagementEvaluation
Preparation for Technical Depth
Candidates felt the need to prepare not only for technical questions but also to articulate their experiences clearly and in detail, as interviewers sought specific, domain-related answers. The ability to connect past experiences to the role was crucial.
PreparationTechnical depthExperience articulation
Outcome & Feedback
Candidates noted that feedback and communication post-interview were generally prompt, with decisions often communicated within two weeks. However, many left without offers, feeling that the interviews did not fully reflect their capabilities.