A leader of two years, determined to build products that bring value to consumers. Collaborating with people from clients, stakeholders, and coordinating ideas with sales, marketing, and developers.
Builds products from ideation to release, connecting the dots and aiding developers to come up with proper systems that bring value. Uses methodologies like Agile Scrum and Kanban to build meaningful products.
Discusses with stakeholders to properly assess requirements and build features. Prioritizes features using strategies like MoSCoW and SWOT.
Builds products with foundations based on UX and QA, making sure that products are not only working, but also easy to use despite complexity.
Experience: 1 - 2 years
My team often uses Scrum, Kanban, or Scrumban depending on the project. We usually use Scrum for products already released, and Kanban for things that may need continuous work, like building new products with ideas still coming in from stakeholders.
Experience: 1 - 2 years
I handle ceremonies such as Sprint Reviews, Sprint Retrospectives, Sprint Planning, and Daily Stand ups for my team. I also manage the product backlog, discussing with developers/engineers to determine which tickets can go through and which tickets we'll need to go over a bit more and properly design its required systems
Experience: 1 - 2 years
More often than not, a whole wall of features will be required and it will be difficult to determine which ones will create the most impact. Using strategies like MoSCoW, we're able to determine which features or functions should be prioritized and which ones can come right after. In some cases we use RICE when there are risks involved, usually when there are new tools or technologies that need to be incorporated.
Experience: 1 - 2 years
Started out creating test plans andwriting down test cases for test suites defined in the product breakdown. After learning a bit more about QA, I started integrating usability, reducing user friction and confusion leading to less traffic in support
Experience: 6 months - 1 year
After a while designing products based in specifications, I was called to handle calls with clients and stakeholders to make sure that things are built according to their vision. If somehow the vision would be a bit of a reach, we can come up with compromises. This involves a lot of back and forth with stakeholders and developers, a necessary step to create a product that addresses all the needs and pain points while also remaining feasible and within budget. This also meant creating several demonstration videos and a bit of QA testing to keep stakeholders updated.
Experience: 1 - 2 years
Able to determine what a system needs, from determining what the must-haves are, the type of database that should be used, determining technical areas that need emphasis and improvements, and creating diagrams to understand how features should interact with the system.
Used this momentarily to run UI tests, soecifically functions accessed through the front end. This let's us automate regression tests to make sure things are still working after unit tests, reducing the amount of testing time used up in the process allowing us to focus on even more unit tests.
Onlinejobs.ph "ID Proof" indicates if "they are who they say they are".
It DOES NOT indicate skill level.
ID Proof scores are 0 - 99 with 99 being the best. It is calculated based on dozens of data points.
It's intended to help employers know who they're talking to is real, and not a fake identity.