1. Feature Ownership & Development Impact

✅ Features developed: "I was responsible for implementing a new authentication system using [OAuth], which enhanced security and streamlined user access."
✅ Performance improvements: "I refactored existing components in React to improve code maintainability and reduce redundancy."
✅ Enhancements: "I contributed to optimizing API calls, resulting in a smoother user experience for our customers."

2. Problem-Solving & Debugging Success

✅ Resolved bugs: "I identified and fixed a critical issue causing app crashes on certain devices, ensuring stability for users."
✅ Optimization: "I refactored legacy code to improve maintainability and reduce load times."

3. Collaboration & Team Contributions

✅ Team collaboration: "I worked closely with UX designers to enhance the user interface of our mobile app."
✅ Knowledge sharing: "I documented best practices for state management in React, which helped junior developers onboard more easily."

4. Learning & Adapting to New Technologies

✅ Adopting new tech: "I quickly adapted to using TypeScript in our project, helping to improve code reliability."
✅ Continuous improvement: "I suggested and implemented unit tests for key features, which increased test coverage."

5. Project & Workflow Efficiency

✅ Improved processes: "I helped migrate our project from JavaScript to TypeScript, which reduced runtime errors."
✅ Automation: "I developed scripts to automate repetitive tasks, reducing manual work for the team."

What You Did Well:

·       Concise and focused: You kept your answer short and to the point, which is helpful for keeping the interviewer engaged.

·       Relevant tools mentioned: You referenced core tools like React.js, Redux, and React Router—which shows your practical experience. Highlighting newer tools, you’re learning like Next.js and React Query also shows a growth mindset.

·       Full stack experience: It’s great that you briefly mentioned your exposure to full stack work (.NET, jQuery, Kendo UI). That can be a plus for clients looking for flexibility.

Suggestions for Improvement:

·       Add a little more structure: Your answer could benefit from a more organized flow. Try grouping your experience into key areas (e.g., front-end, back-end, ongoing learning) and wrapping up with a value statement.

·       Show your impact: Right now, it’s tool focused. Consider adding a brief example of how your work made a difference—like improving performance, user experience, or solving a client problem.

·       End stronger: Instead of just “thank you,” wrap up with a line that sells your motivation or the kind of value you bring to a team.

Suggested Version (More Comprehensive & Client-Focused):

“Hi, my name is Faris Adam Gunawan, and I’m a front-end-focused software engineer with about three years of experience.

Most of my work has been with React.js, using Redux and React Router to build scalable, responsive web applications. I’ve also worked on full stack projects using .NET and Kendo UI, which gave me a solid understanding of how front-end and back-end systems connect.

In my last project, I helped improve page performance by optimizing React components, which reduced load time by 30%—something that had a direct impact on user experience.

Lately, I’ve been expanding my skills by learning Next.js, React Query, and Formik, so I can bring more up-to-date solutions to the table.

I’m excited about opportunities where I can contribute to building high-quality products while continuing to grow technically.”

What You Did Well:

·       Clear project scope: You mentioned two distinct applications—public-facing and internal—which shows that you can work on different types of products.

·       Defined responsibilities: You listed the specific parts you built, such as the landing page and tables, which helps the interviewer understand your involvement.

·       Tech stack awareness: You outlined the tools you used—React, React Router, Redux, and OpenID—so it’s easy to see your technical foundation.

Suggestions for Improvement:

·       Make it more structured: It’ll be easier to follow if you separate the two apps clearly and explain your contribution to each with a quick “what” and “why it mattered.”

·       Show the impact: What was the result of your work? Did your component improve usability? Did the HR tool make internal processes smoother? Add just a sentence or two to demonstrate the outcome or benefit.

·       Clarify your ownership: Use stronger language like “I was responsible for...” or “I led the development of...” to emphasize your role and initiative.

Suggested Version (More Comprehensive & Client-Focused):

“In my last project, I worked with StackOn to develop two applications simultaneously. The first was a public job vacancy site, and the second was an internal HR and project management tool.

For the job site, I was responsible for building the landing page, job detail views, and the application progress tracker. These components helped users easily search for jobs and stay updated on their application status, improving user engagement.

For the internal app, I created dynamic data tables and detail views to help HR manage employee and project data more efficiently.

Both applications were built using React.js, React Router, Redux for state management, and StackTable for data presentation. For authentication, we implemented OpenID via Microsoft’s platform.

This project helped me improve my component architecture skills and work more closely with backend APIs and authentication flows.”

What You Did Well:

·       Realistic example: Highlighting a scheduling and prioritization challenge is relatable, and it shows that you’ve worked under pressure.

·       Team communication: You involved your lead, product owner, and tester — showing good collaboration and communication.

·       Initiative: You broke tasks down and focused on completing smaller chunks first, which is a smart approach.

Suggestions for Improvement:

·       Clarify the story flow: Your points are great but could be structured more clearly using the STAR method (Situation – Task – Action – Result). This makes it easier for the interviewer to follow.

·       Use more confident, polished language: Avoid phrases like “I think it is…” or “because the text is still many.” Clean grammar and phrasing give your answer more impact.

·       Highlight the result: You mentioned overtime, which is honest, but don’t forget to mention the positive outcome — did the feature go live successfully? Was the client satisfied?

Suggested Version (Clearer & More Impactful):

[Situation] “One of the hardest challenges I’ve faced wasn’t technical — it was working under a very tight deadline.

[Task] At the time, we still had many features left to build, and the timeline was short.

[Action] To manage this, (first) I asked my team lead to help me prioritize the tasks based on importance.

• Then, I broke down the larger features into smaller, manageable pieces and started with the highest-priority items. 

• For each completed task, I committed the code as soon as possible so the QA team could begin testing right away.

• I also regularly updated the product owner to keep communication clear.

[As a result,] although we needed to put in some extra hours, we were able to finish the work on time, and the product was delivered as scheduled.

[Reflection] This experience taught me the importance of smart planning, clear communication, and staying calm under pressure.”

What You Did Well:

·       Positive mindset: You clearly stated that you’re confident about joining, which gives a good impression.

·       Self-awareness: You were honest about areas where you have less experience, like BTEC.

·       Growth attitude: Willingness to learn before joining the team is a great way to show commitment.

Suggestions for Improvement:

·       Use stronger language: Instead of “I’m very confident,” try “I’m confident I can contribute from day one” — it shows readiness.

·       Reframe gaps more positively: Rather than saying, “I don’t have experience,” say, “I haven’t used BTEC yet, but I’m already exploring it to hit the ground running.”

·       End with a benefit for the team: Reinforce what you bring to the table, not just what you’ll learn.

Suggested Version (More Confident & Polished):

“I’m confident I can contribute to your team from day one because many of the technical requirements align with my experience, especially in front-end development using React.

While I haven’t worked with BTEC yet, I’ve already started learning about it so I can support the team more effectively.

I’m a fast learner and very motivated to pick up any tools or frameworks that help the project succeed.

With my current skill set and eagerness to grow, I believe I can add strong value to your team.”

What You Did Well:

·       Clear learning steps: Starting with documentation and then building a dummy project is a great approach — it shows that you learn by doing.

·       Hands-on practice: Mentioning local testing and dummy projects shows practical thinking.

Suggestions for Improvement:

·       Add confidence: Show that you’ve done this before with a quick example (“For instance, I learned X this way.”).

·       Clarify the value: Reinforce that your learning helps you ramp up quickly and contribute sooner.

·       Polish grammar and phrasing: Replacing phrases like “search the example of work project” with “find real-world examples on GitHub” will make your answer clearer and more professional.

Suggested Version (Stronger & More Polished):

“When I need to learn a new technology, I usually start by understanding the basics through official documentation or beginner-friendly tutorials.

After understanding the core concepts, I try to apply what I’ve learned by building a small project locally — usually something similar to how the technology is used in real scenarios.

For example, when I wanted to learn React Query, I practiced by connecting it to a dummy API and managing state.

I also explore sample projects on GitHub to see how others structure their code.

This approach helps me learn quickly and apply new technologies effectively in a real project.”

What You Did Well:

·       You communicate under pressure: Asking your lead or product owner for priority tasks shows you're proactive rather than stuck.

·       You're solution-focused: You didn’t panic — you picked up the task and got it done.

Suggestions for Improvement:

·       Make the example clearer and more structured. Right now the timeline and steps feel a bit vague.

·       Use STAR format (Situation–Task–Action–Result) to walk the interviewer through the story.

·       Highlight the result or impact — what happened after you delivered the work? Was the deadline met? Did the PO appreciate your initiative?

Suggested Version (Clearer & More Client-Facing):

“One high-pressure situation I faced was during a project where we had a very tight deadline and too many tasks to complete.

I could see the team was overwhelmed, so I approached the product owner to ask which tasks were highest priority and still unassigned.

Once I got clarity, I volunteered to take one of the most urgent tasks.

I broke it down into smaller steps, delivered it as fast as I could, and updated the team right away so it could be tested early.

Thanks to that, we managed to meet the deadline, and I learned how important clear communication and quick decision-making are during busy times.”

What You Did Well:

·       You show initiative by subscribing to mailing lists and following tech influencers.

·       You focus your learning: You prioritize staying up to date in technologies relevant to your stack like React and JavaScript.

·       You’re honest about your time constraints, which makes the answer relatable and realistic.

Suggestions for Improvement:

·       Frame it with more confidence and structure. Instead of saying you only read for 30–60 mins, reframe that as a focused daily habit.

·       Add a learning goal or example — for instance, mention a tool or trend you’ve learned recently from one of those sources.

·       Show how it benefits your work, not just that you're consuming content.

Suggested Version (More Client-Facing):

“To stay current with trends, I dedicate time daily — usually around 30 to 60 minutes — to follow trusted sources like JavaScript newsletters, YouTube tech channels, and industry experts on Twitter. I focus mostly on React and JavaScript-related updates.

For example, I recently started exploring [React Server Components / Next.js App Router / React Query] after seeing it discussed in a post. I try to apply what I learn in small demo projects or during my tasks at work.

This habit helps me stay confident in applying modern practices to real projects.”