Timeline for Re-negotiating a raise after informally accepting
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 17, 2016 at 15:04 | vote | accept | Luke | ||
| May 11, 2016 at 14:45 | comment | added | user17163 | @RaoulMensink it's possible to have the experience to be a Senior Developer without having the role-specific knowledge and skill set needed to be effective. | |
| May 11, 2016 at 13:25 | comment | added | MK2000 | That's a point someone else made in the main comments: if OP has just graduated, they have little to gain in working somewhere in which they will not be learning. | |
| May 11, 2016 at 11:42 | comment | added | Raoul Mensink | @Thebluefish how can someone he trained be Senior developer when he himself is not? | |
| May 11, 2016 at 9:03 | comment | added | user17163 | +1 for "but 'senior' is usually a matter of experience." - This is a distinction that many people will take as someone with deep knowledge about multiple aspects of a given role. In the software industry, "senior" many times means skilled in multiple areas with 10+ years of experience. Calling yourself "senior" after having recently received your degree can come off as arrogant and leave a bad taste. Let the skills come first, and leave the titles behind for now. | |
| May 10, 2016 at 20:10 | history | edited | MK2000 | CC BY-SA 3.0 |
added 161 characters in body
|
| May 10, 2016 at 20:03 | history | answered | MK2000 | CC BY-SA 3.0 |