Being someone from a non-IT educational background, it has been some journey jumping into the DevOps and SRE world. Although still at the very early stage, I have consumed lots of resources around the internet to understand things and wrap my head around the technical jargon and some fundamentals which are very much required for staying relevant in this field.
For those who don't know me, here’s a bit of my background from the about section of my LinkedIn:
I’m an SRE Consultant with about 2.5 years in Cloud Infrastructure and DevOps, plus six years of engineering experience. I started out as an Aircraft Maintenance Engineer, where I learned to obsess over reliability, stick to SOPs, and now I am adding a bit of innovation into the mix.
At early-stage startups, I helped set up infrastructure from the ground up, getting hands-on with AWS, Kubernetes, and building scalable backends.
I’m a big believer in nailing the fundamentals to create a solid foundation, especially now in this AI-driven world. Outside of work, I’m a football nut, love calisthenics, and love diving into philosophy, especially discussing deontology versus utilitarianism.
How I came across the SRE Bootcamp
PS: In case you haven't caught on, I came across the SRE Bootcamp before I joined One2N.
I was on the hunt for a proper way to learn SRE after messing around with DevOps and cloud tasks. A quick Google search for “SRE bootcamp” led me to One2N’s SRE Bootcamp. It’s a milestone-based challenge where you build everything from scratch on your local machine, which is very hands-on and practical.
My experience with the Bootcamp
Why would I suggest this bootcamp to developers or DevOps/SRE newbies when there are tutorials with millions of views? It’s not about replacing self-learning or real-world experience; it’s about adding a practical, problem-solving layer.
Instead of preset labs, this bootcamp throws real problems at you. For example, deploying Vault in production mode on a Minikube cluster meant tweaking storage settings or picking a new storage class. You’re not just learning about Vault; you’re diving deep into how storage works.
Tutorials often give you a readymade fix, which can limit your thinking. Going through the One2N bootcamp feels like real engineering: here’s a problem, go solve it.
It’s like a mini production environment on your machine, which complements the messy, real-world lessons I got from startups. Isn’t that what engineering’s about, figuring stuff out from scratch?
The bootcamp gives you resources for each milestone, which helped me spot gaps in what I knew. I set up a public GitHub repo to share my code, sticking to three rules:
It’s gotta work.
Follow best practices.
Make it production-ready.
There was no time-boxing method followed by me while doing this; it restricts the learning mindset and gets you obsessed with the outcome, but I did keep an approximated timeline for each milestone.
One more reason for you to check out this bootcamp is that it isn’t just a learning resource for the public to consume; it’s a part of One2N’s official training program. Every new hire who is new to SRE is made to go through the SRE bootcamp.
Bootcamp at One2N: a culture of learning
The second time around the bootcamp, which I did after joining One2N, there were code reviews by tech buddies; at every stage, I was told how I could do that thing better. Along with the bootcamp, there were sessions with senior folks where they shared their production stories.
After joining, I realized how things were being taken from an intermediate to an advanced level and how a solution for a problem should be designed using first principles.
Now, I not only followed best practices, I was creating videos explaining my solutions, getting my PRs reviewed, and explaining why I chose a particular solution and why the trade-offs involved were worth it.
Currently, we are reviewing stories on how an observability stack for a particular organization evolves over time and how things are resource constrained. How a complex four-line-long PromQL query can be broken down into pieces and understood in a way that makes sense for it to be there.
Limitations: areas for improvement
The bootcamp could use a bit of an update.
Integrating more of cloud related services.
Could ask the learners to integrate and use their own domain name for deployment of their application.
More focus on topics like SSL and TLS and integrating them with the domain.
In Kubernetes one could create a service and then use it as a production url.
But honestly, this can at least act as a resource to help you get your foot in the door. After completing it, you’ll have a solid baseline to build on.
One personal suggestion
Want to get noticed? Share your progress on Twitter or LinkedIn, tag One2N’s official handle, and you might get feedback from the experts. Make videos, stay consistent, and keep an eye on your DMs because you never know who might notice.
Final thoughts: is the One2N SRE Bootcamp worth it?
Along with my past experience, this bootcamp gave me simulated production experience and helped me fill gaps in my understanding. While going through it for the first time, I also had the chance to interview at One2N. If you’re curious about their interview process, take a look at their playbook: One2N Playbook.
Moreover, I believe that solving a jigsaw puzzle is also about understanding fundamental shapes, and if these shapes are clear in your head, you can automatically move on to solving complex puzzles.
References
Bootcamp: https://one2n.io/sre-bootcamp
My public repo: https://github.com/pmgoriya/SRE-Bootcamp-One2N
Being someone from a non-IT educational background, it has been some journey jumping into the DevOps and SRE world. Although still at the very early stage, I have consumed lots of resources around the internet to understand things and wrap my head around the technical jargon and some fundamentals which are very much required for staying relevant in this field.
For those who don't know me, here’s a bit of my background from the about section of my LinkedIn:
I’m an SRE Consultant with about 2.5 years in Cloud Infrastructure and DevOps, plus six years of engineering experience. I started out as an Aircraft Maintenance Engineer, where I learned to obsess over reliability, stick to SOPs, and now I am adding a bit of innovation into the mix.
At early-stage startups, I helped set up infrastructure from the ground up, getting hands-on with AWS, Kubernetes, and building scalable backends.
I’m a big believer in nailing the fundamentals to create a solid foundation, especially now in this AI-driven world. Outside of work, I’m a football nut, love calisthenics, and love diving into philosophy, especially discussing deontology versus utilitarianism.
How I came across the SRE Bootcamp
PS: In case you haven't caught on, I came across the SRE Bootcamp before I joined One2N.
I was on the hunt for a proper way to learn SRE after messing around with DevOps and cloud tasks. A quick Google search for “SRE bootcamp” led me to One2N’s SRE Bootcamp. It’s a milestone-based challenge where you build everything from scratch on your local machine, which is very hands-on and practical.
My experience with the Bootcamp
Why would I suggest this bootcamp to developers or DevOps/SRE newbies when there are tutorials with millions of views? It’s not about replacing self-learning or real-world experience; it’s about adding a practical, problem-solving layer.
Instead of preset labs, this bootcamp throws real problems at you. For example, deploying Vault in production mode on a Minikube cluster meant tweaking storage settings or picking a new storage class. You’re not just learning about Vault; you’re diving deep into how storage works.
Tutorials often give you a readymade fix, which can limit your thinking. Going through the One2N bootcamp feels like real engineering: here’s a problem, go solve it.
It’s like a mini production environment on your machine, which complements the messy, real-world lessons I got from startups. Isn’t that what engineering’s about, figuring stuff out from scratch?
The bootcamp gives you resources for each milestone, which helped me spot gaps in what I knew. I set up a public GitHub repo to share my code, sticking to three rules:
It’s gotta work.
Follow best practices.
Make it production-ready.
There was no time-boxing method followed by me while doing this; it restricts the learning mindset and gets you obsessed with the outcome, but I did keep an approximated timeline for each milestone.
One more reason for you to check out this bootcamp is that it isn’t just a learning resource for the public to consume; it’s a part of One2N’s official training program. Every new hire who is new to SRE is made to go through the SRE bootcamp.
Bootcamp at One2N: a culture of learning
The second time around the bootcamp, which I did after joining One2N, there were code reviews by tech buddies; at every stage, I was told how I could do that thing better. Along with the bootcamp, there were sessions with senior folks where they shared their production stories.
After joining, I realized how things were being taken from an intermediate to an advanced level and how a solution for a problem should be designed using first principles.
Now, I not only followed best practices, I was creating videos explaining my solutions, getting my PRs reviewed, and explaining why I chose a particular solution and why the trade-offs involved were worth it.
Currently, we are reviewing stories on how an observability stack for a particular organization evolves over time and how things are resource constrained. How a complex four-line-long PromQL query can be broken down into pieces and understood in a way that makes sense for it to be there.
Limitations: areas for improvement
The bootcamp could use a bit of an update.
Integrating more of cloud related services.
Could ask the learners to integrate and use their own domain name for deployment of their application.
More focus on topics like SSL and TLS and integrating them with the domain.
In Kubernetes one could create a service and then use it as a production url.
But honestly, this can at least act as a resource to help you get your foot in the door. After completing it, you’ll have a solid baseline to build on.
One personal suggestion
Want to get noticed? Share your progress on Twitter or LinkedIn, tag One2N’s official handle, and you might get feedback from the experts. Make videos, stay consistent, and keep an eye on your DMs because you never know who might notice.
Final thoughts: is the One2N SRE Bootcamp worth it?
Along with my past experience, this bootcamp gave me simulated production experience and helped me fill gaps in my understanding. While going through it for the first time, I also had the chance to interview at One2N. If you’re curious about their interview process, take a look at their playbook: One2N Playbook.
Moreover, I believe that solving a jigsaw puzzle is also about understanding fundamental shapes, and if these shapes are clear in your head, you can automatically move on to solving complex puzzles.
References
Bootcamp: https://one2n.io/sre-bootcamp
My public repo: https://github.com/pmgoriya/SRE-Bootcamp-One2N
Being someone from a non-IT educational background, it has been some journey jumping into the DevOps and SRE world. Although still at the very early stage, I have consumed lots of resources around the internet to understand things and wrap my head around the technical jargon and some fundamentals which are very much required for staying relevant in this field.
For those who don't know me, here’s a bit of my background from the about section of my LinkedIn:
I’m an SRE Consultant with about 2.5 years in Cloud Infrastructure and DevOps, plus six years of engineering experience. I started out as an Aircraft Maintenance Engineer, where I learned to obsess over reliability, stick to SOPs, and now I am adding a bit of innovation into the mix.
At early-stage startups, I helped set up infrastructure from the ground up, getting hands-on with AWS, Kubernetes, and building scalable backends.
I’m a big believer in nailing the fundamentals to create a solid foundation, especially now in this AI-driven world. Outside of work, I’m a football nut, love calisthenics, and love diving into philosophy, especially discussing deontology versus utilitarianism.
How I came across the SRE Bootcamp
PS: In case you haven't caught on, I came across the SRE Bootcamp before I joined One2N.
I was on the hunt for a proper way to learn SRE after messing around with DevOps and cloud tasks. A quick Google search for “SRE bootcamp” led me to One2N’s SRE Bootcamp. It’s a milestone-based challenge where you build everything from scratch on your local machine, which is very hands-on and practical.
My experience with the Bootcamp
Why would I suggest this bootcamp to developers or DevOps/SRE newbies when there are tutorials with millions of views? It’s not about replacing self-learning or real-world experience; it’s about adding a practical, problem-solving layer.
Instead of preset labs, this bootcamp throws real problems at you. For example, deploying Vault in production mode on a Minikube cluster meant tweaking storage settings or picking a new storage class. You’re not just learning about Vault; you’re diving deep into how storage works.
Tutorials often give you a readymade fix, which can limit your thinking. Going through the One2N bootcamp feels like real engineering: here’s a problem, go solve it.
It’s like a mini production environment on your machine, which complements the messy, real-world lessons I got from startups. Isn’t that what engineering’s about, figuring stuff out from scratch?
The bootcamp gives you resources for each milestone, which helped me spot gaps in what I knew. I set up a public GitHub repo to share my code, sticking to three rules:
It’s gotta work.
Follow best practices.
Make it production-ready.
There was no time-boxing method followed by me while doing this; it restricts the learning mindset and gets you obsessed with the outcome, but I did keep an approximated timeline for each milestone.
One more reason for you to check out this bootcamp is that it isn’t just a learning resource for the public to consume; it’s a part of One2N’s official training program. Every new hire who is new to SRE is made to go through the SRE bootcamp.
Bootcamp at One2N: a culture of learning
The second time around the bootcamp, which I did after joining One2N, there were code reviews by tech buddies; at every stage, I was told how I could do that thing better. Along with the bootcamp, there were sessions with senior folks where they shared their production stories.
After joining, I realized how things were being taken from an intermediate to an advanced level and how a solution for a problem should be designed using first principles.
Now, I not only followed best practices, I was creating videos explaining my solutions, getting my PRs reviewed, and explaining why I chose a particular solution and why the trade-offs involved were worth it.
Currently, we are reviewing stories on how an observability stack for a particular organization evolves over time and how things are resource constrained. How a complex four-line-long PromQL query can be broken down into pieces and understood in a way that makes sense for it to be there.
Limitations: areas for improvement
The bootcamp could use a bit of an update.
Integrating more of cloud related services.
Could ask the learners to integrate and use their own domain name for deployment of their application.
More focus on topics like SSL and TLS and integrating them with the domain.
In Kubernetes one could create a service and then use it as a production url.
But honestly, this can at least act as a resource to help you get your foot in the door. After completing it, you’ll have a solid baseline to build on.
One personal suggestion
Want to get noticed? Share your progress on Twitter or LinkedIn, tag One2N’s official handle, and you might get feedback from the experts. Make videos, stay consistent, and keep an eye on your DMs because you never know who might notice.
Final thoughts: is the One2N SRE Bootcamp worth it?
Along with my past experience, this bootcamp gave me simulated production experience and helped me fill gaps in my understanding. While going through it for the first time, I also had the chance to interview at One2N. If you’re curious about their interview process, take a look at their playbook: One2N Playbook.
Moreover, I believe that solving a jigsaw puzzle is also about understanding fundamental shapes, and if these shapes are clear in your head, you can automatically move on to solving complex puzzles.
References
Bootcamp: https://one2n.io/sre-bootcamp
My public repo: https://github.com/pmgoriya/SRE-Bootcamp-One2N
Being someone from a non-IT educational background, it has been some journey jumping into the DevOps and SRE world. Although still at the very early stage, I have consumed lots of resources around the internet to understand things and wrap my head around the technical jargon and some fundamentals which are very much required for staying relevant in this field.
For those who don't know me, here’s a bit of my background from the about section of my LinkedIn:
I’m an SRE Consultant with about 2.5 years in Cloud Infrastructure and DevOps, plus six years of engineering experience. I started out as an Aircraft Maintenance Engineer, where I learned to obsess over reliability, stick to SOPs, and now I am adding a bit of innovation into the mix.
At early-stage startups, I helped set up infrastructure from the ground up, getting hands-on with AWS, Kubernetes, and building scalable backends.
I’m a big believer in nailing the fundamentals to create a solid foundation, especially now in this AI-driven world. Outside of work, I’m a football nut, love calisthenics, and love diving into philosophy, especially discussing deontology versus utilitarianism.
How I came across the SRE Bootcamp
PS: In case you haven't caught on, I came across the SRE Bootcamp before I joined One2N.
I was on the hunt for a proper way to learn SRE after messing around with DevOps and cloud tasks. A quick Google search for “SRE bootcamp” led me to One2N’s SRE Bootcamp. It’s a milestone-based challenge where you build everything from scratch on your local machine, which is very hands-on and practical.
My experience with the Bootcamp
Why would I suggest this bootcamp to developers or DevOps/SRE newbies when there are tutorials with millions of views? It’s not about replacing self-learning or real-world experience; it’s about adding a practical, problem-solving layer.
Instead of preset labs, this bootcamp throws real problems at you. For example, deploying Vault in production mode on a Minikube cluster meant tweaking storage settings or picking a new storage class. You’re not just learning about Vault; you’re diving deep into how storage works.
Tutorials often give you a readymade fix, which can limit your thinking. Going through the One2N bootcamp feels like real engineering: here’s a problem, go solve it.
It’s like a mini production environment on your machine, which complements the messy, real-world lessons I got from startups. Isn’t that what engineering’s about, figuring stuff out from scratch?
The bootcamp gives you resources for each milestone, which helped me spot gaps in what I knew. I set up a public GitHub repo to share my code, sticking to three rules:
It’s gotta work.
Follow best practices.
Make it production-ready.
There was no time-boxing method followed by me while doing this; it restricts the learning mindset and gets you obsessed with the outcome, but I did keep an approximated timeline for each milestone.
One more reason for you to check out this bootcamp is that it isn’t just a learning resource for the public to consume; it’s a part of One2N’s official training program. Every new hire who is new to SRE is made to go through the SRE bootcamp.
Bootcamp at One2N: a culture of learning
The second time around the bootcamp, which I did after joining One2N, there were code reviews by tech buddies; at every stage, I was told how I could do that thing better. Along with the bootcamp, there were sessions with senior folks where they shared their production stories.
After joining, I realized how things were being taken from an intermediate to an advanced level and how a solution for a problem should be designed using first principles.
Now, I not only followed best practices, I was creating videos explaining my solutions, getting my PRs reviewed, and explaining why I chose a particular solution and why the trade-offs involved were worth it.
Currently, we are reviewing stories on how an observability stack for a particular organization evolves over time and how things are resource constrained. How a complex four-line-long PromQL query can be broken down into pieces and understood in a way that makes sense for it to be there.
Limitations: areas for improvement
The bootcamp could use a bit of an update.
Integrating more of cloud related services.
Could ask the learners to integrate and use their own domain name for deployment of their application.
More focus on topics like SSL and TLS and integrating them with the domain.
In Kubernetes one could create a service and then use it as a production url.
But honestly, this can at least act as a resource to help you get your foot in the door. After completing it, you’ll have a solid baseline to build on.
One personal suggestion
Want to get noticed? Share your progress on Twitter or LinkedIn, tag One2N’s official handle, and you might get feedback from the experts. Make videos, stay consistent, and keep an eye on your DMs because you never know who might notice.
Final thoughts: is the One2N SRE Bootcamp worth it?
Along with my past experience, this bootcamp gave me simulated production experience and helped me fill gaps in my understanding. While going through it for the first time, I also had the chance to interview at One2N. If you’re curious about their interview process, take a look at their playbook: One2N Playbook.
Moreover, I believe that solving a jigsaw puzzle is also about understanding fundamental shapes, and if these shapes are clear in your head, you can automatically move on to solving complex puzzles.
References
Bootcamp: https://one2n.io/sre-bootcamp
My public repo: https://github.com/pmgoriya/SRE-Bootcamp-One2N
Being someone from a non-IT educational background, it has been some journey jumping into the DevOps and SRE world. Although still at the very early stage, I have consumed lots of resources around the internet to understand things and wrap my head around the technical jargon and some fundamentals which are very much required for staying relevant in this field.
For those who don't know me, here’s a bit of my background from the about section of my LinkedIn:
I’m an SRE Consultant with about 2.5 years in Cloud Infrastructure and DevOps, plus six years of engineering experience. I started out as an Aircraft Maintenance Engineer, where I learned to obsess over reliability, stick to SOPs, and now I am adding a bit of innovation into the mix.
At early-stage startups, I helped set up infrastructure from the ground up, getting hands-on with AWS, Kubernetes, and building scalable backends.
I’m a big believer in nailing the fundamentals to create a solid foundation, especially now in this AI-driven world. Outside of work, I’m a football nut, love calisthenics, and love diving into philosophy, especially discussing deontology versus utilitarianism.
How I came across the SRE Bootcamp
PS: In case you haven't caught on, I came across the SRE Bootcamp before I joined One2N.
I was on the hunt for a proper way to learn SRE after messing around with DevOps and cloud tasks. A quick Google search for “SRE bootcamp” led me to One2N’s SRE Bootcamp. It’s a milestone-based challenge where you build everything from scratch on your local machine, which is very hands-on and practical.
My experience with the Bootcamp
Why would I suggest this bootcamp to developers or DevOps/SRE newbies when there are tutorials with millions of views? It’s not about replacing self-learning or real-world experience; it’s about adding a practical, problem-solving layer.
Instead of preset labs, this bootcamp throws real problems at you. For example, deploying Vault in production mode on a Minikube cluster meant tweaking storage settings or picking a new storage class. You’re not just learning about Vault; you’re diving deep into how storage works.
Tutorials often give you a readymade fix, which can limit your thinking. Going through the One2N bootcamp feels like real engineering: here’s a problem, go solve it.
It’s like a mini production environment on your machine, which complements the messy, real-world lessons I got from startups. Isn’t that what engineering’s about, figuring stuff out from scratch?
The bootcamp gives you resources for each milestone, which helped me spot gaps in what I knew. I set up a public GitHub repo to share my code, sticking to three rules:
It’s gotta work.
Follow best practices.
Make it production-ready.
There was no time-boxing method followed by me while doing this; it restricts the learning mindset and gets you obsessed with the outcome, but I did keep an approximated timeline for each milestone.
One more reason for you to check out this bootcamp is that it isn’t just a learning resource for the public to consume; it’s a part of One2N’s official training program. Every new hire who is new to SRE is made to go through the SRE bootcamp.
Bootcamp at One2N: a culture of learning
The second time around the bootcamp, which I did after joining One2N, there were code reviews by tech buddies; at every stage, I was told how I could do that thing better. Along with the bootcamp, there were sessions with senior folks where they shared their production stories.
After joining, I realized how things were being taken from an intermediate to an advanced level and how a solution for a problem should be designed using first principles.
Now, I not only followed best practices, I was creating videos explaining my solutions, getting my PRs reviewed, and explaining why I chose a particular solution and why the trade-offs involved were worth it.
Currently, we are reviewing stories on how an observability stack for a particular organization evolves over time and how things are resource constrained. How a complex four-line-long PromQL query can be broken down into pieces and understood in a way that makes sense for it to be there.
Limitations: areas for improvement
The bootcamp could use a bit of an update.
Integrating more of cloud related services.
Could ask the learners to integrate and use their own domain name for deployment of their application.
More focus on topics like SSL and TLS and integrating them with the domain.
In Kubernetes one could create a service and then use it as a production url.
But honestly, this can at least act as a resource to help you get your foot in the door. After completing it, you’ll have a solid baseline to build on.
One personal suggestion
Want to get noticed? Share your progress on Twitter or LinkedIn, tag One2N’s official handle, and you might get feedback from the experts. Make videos, stay consistent, and keep an eye on your DMs because you never know who might notice.
Final thoughts: is the One2N SRE Bootcamp worth it?
Along with my past experience, this bootcamp gave me simulated production experience and helped me fill gaps in my understanding. While going through it for the first time, I also had the chance to interview at One2N. If you’re curious about their interview process, take a look at their playbook: One2N Playbook.
Moreover, I believe that solving a jigsaw puzzle is also about understanding fundamental shapes, and if these shapes are clear in your head, you can automatically move on to solving complex puzzles.
References
Bootcamp: https://one2n.io/sre-bootcamp
My public repo: https://github.com/pmgoriya/SRE-Bootcamp-One2N
