Live data from Hacker News

School of SRE: Curriculum for onboarding non-traditional hires and new grads

github.com

31–40 of 73 posts

Re: School of SRE: Curriculum for onboarding non-traditional hires and new grads

#32
post #19
post #7

Earlier quoted context omitted.

You could probably at least get a phone interview if you did...

I don't really understand, how going through this will get you a phone interview? I mean, it doesn't change anything on your resume... Source: I'm a new grad, I went through almost all this, but my application wasn't shortlisted. Not a native speaker, so maybe I just don't understand what you're saying.

My implication is that you either somehow indicate on your resume that you've done all this work, or better yet, take up a small project that lets you apply some of the skills.

As a hiring manager there is no way to know you've done this unless you somehow demonstrate it.

Re: School of SRE: Curriculum for onboarding non-traditional hires and new grads

#34

I'm not sure, but maybe this is only for internal transfers? I mean this is obviously less difficult than the interviews of the big ones, or maybe Linkedin doesn't have difficult interviews?

Where are people getting that this is their interview process (or a prep book of some sort)? This afaik from the intro page is that they use this for onboarding. It’s to make sure everyone’s on the same page.

Re: School of SRE: Curriculum for onboarding non-traditional hires and new grads

#35
post #32
post #19

Earlier quoted context omitted.

I don't really understand, how going through this will get you a phone interview? I mean, it doesn't change anything on your resume... Source: I'm a new grad, I went through almost all this, but my application wasn't shortlisted. Not a native speaker, so maybe I just don't understand what you're saying.

My implication is that you either somehow indicate on your resume that you've done all this work, or better yet, take up a small project that lets you apply some of the skills. As a hiring manager there is no way to know you've done this unless you somehow demonstrate it.

Classic software chicken and egg problem.

Re: School of SRE: Curriculum for onboarding non-traditional hires and new grads

#36
post #29
post #12

with cloud being the talk of the industry these days. how pervasive are SRE roles. I would wager a good system admin | SRE can save a company thousands if they provisioned their own hardware i.e colo instead of cloud instances etc

Considering LinkedIn is owned by Microsoft they don't exactly need their own hosting.

Eventually they won't: https://engineering.linkedin.com/blog/2019/building-next-inf...

Re: School of SRE: Curriculum for onboarding non-traditional hires and new grads

#38
post #31

looks pretty good but still missing a lot of other things such as CI/CD, Software Testing, Bug management, Feature Development, Code Review as per Styleguide etc that should be taught to any newbie SWE based on the team/company workflow

As a self-learnt developer I know a little bit about those things on my stack. Do you think I could try and recompile that info into blogposts or a repo or ebook or whatever?

Re: School of SRE: Curriculum for onboarding non-traditional hires and new grads

#39
post #8
post #5

Noticed in the NoSQL section that they still call Cassandra as wide column DB. It’s not true for a long time - CQL requires schema definition, and although it’s possible to emulate old behavior, it’s not wide column anymore - people just copy old things...

I'm not 100% sure, but I think LinkedIn still uses it as a wide column store. At least, they've been using it a very long time and certainly used it that way before.

Even in 2019 it was late to use Thrift... And with C* 4.0 it should go away completely

Re: School of SRE: Curriculum for onboarding non-traditional hires and new grads

#40
post #38
post #31

looks pretty good but still missing a lot of other things such as CI/CD, Software Testing, Bug management, Feature Development, Code Review as per Styleguide etc that should be taught to any newbie SWE based on the team/company workflow

As a self-learnt developer I know a little bit about those things on my stack. Do you think I could try and recompile that info into blogposts or a repo or ebook or whatever?

sure, it will only help others
Post reply on HN