Tell me about yourself.

I’m Rochelle Macatiag, a 25-year-old. I graduated last June 25, 2024 with a Bachelor of Science
degree in Information Technology from Quezon City University. I’m applying for the position of
Social Media Backer. Over the past 2 years, I have been working freelancer as my parttime job
while I was student, it is a remote work, and my role there was focusing on evaluating social
media content, addressing user queries ,social media platforms, and reviewing advertisements.
This experience has enhanced my analytical skills and given me a deep understanding of digital
content and user engagement.

During my On-the-Job Training (OJT), I worked as a chat support agent for Rapidoo PH, it is a
food delivery service. In this role, I was responsible for addressing concerns related to the
application used by riders, I’m assisting them in troubleshooting technical issues to ensure
smooth operations. In this job it helps me to improved my problem-solving skills and
strengthened my dedication to providing great customer support.

One of the significant part of my role at Rapidoo PH was conducting Quality Assurance (QA) for
their app. I explored the app to identify any bugs, errors, or inconsistencies. And I documented
these issues and provided detailed feedback to the development team. I also offered suggestions
for improvements to the app’s functionality and user experience, that contributing to the overall
success of the application.

Additionally, I served as a desktop support technician at Collective Solution Inc. during my OJT.
I was responsible for troubleshooting various hardware and software issues, ensuring that the
technical environment remained efficient and reliable for all users. This experience provided me
with a solid foundation in IT support and further developed my technical expertise.

In my free time, I enjoy playing online games, watching Korean dramas, and reading books.
These activities help me relax and relieve stress, allowing me to maintain a work-life balance.

I actually build and develop my management, creativity, digital marketing, negotiation,

and social media management skills at rapidoo ph.

Strength and weaknesses

For my strength, I think my strength are I am dedicated person, I’m hardworking and I know
how to handle my time.
I was dedicated to finished my study. And for that to happened I need to work hard,
so when I was a student I have work which is the freelance
 and its not included in my resume but I also babysit my cousin so my aunt give me a money for
that.
And aside from that I also take my on the job training so I was a busy person that some people
would think that I don’t have enough time for myself, but I’m actually know how to manage my
time, So I can spend time with friends, family and especially for my self like what I’ve said
earlier my free time is my me time.

And for my weaknesses, I think I am an overthinker and a perfectionist.

This is my weakness, but sometimes it helps me because, as a student before,
I overthink my projects. Like for example, in our capstone project, I always thought about the
best features or functions and the best UI for our system, that caused me a lot of stress.
The capstone project was a crucial part of my college life, so it had to be perfect.
And I keep on thinking of suggestions on how to improve our system. And as a perfectionist,
especially regarding UI design. Since I was part of the frontend team, I was never satisfied with
just "okay output" I wanted it to be the best, so I kept changing the design until I was satisfied
with the results. And It’s quite hard to be like that because for some people they want to settle for
less and I don’t want to be like that. So, I think my weakness also helps me to improve all the
things I want to do.
So those sleepless nights, all the hard work and overthinking were worth it because, we finished
our system, we defended it to the panelists, and received high grades. Well, I don’t want to say
that it happens just because of me, but it happens because of our team collaboration and hard
work.

Where do you see yourself 5 years from now

In five years, I see myself growing both personally and professionally within this company. I aim
to take on increasing responsibilities and contribute significantly to major projects. I hope to
further develop my skills, particularly in quality assurance, and perhaps share my knowledge and
skills with others. I’m committed to continuous learning and look forward to contributing to the
company's success while achieving my career goals.

Why should we hire you?

- My experiences might not be that long however, I believe that my hard work, dedication, my
willingness to learn will help improve and provide an excellence performance for this position.
I am excited about the opportunity to contribute to your company's success and to grow both
personally and professionally within your company.
Why do you want to work from us
Based on my research about your company, I found that you offer remote work or a work-
from-home setup. I think this will greatly benefit employees by eliminating the need for
early morning commutes and allowing for a better work-life balance. Additionally, I am
particularly impressed by the comprehensive support you offer to your employees, which
shows your commitment to their well-being. Experiencing these benefits directly is one of
the key reasons I am eager to join your team. Furthermore, I believe that the flexibility and
support provided by your company will enable me to perform at my best and contribute
meaningfully to your success.

I want to be part of Alorica because the company offers great benefits that really stand out to me.
And I want to experience those benefits.

The variety of accounts available, non-voice, and easy accounts, means I can find work that suits
my skills.

Overall, alorica a place where I can grow professionally and personally. I am excited about the
opportunity to work at Metacom and be part of a company that values and supports its
employees.

Why did you not pursue your degree:

- As a fresh graduate in the IT Field the salary is a bit low and they are demanding with regards
to the skills and qualifications, that is why I decided to transition as a customer service instead
since BPO is one of the industry that is also indemand right now. I am always curious about
working in a BPO company that is why I wanted to try and see it for myself.

What is your Long term goal?

- In five years, I want to see myself as a trainer in this company so that I can share my learnings
and experiences to those newly hired like me at the moment.

What is your short term goal?

- To be hired or get this job at your company.
How do you handle stress/pressure?
- I handle stress/pressure by maintaining compose and being calm to focus and analyze things
first and organize my thoughts to be more productive.

WHAT IS CUSTOMER SERVICE?

- Customer service is providing assistance to the customers by giving them the informations
relevant to their inqueries and providing the best possible resolution to their concerns.

WHAT IS CUSTOMER SATISFACTION?

- Customer satisfaction is going beyond the customers needs and making sure that the solutions
provided exceeds the customers expectations.

What will you contribute to the company?

- What I can contribute to the company is my dedication to work and my positive outlook in life,
As social media backer, the job is a bit challenging since we are dealing with diverse clients
needs. I believe being dedicated to work helps me give my best everytime I handle customers
query and concerns and my positive outlook in life helps me to always look for the bright side to
think clearly and come up with a resolution so that customers and clients will be satisfied and
happy with our company's services.

- The skills I obtain from my previous work experience along with my technical skills will help
me improve and be the best professional that I can be to perform well in this position.
Technical Interview:
What is Black box testing and white box testing?

Black box testing and white box testing are fundamental approaches to software testing.

Black box testing is the testing of software functionality without examining the internal code. It
focuses on input-output: the tester provides input to the software and checks the output against
the expected results. Black box testing can be performed by testers who do not have knowledge
of programming or the internal workings of the software.

In contrast, white box testing (clear box testing) focuses on the internal structures of an
application. This type of testing examines the internal logic and code structure, concentrating on
the internal workings of the application and requiring knowledge of the internal code.

Functional and non-functional requirements

Functional and non-functional requirements are essential aspects of software development and
quality assurance (QA).

Functional requirements specify what the system should do. They describe the functionalities or
features that the software must provide to users.

Example: for example the in the ordering system, the system should calculate the total cost of
items in a shopping cart.

Non-functional requirements describe the qualities and characteristics of a system. They outline
how the system should perform and behave, focusing on aspects like speed, security, reliability,
and usability, rather than what the system specifically does.
Example: The system should encrypt all sensitive user data as part of the security.

My experience at Rapidoo PH involved manual testing, I explored their application and identified bugs
like Missing Functionality, not user friendly, slow response time and etc. It falls under black box testing.
Because I didn't look at the internal codes. It was all manual, as we didn't use test scripts, we just Google
Forms to document the bugs we encountered and our suggestions for the app's UI. The developers in
the IT department handled the issues. After they fixed and updated the app, they had us test it again.
The app was still in ongoing development and wasn't released on the Play Store yet. Instead, it was
installed directly on our phones by the developers.

The knowledge that I can share is I have experience in black box testing so I have idea how it’s done and
in our capstone project I am part of the programming team, frontend to be specific and I know basic
backend parts so it is easy for me also to understand how to execute white box testing since I can read
codes, pathing and etc.

1. Test Plan

 A document outlining the scope, approach, resources, and schedule of intended test
activities. It identifies test items, features to be tested, testing tasks, and who will perform
each task.

2. Test Case

 A set of conditions or variables used to determine if a system under test satisfies

requirements and works correctly. It includes inputs, execution conditions, and expected
results.

3. Test Suite

 A collection of test cases that are intended to be executed together to test a particular
component or system.

4. Test Script

 A set of instructions executed by a testing tool or tester to verify a certain functionality or

aspect of the system.

5. Bug/Defect

 An error, flaw, or fault in a software program that causes it to produce incorrect or

unexpected results, or to behave in unintended ways.

6. Regression Testing

 A type of software testing that ensures that recent code changes have not adversely
affected existing features. It involves re-running previously completed tests to verify that
existing functionality works as intended.

7. Smoke Testing

 A preliminary test to reveal simple failures severe enough to reject a software release. It’s
often referred to as "build verification testing."

8. Sanity Testing
  A subset of regression testing, sanity testing is performed to verify that a specific section
of the application is still working after a minor change or bug fix.

9. Exploratory Testing

 A type of testing where test cases are not created in advance but testers check the system
on the fly. They may note down ideas about what to test before test execution, but the
testing itself is exploratory.

10. User Acceptance Testing (UAT)

 The final phase of testing before software is released to the market or to production. It is
conducted to ensure that the system meets the business requirements and is ready for use
by end-users.

11. Automated Testing

 Using automated tools to execute tests. It involves writing scripts and using software to
perform tests that would otherwise be done manually.

12. Manual Testing

 The process of manually testing software for defects. Testers execute test cases without
the use of any automated tools.

13. Load Testing

 A type of performance testing conducted to understand the behavior of the system under
a specific expected load.

14. Stress Testing

 A type of performance testing used to evaluate a system beyond the limits of its specified
requirements to determine how it reacts under extreme conditions.

15. Performance Testing

 Testing conducted to evaluate the compliance of a system or component with specified

performance requirements. It can include load testing, stress testing, and scalability
testing.

16. Integration Testing

  Testing in which individual software modules are combined and tested as a group. It aims
to expose defects in the interfaces and interaction between integrated components or
systems.

17. Unit Testing

 Testing individual units or components of a software. It typically involves testing a single

function or method to ensure it behaves as expected.

18. Beta Testing

 The testing performed by real users of the software application in a real environment. It
occurs after the alpha testing phase.

19. Alpha Testing

 Testing conducted by internal staff before releasing the product to external testers or the
public. It is typically the first phase of testing after the initial development is complete.

20. Continuous Integration (CI)

 A practice in software engineering where code changes are automatically tested and
merged into the main branch frequently. It involves automated build and test processes.

21. Continuous Deployment (CD)

 An extension of continuous integration where code changes are automatically deployed

to production environments after passing automated tests.

22. Test Coverage

 A measure used to describe the extent to which the code of a program is tested by a
particular test suite.

23. Mocking

 A technique used in unit testing where external dependencies are replaced with mock
objects to isolate the behavior of the tested unit.

24. Acceptance Criteria

 Conditions that a software product must satisfy to be accepted by a user, customer, or

other stakeholders.

25. Verification and Validation (V&V)

 Verification: Ensuring the product is built correctly, checking if the software conforms to
specifications.
 Validation: Ensuring the right product is built, checking if the software meets the needs
and requirements of the user.