Programming

17313 readers

399 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Any recommendations for a career change? (self.programming)

submitted 11 months ago by thefloweracidic to c/[email protected]

36 comments fedilink hide all child comments

I spent 8 years doing Java development, layoffs are coming soon (my second time this year! 😊), I know how hard it is to get a job out there, and I'm tired of Java. So I was wondering if anyone had any advice for pointing my career in a new direction. I'd like there to be some technical aspect to it still, which is why I am posting here instead of elsewhere.

Right now I'm really into Lua, Vue.js, and am considering picking up CompTIA and AWS certifications just to make myself more marketable.

I have good people skills too, so if a career involves talking more than coding I'll be okay with that. I spent part of this year teaching programming and loved it (but due to the state of the industry many academic businesses are closing down).

Or you know, should I sell my home and just go live in the woods until I die of malnutrition because at this rate we'll all end up there anyways?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago) (1 children)

Naw. I always think of customer engineer as having a large overlap with the person who quotes you a price for some project (building, car repair, etc).

They look at what you need and try to figure out how to use their companies software to make it happen. But the critical difference is they don't really build anything other than a demo or proof of concept. They might spec out something and give you a cost estimate. Or they might work with you to architect some piece (as in "hey you could use s3 here and dynamodb there and make sure that you don't have a single region point of failure".

At the end of the day it is sales. It's just trying to show people they can use your companies tools to do what they want.

Also I work for one of the cloud companies. I spent most of my career as a software engineer but the most common skill I use is really more devops stuff. Customers aren't asking me to design their business logic, they are often asking me to design their multi region high availability story.

[–] [email protected] 1 points 11 months ago

Sales engineers work on the pre-sales side and there’s a bit of sales in it. But, at least at companies I’ve worked at, customer engineer are more about solving problems and getting the most out of whatever they bought.

I always tried to be honest, to the point where I would tell customers if they don’t need something or if something else would be a better fit, much to the chagrin of the sales people.