31–36 of 36 posts
Get a Hetzner vps for buttons. Put a docker image on it with nginx and java. Create a simple site and push it to a bare git repository on the docker image. Tweak the bare repo config to checkout files to the public web folder after it receives the push. When asked about cloud deployments and containers say, "doing it".
Maybe try getting an AWS certification. Just going through that process will definitely expose you to enough of AWS to answer any possible interview question, and would probably help get you pass any resume screening too. It worked for me, and I started out as an electrical engineer!
It definitely won't make you answer any possible interview question, paper tigers often have issues with putting things together, cicd, iam and practical IaC setups. It's pretty easy to tell theoretical experience from actual experience.
Stick those on your profile/CV and relate it the work you currently do - e.g. how would you migrate from on premise to the cloud etc...
Step 2: Put "Docker, AWS/GCP" in your resume in your "skills" section and in the section that belongs to your current job.
Profit.
If you know about containerization then it doesn't really matter if you have learn it in your side projects or your work. If you pass the interview that means the company is comfortable with your knowledge about containers.
Your CV is whatever you want it to be (with some limitations of course). If HR is expecting to see X in your CV, you can easily put it there if you do your homework. It doesn't really matter if you didn't use X in your last job, just put it there and demonstrate in the interview how well you know X.
Get a Hetzner vps for buttons. Put a docker image on it with nginx and java. Create a simple site and push it to a bare git repository on the docker image. Tweak the bare repo config to checkout files to the public web folder after it receives the push. When asked about cloud deployments and containers say, "doing it".