1. Sample questions

1.1. Tell me example when you get a touch feedbacks

1.2. Tell me example when to failed to meet commitment you promised

2. Topics

2.1. Bias for action

1. Took swift action to resolve problem: qucikly assembled a reponse team, indentified root cause => implement temporary work-around to minimize downtime => communicate with customer to manage expectations.

2. Taking immediate action led significant improvement (Note): discover a major quaility issue close in the launch date => decide halt the production line and relocate resources to address the issue immediately => correct the problem and meet quality standards.

3. Priority tasks with multiple urgent issues: using matrix to categorize each issue based on potential consequences and required response time => address highest-priority items first while delegating or scheduling lower-priority taks later.

4. Made decision with limited information: choose alternative vendor => And it work.

5. Balance need of quick action and potential risks: Assesing as much relevant information as possible => consult with key skateholders and consider possible scenarios => migrate risks and ensure the actions taken both timely and well-considered.

6. Act quickly to seize business opportunity: to find the feature above the competitors.

7. Encourage team to take immedate action: live new features and outlining a clear rollback plan and benefits of user feedbacks.

8. Quick decision still aligned with long-term goals: strategic objective and used them for decision-making => invole key stakeholders in decision process to gain different perspectives => balancing immediate action with strategic vision

9. Delay led to negative consequences (Note): delay to address critical bugs => led to user complains and negative impact on customer satisfaction => took immediately to fix it and implementing a testing process => communicate transparency about the resolution to restore trust and improve our support processes.

10. Manage pressure of quick decisions: Focus on the facts and prioritize clear communication => establish process + my experience to guide decision-making => make informed decisions while remaining effective.

11. Taking action before all the answer is necessary

12. Taking initiative and acting quickly: setting clear expectation and rewards for members who make decisive action => provide training on problem-solving and decision-making skills => create environment when quick, thoughful actions are valued.

13. Quick decision that was initial unpopular: I made the quick decision to reallocate funds from one department to another to address an urgent need => analyze what decision would benefits in the long-term => affect departments.

14. Evaluate potential impact of the decision when making decision: most critial factors and potential outcomes => consider short-term and long-term effects, relevant skateholders => to inform my decision.

15. Turn quick decision into strategic advantage

2.2. Deliver result

1. Deliver project successfully under a tight deadline (Note):

2. Face significant obstacles but still achieve your goals:

3. Ensure you meet or exceed your targets:

4. Deliver results with limited resources:

5. Handle when you do not meet your goals: research + action.

6. Manage competing priorities to achieve results:

7. Motivate your team to achieve challenging objectives:

8. Measure success of project or initiative:

9. Pivot your strategy to deliver results:

10. Align with team or department to achieve common goals:

11. Priority tasks when working in multiple projects (Note):

12. Exceed the performance targets:

13. Stay focused and maintain momentum when working towards long-term goals:

14. Deliver results in high-pressure situation:

15. Ensure quality when working aggressive deadlines:

2.3. Learn and be curious

1. Seek out new knowledge to improve work performance: online course to learn data science and AI, apply new methods to our analytic processes.

2. Curiousity to discover a problem that others overlook: Curiousity led me dive deeper into our support ticket data => find opporunities and patterns to improve the feature.

3. Stay current with developments in industry: reading industry journals + attending webinars + participaing professional networks => follow thought leaders on social media and online forums to exchange ideas and insights.

4. Learn outside comfort zone: Used a new project management tool => learn the software through tutorials and practice.

5. Approach to learn topic or technology you unfamiliar with: break the topic into managable parts, used online courses, articles, specific learning goals and regularly practical application and discussions with colleagues.

6. Curiousity to solve complex problem: Explore native supply chain models and technologies => reduced costs by 15%.

7. Learn different department: understand marketing in product development => shadowed a colleague in the marketing department for a few weeks => the valuable insights about how marketing strategies are formulated and how they influence the product features.

8. Encouter problem don’t know how to solve: Gather as much as information as possible to understand context => seek advice from colleagues and experts => research potential solutions to test them with real projects.

9. Willing to learn new idea and innovation: learn about new automation tools => Have an idea to build a chatbot to handle common queries => significantly improving overall customer satisfaction.

10. Encourage learning and curiosity in team: Host a sharing sessions between members of the team + learning sessions, workshops + encourage team members to pursure courses or certifications.

11. Learn from failure and mistake: missed key deadlines due to lack of through learning and underestimate => reflect on experience + took a course in project management skills => apply to future projects, leading to more accurate planning and successful project completion.

12. Learn with career goals: review and reflect my career goals => identify skills and knowledge gaps that could hinde my progress => seeking out learning opportunities => target approach ensure my learning contribute to my career goals.

13. Discover new tool for team’s efficiency: new project management tool => research its benefits + introduced it to my team + led the training sessions => improved tasks visibility and enhance collaboration.

14. Balance need to continuous learning with responsibility: Integrating learning into my daily routine => Allocate specific times for professional development (regular schedule) + apply new knowledge into my work.

15. Help other learn and grow: many members were struggling with new software tool => training sessions and comprehensive guide to help them use to tool effectively.

2.4. Dive deep

1. Investigate a complex issues:

2. Attention to details:

3. Gather and analyza data:

4. Understand the process or system in detail to improve it (Hay):

5. Solve a problem with limited information: focus on previous data => to propose a feature.

6. Deep understanding of a subject to significant improvement or innovation:

7. Show analysis and finding is accuracy and reliable:

8. Dive deep customer feedback to address concern:

9. Prioritize which areas to investigate when solving complex problem: most critical factors where issues most likely to occur.

10. Challenge existing assumption:

11. Not missing details when analyze data:

12. Deep analysis the root cause:

13. Keep update with latest trends and best practices:

14. Used deep knowledge of the process to implement successful change:

15. Communicate complex findings with non-tech skateholders:

2.5. Earn trust

1. Build trust with new team and skateholder: priority each member’s strengths and chllenges => one-to-one meeting to listen their concerns and offered support where needed => transparent goals and consistently following thorugh on my commitments => buit trust and established environment.

2. Build trust after a mistake (Note): Delay a project => Take immediately responsibility and communicated openly with team about the mistake => proposed a revised timeline and worked extra hour to correct the issue => rebuild trust and learned from experience.

3. Transparent and honest when communicate with team: providing clear and regulate updates on project status => encourage open dialogue and make my self available for questions and feedback.

4. Handle conflict and disagree to maintained trust (Note): resource allocation => faciliate a meeting where everyone could voice their concerns and proposed a compromise that address key issues and both sides => listen to maintain trust and help them reach mutually agreeable solution.

5. Deliver feedback while maintaining trust (Note): feedback are constructive + offer actionable suggestion for improvement.

6. Gain trust of a skeptical skateholder: understand their concerns + provide clear updates => meeting deadlines and address their feedback promptly.

7. Demonstrate reliability and follow-through: communicate any potential issues + work to resolve them before impace the project => track record and being accountable => build + reinforce trust with my colleagues and skateholders.

8. Honest and problem or limitation

9. Build trust with member with different working styles or perspectives (Note): Open communication + collaboration => find common ground when possible => build mutual trust and respect.

10. Handle situation where to make touch decision affect your team (Note): reduce team size due to budget cuts => offer support to affect team member work to redistribute responsibility fairly.

11. Building trust with clients and customers: deliver on time and match with their expectations.

12. Collborate with others to achieve a goal:

13. Stay transparent and trustworthy even high-pressure

14. Help other to build trust within a team: help them to understand the team dynamics => improve communication and collaboration => using contribution to show and build trust.

15. Ensure actions align with values and priciples of business (Note)

2.6. Ownership

1. Do the job outside the scopes: see the customer feedback loop was inefficient => colab with customer service team to gather more insights => reduce time to implement customer-driven changes 30%.

2. Find improvement in team: code review prcess was slowing down the release of the feature => propose new scheduled pairing junior and senior ones => introduced automated tools to catch baisc errors before code reviews => led to 20% faster release cycle.

3. Balance taking ownership and empowering team members: leading by example, made it clear that they had full responsibility for their tasks but I was always available for support => each team member contributing significantly to the outcome.

4. Make decision long-term impact: whether invest new automation technology to warehouse => The initial cost was high, but I took ownership of decision for cost-benefit analysis, and potential ROI => After next year, operational efficientcy increased 40%.

5. Take ownership of a mistake, handle and learn from it: approved a discount that led a loss on a major contract => take ownership, inform my manager, propose a solutuon => work closely with finance team to offset the loss of selling and cross-selling opportuinites => lesson to double-checking approvals and value of transparent communication.

6. Ownership principles: take full reponsibility to outcomes of my work and thinking about long-term impact => See the customer retention rates were dropping => rather than waiting for instructions => identify the key pain points, developed strategy to improve customer engagement and follow-up questions => increase 15% over the next quarter.

7. Motivated to take ownership, even the task are challenging and outside of comfort zone: focus on big picture and the impact of my work to company and its customers => take new challenge because of the company’s growth => commit to learn quicky, seeking advice from experts, focus on the end goal => grow professionally and contribule meaningfully.

8. Take ownership that other avoids: disruption from key supplier failing to deliver materials on time => contact alternative supplier + negotiateed deliver terms + coordinated with logistic teams to minimize delay => avoid production downtime.

9. Take ownership that limited resources: low cost => focus more on high-impact, low-cost strategy => engaging with influencers to creating compelling content to our target audience => exceed the sales target.

10. Take ownership for process was not working efficiently: Ticket resolution time was longer than it should be => took ownership to analyzing workflow and identify bottlenecks => implement new system + weekly training sessions to improve team’s problem-solving skills => lead to 25% reduction in resolution time.

11. Take ownership for project that failed: develop a feature that do not resonate for the users => gatering feedback, conduct though post-mortem analysis, present my finding to the team => learned to involving customers earlier in development process => validate ideas before investing heavily in them.

12. Take ownership for project that require cross-functional collaboration: launching new internal tool that required input from multiple departments, including IT, HR, Finance => setting up cross-functional meeting + clear communicaiton + align everyone to project goals => launch the tool on time within budget.

13. Take ownership for project that you disagree with the direction provided by your superiors: disagree with short-term approach for a critical project, because in long-term strategy would better serve our customers => Ownership by resarch and present data-drivent alternative + communicate findings to my supervisor + framing my feedback through overall success rather than personal preference => Took full ownership for its implementation, developed an action plan, coordinated with team to keep the project stayed on track => sustainable and successful outcome.

Notes: If you want to details, describe the name of the project in the first + output metrics in the ends.

1. Take ownership for project that you are limited information: major marketing cmapaign without market research => gathering all information from relevant skateholders, including the sales and finance teams => weighted the potential risks and benefits => test key elements on smaller scale but fully commiting => launch successful and strong ROI => make complex decision and manage uncertain effectively.

2. Take ownership for project that noticed a process inefficiency: onboarding process for new employees is time-comsuming => conduct analysis of the current project => proposed a streamlined onboading program and automating several administrative tasks => implement changes, colloborated with HR to update training materials + feedback loops to improve the process => The onboarding time reduced 40%, our new employees were granted more quickly.

3. Reflection

1. Receive feedback from EM to design and implement onelink.

2. Do not testing deploy service to production => cause restart service + dump 1 billions of log in production.

3. Request SSH to log to query data and do analytic and process jobs.

4. Hot fix incendent the downtime of CDN internal => cause fund loss, and redis is out of mem and read to DB in Tet holiday.

5. Receive feedback from manager to build internal tools but very difficult to use for operation team.

6. Build template boilerplate code including file script integrate with BOM + CI/CD services for other team members to reuse.

7. Priority task for campaign of company to match with “Scan with Miss Universe” of company.

8. Query number of authorize member of marketing content in website to reconcile with office.

9. Consoliate 3 mini apps to 1 tool so that reduce cost and operation cost.

10. Design custom dashboard for fraud detection onelink.

11. Autofill mini app in config, download mini app config in tool, monitoring mini app trends.

12. Write documents and guidelines support.

13. DDoS + onelink can not load in platform.

14. Dive deep in mobile code, trace log to find issues => deep dive.

15. Explain for non-tech members.