Timeline for Resume: How to quantify my contributions as a software engineer?
Current License: CC BY-SA 4.0
24 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 8, 2021 at 17:22 | answer | added | Zain Saleem | timeline score: 1 | |
Nov 12, 2020 at 12:51 | answer | added | Gabor Zold | timeline score: 0 | |
Oct 4, 2019 at 9:32 | comment | added | Austin France | A skills matrix on the first page below the initial basic info about yourself. List skill (such as language, o/s, database etc) your evaluation of your level of experience (basic, adept, expert) and the number of years experience. Present in a compact but readable table. Pages 2+ of the CV can fill in the details such as education, companies worked for, details of projects worked on etc. | |
Oct 3, 2019 at 1:07 | answer | added | joshstrike | timeline score: 2 | |
Sep 18, 2019 at 6:00 | history | tweeted | twitter.com/StackWorkplace/status/1174201413376913409 | ||
Sep 11, 2019 at 20:06 | answer | added | Andy Lester | timeline score: 15 | |
Sep 11, 2019 at 16:41 | comment | added | Jacob is on Codidact | I have interviewed people with this kind of CV and rejected them for being too "corporate bullshit"-minded, and appearing to be more competent at interviewing than actually working. I suggest not even bringing the numbers up unless you have something very concrete with clear causality. | |
Sep 10, 2019 at 21:23 | answer | added | wallyk | timeline score: 2 | |
Sep 10, 2019 at 19:26 | comment | added | Gabe Sechan | To any software engineer, a resume with stats like that smells like bullshit, and is more likely to get you rejected than hired. Concentrate on what you built, skills you used, and technical accomplishments. If you're going to give numbers, give it on technical things that you actually did (cut latency in half), not "doubled growth" which an engineer has no direct effect on. | |
Sep 10, 2019 at 18:20 | answer | added | tbdevmanager | timeline score: 19 | |
Sep 10, 2019 at 17:52 | comment | added | PhD | Try MEDIC phrases: Maintained, Eliminated, Decrease, Increase, Create - they serve as good proxies for measures without the need of objective metrics. Example, “increased user engagement by doing X”, or “decreased downtime by tweaking architecture” etc. Works just as well. | |
Sep 10, 2019 at 14:49 | comment | added | MonkeyZeus | I would be really interested to know which industry can support an almost 1:1 ratio of employees to customers. This doesn't seem scalable; is the startup still operational? | |
Sep 10, 2019 at 14:48 | answer | added | Robin Bennett | timeline score: 1 | |
Sep 10, 2019 at 13:03 | history | became hot network question | |||
Sep 10, 2019 at 10:54 | comment | added | Justin | And this: workplace.stackexchange.com/a/136895/93518 (disclaimer:Me! Me, again) | |
Sep 10, 2019 at 9:51 | comment | added | nvoigt♦ | Related: workplace.stackexchange.com/questions/136901/… | |
Sep 10, 2019 at 9:13 | answer | added | Andrei Goldmann | timeline score: 9 | |
Sep 10, 2019 at 7:44 | vote | accept | earthling007 | ||
Sep 10, 2019 at 6:50 | answer | added | virolino | timeline score: 121 | |
Sep 10, 2019 at 6:33 | answer | added | Player One | timeline score: 69 | |
Sep 10, 2019 at 5:35 | review | Close votes | |||
Sep 11, 2019 at 17:39 | |||||
Sep 10, 2019 at 5:26 | history | edited | earthling007 | CC BY-SA 4.0 |
edited title
|
Sep 10, 2019 at 5:04 | history | edited | earthling007 | CC BY-SA 4.0 |
edited title
|
Sep 10, 2019 at 4:59 | history | asked | earthling007 | CC BY-SA 4.0 |