Post #2293388

Well, it has finished (I got another interview for another job 2 hours before this one @_@) Thankfully my brain it's still functional and I was able to remember most if not all things, 60% of the interview was going well, even when we talked about aws IAM, roles, CloudWatch, CloudTrail, S3 buckets, RDS databases, a tiny bit about the transition from iptables to nftables (I was an idiot thinking he would ask literally the syntax of the files via a webcam interview), I was able to expand on some DevOps related things (always because he would ask first), like RESTful APIs (eg json continuous dataflow) vs SOAP (xml), and a bit of Python/Flask/Django and PHP/Laravel. The whole thing began to crack when I tried to be "smarter" telling I used Kubernetes with NetworkManager using LoadBalancing for the usual deployments, and direct Ingress with IPs with SSL using the Kubernetes integrated ip forwarding that also added TLS to continuous data flow (this was after explaining what were the Secret kind YAML files and how they worked). He told me that was "interesting", but he was interested in my expertise in EKS. I KNEW what it was, but I didn't have any "expertise". Since I became silent he asked "do you have experience with EKS?" "do you know what it is EKS?", then I exploded and answered that, NO, I don't have experience with EKS, but I know how it works, it is aws Elastic Kubernetes Service, it automatically integrates in a Kubernetes or from a Terraform configuration and connects to the LoadBalancer that's expecting an IP from aws. Then it manages all the security itself automatically. He told me that my intuition or knowledge was right, that I could even learn EKS in some days, but he *needed* someone with EKS experience. When presented himself at the beginning, he told me he was a SecOps Engineer working for the federal reserve of the US, but he was from Norway. Also, at the beginning he told me sorry for not having a camera (I didn't care anyways), and at the end, told me it was "rare" to find someone with so much broad knowledge as me, he liked a lot the example I gave him about continue delivery (REST APIs and SOAP), but I was still missing some parts of DevOps, though it was fine what I knew anyways, his problem was (he kept insisted) really needed someone with with EKS expertise. When I presented myself, I began telling him we used Sun Solaris and FreeBSD mostly on Telmex during the first years, and later we began introducing Linux, and even more later, it was mostly a mix of FreeBSD with RHEL, etc. It was a nice moment before we both closed the interview, that he asked me something like "do you have something you would like to ask before we go?" and I told him "YES, I knew I wouldn't knew absolutely everything I was gonna be asked for this job, but I wanted to try to rise up to the challenge, I thank you for your time" and he answered "oh no no, I got the pleasure to talk with a fellow Solaris of the old school and BSD admin, it's all fine, and you did ok, you should keep applying wherever you have the opportunity to learn more if you feel like, next time you may remember this interview and have experience with EKS"