Content
@
0 reply
0 recast
0 reaction
nyc-crypto-cabal-kid
@zinger
Alright I'm back, please roast my resume ๐ฅ
12 replies
5 recasts
64 reactions
ted (not lasso)
@ted
great start! would recommend being more specific about your contributions and quantifying their impact in order to take it to the next level. other feedback: - "built more frames experiments" reads as fluffy w/o any context, recommend adding in some context and any stats on growth or timeline - combining the dev and the community work feel off because the community work reads as hobby/interest section unless you include growth or retention or engagement stats - for the other roles + bullets, you do a great job of including the "what" but not the "so what?" behind what you did, i.e. did your work lead to increases in user retention, bids placed, notification reliability, etc.? - under Grove, would recommend axing "got a few paying users before pivoting" (too fluffy) and include X cusomters, $Y MRR before strategic pivot to XYZ - the format makes it read as if you work for farcaster vs. freelance dev / community builder - if there's lots of engineering references, recommend adding a link to your github
1 reply
0 recast
5 reactions
six
@six
I think you should reframe the first part based on whether or not you think the employer will know what Farcaster is or not Like have two versions of the resume with slightly edited wording
1 reply
0 recast
1 reaction
veekay
@veekay
thats one heck of a resume i love it
0 reply
0 recast
1 reaction
Varun Srinivasan
@v
it's pretty good. the one change i would make is talking less about specific features that you built at each role. the most useful datapoints are: 1. was the company legit? (implicit in name) 2. what results did you achieve? 3. what authority was granted to you by your employer?
1 reply
0 recast
13 reactions
JB Rubinovitz โโจ-โจ
@rubinovitz
As a hiring manager itโs unclear to me from this what type of software development you excel at and so Iโm left to wonder if you are a rapid prototyper. Being a rapid prototyper is fine, but if youโre a great sr engineer would need to show that more. Itโs also unclear what type of role you want/what your career story is. Itโs possible if youโre applying for product and SWE roles you have two separate resumes each drilling down into details. Eg on the SWE resume Iโd want to hear if you built the 10k concurrency system yourself vs using an API.
1 reply
0 recast
1 reaction
GENUINE JACK
@genuinejack
babson! nice!
1 reply
0 recast
1 reaction
Syed Shah๐ดโโ ๏ธ๐
@syed
Curious what this would look like if it only had bullet points that had a specific numerical metric and that metric was the only highlight of that sentence
0 reply
0 recast
2 reactions
Saadiq
@saadiq
What jobs are you looking for? Your resume shouldnโt be a biography but instead a persuasive argument for why you are great for the role in question. The more specific and quantitative you can be the better. I find it helpful to keep a copy of my resume that has as exhaustive a list of my accomplishments as possible and then for particular roles I use that as an input to a role specific version. My 2 cents.
0 reply
0 recast
1 reaction
big tone ๐ฉ๐งพ
@bigtone.eth
well im impressed
0 reply
0 recast
1 reaction
basement5k.โโจ-โจ ๐ก
@basement5k.eth
"GrEaT uSe Of WhItE sPAcE". and yes you can use me as a reference on your 2nd page....
0 reply
0 recast
1 reaction
dude
@imthedude
That's like... your perspective, man
0 reply
0 recast
0 reaction
rommy
@fingerguns.eth
Wait your name is really Zinger? Iโm on it.
0 reply
0 recast
0 reaction
