Should I Take a General Software Engineering Job or Hold Out for an AI/ML Role?

0
0
Asked By MellowPine42 On

I'm based in Greece and have about three years of experience as an AI/ML Engineer and Project Manager at a major research centre, where I worked mainly on EU-funded projects. I have a BSc in Computer Science, two MSc degrees in AI/Data Analytics and Robotics, and more than 15 publications focused largely on AI and Computer Vision.

I left because the role had gradually shifted away from hands-on implementation toward meetings, project coordination, reviewing colleagues' work, and technical guidance. I don't plan to pursue an academic career and was concerned that staying too long in a research-focused environment might make it harder to move into industry.

I recently received an offer from a small Greek software company with two founders that is hiring additional employees. The position is fully remote and officially titled Senior Software Engineer, although the initial work would involve general frontend and backend development for an EU-funded project and commercial contracts. The company says it may introduce AI-related work later, but there is no specific timeline or guarantee. They describe the workload and environment as fairly relaxed.

My previous income was approximately €1,750 net per month as a contractor, paid over 12 months. I initially told the company that I would seriously consider the position at around €2,000 net per month or more, taking into account that Greek employees commonly receive 14 salary payments while contractors are usually paid over 12. They seemed comfortable with €2,000 immediately, so I'm wondering whether I anchored too low.

Would accepting this role damage my chances of moving into senior AI/ML positions later, particularly if I spend a year doing little AI work? How do recruiters view experience from EU-funded research projects and small companies? Should I accept the offer while continuing to apply for AI/ML roles, and what salary figure should I give them—perhaps €2,300–€2,500 or €2,300–€2,600 net per month?

4 Answers

Answered By QuietHarbor17 On

The small company itself is not necessarily a negative. Future employers will care more about what you actually built, the technologies you used, your ownership, and the impact of your work than the company’s headcount. Your research-centre background can also be valuable, but you should translate it into industry language: production systems, software architecture, delivered projects, stakeholders, deadlines, and business or user outcomes rather than only publications and research goals.

Answered By NorthwindM4 On

Since they accepted €2,000 without hesitation, I would come back with a higher target. Something like €2,300–€2,600 net per month, adjusted clearly for whether there are 12 or 14 payments, gives them room to counter. If possible, use one target number rather than a range, because employers usually treat the bottom of a range as the real figure. Also compare the total annual gross compensation, benefits, taxes, leave, and employment protections—not just the monthly net amount.

Answered By SilverMaple63 On

You probably gave away some negotiating leverage by naming €2,000 first, but that doesn’t mean the offer is bad. You can explain that after reviewing the responsibilities and compensation structure, your preferred target is higher. If they cannot move, decide whether the experience and financial stability are worth it, then set a personal deadline for reassessing the role. Keep your AI skills active through practical projects, applications, and relevant technical work so the transition back is easier.

MellowPine42 -

I’ve already researched local salaries and the original figure is not unreasonable for Greece, but their quick agreement made me suspect there was room to ask for more. I also dislike leaving a small growing company immediately, so I’m trying to balance loyalty with protecting my long-term career direction.

Answered By CedarLane8 On

If you don’t have another offer, accepting it is probably reasonable. A general software role shouldn’t automatically hurt your career, especially if you can point to real engineering responsibilities and measurable results. Keep applying for AI/ML positions, though, and don’t stay indefinitely if the promised AI work never materializes. A short period of four to six months is unlikely to ruin your CV, particularly if you can explain that you were looking for a better long-term fit.

MellowPine42 -

That makes sense. My main worry is that AI/ML is changing so quickly that even a year away from the field could make me less competitive, but I also don’t want to reject a solid offer when I currently have no alternative.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.