nostrademons made some excellent points. I agree with him and also will emphasize that it is a wide spectrum. Very few "senior folks" are never interested in t

nostrademons made some excellent points. I agree with him and also will emphasize that it is a wide spectrum. Very few "senior folks" are never interested in the "how" and "what". It is just that you go through a cycle where initially someone else drives a lot of your projects; then you find yourself working independently on many projects. As you pick up more and more projects, you start delegating/helping other people pick up more work. Enabling you to do more things. Now what title you have is a function of your companies internal procedures. If you are new, I would worry more on aggressively just doing more and more projects. Till you feel comfortable going beyond the nitty gritty of programming to the why we take up one project vs the other; technical tradeoffs, business risks etc.