Professor of Computer Engineering

A Professor of Computer Engineering occupies a role that is really three jobs running concurrently: researcher, educator, and institutional citizen. The balance among those three shifts depending on whether the position is at an R1 research university, a master's-granting institution, or a teaching-focused school — but none of the three ever fully disappears.

On the research side, a faculty member running an active lab might oversee four to eight graduate students working on problems in computer architecture, reconfigurable computing, hardware security, or chip design automation. The professor's role in that lab is part scientific director (setting research direction, reviewing results, co-authoring papers), part project manager (keeping students on schedule toward graduation), and part fundraiser (writing the NSF and DARPA proposals that pay for student stipends, equipment, and conference travel). A successful research program at an R1 produces two to four journal publications per year and brings in $300K–$800K annually in external grants.

In the classroom, the work ranges from teaching 200-student introductory digital systems courses to running 8-person graduate seminars on current literature in processor design. Course preparation at this level is ongoing — the field moves fast enough that a computer architecture syllabus from 2020 needs meaningful revision by 2026. ABET accreditation requirements add a documentation layer: student outcomes must be defined, measured, and used to drive curriculum improvement.

Service is the third rail. Department committees, hiring committees, curriculum reviews, graduate admissions — these require real time and attention, and junior faculty often underestimate the load. Senior professors add editorial board memberships, conference program committee chairs, and national panel service to that mix.

The day-to-day reality for a mid-career computer engineering professor at a research university is a calendar that is never fully under their control: teaching blocks, student meetings, committee work, and grant deadlines run in parallel, with summers nominally free but typically consumed by research catchup and proposal writing.

Education:

• Ph.D. in computer engineering, electrical engineering, or computer science (required for tenure-track positions at four-year universities)
• Postdoctoral research appointment (1–3 years; expected by most R1 hiring committees)
• Strong undergraduate preparation in digital logic, circuits, computer architecture, and systems programming

Research credentials:

• Publication record in peer-reviewed IEEE or ACM venues: IEEE Transactions on Computers, IEEE Transactions on VLSI Systems, IEEE Micro, DAC, ISCA, MICRO, or HPCA depending on subfield
• Demonstrated history of or clear potential for external research funding
• NSF CAREER award (highly valued; expected by top programs at or shortly after tenure)
• Thesis work that established an independent research identity, not just contribution to an advisor's existing agenda

Technical depth — common areas of specialization:

• Computer architecture: processor microarchitecture, memory systems, interconnects
• Embedded and real-time systems: microcontroller programming, RTOS, hardware-software co-design
• VLSI and digital design: RTL design, synthesis, physical design, EDA tools (Cadence, Synopsys)
• Hardware security: side-channel attacks, trusted execution environments, secure boot
• Reconfigurable computing: FPGA design and high-level synthesis
• AI hardware: neural network accelerators, in-memory computing, neuromorphic architectures

Teaching competencies:

• Curriculum design including learning objective mapping and ABET outcome alignment
• Laboratory instruction experience with FPGA development boards, oscilloscopes, and embedded platforms
• Graduate-level advising: the ability to move a doctoral student from vague research interest to defensible dissertation

Soft skills that matter:

• Ability to write grant proposals that are technically credible and reviewable in 15 minutes by a non-specialist panel member
• Patience for the iterative, often discouraging pace of doctoral training
• Willingness to do the service work — the faculty who refuse committee assignments create friction that follows them through the tenure process

The academic job market in computer engineering has been structurally tight for decades — there are consistently more qualified Ph.D. graduates than tenure-track openings. That hasn't changed. What has changed is the competitive environment at the top and the alternatives available to candidates at the bottom.

At research-intensive universities, competition for open positions is intense. A strong opening might attract 150–300 applicants. Search committees shortlist candidates based primarily on research trajectory: publication venues, citation counts, external fellowship awards, and letters from well-regarded advisors. Candidates from a handful of highly ranked programs have a structural advantage, and the market for faculty positions at peer institutions is largely separate from the market for positions at regional schools.

The salary picture is better than it was a decade ago, driven by competition with industry. Google, Microsoft, Nvidia, and Intel are paying new Ph.D. graduates $200K–$300K+ in total compensation. Universities can't match that, but they've responded by raising starting salaries, offering startup packages of $500K–$1.5M for lab equipment and graduate student funding, and creating named chair positions that carry supplemental stipends.

In terms of subfield demand, computer engineering faculty with expertise in hardware for AI, hardware security, and chip design automation are the most actively recruited. The CHIPS Act and its academic research investment provisions have created new federal funding streams specifically for semiconductor education and research, and NSF's semiconductor-focused programs have expanded. Schools are hiring to capture that funding.

For candidates who want an academic career but can't land an R1 position immediately, the path often runs through a postdoc extension, a position at a teaching-focused institution, or industry work with continued publishing — then a return to the market. The pipeline is long and the attrition is real, but computer engineering faculty who reach tenure at any institution have a stable, well-compensated career with substantial intellectual autonomy. That combination is genuinely rare.

Dear Search Committee,

I'm applying for the tenure-track Assistant Professor position in Computer Engineering at [University]. My research focuses on hardware security — specifically, microarchitectural side-channel vulnerabilities and the design of hardware countermeasures that impose minimal performance overhead. I completed my Ph.D. at [University] in May and am currently finishing a postdoc in the [Lab Name] group at [Institution].

My dissertation introduced a class of cache partitioning schemes that reduced cross-tenant information leakage in cloud processors without the 15–25% performance penalties associated with prior isolation approaches. That work produced three IEEE Transactions on Computers papers and a presentation at ISCA, and it formed the basis of an ongoing collaboration with [Company], which has sponsored the last 18 months of my postdoctoral work.

I have taught twice as instructor of record — once for an undergraduate computer organization course of 80 students and once for a graduate seminar on hardware security — and I've supervised three M.S. students through thesis completion. My teaching evaluations have been consistently strong, and I've found that hardware security translates well into the undergraduate curriculum because the attack-and-defense framing gives students an intuitive reason to care about microarchitectural details they'd otherwise treat as trivia.

My research agenda for the first three years at [University] centers on securing heterogeneous computing systems — particularly the security implications of CPU-GPU shared memory architectures. I have a draft NSF CAREER proposal in progress and have had preliminary conversations with the NSF program officer in the Secure and Trustworthy Cyberspace cluster.

I'm drawn to [University] specifically because of [Faculty Member]'s work on reconfigurable architectures — there's a natural intersection with my security research that I think could produce collaborative grant opportunities.

Thank you for your consideration.

[Your Name]