Skip to content

Latest commit

 

History

History
55 lines (39 loc) · 2.48 KB

InterviewTip.md

File metadata and controls

55 lines (39 loc) · 2.48 KB

STAR

Situation: situation you were in, or the task that you needed to accomplish

Task: what goal were you working toward?

Action: actions you took to address the situation. keep the focus on you avoid use the word "We", use the word "I".

Result: describe the outcome of your actions, how did the event end. What did you learn.

  1. UI Design Story
  • One tool is very old, not support new technology, keep it running spent a lot of money from buisness.
  • Build a UI for replacing the old tool, migrate the data
  • Gather requirements, build the UI, review with users, improve the look feel and functions.
    • You don't have to meet all the requirements.
    • When you replace the old tool, make sure understand how user use it before.
    • Don't try to make a perfect delivery first time, provide something small simple, and extend on that.
  1. Data migration for CORE
  • An old database, has a lot of network data. 30+ teams run queries pull data everyday. super slow, leadership want to provide better way for downstream consumers.
  • migrate data, let our team become the source of the truth.
  • Build ETL jobs to run query against DB, and prepare the s3 files for other system.
    • Need very careful monitor the job.
    • add email notification, split team member to on call, have standard operation procedure when job fail
    • add data validation, size, type and etc.
  1. Customer support after CORE live.
  • Data issue, user not familiar with new tool

  1. AP stacking issue.(bias for action) Feature is in production, people can create AP on top of another AP. Task: Data is incorrect, need to fix it. Actions: 1. work on the code, take long time. 2. work on db, quickly update. Result: split team, follow a procedure update db, make copy, write update time, user. another team work on the code.

  2. Missing Nodes/Duplicate Nodes issue

  3. (incomplete info at the begin)Data incorrect for downstream system(node Housing). need the field to correlate the roll truck to the field.

  4. Repeat UI data and causing db doc size over 30 MB

  5. CRD Tool that no one use.

    • Engineer spend long time to prepare a config and a lot of manual work
    • Build tools to easy this process.
    • Work with data expert, build UI/API
    • A tool user use everyday.
    • Spend weeks build the tool, but no one use it.
    • Get support from leadership, work with engineers, add more functions they need essentially.

  6. PMA

https://www.amazon.jobs/en/landing_pages/in-person-interview