Mid-level Engineer Interview

Can you describe a project where you were responsible for building an end-to-end feature in a web or mobile application?

In my previous role at EmloymentHero, our team handle the module of documents, we need to migrate all of the legacy UI to React UI and prepare for mobile app, I was in charge of the module uploaded document migration, where we allowed user to upload file relate to policy contract and identities and secure it. At that time I want to handle totally whole modules from BE, FE, and mobile app as I want to learn more about FE and mobile work, I developed an API convert the existing flow to our service object pattern to prevent fat controller, document the API that I developed, coordinated with Designer to confirm the logic, had sprint planning to instroduce my plan and gather the oppinion from the team, the daily stand up to update the progress. Reached out to mobile team to have the code review as at that time I'm new to mobile development,

Your answer adequately addresses the interview question by providing a specific project example where you were responsible for building an end-to-end feature. You clearly outline your role, the technologies involved, and the collaborative aspects of the project, which are all important in demonstrating your capability as a mid-level engineer.

However, there are areas for improvement. Your response could benefit from structure and clarity. Start by briefly summarizing the project's goal, then detail your specific responsibilities and actions taken, mentioning the technologies used in more direct terms. Emphasize outcomes or results—mention how your contributions impacted the team or improved the application. For instance, did the migration increase efficiency or enhance user experience? Finally, consider refining your terminology (e.g., "document migration" may be better framed as "document upload feature development" to clarify your focus on functionality).

To improve your answer, you might say, "At EmploymentHero, I led the development of a document upload feature as we migrated our legacy UI to React. My role encompassed backend, frontend, and mobile components. I created an API to support user file uploads related to policy contracts and identities, ensuring secure handling of documents. I collaborated closely with our designer to align on UI logic, participated in sprint planning to gather team feedback, and provided updates during our daily stand-ups. I also reached out to the mobile team for code reviews to enhance my understanding of mobile development. This project not only reinforced my skills across the stack but also improved our document management efficiency."

Overall, I would rate your answer a 3.5/5. With some restructuring, clearer outcomes, and refined wording, you could significantly enhance your response.

What experience do you have with Ruby on Rails and React, and how have you applied these technologies in previous projects?

In my previous role at Emloyment hero, we use Rails as the Primary BE API framework, we defined API, and document it, prepare unit tests by using Rspec for each code in services, controllers, modules and background job by using Sidekiq that we have defined and we document the API using swagger so other teams could utilise once needed.
We use React as main FE library, we also develped the UI Design system that call HeroDesign which proivded common components for both web UI and mobile UI, we would based on the API document and coordinate with designer to implement the UI, prepare test for those by using Jest.
I also have the similar setup for my sideproject which also use Ruby Rails, React, Sidekiq Rspec, Docker,

Your answer provides a solid overview of your experience with Ruby on Rails and React, showcasing relevant technologies and methodologies. Here’s an evaluation of your response:

1. Clarity and Structure: You start by identifying Ruby on Rails as the backend framework. You mention key practices, like API documentation and unit testing, which illustrates a thorough understanding of the development process. However, there are a few minor grammar issues (e.g., "Emloyment hero" should be "Employment Hero," and "develped" should be "developed").

2. Technical Detail: You provide specific details about tools and libraries (e.g., RSpec, Sidekiq, Swagger) which demonstrates technical competence. Mentioning your work with a design system (HeroDesign) adds depth to your frontend experience with React.

3. Relevance: You effectively relate both your professional role and a personal project, reinforcing your familiarity with the tech stack. This dual perspective can be valuable to potential employers.

4. Improvements: To enhance your answer, you could:
- Share specific outcomes or achievements from your projects (e.g., performance improvements, user satisfaction).
- Briefly explain how you overcame challenges in either technology.
- Provide a more concise connection between how your experiences directly relate to the job you’re interviewing for.

5. Rating: Considering the strengths and areas for improvement, I would rate your answer a 4/5. Your experiences are relevant and well-articulated, but clarifications and specific examples of impact could elevate your response further.

How do you approach understanding and solving customer problems when developing software?

We need to analyse the customer problems to align with what our product to categorise, what are the problems we can support, we already supportted and hard to support with the alternative proposal, level of the urgency of the problem, to decide when to take action.
So let's say if the problems affect many clients and it stops client from using the applicaiton, it should be in the highest priority, we need to focus on resolving, by identify the problem via code, log, step to reporeduce, implement to quick fix soon if possible in case, we should find the long term fix the root cause of the issue and fix to prevent the similar issue to happend again. after fixing the issue, we should prepare the postmortern analysic which mentioned the reason, how was it happen when was it happen and how could we fix it, related ticket, code change and share to the college.
for the lower priority we also fix it at our convinience at the customer needed

Your answer provides a good foundation by highlighting important aspects of problem identification, prioritization, and resolution in a customer-focused context, particularly in the construction technology industry. You mention key steps such as analyzing customer issues, categorizing problems, and distinguishing between urgent and lower priority issues, which demonstrates a structured approach to software development and customer service.

However, there are areas for improvement. For instance, you could emphasize the importance of direct communication with customers to fully understand their needs and frustrations. Understanding not just the "what" but the "why" behind customer problems can lead to more effective solutions.

In addition, consider discussing the iterative nature of software development, emphasizing how customer feedback loops can inform future product iterations. You could also touch on collaboration with teams (like QA and product management) to ensure that solutions align with broader business goals and user experience.

Lastly, clarity and conciseness are crucial in interview responses. While your answer covers essential points, it could benefit from clearer structuring and a more polished presentation to enhance comprehension.

Rating: 3.5/5

To improve your answer, focus on these aspects:
1. Direct customer engagement for deeper understanding.
2. Iterative development and feedback loops.
3. Clearer structure and better presentation for clarity.