5 ms·

Could you actually get an SRE job if you went through this?

• jedberg 6y ago
  You could probably at least get a phone interview if you did...
  • vsareto 6y ago
    This is just positioned weirdly. They use it for on-boarding, which means you already got the job without knowing it or only partially knowing it, so it's not a hard requirement. The real requirement is the ability to learn. But if that's true, they shouldn't have much trouble finding people to train into SREs: >Because of the lack of these resources, we felt that individuals have a tough time getting into open positions in the industry
  • RMPR 6y ago
    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.
    • jedberg 6y ago
      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.
      • pm90 6y ago
        Classic software chicken and egg problem.
        • TheHypnotist 6y ago
          It's an amazing phenomenon. In order to get industry experience using a tool/skillset you need to be part of that industry using that tool/skillset. It's becoming more apparent to me that in order to pivot in IT, you need to do something (ie a project) on your own time or just lie.
          • pm90 6y ago
            Well the part that companies don’t say out loud is that college recruitment is the source of most of their new grads. Which colleges becomes a function of alums with influence in the company.
          • treeman79 6y ago
            Build some personal projects. Try and use various popular tools and frameworks. Build an app. Doesn’t need to be good. Just show initiative to improve. I normally won’t hire a jr. But I have made exceptions if they have clearly worked through a lot of code exercises, koans, etc. My daughters boyfriend thought he was hot stuff for getting a masters degree. After a friendly chat, I informed wife that boy was going to have a bad time getting anything. This is someone that had a lot of connections. A year later and he sells mortgages.
          • joshuanapoli 6y ago
            It is easier to pivot to a new job within an organization, where you already have trust and a good reputation. Supporting these lateral moves was part of LinkedIn's motivation in putting this resource together.
          • nullsense 6y ago
            The alternative strategy is just make sure when you change jobs you're getting hired for 2x skills you know deeply well and the job offers you the chance to pivot into a new technology that is a gap in your skills. It's harder if you're trying to get hired specifically for a technology that's a gap in your skills.
    • chaps 6y ago
      It's good with these sorts of things to simply get an understanding of the terminology used by these teams. Going through a guide like this won't get you 100% of the way, but it'll let you have conversations with someone over the phone. IME, SRE roles are jack of all trades position, so you're not necessarily expected to be an expert in any one thing, which makes it easier to learn many things at the surface level, instead of learning a few things in depth. Which practically means that you will learn a lot on the job. This is especially true, since you're expected to learn some technology that's only seen internal to the company. So, showing they you have the ability to learn can perceived as much more important than specific knowledge.
• nickthemagicman 6y ago
  Oddly, the Linked-in SRE interview is more challenging, than this.
  • johnnujler 6y ago
    Although the degree of difficulty w.r.t a question may differ, I think being proficient in these concepts can get you a job. It’s just that most of us struggle with solving problems(in an interview). I think these concepts cover pretty much everything a SRE would need to know.
    • vultour 6y ago
      Knowing these things will absolutely help you get a job. The problem is that most SRE positions expect significant experience, so a "non-traditional" or "college grad" hire will not even be considered regardless of what they know.
    • vsareto 6y ago
      That's another thing that was bugging me: this is pretty easy level stuff for an SRE position from what I know. The other surprise was new grads being directly hired to SRE positions and it was my impression you needed professional skills in another area (at least sysadmin/cloud or programming) to transition over. That means there's a whole isolated career track for SREs now, but maybe LinkedIn hiring new grads for SRE is an anomaly.
      • treeman79 6y ago
        Can almost be better not to transition. Newer Devops / SRE is about be declarative, letting them system build itself up. Mindset of old sysadmins is more tribal knowledge. You can get stuff done crazy fast are are awesome. But heaven help anyone that needs to mess with it.
  • dkdk8283 6y ago
    LinkedIn has so many tools you just have to be really good at a lot and hope the panel isn’t full of asshats.
• 0xbadcafebee 6y ago
  As former Presidents of the USA have proved time and again, qualifications are no barrier to getting a job. You could get an SRE job without this. But could you get a decent SRE job with this? Nope.
• suyash 6y ago
  yes by being good at solving programming puzzles, which is the big irony.