
Episode 201: Too soon for a raise and management, masters, maybe?
About this episode
In this episode, Dave and Jamison answer these questions:
-
I started a new job 6 months back and a lot has happened since then. I signed on as a junior dev and have since been given more and more responsibility. Including (but not limited to) deploying and releasing after hours, shared responsibility with the resident senior devs for reviewing pull requests, and aiding in the creation of new processes and overall advancement of our company’s software development process and culture. How soon is too soon to ask for a raise after starting a new job?
-
Listener Andrew asks,
As a military veteran of 8 years, I have the opportunity to enroll in a masters program for little to no cost, but I’m not sure what kind of program to choose. I’m a web developer and also serve as my team’s ”Agile Owner” (kind of like a Scrum Master) which I really enjoy. In fact, before I got my first dev job, I trained in Scrum to try to get a leadership role in the software industry and use my bachelor’s in engineering management. It seems logical to continue in that vein and choose an engineering management masters program, but I enjoy being a direct contributor and applying my Agile training without any real responsibility as a manager would have. I sometimes think I should go for a masters in computer science and double down as a technical knowledge worker, but I fear I’d be in way over my head since I don’t have an institutional computer science background. On the opposite end of the spectrum, part of me thinks I should get an MBA like some friends from college to hedge my bets for climbing corporate ladders in the future. On top of that, lately I’ve been very interested in learning more about design. I’m just not sure what to do, and I have a habit of making big decisions with my head instead of my heart which sometimes leads to 8 years in military service which I don’t much enjoy, so I’d love any advice I can get. Thanks! Soft Skills Eng is my absolute favorite software industry podcast.
Get every episode summarized
Each time Soft Skills Engineering publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Soft Skills Engineering

Episode 529: Zoom calls on my open floor plan and laconic staff engineer
Soft Skills Engineering

Episode 528: Sleepy family software business and leaving after an acquisition
Soft Skills Engineering

Episode 527: I lost my job after 10 years and am I too old to switch to a securi...
Soft Skills Engineering

Episode 526: Why can't I get promoted so quickly after my last promotion and I g...
Soft Skills Engineering