Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Ask HN: Software Engineer Role Abuse?
6 points by rrgok on Oct 7, 2022 | hide | past | favorite | 5 comments
Disclaimer: I'm not a native english speaker. I hope and try to convey the message clearly without appearing rude.

This is not my first job as Software Engineer. I currently work as a solo Software Engineer for company, developing internal apps. This is a company which provide Network and Security services, so not primarily software. I'm not a freelance, so I'm their employee. I work for them part-time (60%). But the things I'm concerned about don't apply only for this situation, it has happened to me as a freelance too. The following could just be my impressions. So, I'm happy to be corrected if I'm wrong.

I'm worried that the Software Engineer role is getting abused in so many ways. What I mean by abused? The expectation people have that I have to do things not related to my job as Software Engineer. The current company I work expect me to (ordered, according to me, form the most unrelated task to the most related for a Software Engineer)

1. Design UI

2. Design UX and interaction design

4. DevOps from production, development and testing.

5. Project management for the software I write. From gathering requirements, give priority, estimation, deadline, sprints, gather user-feedback, schedule meeting...

6. Training for the software I write.

7. Customer support, help-desk, 100% of the time on call support for the software I write.

8. Write User Manuals, Administrator Manual.

9. Write Technical Manual

10. Design, Develop and Test the actual code, database...

Sometime I feel like my role would be just 9 and 10, maybe 8 also. I'm burned out. I feel people doesn't appreciate what I'm doing. Just today the CEO of the company messaged me in slack "Does't work shit" because the browser was somehow unresponsive. He didn't give me the time to look at the logs and see what was causing the hang-up. I don't know what to do honestly. One of the reason I choose SE because I don't like dealing with people. They don't know what they want from the software they want me to build for them, and I don't want to think for them (sorry if this appear insensitive). And I honestly don't want to participate in that kind of decision making roles. The company is not toxic or bad, but I feel like they don't truly understand how software development happens. There isn't a clear process from issue tracking to finished product.

Maybe SE is not a career I like, even though I spend my free time reading and learning new things about SE.

I hope to get some feedback from HN, because I don't know where else to discuss about it.




> I currently work as a solo Software Engineer for company, developing internal apps.

Yes, if you are the only dev working on internal apps, the variety of the work expected of you sounds about right. To specialize on just coding, you need an entire team working with you. It sounds like you would prefer to be on a larger team. There is nothing wrong with that desire, but that doesn't mean you are being abused.

At least, the variety of work expectations are not abusive - if the leaders are treating you poorly because of expecting too much work in too short of a time that is a different story.


If you got into software engineering, at least in part, because you prefer to not deal with people directly, then I imagine being the only software engineer for an organization doesn't give you a lot of space to avoid dealing with people. You might consider looking for work in another organization with more software engineers, where there is likely more opportunity for some people to be out front talking to users/customers, and for some people to stay behind the scenes.

For example, in many larger companies with large software teams, each of your bullet points may well be a different person, or even team of people, so if you wanted to focus on doing #10 and nothing but #10, you could do so.

And nothing wrong with that! Some people do their best work wearing a little bit of all of those hats, others do their best emphasizing just one or two of them.


For better or worse, people will often judge you and set expectations via a halo effect. If you're good with writing backend code they likely assume you are good at writing front end code and thus also good at UX.

I sometimes find that I need to reset expectations myself when a business person say for example asks me to create some vector art because I used to do web dev.

Be clear to your co-workers about where your strengths lie and where they would be more productively served by someone else.


I mean it sounds like you already have a pretty clear understanding of the issue: Some companies respect Software Engineer/Developer as a distinct and fairly high-status role, but some don't. You've discovered that working at the latter kind of company irritates you. Realistically, you're not going to be able to drastically change a particular company's culture, as a self-described non-people-person.


I have Sr. SWE(Backend) title and my work is limited to 9th and 10th point only and nothing more.. Rest are taken care by Product Owner + Business Analyst + Tech Lead + Scrum Master + Frontend Dev for frontend Stuffs + Devops team. All of them are individuals and they manage their own responsibility and do not interfere with other points out of their scope




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: