Real, anonymous reports from people who interviewed for Software Engineer at Amphenol Borisch Technologies, newest first and distilled into what to expect across the loop.
I ended up interviewing through a career fair, and the whole experience felt pretty light on technical depth. The process started with an initial recruiter conversation and then moved into meeting managers back-to-back. I talked about myself and my background, and I got a lot of conversation time aimed at explaining what the company was like and where I’d fit. There weren’t any formal technical tests, and the questions skewed toward my experience and interest rather than problem-solving.
My process started with a recruiter conversation where they asked about my previous experience and also brought up salary expectations. It was the kind of HR round where the tone was friendly, and it mainly set context for what they were looking for before I moved on.
The interview process typically begins with a friendly recruiter conversation focused on background, experience, and salary expectations, setting a positive tone for the subsequent interviews.
Candidates can expect technical discussions that emphasize fundamental concepts rather than deep coding challenges, often involving practical applications and problem-solving related to the role's requirements.
Many interviews prioritize assessing cultural fit and alignment with the team's needs over rigorous technical testing, with interviewers often seeking to understand candidates' experiences and how they relate to the company's work.
The interview process is generally organized and streamlined, often consisting of a sequence of discussions that may include technical evaluations followed by HR interactions, ensuring a clear progression.
Candidates report a casual and friendly atmosphere throughout the interviews, which helps reduce stress and encourages open communication, although some may find the lack of depth in technical questioning surprising.
Candidates often leave interviews without offers but reflect positively on the experience, noting that the process felt more like a learning opportunity than a high-pressure evaluation, emphasizing the importance of solid foundational knowledge.