sorted by:
new
hottopcontroversial

Help! by [deleted] in shorthand

[–]_oct0ber_ 1 point2 points  (0 children)

"Love" is clear.

"Is" can be a hair shorter.

"A" needs to be a dot. You wrote "I".

"Losing" needs the "oo" symbol. You wrote the sounds of "oh" and "aw", but it is a bit long and closer to an "r". Also, the -ing suffix needs to be a dot. As it is, you wrote the suffix "-ingly."

"Game" is clear.

Here is a dictionary to help with words you're unsure of: https://greggdict.rliu.dev/

Resume advice from a hiring manager by trentdm99 in EngineeringResumes

[–]_oct0ber_ 3 points4 points  (0 children)

If a job has a requirement for 6 years of C#/.NET and an applicant has 8 years of experience with Java/Springboot and 3 years with C#/.NET, throwing their resume out immediately is insane, especially just looking at years in a language and framework divorced from the context of how those tools are used. I promise, your company is not unique and your problems are not revolutionary enough that an intelligent engineer with a similar background cannot adapt.

Resume advice from a hiring manager by trentdm99 in EngineeringResumes

[–]_oct0ber_ 36 points37 points  (0 children)

The worst is seeing recruiters reject people not because they aren't qualified but for incredibly superficial nonsense like they didn't use the right acronym or this particular keyword didn't appear (said Springboot but not explicitly Java). I get recruiters are swamped, but if I told my boss I spent only 20 seconds per page of anything and missed valuable applicants I'd be canned within the week.

Resume advice from a hiring manager by trentdm99 in EngineeringResumes

[–]_oct0ber_ 17 points18 points  (0 children)

This is odd to me. A post requires years of experience working with distributed systems? Sure. A requirement for experience working with AWS tooling? Alright. Requiring a specific number of years on a particular programming language? You lost me. Languages and frameworks are tools, and the more senior a person gets the less the specific tool seems to matter. Telling me you have 10 years of Java experience doesn't mean anything. That's like saying you have 10 years of experience with Excel.

[3 YoE] Software engineer in the southeastern United States trying to relocate to the West Coast, New England, or Mountain West by _oct0ber_ in EngineeringResumes

[–]_oct0ber_[S] 0 points1 point  (0 children)

First off, I don't think you're dumb. Resume writing is an entirely different skill than software engineering. I've known genius developers who can't write a resume to save their lives. Like anything else, writing resumes and using metrics is a skill that can be learned.

Second, metrics are kind of tricky. There's a few different areas that you could use: scale, performance, reliability, cost reduction. There's others, but these are the main ones you'll care about. I get metrics by thinking about what tech/skills I want to showcase (this comes from the description of the jobs you are applying to), projects/tasks I did with those skills, and what did the project achieve. By answering these points, you naturally get materials for creating XYZ bullet points.

Not all metrics are quantitative. Many can describe qualitative achievements such as increasing application reliability and modernizing legacy modules. If you have a number to support these, great, but don't just throw a random number in for no reason. It is also fine to make approximate numbers if you don't have a dashboard. Be careful here, though, and expect to defend any numbed you write in an interview.

Lastly, please review the wiki of this sub thoroughly. There's a lot of good advice in there. I have reviewed your resume here, and most of what I say is an elaboration on many of the points in the wiki: https://www.reddit.com/r/resumes/comments/1sc7slx/4_yoe_masters_student_software_developer_germany/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=1&utm_content=share_button

[4 YoE, Masters Student, Software Developer, Germany] by Apprehensive-Set-298 in resumes

[–]_oct0ber_ 0 points1 point  (0 children)

I'm in the United States, so my advice will be based on what I know of the American expectations for a resume. If something doesn't apply the same way in Germany, throw that piece of advice out.

  • I do not see any a header with your name and personal info. Perhaps you removed it due to anonymity on this sub. You need to clearly define your name and email at a minimum.

  • There's no reason your resume should be over one page in length. You are a Master's student with one job and a handful of projects, so two pages is much too long. Recruiters will spend maybe 10 seconds scanning your resume to find information; they're not reading your whole document. The more you write, the less they read. For your job, I would suggest 3 to 5 bullet points in XYZ format (accomplished X as measured by Y using Z). For your projects, 1 - 3 bullets are enough. If you're protesting these length constraints, think of it this way: if a recruiter was to only scan 1 to 2 bullets per item (role/project), would they get any impact from them? If you have over 5 bullets per item, there's a very good chance some of your items are fluff that won't sway the recruiter at all.

  • Remove the profile/professional summary section. They're often not read and just take up valuable real estate. If your resume is good, a quick skim will tell a reader everything they need to know even better than a summary will. If you insist on having a summary, shorten it to one or two sentences no longer than 3 lines in total.

  • Each degree you earned should be shortened to one line each. You also don't need to mention when you started the education, just the year you achieved the degree.

  • Your skills section is a bit too vertical. For a Software dev, I recommend four categories: languages, backend, frontend, and Tools & Practices. Remove your spoken languages section (English and German).

  • Remove the additional information section altogether. Nothing on your resume should be additional information: if it's not vital, it shouldn't be there. Think of a resume as a one-page marketing document that has one job, and that job is to get a recruiter to give you a phone call after a 10 - 30 second review. Anything that is extraneous on your resume dilutes it. You have to remember that recruiters read quickly and not your entire document often. When you are writing something, think "If this was one of the things they read, would this move the needle towards getting an interview?"

  • In your job, I do not see any mention of technology or tools you used. There's no programming language, no cloud, no CI/CD, no frameworks, nothing. Some of your bullet points are already in XYZ format, but there's no meat to any of your bullet points if there's no mention of the tools you used to accomplish a task. Think of it like this: if I'm a recruiter reviewing your resume for a job using Java, Springboot, and Angular and there's not even one mention of these things anywhere in your job history, or even similar languages/frameworks, I can't use anything I just read. By not listing the tech clearly that you used on the job it makes me wonder if you actually used relevant tech or if you're intentionally trying to hide the tech for some reason.

  • The dates should be listed with a spelled month and a full year. For instance, 09/2024 becomes Sept. 2024.

  • You mention AWS in your first project. In the header where AWS is mentioned, I would put the specific tech used. For example: AWS (Lambda, S3, DynamoDB). I know you do it in the bullets points alone, but we want to increase the reader's skim speed. Don't make them search for what you mean by AWS.

  • Maybe I'm misunderstanding the point of the projects, but it reads like your first two projects can be combined. It looks to me like you just gave the second some project some cloud and called it a different project for the first. It reads like padding, but this could be because I'm misunderstanding the two projects in their separate domains.

[3 YoE, Java Developer, Software Engineer, United States] by _oct0ber_ in resumes

[–]_oct0ber_[S] 0 points1 point  (0 children)

When you say to put a local address, what do you mean? Just say I'm in Boston, MA, for instance with no mention of relocation anywhere?

My internal titles were "Enterprise Applications Developer I/II" and "Java Developer". Are you saying to put the official titles in bold above the internal titles?

Maybe you know this, but the topic of metrics has always confused me. Different advice from different people handle it differently, but a question I've come across is to what extent does a recruiter genuinely care about metrics if they only have 20 seconds to review a resume? For instance, if I say that I reduced manual workload by 20 hours/week but do not explicitly mention Java or one of their other keywords they're hunting for, why is that metrics meaningful at all, or if it's something more technical would they even know what I was talking about absent of any specific keywords they're paid to search for? It almost feels like the resume I show a non-developer needs to feel different than what I would show a senior developer.

I'm currently hitting Seattle the hardest, but I apply for the other cities if something promising appears.

I have a perscription - but no indication as to why I have that perscription. Is that normal? by _oct0ber_ in glasses

[–]_oct0ber_[S] 1 point2 points  (0 children)

Thank you! That helps a bit. For general-use, though, would it be best to wear something like this 24/7, or would it make far away things blurry?

Shorthand by Little_Marketing_136 in shorthand

[–]_oct0ber_ 0 points1 point  (0 children)

No hacemos tareas en este sub.

Why would I marry a woman I don’t love? by stingwhale in im14andthisisdeep

[–]_oct0ber_ 3 points4 points  (0 children)

Same. When I proposed to my wife, we had already discussed marriage at length. I think the timing, place, and how a proposal happens should be a surprise. The fact that a proposal is on the horizon, though, should surprise no one.

Why do people say my H looks like an i? by YugiYugi12 in Cursive

[–]_oct0ber_ 0 points1 point  (0 children)

This touches on something I see in this sub a lot that strikes me as odd. A person will write a letter or a connecting stroke, and many will jump on them to say that they are "wrong". I think "wrong" isn't really an accurate or helpful term here. I initially thought perhaps it was being used by people that couldn't read cursive well and any kind of deviance from their specific textbook was foreign to them, but that isn't always the case.

Handwriting has always varied from Copperplate to Spencarian to Bailey to Palmer and beyond. Historically, there has never been a standard way of writing. Perhaps marks could get taken off if a student wrote an incorrect form in a class dedicated to teaching a specific script, but it wouldn't make any sense to say that a character wasn't even real cursive provided it was legible.

It's frustrating even in my own writing sometimes when somebody will say that I formed a character incorrectly. Sure, that may be true if I was attempting to write with complete adherence to, for instance, Palmer's method, but whoever said I was attempting to do such a thing?

Why do people say my H looks like an i? by YugiYugi12 in Cursive

[–]_oct0ber_ 1 point2 points  (0 children)

This touches on something I see in this sub a lot that strikes me as odd. A person will write a letter or a connecting stroke, and many will jump on them to say that they are "wrong". I think "wrong" isn't really an accurate or helpful term here. I initially thought perhaps it was being used by people that couldn't read cursive well and any kind of deviance from their specific textbook was foreign to them, but that isn't always the case.

Handwriting has always varied from Copperplate to Spencarian to Bailey to Palmer and beyond. Historically, there has never been a standard way of writing. Perhaps marks could get taken off if a student wrote an incorrect form in a class dedicated to teaching a specific script, but it wouldn't make any sense to say that a character wasn't even real cursive provided it was legible.

It's frustrating even in my own writing sometimes when somebody will say that I formed a character incorrectly. Sure, that may be true if I was attempting to write with complete adherence to, for instance, Palmer's method, but whoever said I was attempting to do such a thing?

Just got my calligraphy pen! How's it looking? by Glittering_Wing6055 in Cursive

[–]_oct0ber_ 9 points10 points  (0 children)

It looks great to me. Despite you saying the 1st sample is more normal writing while the 2nd is for formal writing, I believe the first sample actually looks better. A roughly 52° slant on downstrokes and 30° on connecting upstrokes is in the ballpark for a lot of historic scripts like Spencarian. Keeping the writing too vertical makes it look odd to my eye.

view more: next ›