As staff+ engineers, we're often thrown into the deep end and expected to navigate huge amounts of ambiguity including ambiguity about what our jobs even are. It's common to feel like there's a huge amount of trial and error or even luck. Getting even a little bit of insight from others can be hugely valuable but sometimes hard to come by.
Have you ever wondered if there are things you should know more about but don't?
Curious about what another staff+ engineer thinks about their job or what they focus on?
In this talk, I will go through an admittedly very biased list of things, both technical and not, that I am glad I know, and in some cases, wish that I learned earlier.
I will talk about:
- Service architecture
- Aligning incentives
- Thinking Bigger
Principal Engineer @Split, Blogger, and Speaker, Previously @Box
Joy is a Principal Software Engineer at Split, leading our backend team from a technical perspective. Prior to Split, she worked at Box. At both Split and Box, she has lead efforts around splitting monoliths into microservices, revamping authentication and authorization frameworks, creating REST API standards, audit logging and more. In addition to designing software and writing code, she also maintains a blog: https://medium.com/@jkebertz. In her free time, she does a lot of traveling, reading, and running ridiculously long distances (mostly on trails).