| Episodes | 60 |
| Mentions | 102 |
| Cited here | 26 |
| First — last | #4 — #729 |
| Top guests | David Kronstein, Colin, Shahriar Shahramian |
| Related | fpga |
A resume is the document by which a candidate for an engineering position presents qualifications, employment history and technical work to a prospective employer. Its function is narrow: the sole purpose of a resume is to obtain an interview, since hiring decisions are made at the interview stage rather than from the document.[124] Because a single opening routinely draws on the order of a hundred applications and a hiring manager can interview only five or six candidates, the resume is usually the only evidence available for the cut that produces that shortlist.[230] Screening for engineering roles targets specific demonstrated experience rather than general capability, so an EDA vendor hiring a board designer looks for prior use of that vendor’s own tool and a large number of boards already designed.[41]
Screening
Resume readers give an individual document on the order of seconds on the first pass.[230] Screening loads of roughly a hundred resumes per opening are routine, and one advertised engineering position drew 29 local applicants alone; interviewing every applicant properly would have taken weeks of full-time work, so the field is cut on the resumes instead.[230] Human screening at that rate both loses good candidates and admits poor-fit ones.[601]
Presentation quality therefore operates as a tiebreaker rather than a primary criterion. For an obvious standout candidate, defects such as spelling mistakes are overlooked; for borderline candidates competing for a small number of interview slots, presentation decides which one is called.[230] Conventional expectations such as dress, spelling and formatting are ordinarily met rather than used to differentiate, so that a candidate’s distinguishing evidence is technical work, and standing out on those conventional items forces extra effort later to recover.[230] Resume presentation matters more than interview attire, because rejection happens at the resume stage whereas reaching the interview already implies the resume passed.[230]
Screening is often automated before any engineer sees the document. Automated application systems reject candidates on mechanical criteria such as a keyword-match percentage, which spelling variants like colour versus color can move, and fixed grade-point cutoffs, usually with no human review and no feedback to the applicant.[262] Filters have rejected candidates whom the hiring team had explicitly said it wanted to talk to, on grounds as mechanical as an unchecked form field and with no notification.[601] Even employers that publicly de-emphasise formal qualifications still route applications through an HR screen, so a resume must satisfy that screen’s checklist before an engineer reads it.[530] University career-services guidance is built around the intake templates of the large employers that recruit on campus, which suits those employers’ screens and is less applicable to applications made outside them.[530] At many university career fairs the company representatives collect resumes but direct every applicant to the online system regardless, so the fair functions largely as advertising.[262]
Documents that fail to produce an interview are not necessarily discarded. Resumes from unsuccessful applicants are commonly retained and are the first place a hiring manager looks when a later opening appears.[262]
Content and structure
On an industry engineering resume, qualifications and publications are placed at the bottom and work experience leads, the reverse of academic convention where publication, patent and funding counts lead.[283] Academic journal publications count for little in practical industry, whereas articles in hobbyist electronics magazines such as Silicon Chip or Nuts and Volts are read as evidence of hands-on work.[66] Length is conventionally held to one or two pages, with one page preferred for an early-career candidate.[530] Where limited space forces a choice, an additional technical project entry displaces unrelated general work experience.[530] Date of birth, marital status and religion are conventionally left off.[124]
Specificity carries more information than breadth. A broad skill claim such as experience in ARM implies only that the candidate could work the subject out given time, whereas naming a specific part family and tool chain, such as the STM32 F0 or L0 series, and what was completed with it reads as an immediately usable skill.[565] Tailoring to a specific role means restructuring the document so the skill the employer is hiring for, such as a particular microcontroller family, becomes its focus rather than one entry among many; a deliberately neutral format is the alternative when the target role is unknown.[124]
Named coursework functions as a credential in its own right. A named online course, such as an edX electromagnetics course, is weighted comparably to the equivalent classroom course, either serving to obtain an interview rather than the job itself.[252] One unusually demanding university course — building a sixteen-bit processor from scratch in Verilog across thirty- to forty-hour assignments — was treated by an engineer recruiting co-ops and interns as sufficient for an immediate interview, courses of that type acting as pre-verified evidence of capability.[343]
Self-directed work can be presented under work experience as a named venture rather than as a hobby entry, without misstating what was built.[496] A self-taught practitioner entering electronics is likewise described by the work actually performed, for example electronics designer, rather than a prior trade label, provided the claim can be substantiated; in some jurisdictions the title engineer is regulated and cannot be self-applied.[288]
Projects and portfolios
A self-published online record of personal projects supplements a conventional resume by showing what a candidate has done rather than only where they have been employed; unpaid technical work such as a university solar car team or home electronics is what stands out to a reviewer.[10] Evidence that a candidate does electronics work outside paid hours has been ranked as the strongest single positive signal on a resume.[124] Screening a field of about thirty student applicants, one hiring engineer weighted side projects above grades and placed candidates with no projects or outside technical interests at the bottom of the list.[231]
Projects are conventionally listed with direct links to where each one is documented rather than described in words alone, a practice candidates commonly omit on the assumption that personal work does not count.[530] An entry pointing to documentation of a specific build, such as a blog write-up or a project page on a site like Hackaday, is followed up by reviewers because it makes the claim checkable.[262] A resume and cover letter with no link to actual work prompts the reviewer to ask where the candidate’s work can be found, and a personal portfolio site is one way to answer that though not the only one.[337] Jeroen Domburg, who never completed his bachelor’s degree, reported that a project portfolio published as a web page with downloadable source code, alongside a resume posted to a job site, produced immediate offers.[359]
Documentation depth is what makes such material persuasive. A thoroughly documented write-up covering board layout, stencils, extensive photographs and spectrum and bandwidth measurements is treated as unfakeable evidence of ability, and one such project can be enough on its own to prompt an interview.[324] Photographs of built hardware also make a resume visually distinct in a stack of a hundred text-only documents and are what a fatigued reviewer remembers.[530]
Physical artefacts sometimes replace the document altogether. Some hiring practitioners ask candidates for photographs of boards they have designed instead of a resume as the first point of contact.[115] Some career-fair representatives are engineers who will actually be hiring, and presenting a physical board or a photograph of a build rather than only a resume is what makes a candidate memorable afterwards.[262]
Where employment has supplied no project experience, contributing to an existing open-source project supplies verifiable material, including in non-design roles such as project management.[79] A short contract engagement of a few months, doing troubleshooting or a small design, likewise supplies the first verifiable line of industry experience for a candidate without a formal qualification.[288]
There are limits on the value of a public portfolio. A fully public project record can count against a candidate targeting defence or security-cleared work, though open-source and past project material can still be shown selectively rather than exposed in full.[151] Taking on a project purely to add a named technology to a resume is a recognised failure mode when the candidate has no route to the time and resources needed to become familiar with that technology.[374] Experience with a free or open-source equivalent of a professional tool is listable without having taken a design to silicon or production, but an employer standardised on a specific commercial tool may still screen the candidate out.[141]
Employment history
Tenures of two to three years per employer read as normal on an engineering resume, while repeatedly moving inside a year reads as a negative signal.[296] Where a role is attached to a multi-year project, a hiring manager reads a consistent two-year job-change pattern as predicting the candidate will leave before the project finishes.[615] A job held for less than a year is conventionally omitted unless the departure had an external cause such as redundancy or the company folding, in which case the reason is stated up front.[615]
The employment record is also self-reinforcing across domains. An engineer’s first position, often an internship or co-op, fixes the application domain recorded on the resume, and later applications tend to stay in that domain because prior experience in it is what employers screen for.[143]
Relationship to interviews and referrals
Interviewers verify resume claims with deliberately elementary fundamentals questions, such as a simple op-amp circuit or naming three types of analog-to-digital converter, because candidates with impressive resumes routinely fail them.[151]
The document is not the only route into a hiring process. Referral hiring runs through a small trusted set, with practitioners routing work to a few people they personally know, because a referral places the referrer’s own reputation at risk.[288]