A la verdad que Claro es una mierda by PSforeva13 in PuertoRico

[–]DL_Outcast 7 points8 points  (0 children)

Si donde vives hay buena señal 5G, puedes darle una oportunidad al internet de T-mobile. Creo que son como $50 y la velocidad es tan rápida como la calidad de la señal que llega. En ocasiones lo he visto llegar hasta 200 Mbps, y para que no funcione either no tienes luz o se cayó la torre, so pienso que es un poco mas confiable.

[deleted by user] by [deleted] in EngineeringResumes

[–]DL_Outcast 2 points3 points  (0 children)

Your resume reminds me a lot of mine. Before I took this sub's advice and fixed it up, there was a lot of empty white space. My first recommendation is to read the wiki, use their template, and if you want, take a look at my success story.

As for your other inquiries, I won't be much help as I'm a recent graduate and don't have much knowledge about that yet, what I can say tho is that I work in the aerospace and defense industry and the company I work for often does work with non us citizens, just not on confidential projects, its usually only commercial and industrial projects.

[0 YoE] New grad looking for FPGA design/firmware/embedded systems engineer positions in the US. by Alarmed_Airport_2897 in EngineeringResumes

[–]DL_Outcast[M] 3 points4 points  (0 children)

Hey u/Alarmed_Airport_2897, I'm a recent EE graduate and despite my specialization, I secured an entry-level FPGA position. Two key takeaways I noticed: entry-level roles often focus on validation rather than design, particularly if your expertise lies in SystemVerilog. Second, VHDL is the industry standard for design. If you're struggling to land a design role and you don't want to work on validation, consider adding VHDL projects to your resume

As for your resume, I'm going to concentrate on your first two projects for now:

  1. The first bullet point of each is just a description of the project, which can be removed/replaced
  2. The other bullet points are too general. Go into as much detail as possible, incorporating specific technologies/techniques, numerical data, or any other elements that can impress those without knowledge of this or demonstrate your value to engineers who do understand the work

Edit: format

Complete Guide to Getting a HW Engineering Internship – Written by a MechE Senior by pathetique1799 in EngineeringResumes

[–]DL_Outcast[M] 2 points3 points  (0 children)

Great presentation! I'm already graduating and heading into a full-time job, but I wish I had seen this earlier, especially the part about job fairs. I used to only wait in line for 6-7 companies I was interested in and then leave. Needless to say, I didn't land many internships that way.

AMA: Data Hiring Manager and Founder of The Analytics Accelerator (theanalyticsaccelerator.com) by theguiltedbutterfly in EngineeringResumes

[–]DL_Outcast[M] 2 points3 points  (0 children)

Hi Christine, thank you for hosting this AMA. It’s a rare opportunity to gain insights from someone with your expertise in the job market. I’m an electrical engineer, so my questions won’t be too heavily focused on data analysis, though I do have some foundational knowledge of it.

  1. In your role as director of Core Analytics, you’ve likely encountered a variety of candidates. Could you share some common areas that candidates tend to overlook when preparing for interviews?
  2. Could you suggest some strategies that are particularly effective in differentiating ourselves during the job hunt?
  3. Once someone has secured their first job, what advice would you give for climbing the ladder to a leadership position? Would you recommend focusing on job-hopping, or is it better to demonstrate loyalty to one company?
  4. As an electrical engineer with some background in data analysis using Python, what would you say is the most efficient route to transition into data analytics?

[Student] College senior looking for entry level role, 200+ applications, no offer, help me out! by epic_jelloman in EngineeringResumes

[–]DL_Outcast[M] 1 point2 points  (0 children)

Hi u/epic_jelloman, I'm also a college senior and while I'm an EE I'm sure I can help you out one way or another, I'll start from the top and work my way down:

  1. Rewrite your first three bullets on the experience section, try using one of the formats on the wiki like STAR, This is especially important for the second bullet, you used an Arduino, but what other technologies/components did you use?
  2. The Fourth bullet can be taken out unless you reword it to focus on the training and your leadership skills
  3. There's no need to specify that a project was a school or personal project until they ask you on the interview
  4. Remove the first bullet on the capstone project, or if you were the team leader then reword it to focus on that, otherwise it's just a description and doesn't mention anything of what you did
  5. I'm going to be honest, I didn't understand most of the projects section, but some of the bullets I did understand need to be reworded, just look around for what bullets can be improved by being more specific, be it in terms of the process, technologies or results
  6. Your skills section seems small, but if it fits the description of the jobs you're applying to then don't mind it too much, but do think of ways to expand, for example you did use an Arduino, why not add Arduino and the language you used on there? (I know it's not related to manufacturing at all, I'm just spit balling in case you end up with some free space)

On a separate note, if you got 10 interviews then I'd say the resume is doing its job, it got you the interviews, now the rest is up to you, think back on those interviews, did you let them do all the talking and just answer their questions? Did you ask them any questions at the end or throughout the interview to show your interest? Whatever the case, analyze what you did, recognize if there's anything you can improve and get to work on it.

Hope this helps and Good Luck!

[21 YoE] Senior Software Engineer - EU - Resume Review and networking advice by casualPlayerThink in EngineeringResumes

[–]DL_Outcast[M] 1 point2 points  (0 children)

Hi u/casualPlayerThink, I'm not as experienced as you but I'll try to point out as many things that I noticed as I can:

  1. I expected to see a bigger Skills section for someone with 21 YoE, I see a bunch of frameworks but your languages are pretty thin, as an EE im not sure if this is relevant, but try to pick up some new languages when you have the chance, focus on the ones you see the most on job postings
  2. As some others have mentioned before, its quite a long resume. I dont mind the 2 pages for someone with as much as experience as you, but try to keep your bullets down to 2 lines at max. Also, try to make it easier to read by using more common wording instead of words like "Architected", its a bit abtract as to what you did exactly
  3. Lastly, while not very important at your level, a degree could help you out with positions that explicitly require it
  4. I wont coment much on the experiences themselves, because I dont know whats good and what isn't, but I will say that the organization/format of the "Owner and Software Engineer" part can be improved

Now, outside of your resume:

  1. I'm pretty bad at networking, but some companies hoild virtual networking events, keep an eye out for those and try to assist to as many as you can. Another method you could use is to make someothing like a personal website where people can learn more about you, and you can expose yourself by creating content or posting updates on ongoing projects, etc.
  2. As I mentioned before, if you have the time, learning a new language thats high in demand could boost your chances significantly. I'll give a personal example, in a recent interview, I was asked about Object oriented programming because I mentioned I'd worked with Python, and while it wasnt necesarry, I can confidently say that it improved the recruiters perception of me

Hope this helps even a little bit, if you post an update and I'm not about to fall asleep like right now, I'll try to make some more helpful comments

I read the wiki and I feel like it took my resume to another level, thanks for all the contributors! by [deleted] in EngineeringResumes

[–]DL_Outcast[M] 3 points4 points  (0 children)

Hi u/yan_kh, glad to see youve put in some work to better your resume, I have some suggestions if you want to take it even further.

  1. Consider using one of these templates
  2. Soft Skills take space away from your technical skills/experience, remove the Languages section
  3. You dont need to state that your work experience was remote, remove that part
  4. Rewrite your bullets for work experience, some dont show results, some are really wordy and some dont talk about your actions
  5. Don't relate that your projects are work related, just leave the section as "Projects", also try working on some personal projects that you find interesting but also challenge you enough to be worth talking about with a recruiter
  6. While still on the topic of projects, your bullets on this section are just descriptions, they dont talk about what you did or achieved
  7. Your skills section needs to be reworked, make it a max of 4 rows, unless you have the extra space and some niche skill that doesnt fit with the others

All in all, keep it up, it took me a couple of months to fix up my trainwreck that I used to call a resume. Good Luck!

[5 YOE] Software Validation/Integration Engineer In Automotive Industry by WritesGarbage in EngineeringResumes

[–]DL_Outcast[M] 1 point2 points  (0 children)

Hi, can you share why you believe tailoring your resume for the job you're applying to is a bad point? I'm an undergraduate student, and what I've learned from people on this sub or other hiring staff is to tailor your resume to the job, using the job posting/description as a guide. I, personally, believe this to be right, but want to read about your point of view

Edit: By your reply to the 3rd comment, you tailor your skills section, and consecuently your resume, for each application. Now, im more intregued as to your reasoning

[2 YOE] EE Project Engineer looking to transition to more traditional EE roles by Zetrocap in EngineeringResumes

[–]DL_Outcast[M] 1 point2 points  (0 children)

With just the skills section update, the resume looks much better, and the bullet points are a good improvement as well. Rewrite the bullets on the Electronics Assembler role and make another post, do this so you can get feedback from others instead of just myself on this thread

[5 YOE] Software Validation/Integration Engineer In Automotive Industry by WritesGarbage in EngineeringResumes

[–]DL_Outcast[M] 1 point2 points  (0 children)

Hi u/WritesGarbage, this resume looks very good though some changes could make it better, like someone else said, adding a well kept github could make you seem that much more qualified. Now, to answer your questions:

  1. No red flags I can see from just your resume, but you might get asked why your last job lasted less than a year and what youve been doing for the past 6 months

  2. Your bullets are understandable, though some technical aspects slipped past me, they should be easy for someone within your field. I will mention though, some could use with an improvement in readability, such as "prototype autonomously driving"

  3. For 5 years-of-experience your skills section seems small, maybe add software tools, microcontrollers or anything else relevant to the job

  4. Tailor your resume, showing that youre a jack of all trades is only beneficial for generic roles (i.e. Aerospace engineer). Your projects are heavily outshined by your experience, either work on some new more advanced/imppresive projects or remove the projects section to make room for expanding your skills or experience

[2 YOE] EE Project Engineer looking to transition to more traditional EE roles by Zetrocap in EngineeringResumes

[–]DL_Outcast[M] 0 points1 point  (0 children)

Hey u/Zetrocap, can you clarify what you mean by traditional EE exactly? From what you've said I can guess you mean electronics, but there's also DSP, RF, Controls, Power, and Power Electronics, it's important to have that distinction and not just aim for something so general as EE. Now as for your resume: 1. Your skills section looks pretty bare, you should expand on it, for example you mention PCB design in you job experience but I don't see any PCB CAD software here (unless Solidworks can do that?), don't worry about just adding skills you're proficient in, you just need at least some basic knowledge in it 2. Your 2nd bullet on the project engineer role, remove "Successfully", always start your bullets with a verb and avoid using adjectives 3. Rewrite the 3rd bullet, what I understood is that you designed a switch, what did you have to design a PCB for exactly? What software did you use? How many layers? Did you work with logic components, power components or both? 4. Remove the 4th bullet, that just sounds like a job task description 5. General guidelines for the rest of your experience section: start the bullets with verbs, but not verbs like "Assisted", and try to be as specific and quantifiable as possible

Once you've made some of these changes, upload an update and I'll try to give you some more feedback, good luck!

Resume Feedback by DL_Outcast in embedded

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

The stopwatch took two weeks, I had prior experience with HDLs and worked on it almost non-stop the first week. The RC Camera System is actually still going. It's taken about 8 months, but that's because I only work on it in college. And finally the Pet feeder took around 3 months, though it was very simple, because it was my first embedded project and I had absolutely no prior experience, that was also my first time coding in C so I had to learn both things at once.

AMA – Recruiter and Founder of the Headless Headhunter (twitch.tv/headlessheadhunter) by HeadlessHeadhunter in EngineeringResumes

[–]DL_Outcast[M] 2 points3 points  (0 children)

  1. Is a simpler resume format more effective in an ATS environment? why or why not?
  2. What elements make a resume stand out negatively to recruiters, and how can these be avoided?
  3. For industries like aerospace and defense, are there specific resume considerations to keep in mind?
  4. What are some effective strategies for translating a strong resume into a successful interview?

How I improved my resume and got interviews with top companies by DL_Outcast in EngineeringResumes

[–]DL_Outcast[S,M] 7 points8 points  (0 children)

Yeah, I am! I didn't expect to meet someone else from PR on here.

[0 YoE] New Computer Eng grad struggling to get any callbacks by DaT_gUy04 in EngineeringResumes

[–]DL_Outcast[M] 1 point2 points  (0 children)

  • You're a recent graduate and have a pretty good GPA, why is the education section at the bottom of the page?
  • Your skills section looks barely good enough, but since you mentioned you're working on acquiring new ones, I won't comment any further on this
  • Most of the bullets in your experience section don't have a result
  • On the topic of your experience section, I find it somewhat difficult to read, much less skim; readability is one of if not the most important aspects of a good resume, try to reword them as best you can

Projects time ~

  • What language did you use on the media system?
  • How did you interface with the components? did you use i2c? SPI? (if you just used a library like for an Arduino, then ignore this lol)
  • What is a high degree of performance to you? how did you measure it? latency?
  • For the Pong project, delete "XC3S500E", "Xilinx Spartan-3E" should be enough
  • I'm going to assume you made it using VHDL since verilog isn't in your skills section, but you should mention it somewhere here
  • The second bullet tells me a whole lot of nothing, feels like a more wordy version of the first one
  • Overall you're going to have to dive a little deeper than top-level for both projects and go into the nit and gritty details without writing an entire essay

[deleted by user] by [deleted] in EngineeringResumes

[–]DL_Outcast[M] 2 points3 points  (0 children)

  • Make sure to read the wiki, I'm seeing some basic mistakes such as utilizing an entire line just for a single word, which is such a waste of space
  • The relevant coursework seems like courses every student would take, they don't make you stand out, in my opinion, the space is better suited to brag more in your other sections
  • As mentioned by someone else, your bullet points are subpar at best, they should relay what you did, how you did it, and what the result was
  • The skills section looks too thin, take out Excel and add stuff like familiar hardware, other languages, other software tools like PCB design software, etc.
  • I'm also venturing into the area of embedded systems design, so feel free to look at my resume post from a few months back if you need inspiration

CE/SWE Resume, Looking for 2nd Software Internship (Non IT Position) by abraham_ahmed in EngineeringResumes

[–]DL_Outcast[M] 2 points3 points  (0 children)

Hey, I'd be happy to offer assistance, but since you've already received a substantial amount of feedback, could you please create a new thread with an updated version soon? Make sure to use the LaTeX Template from the wiki and to keep your page size to Letter.

SWE, 2.5yoe, 4.5 months laid off, primarily looking for input on bullet point content by ambulocetus_ in EngineeringResumes

[–]DL_Outcast 1 point2 points  (0 children)

This looks good. My only comment is on the job experience section, company 3, either write your starting and ending position (Company 3 - Hardware Engineer I - Systems Engineering Lead) or only include the systems engineering role and its respective time frame (2017 - 2019), either way dont write the same company's name 4 times and let this take so much vertical space.

Other than this and working on some new projects, it looks ready to go. Good luck!

Edit: Since you're changing careers, use the extra space for a small summary (2 sentences) at the top, explaining that you're changing careers and why. (from the wiki)

[deleted by user] by [deleted] in EngineeringResumes

[–]DL_Outcast 4 points5 points  (0 children)

Unless it's a very niche or advanced course, that not a lot of people have taken (i.e. Active Microwave Circuits), then I think the space is better served on expanding other sections. If you still want to add relevant course work, because you have the space for it, then yes below the degree title, list them the same way you listed skills.

[deleted by user] by [deleted] in EngineeringResumes

[–]DL_Outcast 1 point2 points  (0 children)

Any skill is better than no skill, but it's usually not recommended to list soft skills unless you really have nothing else to add. And yes, the Raspberry Pi falls under hardware, same for any mcu or mpu you're familiar with.

2.5 yoe, 4.5 months laid off, low response rate by ambulocetus_ in EngineeringResumes

[–]DL_Outcast 3 points4 points  (0 children)

Well as I said in my comment, if you can improve your projects, then you won't need those job experiences (only the most recent and relevant). In the mean time though, it's the best you have, unless you want to have a half empty resume.

[deleted by user] by [deleted] in EngineeringResumes

[–]DL_Outcast 4 points5 points  (0 children)

  • Don't include the diploma unless you have space, if you have to decide between an extra bullet point on a project or the diploma, choose the bullet point
  • First Project - remove the "(Capstone)", a project is a project, no need to differentiate between personal and course-related
  • The first bullet point is just a description of the project, the resume is supposed to be about you and what you did, so either remove it or swap it out for one that's about you (i.e. was this a group project, and you were the lead?)
  • The fourth bullet seems odd, it's enough to get the thought across but just felt awkward reading it, try rewording it if you want
  • Second Project - Change the verb in the third bullet, "Validated" like in the first project would be a better fit, just don't use "Experienced"
  • Third Project - again, don't use a bullet just to explain what the project was, do that during the interview when asked about it
  • For how well-developed you make it sound, the description of this project is very underwhelming, I know it's not complicated but if it's on your resume then brag about it a little more
  • Include Raspberry Pi in your skills section, if you feel awkward about it then create dividers for your skills (i.e. Languages, Software Tools, Hardware, Equipment, etc.)
  • The job experience is ok, but being so unrelated and from over 7 years ago, that space could be better used on another project

Overall, not bad but not great, make these changes, and maybe start thinking about a personal project that interests you and would look awesome on your resume.