3 ms·
Don't overthink it. There are no standards for job titles in the software industry. Recruiters, HR, and hiring managers already know that title inflation is r
by ThrowawayR2 5y ago
Don't overthink it. There are no standards for job titles in the software industry. Recruiters, HR, and hiring managers already know that title inflation is rampant and "senior" (and titles beyond that) are often handed out like candy. That's why interview loops are long and painful in this industry (I'm not defending it, merely describing the way things are) and tales of "senior" people who are objectively not that good are legion. I usually set my expectations when evaluating a resume based on the number of years of industry experience rather than the job title and that seems to be a common practice.
So relax. If your job title in the HR records was "senior", there's no reason not to put it on your resume.
[EDIT] As a brief follow-up, if the source of your concern is the job titling system used by FAANGs (SWE 1, SWE 2, SWE3, Senior SWE, Principal SWE, ...) as seen on levels.fyi, check to see if your employer is using an alternate job titling system used at a few employers where "senior" is the first level above the introductory level (Engineer, Senior Engineer, Staff Engineer, Senior Staff Engineer, Principal Engineer, ...).
- emestifs 5y agoYes, there's a similar system here (Junior, Engineer, Senior, Staff, Senior Staff, Principal, Principal Staff, etc...among other variations of Manager, Engineering Manager, etc). Thanks for the response. My only concern is if I put senior and I apply for a 2-3yr experience position, I feel the "senior" title on resume is going to automatically increase the scrutiny I'll see during interviews and screens. Which is fine, but a bit misleading to them and misrepresentation of what I'm able to bring to them due to how they may interpret "Senior" at their company.