Timeline for Taking over another fired developer's role
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2021 at 8:13 | comment | added | Farid | Agree. OP, I have done both: a specialist software developer in big company and a generalist IT guy (software dev + test + devops + infra) in a small company. They both have pro and cons. Some people would prefer to be one over the other, some have no problem with either choice. It is up to you to experience it, and then you would have to decide which one do you like. | |
| Apr 4, 2021 at 14:29 | comment | added | cjs | If you're going to be a really good senior developer at some point, you'll need at least some experience in all facets of development, from business-case planning to the support process after the software is released. (A system won't cohere well unless at least someone in the development team has a reasonable understanding of things end-to-end; I would demand this of any developer I hired, or be prepared to train them to some degree on all aspects of the system.) So this sounds like a good opportunity to get exactly that sort of experience. | |
| Apr 3, 2021 at 8:28 | comment | added | Aaron | Agree. My last job at a small business was customer support, software developer, database developer, front and back-end web developer, and info-sec officer. While there was no bump in pay (an annoyance), I was gaining a massive skill-base that I then took elsewhere for double my previous pay. | |
| Apr 3, 2021 at 7:52 | comment | added | toolforger | Excellent answer, but I think the last bullet point under "Cons" is too pessimistic. Even if he's a generalist, he'll have more skills than before and be able to grab more job opportunities. | |
| Apr 2, 2021 at 19:35 | comment | added | cela | @Donald or they just want to see how he performs and provide a raise based on that. | |
| Apr 2, 2021 at 17:19 | comment | added | Donald | Don't get me wrong, it appears the author's career goals align with taking the job, but we both have different experiences so who are we to determine that. I just see a huge increase in duties without a pay raise as a red flag that perhaps something isn't right with the company. | |
| Apr 2, 2021 at 17:16 | comment | added | Kevin | @Donald - sort of. I mean, some places (especially small businesses) you have to push for your own raises. I wouldn't view it as a red flag - more something the OP needs to keep in mind: they're likely going to need to negotiate a larger salary in the coming months. Personally, in OP's shoes, I'd take the job (even without an immediate salary increase.) Then, 6 months later, use the success in the position as a bargaining tool - not only will they be able to point to a (presumably successful) track record, but also have a much stronger BATNA (to leave) since they'd have dev experience. | |
| Apr 2, 2021 at 17:07 | comment | added | Donald | This is a good answer, and I agree with all the points, but the only concerning thing is the fact those additionally duties typically come with adequate pay increases. Otherwise the guy who had to learn 20 different things never stay long enough to learn 5 of them. | |
| Apr 2, 2021 at 14:03 | history | answered | Kevin | CC BY-SA 4.0 |