> But my background kept leading hiring managers to suggest putting me on cloud teams doing orchestration in Go around a database rather than working on the database itself.
This is extremely annoying. This also means if your first job is doing X, it is very difficult to break into Y even if you know quite well about Y, and even have side projects. I have tried attaching cover letters indicating even if my current experience is in X, I am quite familiar with Y, to no luck. (No one reads those stuff).
To me it seems like the majority of recruiters barely read past company name and job title.
I switched from Dev to SRE at the same company, and within like one week of remembering to update LinkedIn job title, the random recruiter messages switched from Dev to "oh we are looking for someone like you with lots of SRE experience" (having worked in SRE for <3 months).
So yea, it's difficult to get traction for something that isn't already your job title.
>> the majority of recruiters barely read past company name and job title
This is a failing of the hiring manager. If the recruiter can't tell who is and isn't a good fit, the hiring manager should have corrected the situation or not partnered with the recruiter.
My entire career was switching from one discipline to another.
For me, the key was twofold:
1) Spend a lot of extracurricular (not work) time, exploring new tech that interests me. This often included purchasing expensive kit, and attending classes, on my own dime (but I could usually use the spend in my tax write-offs).
2) Be willing to accept being paid a lot less than my peers.
My career is a fairly eclectic one. I’m now retired, and spend a lot of time learning stuff, which is fun.
This is me to a big extent. Sometimes I feel like I to learn for learning's sake. Which is okay, or at least that is what my therapist tells me. I struggle with the fact that I "think about doing" vs actually doing.
My work is my hobby too, that is why I struggle sometimes wondering if I will ever retire. Why retire when what I'm doing is for the most part fun. Sure, there are days that I'd rather be "doing X", or more like "studying X" than actually working but I'm enjoying work so much lately that it soon passes.
Work also forces me to actually DO instead of thinking about doing. I have to perform. People are depending on me to get stuff done and that is a big motivator. With my personal projects, no one needs it or is expecting it so it is too easy to abandon.
The overwhelming majority of people who work around 40 hours a week have plenty of free time.
"I don't have freetime" is usually a tell sign that people either don't know how to manage their time / prioritize free time activities, or have made choice that they refuse to see as choice but as obligations instead (which implicitely just means they prioritize this activity a lot)
> The overwhelming majority of people who work around 40 hours a week have plenty of free time.
Overwhelming majority? Plenty of people don't make enough from their 40h/w job to pay all their expenses and have to get another job or have to share responsibilities with a working spouse. Having kids or aging parents is also a common demand on ones time.
Yeah. I worked 30 hours/week when I went to undergrad full time for CS. Later I went back to grad school while also working full time. There is a lot of free time in many people's day. I'm also not saying it all has to be productive, I know mine certainly isn't, but it should be deliberate. I love sitting down to watch a movie or play a game, and I hate when I get sucked into some social media for 30 mins or an hour without realizing it.
I find it's easier to prove that within a small company after you're in. You just fix a problem in the area you want to work in, then you fix another problem, and soon after people want you on their team or a team is created around you to fix that class of problem. But lots of engineers just wait to be picked while only doing the stories assigned to them. Or they are in big companies, of which I don't know about.
> I also wanted to cover what it's like coming from engineering management and founding companies to going back to being an individual contributor. (Spoiler: incredibly enjoyable.)
I've done the IC to engineering manager back to IC thing and it is indeed a huge relief to learn that it's OK to do that. My favorite piece of writing on that is The Engineer/Manager Pendulum by Charity Majors: https://charity.wtf/2017/05/11/the-engineer-manager-pendulum...
Charity makes a very convincing case that it's OK to swing from manager to IC and back again several times over the course of your career and that doing so will make you more effective at both of those things.
Watching Eaton's journey online was very inspiring but sadly I have also seen a lot of people doing this to no avail. This is eerily similar to how musicians do busking until they got noticed by a record label.
My experience (as a non-CS person) has been that aside from where there is a very large maths component which might block people without further academic-style study (and I wouldn't necessarily even count ML in that, since the maths needed for much of ML is relatively low level, it's certainly not graduate school level understanding maths), there are relatively few areas of software which have high barriers to entry in actually doing stuff - where the barriers are are people willing to take a risk on letting you have a go. That's usually much much easier once you're in a company than if you're applying for a role from the outside.
Every time I've felt like I didn't understand something and felt overwhelmed at the scale at a task, 3-6 months down the line of throwing myself at the problem and trying to understand it, I've realised it's not as hard and part of the barrier was just the unfamiliar terminology and unfamiliar tools. Sure, there is a degree of needing to learn new stuff - which is true in any job and in life - to do new things. But those barriers are not normally insurmountable. That's been true for me in basically every area. It is also why I'm fairly willing to give people a chance, so long as they are able to demonstrate some knowledge which would be able to transfer.
> I was unhappy with this type-casting so I held out while unemployed and continued to write posts and host virtual hackweeks messing with Postgres and MySQL. I started the first incarnation of the Software Internals Book Club during this time, reading Designing Data Intensive Applications with 5-10 other developers in Bryant Park. During this time I also started the NYC Systems Coffee Club.
I enjoyed reading this. It could be because I'm thinking of doing more of system/network programming (and learning Zig). I've spent the last 6 years in the JavaScript land and bored of yet-another-bundling or SPA-like pattern.
So there's hope that with consistency and patience, one could build expertise in a totally different area
I'm also interested in more low level or systems programming, though I am coming from a mostly backend/system integration background. I feel like a roadblock is that I am self taught, and though I have been doing software engineering professionally for 15 years and software as a job for 20, I still can't call myself an engineer legally. I certainly know I can do the work, but I worry about hiring being wary of a lack of credentials as a legal liability for lower level stuff.
I would love to hear people's stories of interesting jobs they've gotten without a degree in this space.
Depends on the use-case, but if your product is <14 month lifecycle App/shovel-ware, than go JS for the labor compatibility... Yet if you are hitting >40k concurrent users, the options winnow down fairly quickly.
Thanks, it is inspiring, And it seems like I'm on the same way of that transition, Here is my individual expirment database for learning db internals and rust..
On a similar note: I've been listening to various podcasts with Allan Judd for probably more than 10 years now. It's amazing to see someone go from a FreeBSD docs contributor and talented systems administrator to C programmer and ZFS developer.
You have to have serious motivation to not just stay with what you know, but it's a nice kick in the butt to the rest of us to see that it can be done, with you put in the work.
> But my background kept leading hiring managers to suggest putting me on cloud teams doing orchestration in Go around a database rather than working on the database itself.
This is extremely annoying. This also means if your first job is doing X, it is very difficult to break into Y even if you know quite well about Y, and even have side projects. I have tried attaching cover letters indicating even if my current experience is in X, I am quite familiar with Y, to no luck. (No one reads those stuff).
To me it seems like the majority of recruiters barely read past company name and job title.
I switched from Dev to SRE at the same company, and within like one week of remembering to update LinkedIn job title, the random recruiter messages switched from Dev to "oh we are looking for someone like you with lots of SRE experience" (having worked in SRE for <3 months).
So yea, it's difficult to get traction for something that isn't already your job title.
>> the majority of recruiters barely read past company name and job title
This is a failing of the hiring manager. If the recruiter can't tell who is and isn't a good fit, the hiring manager should have corrected the situation or not partnered with the recruiter.
My entire career was switching from one discipline to another.
For me, the key was twofold:
1) Spend a lot of extracurricular (not work) time, exploring new tech that interests me. This often included purchasing expensive kit, and attending classes, on my own dime (but I could usually use the spend in my tax write-offs).
2) Be willing to accept being paid a lot less than my peers.
My career is a fairly eclectic one. I’m now retired, and spend a lot of time learning stuff, which is fun.
How do you have the time to do this? I already barely have free time, let alone time to attend classes
In my case, I'm a bit obsessed. I'm "on the spectrum," and that helps me to concentrate and understand stuff.
Also, I just like doing this stuff. My work is also my hobby. There's not that many things that I'd rather be doing.
I have also had a very good venue for doing volunteer work, and that has always provided a driving force.
Of course, now that I'm retired, I have the time.
This is me to a big extent. Sometimes I feel like I to learn for learning's sake. Which is okay, or at least that is what my therapist tells me. I struggle with the fact that I "think about doing" vs actually doing.
My work is my hobby too, that is why I struggle sometimes wondering if I will ever retire. Why retire when what I'm doing is for the most part fun. Sure, there are days that I'd rather be "doing X", or more like "studying X" than actually working but I'm enjoying work so much lately that it soon passes.
Work also forces me to actually DO instead of thinking about doing. I have to perform. People are depending on me to get stuff done and that is a big motivator. With my personal projects, no one needs it or is expecting it so it is too easy to abandon.
> With my personal projects, no one needs it or is expecting it so it is too easy to abandon.
In my case, I was fortunate to have projects that people depend on. Even my "hobby" work has always shipped.
The overwhelming majority of people who work around 40 hours a week have plenty of free time.
"I don't have freetime" is usually a tell sign that people either don't know how to manage their time / prioritize free time activities, or have made choice that they refuse to see as choice but as obligations instead (which implicitely just means they prioritize this activity a lot)
> The overwhelming majority of people who work around 40 hours a week have plenty of free time.
Overwhelming majority? Plenty of people don't make enough from their 40h/w job to pay all their expenses and have to get another job or have to share responsibilities with a working spouse. Having kids or aging parents is also a common demand on ones time.
Yeah. I worked 30 hours/week when I went to undergrad full time for CS. Later I went back to grad school while also working full time. There is a lot of free time in many people's day. I'm also not saying it all has to be productive, I know mine certainly isn't, but it should be deliberate. I love sitting down to watch a movie or play a game, and I hate when I get sucked into some social media for 30 mins or an hour without realizing it.
Wild guess: gp is self-employed and can manage their own time. I’m assuming that with some planning you can carve “learning time” across contracts.
No, I always worked for companies.
However, there was never the "996" shit, you see, these days. I generally did about 50 hours per week. Sometimes more; sometimes, less.
Sometimes, if the extracurricular stuff also benefitted my day job, I could get the company to help out, there.
I see, thank you for correcting me!
Is there a way to work around this?
Lie on LinkedIn, get a foot in the door and explain in the interview
references, apply for a company rich enough to fund various projects ( like crypto company, if your moral compass allows ).
I find it's easier to prove that within a small company after you're in. You just fix a problem in the area you want to work in, then you fix another problem, and soon after people want you on their team or a team is created around you to fix that class of problem. But lots of engineers just wait to be picked while only doing the stories assigned to them. Or they are in big companies, of which I don't know about.
> I also wanted to cover what it's like coming from engineering management and founding companies to going back to being an individual contributor. (Spoiler: incredibly enjoyable.)
I've done the IC to engineering manager back to IC thing and it is indeed a huge relief to learn that it's OK to do that. My favorite piece of writing on that is The Engineer/Manager Pendulum by Charity Majors: https://charity.wtf/2017/05/11/the-engineer-manager-pendulum...
Charity makes a very convincing case that it's OK to swing from manager to IC and back again several times over the course of your career and that doing so will make you more effective at both of those things.
>I held out while unemployed
Watching Eaton's journey online was very inspiring but sadly I have also seen a lot of people doing this to no avail. This is eerily similar to how musicians do busking until they got noticed by a record label.
My experience (as a non-CS person) has been that aside from where there is a very large maths component which might block people without further academic-style study (and I wouldn't necessarily even count ML in that, since the maths needed for much of ML is relatively low level, it's certainly not graduate school level understanding maths), there are relatively few areas of software which have high barriers to entry in actually doing stuff - where the barriers are are people willing to take a risk on letting you have a go. That's usually much much easier once you're in a company than if you're applying for a role from the outside.
Every time I've felt like I didn't understand something and felt overwhelmed at the scale at a task, 3-6 months down the line of throwing myself at the problem and trying to understand it, I've realised it's not as hard and part of the barrier was just the unfamiliar terminology and unfamiliar tools. Sure, there is a degree of needing to learn new stuff - which is true in any job and in life - to do new things. But those barriers are not normally insurmountable. That's been true for me in basically every area. It is also why I'm fairly willing to give people a chance, so long as they are able to demonstrate some knowledge which would be able to transfer.
> I was unhappy with this type-casting so I held out while unemployed and continued to write posts and host virtual hackweeks messing with Postgres and MySQL. I started the first incarnation of the Software Internals Book Club during this time, reading Designing Data Intensive Applications with 5-10 other developers in Bryant Park. During this time I also started the NYC Systems Coffee Club.
That's the spirit! And it worked.
I enjoyed reading this. It could be because I'm thinking of doing more of system/network programming (and learning Zig). I've spent the last 6 years in the JavaScript land and bored of yet-another-bundling or SPA-like pattern.
So there's hope that with consistency and patience, one could build expertise in a totally different area
I'm also interested in more low level or systems programming, though I am coming from a mostly backend/system integration background. I feel like a roadblock is that I am self taught, and though I have been doing software engineering professionally for 15 years and software as a job for 20, I still can't call myself an engineer legally. I certainly know I can do the work, but I worry about hiring being wary of a lack of credentials as a legal liability for lower level stuff.
I would love to hear people's stories of interesting jobs they've gotten without a degree in this space.
Same. It’s good to know that other people feel the same way.
There are JS frameworks that port to most platforms in about 3 minutes (use a Mac for iOS builds):
https://quasar.dev/introduction-to-quasar/
That being said, Erlang/Elixir abstracts most db use-cases with ecto, and has some other incredibly powerful scalable features for sites:
https://www.phoenixframework.org/
* Distributed
* Fault-tolerant
* Highly available
* Hot swapping
Depends on the use-case, but if your product is <14 month lifecycle App/shovel-ware, than go JS for the labor compatibility... Yet if you are hitting >40k concurrent users, the options winnow down fairly quickly.
Have fun =3
Thanks, it is inspiring, And it seems like I'm on the same way of that transition, Here is my individual expirment database for learning db internals and rust..
https://github.com/maxnilz/sboxdb
Now, trying to implement a rocksdb-like LSM based storage in modern C++ and call it from the sboxdb, just for refresh my old C++ memory.
On a similar note: I've been listening to various podcasts with Allan Judd for probably more than 10 years now. It's amazing to see someone go from a FreeBSD docs contributor and talented systems administrator to C programmer and ZFS developer.
You have to have serious motivation to not just stay with what you know, but it's a nice kick in the butt to the rest of us to see that it can be done, with you put in the work.
I would like to have this kind of transition to the Compiler world.
It's a fairly easy transition to do, once your bank account is empty you're halfway there.
If you can wrangle CSS, you can probably wrangle SQL pretty well.
Both are declarative ways of traversing graph-like datasets (DOM nodes vs tabular relations).
That is not what "database developer" means in this context.