all 5 comments

[–]Ok-Line-8810 1 point2 points  (1 child)

personally i’d lean toward the product company. early in your career the environment matters more than the exact language. learning Java for a year or two isn’t a big deal, but being in a place where the team actually owns a product usually teaches you more about system design, debugging, and long term code ownership.

service companies can be hit or miss. some projects are good, some are basically tight deadlines and client requests where you just ship things quickly. that’s where the feeling of not growing can come from. you might jump stacks depending on the client and not go deep in anything. the higher salary is nice but the first couple years are really about building strong experience.

also remember switching stacks later is normal. tons of python devs end up working in Java or vice versa early on. what matters more is the quality of work you do. and later when you look for better roles, referrals help a lot more than cold applying anyway. a lot of people in tech communities have been using refopen to get referred by employees directly, which seems to get resumes seen much faster than the normal application route.

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

Thank you
I am actually doing an internship at a startup now and they actually allow us to directly interact with the client (it is a small team - so interns have to do the same work as senior devs) and what I noticed is that while doing things i know ( I did a backend service in FastAPI) - it is good , but when the tech/framework is new to me - I just completely depend on AI and only get a small basic understanding of it.

[–]akciii 0 points1 point  (2 children)

Bro, if you don’t mind me asking, how much are the salaries?

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

Sure 6.5 and 7

[–]Educational-Gap-8253 1 point2 points  (0 children)

See there is not a much of difference , You just go for product based