It's going to take you a while to learn the architecture of your company, and you will probably not learn all of it. It can take months to learn how even a simp

It's going to take you a while to learn the architecture of your company, and you will probably not learn all of it. It can take months to learn how even a simple distributed system works. My suggestion is to do the work that they throw your way. You will most likely be working in a small area of the architecture (for example WebServices). Learn your small bit of architecture first, and become an expert on it. You will naturally start learning about other pieces of the architecture through your own (if you are building Services you will learn about where you are getting your data, etc). However, don't be complacent, force yourself to learn the pieces of architecture that connect to your piece, and move in a direction that makes sense for you. If you are starting out building services and want to do more front-end work, learn about the rendering stack, etc that is consuming your service. If you're more interested in the back-end, start learning whatever database you are consuming in your services really well. As you grow in the company you should constantly do this. Once you become more of a value than a liability in one area move onto the next. This process should take months, if not years, so be patient and give yourself grace.