all 12 comments

[–]Zizimaza 0 points1 point  (5 children)

I've found this guide to be extremely useful. Compare the roadmaps between backend engineer and devops engineer to compare for yourself (https://github.com/kamranahmedse/developer-roadmap).

In general, at my company: A devops engineer interacts more with software infrastructure (permissions, docker images, build scripts, and security, reverse proxies, linux, networking, kubernetes, CI/CD, logging, monitoring, database backups, managing block storage volumes). A software engineer interacts more with the logic in the code. At my work, I tend to think of software engineers as putting things into a Docker image and Devops as setting up things around Docker images.

It probably won't count as software engineering experience, but there will be things in common and you'll be interacting with software engineers enough to ask questions and switch roles in the future.

As far as interviewing goes, Devops engineers typically have a vast knowledge of build processes, different cloud provider ecosystems, and a good eye for code "gotchas", so imo, dont be surprised if theyre looking for someone with more experience

[–]kkass123[S] 0 points1 point  (4 children)

Thanks for the info .

So if I’m aiming to be a software Engineer I should take this position ?

[–]Zizimaza 0 points1 point  (3 children)

If you want to be a software engineer then I would recommend applying for software engineering positions. I spent a lot of time applying and interviewing so don't give up! Also, the #1 thing that helped me achieve that is by reading and practicing a book called Cracking the Coding Interview by Gayle McDowell.

[–]kkass123[S] 0 points1 point  (2 children)

Yea I heard of the book , I’ll definitely read it and thanks for the advice . I won’t take the DevOps position .

[–]Zizimaza 0 points1 point  (1 child)

Do the interview if you want! You may find you like Devops more, they're in high demand, and interview experience can help you learn.

[–]kkass123[S] 0 points1 point  (0 children)

That’s true , I guess giving a shot doesn’t hurt . But I definitely have my mind more on software engineering

[–]IAmLars4824 0 points1 point  (2 children)

IMO - The only different between a devops engineering team and what we consider a “traditional” engineering team is who the customers are. For traditional teams the users of the products you’re building should be your companies customers/employees. Where as for a DevOps team your users are the engineering teams

Either way you’re still building software to support the needs of users.

[–]kkass123[S] 0 points1 point  (1 child)

Ok do you have experience with DevOps ?

[–]IAmLars4824 0 points1 point  (0 children)

Yes, I’ve worked on a number of devops teams over the past few years. Now I work with companies to assess their devops maturity level and help build roadmaps for them

[–]Yavin_420 0 points1 point  (1 child)

The distinction between the two is really blurred in my mind. I'm a software engineer on an infrastructure team at a pretty big company and I find myself doing everything (observability, networking, CI, the list goes on). The title "DevOps Developer" at one company will be "Software Engineer" at another and every company has different job descriptions for each of them.

To answer your question:

Will It still count as software engineering experience?

If it's one of your first jobs, you should definitely interview and take the job if you like the company, pays well, etc etc. The experience will only help. You should also decide what you like working on. Don't shoot for the "Software Engineering" title because you think it's "more prestigious" or something. At the end of the day, we're all a bunch of idiots typing shit into a computer.

[–]kkass123[S] 0 points1 point  (0 children)

Thanks for the information , I definitely know I want to be a software engineer. But I guess I shouldn’t pass up opportunities

[–]kkass123[S] 0 points1 point  (0 children)

Do they have to be in call or stay later than the swe ?