Hello, my name is Yacob. I'm a software developer with 10 years of experience. I'm specializing in back-end and front-end development.

I have been working in Mitrais for the last four and a half years, and my most recent experience with Mitrais is working with around eight members. We are a team working on a CRM product. This CRM product is rely (relies) heavily on many AWS services.

Our main stack for this project is our Node.js, React.js, TypeScript, and we also use various AWS services and rely heavily on AWS Connect. We are creating this application in serverless architecture, so we use services like DynamoDB, API Gateway, et cetera, that is mainly on serverless architecture. In my last project, I'm mainly responsible around 60% front-end and 40% back-end.

Previously, prior to joining Mitrais, I'm also working on a geomapping application with the same stacks, Node.js, React.js, JavaScript, and also AWS. In total, I have six years of experience with my current stack, Node.js, React.js, and AWS. Thank you.

My last project, I work with around eight members in a team. We work on a CRM product. And this CRM product relies heavily on AWS services, especially AWS Connect.

And we use AWS serverless architecture. So, for the cloud infrastructure and for the front-end side, we use React.js with TypeScript. And on the back-end side, we use Node.js to write Lambda functions.

So, the stacks are around JavaScript and also AWS services. So, in my last project, I'm responsible both in front-end and back-end side. And I'm also familiar with many various AWS services that we use.

DynamoDB, API Gateway, CloudWatch, and the serverless framework itself. And the project lasts for four and a half years, I think. That's a very long time for a server engineering team.

And I was the first person among the first person that the team acquired. So, I'm responsible for a lot of onboarding projects. Sorry. Onboarding for new members on the team. Yeah. That's all.

Thank you.

My hardest challenge on the last project, especially when the tech leader decided to switch from serverless architecture to containerized architecture, which I'm not familiar with the technologies and the stacks. So, to overcome that, I have to learn the containerized architecture and technologies and set myself up some time for self learning, learning Docker, learning Festify, and a lot of things that are related to container architecture.

So, at first, it was really hard. Because I work with team members that have many experience already. So, with them around me, I have the opportunity to learn.

And at first, the learning spike, learning curve is really high. But thankfully, I can set a time to learn for myself. And also, when I face difficulties, I rely on asking my teammates to set the same frequencies and also to catch up with the technologies.

I think I'm the right fit for your project. Especially if you're looking for a person who are able to do a lot of things in different roles. On my previous project, I have been working on different roles on the front end side, on the back end side, and also on the infrastructure.

And also, I conducted onboarding process for all my team members. So, whether it's a new team or a team that is already existing, I can fit in well. Thank you.

Learning new technologies can be quite challenging, especially given a short timeline. And I have experienced requests from previous clients to learn some new things. And for learning new things, I mostly rely on doing a short project, for example, and to apply all the required technologies.

We also have CDC, company development center that have a bootcamp, various bootcamp projects, and also self learning bootcamps. And also, I have my own resource of learning, which is from Udemy and also from documentation. So, usually, me and my team will create a short project or a sample project that will include all the new technologies that we learn on.

I don't mind doing something specific, such as dealing with old technologies, as long as you have documentation for the old technologies. And so, I have clear understanding and have clear guidelines on how to learn and how to meet the requirements for that specific task.

The best part about my last project is that the project lasts for four and a half years.

And four and a half years is a very long time and very rare for a software engineering team. So, I love being on the team that is last long. And so, we are putting commitment for such a long time. It's amazing for me. So, I get to know each other, my tech leader, even my product owner, and my team members. It is an amazing experience to be on a team that trusts each other, that's open, and have courage to do something.

And we are able to add values on the team. So, the team does not get boring and always have something fresh and have also have new challenges every span of time. So, having on the team for so long is the most amazing thing for me on my last project.

And when facing a high pressure situation on my last project, the most important thing that I learned is that I have to be honest to the other team members about the situation that I'm facing. And so, we are as a team analyzing what is the impact of this mistakes or the situation that I'm facing that will probably affect the others as well. So, after being open about the situation, I will work with the team to make a plan. Make a plan and ask the tech leader or the scrum master to prioritize the situation.

If the impact is huge or this situation is impacting a lot of stakeholders and a lot of modules that maybe the other team members is working as well. So, being honest and have the courage to take responsibility and also open to getting help from the other team members to solve the situation and break down tasks.

And also spend more time to work on the problem. So, we can have smaller tickets or smaller tasks. So, it is easier to handle as a team.

So, keeping up with current technologies is very hard, especially in this information technology fields where the number of technologies are growing year by year. So, I am keeping up by reading. First, I am reading from a lot of resources, especially Medium.

And I periodically also creating a mini project that are using new technologies. And also, I'm tracking some open source projects, for example. But for the most part, I'm creating a mini project that is my own interest and applied the technology stacks in that mini project.

And also, yeah, I'm keeping up with a lot of readings as well. So, that's my way of keeping up with technologies.

Strengths:

• Emphasizing communication and collaboration shows you’re a team player.

• Breaking down tasks into smaller, manageable parts demonstrates a systematic approach to problem-solving.

Room for Improvement:

• Provide a specific example of a high-pressure situation you handled successfully.

• Highlight the positive outcome of your efforts to show how your approach made a difference.

Suggested Answer:

"In a high-pressure situation on my last project, our deployment pipeline failed close to a release deadline. I immediately informed my team and collaborated with the tech lead to analyze the issue.

We identified a configuration error in the pipeline and broke the tasks into smaller tickets for faster resolution.

By prioritizing tasks and working as a team, we resolved the issue within a tight timeline, ensuring the release was successful.

This experience reinforced the importance of transparency, teamwork, and staying calm under pressure."

Strengths:

• Highlighting personal initiatives like creating mini-projects shows genuine interest and curiosity.

• Mentioning resources like Medium and LinkedIn demonstrates your engagement with industry trends.

Room for Improvement:

• Add a specific example of a trend or technology you’ve recently explored and how it benefited your work.

• Connect your continuous learning efforts to how they can bring value to future projects.

Suggested Answer:

"I stay updated on trends by reading articles on Medium, following industry leaders on LinkedIn, and exploring open-source projects.

Recently, I’ve been learning more about serverless architecture and experimenting with AWS Lambda through mini-projects.

These hands-on experiences help me understand how new technologies can be applied to solve real-world problems.

By staying curious and proactive, I ensure I’m always equipped with the latest tools and knowledge to bring value to my team and projects."

Suggested pronunciation:

resources

UK /rɪˈzɔː.sɪz/ or /ˈriː.sɔː.sɪz/

US /ˈriː.sɔːr.sɪz/ or /rɪˈzɔːr.sɪz/

Sentence: I am reading from a lot of resources.

Strengths:

• Clear and concise overview of your experience, roles, and technical expertise.

• Mentioning specific tools and technologies like Node.js, React.js, and AWS gives depth to your profile.

• Highlighting your six years of experience with your stack demonstrates consistency and reliability.

Room for Improvement:

• Consider adding a measurable impact, such as how your work contributed to the success of a project (e.g., improving efficiency or scalability).

• Your introduction could end with a statement about what makes you unique or your passion for software development.

Suggested Answer:

• "Hello, my name is Yacob, and I’m a software developer with 10 years of experience, specializing in both back-end and front-end development.

• For the past four and a half years at Mitrais, I’ve been working on a CRM product heavily reliant on AWS services. Our stack includes Node.js, React.js, and TypeScript, with a serverless architecture leveraging tools like DynamoDB and API Gateway.

• My primary responsibility involves a 60/40 split between front-end and back-end, where I ensure seamless functionality and scalability.

• In my previous role, I worked on a geomapping application with similar stacks. I take pride in creating efficient and reliable systems, and I’m passionate about applying my expertise to solve complex problems and deliver value to clients."

Suggested pronunciation:

• developer
  UK /dɪˈvel.ə.pər/
  US /dɪˈvel.ə.pɚ/

• I'm a software developer with 10 years of experience.

Strengths:

• Clear explanation of your role and responsibilities.

• Mentioning tools like AWS Connect, Lambda, and DynamoDB highlights your technical expertise.

• Bringing up your onboarding contributions adds a leadership angle.

Room for Improvement:

• Talk more about the impact your work had on the project or the client (e.g., improved user experience, reduced downtime).

• Structure your response for clarity—group responsibilities, technologies, and contributions.

• Avoid repetition (e.g., you mention the tech stack multiple times).

Suggested Answer:

• "My last project was a CRM application for a client, where I worked as part of an eight-member team for four and a half years. The application relied heavily on AWS services, such as AWS Connect, DynamoDB, and API Gateway, within a serverless architecture.

• My role involved a mix of front-end development using React.js with TypeScript and back-end work creating Lambda functions with Node.js. One of my key contributions was streamlining the onboarding process for new team members, which improved productivity and team integration.

• Additionally, I ensured smooth data flow and functionality across services, contributing to the app's scalability and reliability. This long-term project allowed me to hone my expertise in serverless architecture while making a tangible impact on the product’s performance."

Suggested pronunciation:

• infrastructure

  UK /ˈɪn.frəˌstrʌk.tʃər/

  US /ˈɪn.frəˌstrʌk.tʃɚ/

• So, for the cloud infrastructure...

Strengths:

• Highlighting a challenging transition (serverless to containerized architecture) makes your story relatable and shows resilience.

• Mentioning tools like Docker and Festify demonstrates technical growth.

• Acknowledging the learning curve and teamwork adds a human element to your response.

Room for Improvement:

• Add a measurable outcome—how did learning these new tools help the team or the project?

• Briefly explain what the containerized architecture change accomplished (e.g., better scalability, easier deployment).

Suggested Answer:

• "The hardest challenge I’ve faced was when my team transitioned from serverless to containerized architecture, which was completely new to me. I had to quickly familiarize myself with technologies like Docker and Festify while continuing my regular responsibilities.

• I dedicated extra time to self-learning and collaborated closely with experienced teammates to understand the nuances of the new stack.

• This teamwork, combined with my determination, helped me adapt and contribute effectively to the project.

• At the end of the day, the transition improved our system's scalability and deployment processes, and I gained valuable expertise in containerized architecture."

Strengths:

• Highlighting your adaptability and experience in different roles (front-end, back-end, infrastructure).

• Mentioning your onboarding experience shows leadership and collaboration skills.

Room for Improvement:

• Focus more on how your skills align with the client’s needs—what unique value will you bring to their team?

• Avoid repeating generic statements like "I can fit in well" and instead emphasize your specific contributions.

Suggested Answer:

• "I’m very confident about joining your team because of my experience working across front-end, back-end, and infrastructure roles. In my previous project, I not only contributed technically but also took ownership of onboarding new team members, ensuring smooth team dynamics.

• I believe my adaptability and ability to collaborate with different team members will help me quickly integrate and contribute to your project. I’m excited about bringing my expertise in serverless architecture, AWS services, and full-stack development to add value to your team."

Strengths:

• Mentioning the use of short projects and bootcamps demonstrates a practical learning approach.

• Highlighting team collaboration in learning new tech shows you're resourceful and open to shared growth.

• Including specific resources like Udemy adds credibility to your learning strategy.

Room for Improvement:

• Consider providing an example of a specific technology you successfully learned using this approach. It will help make your answer more relatable and impactful.

• Tie the response to client benefits—how your ability to adapt quickly can contribute to their project’s success.

Suggested Answer:

"When I need to learn a new technology, I start by exploring online resources like Udemy courses, official documentation, and company bootcamps. For example, when I had to work with Docker for the first time, I built a short project to understand its practical use.

Additionally, I collaborate with my team to create sample projects incorporating the new technology, which helps me understand its application in real-world scenarios.

By doing this, I ensure I can quickly adapt to new tools and deliver value to the project while minimizing the learning curve."

Strengths:

• Emphasizing the importance of clear documentation shows you value understanding and clarity before diving into tasks.

• Highlighting adaptability reassures the client of your willingness to meet their specific needs.

Room for Improvement:

• Add an example where you’ve worked with older technologies before, demonstrating your ability to adapt and deliver results.

• Mention how your experience in learning new technologies can also apply to mastering legacy systems.

Suggested Answer:

"I’m comfortable working with older technologies, especially if there’s clear documentation and guidelines available.

For example, in a previous project, I had to work with a legacy system for manufacturing operations, which required adapting to older frameworks.

I ensured that I fully understood the system by reviewing documentation and consulting with team members.

This adaptability allows me to effectively contribute to the project while learning and improving the system where needed."

Strengths:

• Mentioning team dynamics like trust, openness, and collaboration paints a positive picture of your work environment.

• Highlighting fresh challenges over time shows that you thrive in evolving projects.

Room for Improvement:

• Discuss your specific contributions to the project and how they added value to the team or the client.

• Include how this experience prepares you for future projects, showcasing your adaptability and teamwork.

Suggested Answer:

"The best part of my last project was the opportunity to work with a committed team for over four and a half years.

During that time, we built trust and collaborated on solving new challenges together, which kept the project engaging.

One memorable contribution I made was streamlining the onboarding process for new team members, which improved productivity.

This long-term experience taught me the value of teamwork, adaptability, and maintaining fresh perspectives, which I’m eager to bring to my next project."