|
|
|
|
|
|
by PortleyFool
1209 days ago
|
|
|
Option A - You take the job in 2024 and put off the Masters. Option B - You start your Masters and put off work until 2025. When I was in your position years ago I took situation B, but before doing that I had good reason to believe I had a job lined up that was interested in the MS. My main reason for choosing B was I felt I’d never have the time to do a masters full time once I entered the job force, and I wanted do have a degree that distinguished myself. All of that worked out fine for me and I have a good job now. However, looking back I would choose Option A. I didn’t learn a lot of new things from my Masters because there was so much overlap with my undergraduate degree. I would have appreciated it more as a part time program later in my career when I had more experience. Also, it took me 5 years to catch up with the salaries my friends who didn’t take the pause were making. I’d recommend taking the job, work for 5 years then revisit the masters. |
|
|
Worth exploring the opportunity cost in a bit more detail.
One possible trajectory is to get a junior permie SWE job on some commercial project, spend a few years learning the ropes, switch to a different org and a different project, get a better salary while learning a bunch new stuff from the new project context, then enter the wonderful world of daily contract rates. It seems very plausible to be making the median SWE daily contract rate (£600) [1] as a contractor after 5 years of relevant commercial experience, one could probably do this even faster if working toward this was a goal, with a little luck.
Suppose you bill 45 weeks per year, 5 days per week as a contractor, with a daily rate of £600 - that's an income of £135k. Money isn't everything, and life isn't a race, but what's the opportunity cost to delay earning good money by pausing a year or so to accrue additional academic credentials?
Another possible trajectory is to start climbing the leadership ladder, towards a technical leadership role, or perhaps sideways to a management role. Doing this likely requires more time spent working in the same organisation, to be internally promoted into one of these roles without having prior experience. For this trajectory, getting some non CS / non-SWE training might be more valuable (MBA?).
[1] https://www.itjobswatch.co.uk/contracts/uk/software%20engine...