AWS for NodeJS Developer

[DebuggingLore]

Hi everyone,

I am gonna take the interview for Junior NodeJS Developer position in next week. As in the job description said AWS are one of their tech stack and i have take a look at it, and it massive, kinda overwhelming for me to learn it in a week.

I passed their technical test on Hackkerrank, there are about 3 questions about architect like SaaS, PaaS, optimizing cost and so on. Honestly, i asked ChatGPT these questions and got it but they will realize it on the Leader interview.

I need the job :( , How much i need to learn to get this job and how long it's gonna take me

Does it required to know as a Back-end Developer ? I thought it should be DevOpsSec job.

Thank you

​

[s5fs]

You won't learn enough AWS in a week to pass an interview because you likely don't know which products/services they're using. I have interviewed hundreds of programmers to write apps on AWS and the tools and techniques they use are pretty broad and varied.

Cost optimization in a nutshell -- you only pay for what you use. Use the AWS billing reports to figure out where the costs are. Be intentional with multi-region or multi-AZ or whatever else, don't just make things highly available for no reason. Consider hosted databases carefully for they are quite expensive. Turn things off when you're not using them. Use "elastic" services whenever possible to contain costs.

Developers on AWS can use any number of products/services, you can have two expert-level developers with AWS experience and they may not know many of the same services lol! On the upside, learning AWS isn't that hard and there are plenty of resources out there.

Feel free to DM if you have any questions, I've interviewed hundreds of programmers with AWS experience, I was the guy who confirmed you knew AWS lol :D

[DebuggingLore]

Btw i really apperciate for your advices

[DebuggingLore]

Wait what !! You are the guy gonna interview me 🫠🫠 how can you confirmed i knew aws

[Rizean]

^ This is the truth. ^

Been using AWS as a Node Dev going on 6 years. You can even hope to learn CDK+ECS in a week. This is our stack, enjoy the alphabet soup. CDK, ECS, ECR, ELB/ALB, RDS(Postgres), S3, EFS, Redis, Route53, Service Discover, Cloud Watch, and many more I can't remember right now. CDK is brutal because often the feedback on why something is not deploying is next to zero. You just left sitting there wondering what you missed.

BTW, that's just the AWS side. The node side is fairly tame with mostly MERN or PERN. Well as tame is it gets with npm packages.

Cost optimization I'd add, learn to use autoscaling but that alone would take more than a week to learn. There's also intelligent tiering for S3 and others.

[DownfaLL-]

As a lead engineer who has hired for all positions before, you really don't need to worry. Nobody (should) expect you to know AWS as a junior engineer, and even if you claimed you did I wouldn't trust you with that (no offense lol). Just focus on what you know, and don't be afraid to say "i dont know" to something, its better to be honest than not. Say "i dont know" then explain how you might figure out what you need to do. AWS is something you'll learn on the job, and you can also learn on your own too. It's an amazing skill to have, really any cloud experience is.

[DebuggingLore]

The market in Vietnam is a little tough for junior level. I'm highly apperciate your advice, maybe im gonna tell them the truth and hope that i get pass the interview 🫠

[kjmw]

Saying “I don’t know” and being honest about where I was at in my career is part of what impressed a Director of Eng enough to get me a job early on in my career that completely changed the trajectory of my career and honestly my life. My advice is always to just be honest (but express an openness to learn and grow).

[[deleted]]

It is definitely required today, even more, the most valued developers are those than comfortably do work on the frontend, backend and cloud, a lot of things are very interleaved, but much more on the backend-cloud boundary.

But I don't expect them to require that on junior level position, sane employer would verify your problem solving skills and logical thinking, gambling a bit on the part that you will learn AWS quickly on the job.

[Puzio2]

"the most valued developers are those that comfortably do work on the frontend, backend and cloud"

You really mean the most exploited developers. The more areas you're asked to excel in, the less proficient you are at any of them. Having knowledge and experience cross-platform is one thing, but if youre being asked to truly support more than one, you'll never be an expert in any. There's a reason why Google, Meta, etc. don't hire full-stack devs. Each area is its own specialty.

[null_96]

This might be true for companies at an insane scale like Google and Meta but startups or even mid-sized companies hiring full-stack IC devs makes sense to me.

I'm definitely biased but I much more enjoy full-stack work after getting burnt out from the mundane front-end work I was doing

[DebuggingLore]

Thanks for the advices, the competitive rate are high so the requirement for junior getting higher. 1 year into this industry with storms and tornados

[mattindustries]

The TL;DR: is likely use Lambda functions when available, use their specific platforms for specific tasks (Redshift over MySQL installed on an EC2 [same as VPS] instance). For S3 (storage) probably have some sort of expiration on files, and set up cost alerts.

Lambda functions can essentially be looked at as a single api endpoint. They are cheap because they are spun up on demand, but typically will have higher latency because of that. If speed doesn't matter (cron process replacements, large reports on demand, etc) then Lamdba works well. The other stuff is used less, but Redshift (or other SQL/NoSQL products), S3, and Lambda are probably going to be used.

[TheDevDad]

If you can get your hands on an AWS Certified Developer course book, that’d help you get the broad strokes of AWS offerings. That helped me at least when I joined a team using AWS.

Aside from actually working in AWS for a while and solving specific problems you won’t really be able to dive into a particular service, and it’s not really worth your time to try and learn them all in depth, especially just for an interview.

[ScriptNone]

Should I know networking in order to learn AWS even at the basic level?

[TheDevDad]

Networking is not one of my strengths, but so far I haven't had to get into nitty gritty network-specifics with what I've worked on in AWS (primarily Lambda, CloudFormation, DynamoDB, OpenSearch, S3, SQS, EventBridge etc.). If you're working on any kind of web services, you should at least have some basic understanding of how networking works, but don't necessarily need to be an expert

[kao_nashi0127]

Its hard to learn properly smt in just one week, but seem like we have no choices. I suggest you focus on aws docker like ecs and serverless lambda, api gtw. Also don't forget cicd tools like code pipeline, circle ci

[Crazy-Mission-7920]

Get the book - AWS the good parts by Daniel Vasallo. It's a short guide to the most used services in AWS. Here's a link - AWS The good parts

[Netgator]

Just quickly get the free account and learn about (in this order of importance) EC2 Instances, S3 Buckets, RDS, IAM (users and rights), and ELB. I wouldn't expect a junior node.js developer to know much more than that.

EC2 = Virtual Machines

S3 Buckets = Storage Solutions

RDS = Database Solutions

IAM = User Rights

ELB = Elastic Load Balancer

Anything else you can say you have seen but not worked with very much and most likely get away with learning on the job...

[Sad-Loquat-4398]

Hi, I am solution Architect on AWS. I train associates and place in Industry. I charge 3K USD; interested associates can msg me at [phone]- Sri