#How to tell good story
21 messages · Page 1 of 1 (latest)
That is an overview of what you do, but what are the specific, short situations that come to mind?
for a behavioral interview or just in general?
if it’s for a behavioral, go through the top 25-50 questions, and write down your answer for each of them. Then go back through them and try to improve the answer
might take awhile tho, just thought of it off the top of my head
there's the whole STAR method
but i think in general it's like
you probably don't have an issue doing this with something you're interested in and/or when talking to a close friend right
Only STAR wont help, it should have good base as well
Time constraint, lack of automated dev workflow, legacy codebase without testing
More specific, any day when something different happened
different like? production issue? incidents?
sure, whatever comes to mind
The point about STAR is that you need something that you did and that had a visible result. These are just the overall situation you were in, but what did you do about it
hmm ill think about it
Lets say i found that X Database enterprise is costing 200k annually and migrated to DB Y which had inhouse support so I need to redesign models/schemas and migrate
this led to saving cost 200k which is result
That's a great result. It sounds you took the initiative as well. What sort of communication and coordination was required to make that change? Did you have to convince anyone?