Seven Bridges Software Engineer Interview Questions
& Process

The first interview was about my past work and the technologies I used in previous projects. Then, a more technical interview followed, where I was asked about solving problems in a microservices architecture. After these two interviews, I had a small programming project to complete.

It was a really nice interview process, with three rounds. The first round was a combined interview with HR and some Software Engineers. I spoke with the engineers about Python specifics and software engineering best practices. I also spoke with HR about my past experience and how I've handled situations like managing difficult personalities, mentoring, etc. I skipped the second round, which involved a take-home task to be completed within a week, likely building an API. The third round was a meeting with the engineering manager and two software engineers. Since I skipped the take-home task, we did a systems design interview instead. It was a casual discussion where we explored my design approach, its pros and cons, and potential improvements, including scalability. I got a written offer about a week after this last meeting. The employer provided good, open feedback throughout the process.

The interview had three rounds. First was a Tech + HR screening. The technical part covered what I did and my interests, then basic CS stuff like data structures, multithreading, databases, software architecture, and OOP. It was a relaxed chat with two leads. The HR screening was also great, the HR person was friendly, went over my CV, asked about my career, experience, plans, and preferences. She was professional and responsive. Second, I had a take-home task to build a mini app with a few endpoints, a good way to show skills. Third was a technical interview with three heads. It felt more like a casual chat with senior colleagues. I presented my solution, we discussed concepts I used, and they asked 'what-if' questions about software architecture, system design, and databases.