Equal Experts Interview Questions
& Process

First up is an initial screening with HR, where they'll chat with you about your background and see if you're a good fit for Equal Experts. They'll also give you the lowdown on how EE works, what kind of projects you might be on, and what they expect. It's a chill chat to make sure you're on the same page before you move on. Next, there's a take-home assignment. This is a coding task designed to see how you tackle real engineering problems. EE likes things simple and clear, so they want to see a solution that's straightforward, well-organized, and easy to follow. They're looking for clean, maintainable code, good structure, solid tests, clear docs, and sensible commit messages. It's less about fancy tech and more about how you engineer and communicate your solution. Then, you'll have a technical round. This has two bits: first, you'll discuss your take-home assignment, talking through your design choices, tests, trade-offs, and how you might improve it or scale it up. They'll also dig into your testing strategy and code quality. The second part of this round is a deep dive into your past projects. You might need to talk about system architecture, your responsibilities, design patterns, decisions you've made, challenges you've faced, and how you deal with complex stuff in real projects. This is to check your experience and technical depth. Finally, there's a consulting and fitment round. This one's all about your consulting skills, how you communicate, and if you'll fit in with the team culture. EE wants engineers who are good collaborators, practical, and can work well with clients. You'll likely discuss how you handle uncertainty, work with stakeholders, solve problems, and help the team deliver. It's to make sure you're aligned with EE's values like simplicity, autonomy, responsibility, and always learning.

The interview had 3 parts. First, a take-home coding assignment that was pretty easy, focusing on TDD and how tests are added, covering both positive and negative scenarios, and using mocks for external services. Then, a 2-part round: the first 45 mins involved pairing and extending the coding assignment, adding features, covering missed scenarios with TDD. The next 45 mins focused on my past projects, asking about architecture, user flows, scalability, error handling, fault tolerance, and my contributions.

Had a screening call with the recruiter, though they kept calling at odd times, which felt unprofessional. Then, there was a take-home test where I had to use the YouTube API to build a small app that included search, infinite scrolling, and displaying results, along with test cases. After that, I had an online interview to go over the take-home test and discuss improvements like adding search suggestions and filtering, and also talk about the test cases.

The first meeting was good. They asked me about my past jobs, what I'm qualified for, and what I'm looking for in a new role. The second interview dove into the technical side of my software delivery experience. We talked about things like agile methods, managing stakeholders, and handling risks. The third interview was about seeing if I'd fit with the company culture and their clients. It was more relaxed, and we chatted about my hobbies and interests outside of work. Even though the interviews were varied, I felt confident in my answers and how I presented myself.