work-stories
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
work-stories [2022/08/17 15:28] – donpdonp | work-stories [2024/01/31 04:08] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 69: | Line 69: | ||
2. Give me an example of a tough or critical piece of feedback you received. What was it and what did you do about it? | 2. Give me an example of a tough or critical piece of feedback you received. What was it and what did you do about it? | ||
- | * My git commit messages are terse and need more detail. First I review the problem to verify it, went over my old messages. | + | |
** Have backbone, Disagree ** | ** Have backbone, Disagree ** | ||
Line 76: | Line 76: | ||
* Per customer custodial accounts vs one large pot; external circumstances I was unaware of, along the lines of minimum balances to earn interest; would have listened longer custodial partner; we had logs, they had logs. seemed safe enough. | * Per customer custodial accounts vs one large pot; external circumstances I was unaware of, along the lines of minimum balances to earn interest; would have listened longer custodial partner; we had logs, they had logs. seemed safe enough. | ||
- | 2. Describe a time when you took an unpopular stance in a meeting with peers and your leader. What was it? Why did you feel strongly about it? What did you do? What was the outcome? | + | 2. Describe a time when you took an unpopular stance in a meeting with peers and your leader. What was it? |
- | * My manager was pushing for extra hours when the team was already working at capacity. | + | Why did you feel strongly about it? What did you do? What was the outcome? |
- | I knew the team was at capacity beacuse I kept up good relations with my coworkers and | + | * My manager was pushing for extra hours when the team was already working at capacity. |
- | | + | |
- | | + | |
- | ; system design, clarifying questions | ||
** Deliver results ** | ** Deliver results ** | ||
1. Give me an example of a time when you were able to deliver an important project under a tight deadline. What sacrifices did you have to make to meet the deadline? How did they impact the final deliverable? | 1. Give me an example of a time when you were able to deliver an important project under a tight deadline. What sacrifices did you have to make to meet the deadline? How did they impact the final deliverable? | ||
- | * Get the stock balancing service ready by the time API approval was given. | + | |
- | | + | |
- | | + | |
- | | + | |
- | deduced from API market data. this was changed to be a manual data entry by the finance dept. That eliminted | + | |
- | | + | |
- | | + | |
- | = This processed trimmed the final deliverable to mininum viable product. | + | |
2. Tell me about a time when you had significant, | 2. Tell me about a time when you had significant, | ||
- | * In an early crowdfunding project, all the dev effort went into the backend and the website. it was unanticipated | + | |
- | | + | |
- | was decided an iOS app was needed. I was thrown onto iOS dev using Objective-c. The obstancle was defining the | + | |
- | | + | |
- | head start. Knowning what I know now, we would have started earlier on the app. | + | |
** Learn be curious ** | ** Learn be curious ** | ||
1. Tell me about a time when you realized you needed a deeper level of subject matter expertise to do your job well. What did you do about it? What was the outcome? Is there anything you would have done differently? | 1. Tell me about a time when you realized you needed a deeper level of subject matter expertise to do your job well. What did you do about it? What was the outcome? Is there anything you would have done differently? | ||
- | * Location Tracking Node.js project needed asynchronous operations with a node version that was pre-async/ | + | |
2. Describe a time when you took on work outside of your comfort area. How did you identify what you needed to learn to be successful? How did you go about building expertise to meet your goal? Did you meet your goal? | 2. Describe a time when you took on work outside of your comfort area. How did you identify what you needed to learn to be successful? How did you go about building expertise to meet your goal? Did you meet your goal? | ||
- | * Crowdfunding Node.js project, front end needed testing help. I joined that team part time. I knew some javascript and html. I had to learn the particular js framework in use to be helpful and file tickets. | + | |
The result was a higher level of confidence in the product. | The result was a higher level of confidence in the product. | ||
Line 115: | Line 105: | ||
** Dive deep ** | ** Dive deep ** | ||
1. Tell me about a time when you realized you needed a deeper level of subject matter expertise to do your job well. What did you do about it? What was the outcome? Is there anything you would have done differently? | 1. Tell me about a time when you realized you needed a deeper level of subject matter expertise to do your job well. What did you do about it? What was the outcome? Is there anything you would have done differently? | ||
- | * location database. POSTGIS was taking too many resources. storage on-disk and indexes from LMDB. created an index specification schema in json to create these indexes, created an | + | |
api to query any existing index. on startup, consistency check and index rebuild if necessary | api to query any existing index. on startup, consistency check and index rebuild if necessary | ||
2. Describe a time when you took on work outside of your comfort area. How did you identify what you needed to learn to be successful? How did you go about building expertise to meet your goal? Did you meet your goal? | 2. Describe a time when you took on work outside of your comfort area. How did you identify what you needed to learn to be successful? How did you go about building expertise to meet your goal? Did you meet your goal? | ||
- | * Working on a node.js backend, realizing the responses were being processed in a single threaded fashion. The usual solution is to load balance multiple node.js processes, but some kind of central synchronization is still needed, such as redis. Complexity of this implementation started rising and rising. Pivoted to a reimplementation away from node. Something comfortable with multithreaded libs. That excluded python/ | + | |
** Bias for action ** | ** Bias for action ** | ||
1. Give me an example of a calculated risk that you have taken where speed was critical. What was the situation and how did you handle it? What steps did you take to mitigate the risk? What was the outcome? Knowing what you know now, would you have done anything differently? | 1. Give me an example of a calculated risk that you have taken where speed was critical. What was the situation and how did you handle it? What steps did you take to mitigate the risk? What was the outcome? Knowing what you know now, would you have done anything differently? | ||
- | < * Interfacing with an exchange API that was launching v2. We wanted those features so we kept in | + | |
- | < contact with their dev team on their open slack server. The beta documentation helped guide | + | |
- | < our system to be ready for API V2 on day 1 of launch. The risks were implementing something | + | |
- | < in api v2 that wasnt going to happen. Being on the slack mitigated that risk. | + | |
2. Tell me about a time when you worked against tight deadlines and didn't have time to consider all options before making a decision. How much time did you have? What approach did you take? What did you learn from the situation? | 2. Tell me about a time when you worked against tight deadlines and didn't have time to consider all options before making a decision. How much time did you have? What approach did you take? What did you learn from the situation? | ||
- | < * Choosing a cloud platform for launch. There are a lot of options with different features and | + | * Choosing a cloud platform for launch. There are a lot of options with different features and prices. A decision was needed in a few days. To speed up evaluation of different platforms I asked devops people I trusted for their recommendations, |
- | < prices. A decision was needed in a few days. To speed up evaluation of different platforms | + | |
- | < I asked devops people I trusted for their recommendations, | + | |
- | < One was selected that worked out well enough. Later on, more niche platforms were found | + | |
- | < that would have made a better first choice. Now that we're on one cloud, its too expensive | + | |
- | < to move, at least over the short term. | + | |
- | ; data struct | ||
work-stories.1660750089.txt.gz · Last modified: 2024/01/31 04:08 (external edit)