Solving problems has always been a driving force in how I've chosen to spend my time both personally and professionally. Since I was young, I've enjoyed the feeling of solving complex problems. There's really no better feeling than inking in the last number of that 9x9 Sudoku grid, until of course you complete that 15x15 monster grid that once seemed out of reach. The drive to solve more and more complex problems is what initially motivated me to pursue a career as a developer at a start-up. However, I found that as a developer, the problems I solved were at a micro level and the larger problems that impacted everything I worked on were handled at a level above, at the product or program's scope. Lucky for me, start-ups tend to grow fast and me with it. It wasn't long before I had the opportunity to lead the same team I had not so long ago started my new career path in. It was an invaluable experience that taught me the value of investing time in empowering others to better solve their own problems, rather than solving problems for them. This eventually led me to take a role in the Product team, with a focus on education and best practices for internal as well as external users. By enabling an even wider audience to more effectively use the product, I hoped to increase revenue through product adoption and decrease user-error incidents landing in our support queue. Over the past five years, I have moved further from my initial start in hands-on development to be entrusted in taking on larger and larger challenges. I am always looking for that next problem to overcome and am fortunate that I have been able to work on projects that impact change on such important sectors as healthcare.