I want to transit from Fullstack dev to Cloud dev (e.g. focus on infra). Any feedback on my CV?

CV Review

Hello,
I've been working as Fullstack dev for around 6-7 years, but now I want to specialize on Cloud/Infrastructure/Architecture. Possible fitting jobs can be called Solution Architect, Cloud Engineer, and even SRE/DevOps. Here is my CV.

​

Basically I want to develop software and automatisation in scope of infrastructure. I desided to do one CV instead of multiple (e.g. one for SRE, one for DevOps, one for Cloud/Platform/Backend). Is it an adequate strategy? Any feedback welcome.

Thanks in advance.

Posted Jan 4, 2023, 3:21 PM UTC

735
[deleted]•

[deleted]

5
darbyShaw96•

Could you clarify your input about ageism? How does it work in the EU? What is usually sought?

3
[deleted]•

[deleted]

1

agism example: because I'm young I get paid 10k less than someone who has 10 years on me, but we have similar CS work experience years and I have more domain-related knowledge.

1
EchoesInBackpackOP•

Thanks for the feedback.
Bulletpoints will take much more space and it would be hard to fit it into one page. But I'll look for such examples.
I left dates for uni cause I left on 5th semester.

2
[deleted]•

[deleted]

2
EchoesInBackpackOP•

Many thanks for the detailed answer

2

Hey! I'm SRE/DevOps. May I ask you for your reasons to move from fullstack to infra? I have been considering if I should move to a fullstack role. I have solid aws, k8s & terraform knowledge but feel like I could work on my dev skills. Is it the opposite for you?

On your CV: I think your skills section needs to be more informative. You list k8s as a skill but I don't see that reflected in your work experience much. What does it mean to you? Does it mean you have seen it once or twice or do you have skills on par with CKA certification for example? It is not clear to me what your skill level is in the skills listed.

2
EchoesInBackpackOP•

Thanks for the feedback. I'll improve my skills section.
Yes, partially. Last year I enjoy working on infra/ci staff. And programming business logic become a bit boring. So it's mostly not about how I want to develop my skills, but what I want to do.

1
Training-Apple1443•

There is no such thing as cloud dev.

cloud engineers are just IT people in the cloud

SRE/DevOps...ok maybe but gets boring quickly

Architects are mostly pre-sales oriented

-5
Aquaticdigest•

Dont listen to this dude. My title is Cloud Engineer but it involves a lot of stuff around programming + automation. I have worked on the following tech since 2 years: Python, Go, Vue.js, Groovy, MongoDB, Terraform, Terragrunt, Microsoft Azure, Jenkins. There is a lot of coding/programming involved. IT people in the cloud are called SysAdmins or Cloud Administrator not Cloud Engineers...

4
Training-Apple1443•

Your sample size of 1?

Please enlighten me why you had to use Vue, Go or Python!

-2
buffer0x7CD•

Okay, I work as an SRE too and have to use C++ , lua , python and golang very much. C++ for writing envoy filters and logging service ( accept logs over a grpc service and do some transformation before sending it out ) Python for Our Paas which uses Kubernetes. Rust and Lua for writing a transparent caching service. Your idea of SRE/Infra is very outdated

3
[deleted]•

[removed]

-6
Aquaticdigest•

Do you not know that most cloud applications are built on Go? like Kubernetes, Terraform etc...

-1
Training-Apple1443•

Do you know that most of those apps are written by application engineers aka devs and not by infrastructure engineers?

2
EchoesInBackpackOP•

All these titles a bit silly. All of that comes to specific roles on the project. But I do see some jobs postings with that title. I chose Cloud Engineer, beacuase it sounds very broad which allows me to maneuver.

0