In this episode, Dave and Jamison answer these questions:

1. My company recently had a big layoff - about 40% of engineers are gone. My job is safe (for now). About 6 months ago, I was promoted to a “Staff”-ish position that I’ve been really enjoying and looks great on my resume if I hold it for a good length of time.

   Besides just enjoying my job, I’ve just moved house and I have a baby on the way, so I’m highly motivated to have some stability (and get paid parental leave.)

   My gut says give it the 9 months to see how it all plays out - but my brain thinks my gut is an idiot. Interviewing while taking care of a newborn for the first time feels like an incredibly difficult thing to do and the job market may not be getting better.

   Do you have any advice for how to navigate this situation?

2. Big fan of the pod! How should I approach being slightly younger than my peers at the workplace? I graduate in December with my bachelor’s in CS but just turned 18 a couple of months ago. I’m actively interviewing at big tech companies and plan to start working as soon as I graduate. Should I avoid the topic or would it be completely inconsequential for my peers to be aware of my age? I’m looking to move up the ranks quickly, and can imagine many developers wouldn’t love knowing their manager is in their early 20s. For what it’s worth as well, I haven’t been open about being slightly younger in my university setting, as early on I noticed professors didn’t respect my contributions as much when they were aware of my age. What’s your take?

In this episode, Dave and Jamison answer these questions:

1. Listener ninjamonkey says,

   I am a new grad who is half a year into the role now at a very large company. Recently, a senior engineer on my team asked me to create a ticket for an infra team for a problem with a service. I provided logs and steps to reproduce the issue and did a health check before submitting.

   Right after, the manager of the team put me into a group chat with their team, asked why I created the ticket and told me to start doing my job and they can’t debug for me.

   From these interactions and comments on the ticket, it feels the infra team will likely not work on the tickets I report or de-prioritize them. This has left me discouraged and hesitant.

   I will have to do lots of this kind of infrastructure work in the future. Additionally, one of the goals my manager set for me is to work with more external teams for the upcoming year.

   What do I do here? Do I tell my manager about these interactions? Do I tell my team lead, staff/seniors to swap out for different kind of story?

2. I work for a small startup. I was the first employee other than the 2 founders.

   Being the first developer hired, naturally means I have the most knowledge about our application. I also have good organisational skills, which has led to me becoming and being referred to as the “Lead Developer”.

   I have recruited 2 of the 3 new developers, and have trained both of them and got them up to speed.

   At first I was pleased with the progression and was keen to grow into the position, and told the founders so.

   Since then, I have changed my mind, I don’t want to be the lead - due to the following:

   • The communication is absolutely pitiful. Any questions we ask of the founders we get about a 30% reply rate no matter the form of communication.
   • We get poorly defined tasks and requirements
   • The CTO will just blast through some of our features over the weekend and say here I fixed it for you

   I don’t want to quit my job (just yet… its a comin though).

   I have actually discussed the above points with them, but I know these 2 founders will never change their ways.

   How do I tell them I just want to go back to being an Individual Contributor like my Employment contract states?

In this episode, Dave and Jamison answer these questions:

1. Dan asks,

   Hey friends! How do you get ahead when your manager gives you mixed signals? I was told there would be lots of opportunities to work on exciting new projects when I interviewed for this role. After six months this hasn’t really happened and I’m beginning to get concerned it never will. Half the team is working on ‘new things’ while the rest of us are working on maintenance work. This is meant to be rotated but my colleagues tell me this isn’t the case. I’ve asked my manager in our one on ones if I can work on the next piece of new work but have got some odd responses. They told me if I want to work on better projects I should look in my managers calendar and invite myself to anything that looks good. This seems bizarre. Is it normal to lurk your managers calendar and just turn up at meetings that ‘look good’?

2. I’ve worked at small but mature companies for about 3 years now, and I feel that I’m soon coming to the point where you would expect me to be a senior engineer given my years of experience (which I’m aiming for!). I’ve struggled a lot to come up with ideas to add value to the team outside of the standard sprint tickets. I know these things aren’t “required” in the job scope, but often with teams at smaller companies, I worry my manager might think I’m not ready for a senior role if I’m not actively thinking outside the box about the team’s goals beyond the tickets I’ve been assigned.

   I do have a lot of initiative and independence, but the thing is I’m just not very creative. As much as I love tech, it’s difficult for me to dream of non-trivial ideas that would actually make an impact. I feel that if I want to progress in my career, I’m going to have to get better at seeing the bigger picture. What tips might you have?