Thread by @tpschmidt_

There you are, on the way to becoming a cloud engineer and architect.

You've...
• learned a lot about AWS' core services
• probably taken some certifications
• built small services yourself

... but how to get into your first project?

What I've learned over the years 🧵↓

I've been in numerous interviews as a technical interviewer ✍️

Upfront & honest: without prior experience, it's not an easy task to get hired.

But there's no need to get discouraged.

There's a lot you can do to drastically enhance your chances.

{ 1 / 13 }

First: About job descriptions and requirements

AWS, Node.js, Java, Containerization/Docker, ECS/Kubernetes, Serverless & 10yrs experience in everything.

Likely, you've seen vacancies like this with only one question in mind:
"Are they looking for a whole team?"

{ 2 / 13 }

Job description and what the company is really looking for can differ enormously.

Don't get discouraged.

Even apply if you're only fulfilling parts of the requirements.
You'll, either way, learn and improve within your day-to-day job.

Your ability to learn is key.

{ 3 / 13 }

Covering Letter

Initially, I thought that's the "nobody will read this anyway" part.

That's not the case.
Mostly, it's really essential.

Show that you know the company.
Tell what's your motivation to work there.

Focus on correct spelling and grammar.

{ 4 / 13 }

Resume / Curriculum Vitae

Nobody will read your resume if it has 10 pages.
Nobody will care about your primary school.

Simple & <= 2 pages:
• small 'about you' part
• your list of skills (no proficiency level bars)
• noteworthy experiences
• previous jobs

{ 5 / 13 }

Small Side Projects & OpenSource contributions

Experiences are important.
If you've got something to show, that's a giant plus.

Regardless if it's your small weekend project at your own AWS account or a PR for an OpenSource repository.

Showcase your hands-on!

{ 6 / 13 }

Technical Writings & Online Presence

Improving your skills requires you to either build something on your own or explaining it to somebody else.

What also works: writing a technical wrap-up article about your new learnings.
It forces you to in-depth explanations.

{ 7 / 13 }

It's also useful for your interview.

If an article of yourself gained some popularity, it may also appear if a recruiter or HR person googles your name in combination with a required skill or technology.

You'll only win anyway.
Writing is a fundamental skill.

{ 8 / 13 }

Certifications

Generally, missing certifications are not a show stopper.
But having them is a plus.

If you've got the time and money, it's worth pursuing them.

It gives your potential client or employer some kind of safe bet that you know what you're doing.

{ 9 / 13 }

Especially the starter certifications aren't hard to get, so you don't need to spend a lot of effort, time, or money.

There are a lot of great & free learning resources
• AWS Cloud Practitioner: dannys.cloud/aws-cloud-prac…
• Azures AZ-900:

{ 10 / 13 }

My interviewer experience showed:
• being motivated & a team-player is the highest good
• long resumes & a masters degree do not automatically imply a great skill-set

Keep this in mind & show that you're either got the skills or you know how to get them!

{ 11 / 13 }

Disclaimer: all experiences are solely based in Europe, especially Germany! 💫

I know there's a heavy focus on really difficult technical interviews in the US, often with live-coding sessions.

For this, it takes another level of preparation.

{ 12 / 13 }

I hope you enjoyed reading this & feeling motivated on getting your first role at your first engineering project! 👨‍💻

I'd be happy if you like & retweet the initial post so others see this!

Follow along if you're interested in cloud & engineering content ☁️ 🏗

{ 13 / 13 }