#SWE, 20 YoE, Feedback Wanted
25 messages · Page 1 of 1 (latest)
which is fine but I would like to see at least one or two more bullets in you last two job listings that are pointing to something more tangible you have done
hmm to be honest you have double experience than me so for me it's not an easy thing to jugde here
I've done 20 interviews this year and I had most feedback in the interview on concrete things
like I had bullet point:
- improved web app speed by 50% using this approach
should be probably your first or second bullet point in the last two jobs
basically something you want to talk about in the interview for at least 5 minutes
yeah, you just point out things you have done, think about achievements you would point out to your manager in yearly (or quarterly or whatever) reviews
I like the second bullet, maybe throw some number as well
into 20+ microservices using asp.net
and maybe try to say what was the result of it
like nice you split the monolith into microservices, but what benefit it gave the project?
IMO hiring managers only care about tech stack for the position they are hiring for
yeah well IMO, what is my strategy for CV is that I am making points for my promotion in the jobs I had if that makes sense
so I am not talking to potential employers but my past managers and I am trying to prove to them they shold promote me / icrease my salary because I X/Y/Z
If you would need to choose between technologies and impact made, I would vote for impact.
If you used a certain language or tool 10 years ago, that is not the same as the stack they are hiring for, then that info is less relevant for an interview decision than the fact that you used technology to make a business difference for that company.
The technology itself is not transferable to the new role, but the fact that you are able to make impact is.
fully aggree with that
like he should point out something like that: split monolith app into 3 separate microservices using ASP.net and Docker removing interdependecies between other teams and creating more stable pipeline
better if he has numbers
This is better and pointing to the right direction.
Maybe possible to take it even further? For example why was the Angular app migrated to AWS? Did reliability improve or performance or maybe time to market for changes? If so, then the bullet could be something like improved performance of Angular app by X% via migrating from on-premise to AWS, using ECS, EC2, etc.
if you say CICD pipeline was reduced from 10 mins to 3 mins because of that
or 66% reduction to deployment time
hopefully you get what I mean
Enabled new SaaS business model instead of per license by succesfully moving Angular app from on-premise to AWS, while keeping the same service level.
If you know that the new business model was successful, you could add that also: Enabled new SaaS business model leading to increased sales...
Imo I think this is going in the right direction. The cherry on top would be metrics if you have them or remember them. If you look up the STAR method, that is a lot of what the advice has been and what I would say. Your experience is impressive, the next step is to show that your impact was equally impressive