Going into a tech company after retail is a bizarre experience. I remember asking where I had to clock in when I started on my first day at Udemy. (I was laughed at, though not unkindly. It was more of a “silly Robbin, that’s not how it works” kind of way.) I majored in psychology and Japanese in college with a minor in education, so I had no background in anything remotely useful when it came to helping a business. I did, however, have a background in classroom education and in selling reading material. If you read part 1, you’ll know that the first lesson I learned was that I should never stop learning. I didn’t need a my job to tell me that, but I took this to heart and dove in whenever my boss asked if I knew how to do something.
Here are some of the three-letter terms I learned on the job, which at first left me feeling scared stiff because I thought it was some kind of secret code:
- KPI: key performance indicator (or, the “how are you going to show me that your project/change/solution actually did anything” variable)
- ROI: return on investment (or, “did that KPI make/save us any money?”)
- SQL: structured query language — what is being referred to when someone asks for a query built by your friendly backend and/or data team, depending on how big the company is (or, “everyone seems to know how to do this data code thing to measure KPIs for ROIs so I guess I should learn it too”)