Give me an example of when you were able to anticipate a customer's need with a solution/product they did not know they needed/wanted yet. How did you know they needed this? How did they respond?

類似題目:


Our infrastructure is not fully Continuous Deployment. We are running microservices, and we record the stable commits in the release book and then deploy those at the scheduled release time. When the time comes, the release manager will input those commits into each service’s production release pipeline. I realized that it was very time-consuming and tedious.

Therefore, I made two things that helped our release manager's life easier. One centralized deploy pipeline for all our services. Auto-generated release book that hooks up with the centralized deploy pipeline. Now release manager only needs to click one button after the go/no go meeting.

She was extremely happy and relax. She mentioned that this task always takes her a lot of time and clicks and now she is able to make a release book and deploy with just one click. She can use the extra time to focus on her other tasks. I cut down our release process time from about 45 mins down to under 3 mins.


套用:這個問題的回答就要對CICD持續集成與交付有一定的了解 但是其實總思路就是你因為了什麼原因然後製作出一個工具來減輕同事的負擔 所以不一定要跟CICD有關 你可以把主要思路換成你曾經做過的小工具就可以了

ST: 大致上的介紹每次發布新的部署所需要的流程 我發現這個流程非常的浪費人工

A: 做了哪些事情來改進這一個部份而減輕同事的負擔

R: 同事可以利用省下來的時間來做其它的事,我做的事情也讓原本花費的時間減少許多