In my current role, I triage bug tickets (console errors -> logs, etc), work with engineers / product people / project managers to catch dropped balls, figure out how stuff works and throw it into documentation, refactor code a bit, turn problems into processes, manage lots of deadlines, and do other stuff like setting up config files / running scripts / fixing my own Python dependency issues (sometimes).Before that, I took a winding path through a few different industries / careers -- I've been a junior software engineer, college administrator, freelance copyeditor / proofreader, and barista. As such, my eclectic collection of professional skills now includes: not bumping into people in narrow spaces (food service!), running effective meetings, clearly explaining technical concepts, solidifying vague project requirements (aka asking too many questions), fast / messy / accurate Excel data analysis and Python scripts, catching items that fall off tables (food service!), seeing problems from multiple teams' perspectives, turning unknown unknowns into known unknowns, creating mental models of projects / situations / systems to determine what will go wrong in the future if events remain unchanged (this one is not always popular), and finding preemptive solutions for these future problems (this one is marginally more popular).The book that's shaped my working style the most is Thinking in Systems by Donella Meadows. You should read it.