#2 YOE, My New Resume Starting Job hunt for Target Junior Android developer position

40 messages · Page 1 of 1 (latest)

worthy sundial
#

2 YOE, My New Resume Starting for Job hunt for Junior Android developer

#

2 YOE, My New Resume Starting Job hunt for Target Junior Android developer position

unique dune
#

Swap experience and skills section

#

Most of your relevant coursework is not relevant lol

#

Don’t write (on the job training)

#

If you are shooting for specifically android jobs, can you tailor your bullets towards more specific android methodologies?

carmine sluice
#

the resume is super cramped and hard to read/scan on an initial look

#

i would drop coursework alltogether, its been 3 years

unique dune
#

id keep if you had an android clas or something but doesnt seem so

carmine sluice
#

im not too worried about an android class, especially since it seems he has at least 2 years of android experience

#

could maybe just CONSIDER dropping the last job, and giving ur current job some breathing room. To make it easier to digest

unique dune
carmine sluice
#

theres also 0 metrics on the resume, what impact did all of that stuff you did have?

worthy sundial
#

hello guys thanks for the feedback's, here is my new updated resume hopefully it will be slightly okey 😆 .

worthy sundial
carmine sluice
#

drop the blurb at the top, not sure why that was added blobcatsipwoah

#

still missing metrics as well

#

looks less cramped though and definitely easier to read

worthy sundial
#

Hi Guys here's my update resume I already add metrics and remove not relevant for andorid position.

unique dune
#

if so downloads dont make too sense

worthy sundial
#

yup

unique dune
#

im not sure if i really like you reusing 'ensuring 100% x/y'

#

you used metrics incorrectly for that then, except for the internal project reviewer app, since 1000 downloads makes sense and is real metrics

#

we are moreso saying if there are parts that were improvable like load times or response times for backend to frontend apis and you sped it up too

worthy sundial
unique dune
#

depending on how fast it actually was

#

or maybe sped it up by 250%

worthy sundial
#

@unique dune can you specify on which bullet point is wrong if that ok with you thanks i really appreciate it.

unique dune
#

achieved 100% accurate

not a big fan of this

#

i love the sentence up to that point

worthy sundial
#

Hahaa now I get it now a real measurements ah! Sorry I didn't get it in the first place sorry my bad😅. I think I'm gonna need some sleep then edit this.

carmine sluice
#

some of ur bullet points are realllly long

#

i think next step would to now be more concise and cut out fluff words

#

for example in projects u say “popular API blah blah” cut that bit, “Leveraged Movie Database API to retrieve movie data dynamically” or whatever. No need to say “seamlessly” “popular” etc

#

and +1 to what the other user has said, your use of metrics don’t make sense

#

“Proactively developed…” -> “Created Unit tests using Junit 4 and Mockito, ensuring code quality and achieving XY% branch coverage” . Thats all that needs ti be said there, all the rest is fluff (not necessary to say nor interesting).

#

words like “successfully” are also unnecessary, as if its on the resume it can be deduced that it was successful. If you failed to complete a project, I doubt you would mention the project nor say “Failed to showcase app..” just say “Showcased”, “Delivered app”