If you’re a senior engineer, then you should have a team of juniors doing most of the coding. Your job is to architect, peer review, meet with stakeholders, etc… At least that has been my experience. Unless you are on one of those small teams with all senior engineers and then you have to do all of the above, and the coding too. I’ve had that experience as well.
If you’re a senior engineer, then you should have a team of juniors doing most of the coding. Your job is to architect, peer review, meet with stakeholders, etc… At least that has been my experience. Unless you are on one of those small teams with all senior engineers and then you have to do all of the above, and the coding too. I’ve had that experience as well.
small team with inexperienced new people that needed a lot of training and we also had “architect” positions and those guys I would never even see or talk to, they were in their own realm somewhere isolated from the actual work. what you are describing was more like the “principal” engineer and we had one of those and he was mostly only doing meetings and occasionally doing some work when the itch struck him sufficiently
If you’re a senior engineer, then you should have a team of juniors doing most of the coding. Your job is to architect, peer review, meet with stakeholders, etc… At least that has been my experience. Unless you are on one of those small teams with all senior engineers and then you have to do all of the above, and the coding too. I’ve had that experience as well.
small team with inexperienced new people that needed a lot of training and we also had “architect” positions and those guys I would never even see or talk to, they were in their own realm somewhere isolated from the actual work. what you are describing was more like the “principal” engineer and we had one of those and he was mostly only doing meetings and occasionally doing some work when the itch struck him sufficiently