#2 YOE looking for feedback

14 messages · Page 1 of 1 (latest)

unborn turtle
#

I'v'e been trying to brush up my resume. I think I've done a pretty good job (I've spent several weekends on this!) and I'm looking for general feedback as well as answers to a few questions I have...

  • Are my points too long? Too short?
  • Should I have more detail on the specifics of my work?
  • Do I have too many bullet points? Could I still add more?
  • Is it readable? I feel the font might be a little too narrow.
  • Should I use a more 'traditional' template?
  • Do the first few points sound like bullshit?
  • Are any of the points too mundane/unimpactful?
  • Should I add a "summary" point describing my role for each experience?

I've read that I should make sure the points fit on one line, but I can hardly get enough detail in with two. I do have some truncated one-line versions of some of them that keep the impact but omit even more details on what I actually did...

redacted-screenshot.png
fair stratus
#

Points are a bit long, but still okish. Font is fine. Definitely check if the template is ATS compatible or not.

#

I wouldn't think a summary would add value. I also wouldn't add more text, as it is already borderline text heavy.

#

What is a payment method display API?

#

You are writing you have 2 YoE. Was the Oracle job an intern position?

#

A shorter version of the first bullet point could be: integrated backend risk models on React Native frontend via AWS Lambda, increasing payment success rate and leading to 450M rise in gross annual sales.

#

Skills list is consistent with projects, easy to read so it highlights your key skills.

#

You could consider using full words, like low severity instead of low sev

#

If the template is ATS friendly, then you could test this CV in real applications, already looks fine.

floral halo
fair stratus
unborn turtle
# fair stratus What is a payment method display API?

I'm referring to an API that's adapting a complex object pertaining to the state of a purchase into "display data" (some structured JSON, more or less) for the payment methods being used. A rendering service calls this API to get that JSON and throw it straight into some rendering templates.

Maybe I need a better way to phrase this?

unborn turtle
unborn turtle