@Cereal_Bowl_Assassin I have a couple questions for you.
How did you get an interview and call back for your first ever engineering job and for the one that you are at now? Did your school help you with that?
I just applied to a bunch if jobs on indeed and angel list. I treated my application process like an actual job and I didnt skip and corners. So if a job requires a cover letter I tailored it to the job if my skills were the right fit, I also did it with my resume. I wasnt the best programmer at school but I was the first person to find a job and I think the reason for that was I was honest about my skillset on my resume and interview. Also people skills are big imo. You know the stereotypical superstar engineer that doesnt talk? Those are the ones that had a tough time finding a job.
The school helped me but they dont offer job placement. They have a bunch of connections and they introduced people to companies if they felt the fit was the right ine.
What skills did you have prior to the job that helped on the job? What skills did they require you to know? Did they train you?
I didnt have any skills to be honest. I attempted a few coding challenges for other schools without much knowledge of coding and I bombed pretty bad.
Holberton required a video intro, then you had to create a website and that was great for me because it was my first real dive into coding. After that they required you to do some things on linux but they just wanted to see how you would figure something out..it wasnt difficult looking back but at the time when it's all new it's very terrifying
Did they ask you technical questions during the job interview? Can you give some examples?[/QUOTE]
Since I work as a DevOps engineer I was required to know system design, networking, automation, be able to read anyone else's code and make changed where necessary, and of course linux is, bash and python scripting and some coding but not much.
However some other companies may want something a bit different like more coding. Nothing to crazy but every DevOps engineer should know how to code.
But to truly answer your question, every programmer,developer,engineer should know algorithms and how to use them within programming. So something like big O notation would be very important.
So an example would be
For a DeVops/SRE:
You have 10GB of text logs. Each log line corresponds to a single HTTP response from web frontend. You goal is to write a simple, reusable tool that returns the percentage of responses that were HTTP 5xx errors, broken down by domain, for a given timeframe.
For a programming position:
Q1.How to convert a list into a string
Q2. Given a sorted linked list and a value to insert, write a function to insert the value in a sorted way.
- Once you answer these questions you should explain the big o time complexity(how many times does your code need to run in order to finish) of your function and explain tour thought process. Always white board as well.
Also my bad for getting back to you so late. Life has gotten in the way a bit lol
