Kevin Wolf

Why this persona fits the audience

Second-year EE student in Manchester building FPGA projects and watching for ASIC summer internships; stores links in Google Sheets, follows a few recruiters on X and LinkedIn, and checks the same company pages every week. Budget-conscious and has never paid for a job board.

• Age: 20
• Location: Manchester, England, UK
• Occupation: Undergraduate student
• Income: £8k part-time
• Education: BEng Electrical and Electronic Engineering
• Years in role: 2

“If you can't simulate it, optimize it, or explain it simply, you don't understand it well enough to build it.”

Kevin Wolf is a twenty-year-old second-year Electrical and Electronic Engineering undergraduate at the University of Manchester, navigating the precarious balance between academic rigor and the early stages of a professional career in semiconductor design. Hailing from a working-class background in Greater Manchester, Kevin has developed a frugal mindset out of necessity, managing a part-time income of roughly £8,000 annually alongside his studies. This financial constraint has fostered a deep reliance on free, open-source, and educational resources, shaping his approach to problem-solving where efficiency and resourcefulness are paramount. Academically, Kevin is driven by a desire to transition from theoretical knowledge to practical hardware implementation. His primary focus lies in Field-Programmable Gate Array (FPGA) development, where he spends countless hours writing Verilog code, debugging timing constraints, and interfacing with peripherals. Unlike many peers who rely solely on coursework, Kevin maintains a personal repository of projects, including a custom UART controller and a basic CPU core, all hosted on GitHub to serve as a portfolio for future recruitment. His job search strategy is characterized by intense organization and skepticism toward commercial intermediaries. Having never paid for a job board, Kevin has constructed a comprehensive, albeit manually updated, tracking system within Google Sheets. He meticulously aggregates internship listings from various corporate career pages, LinkedIn, and Twitter, tagging them by role type, deadline, and required skill sets. He follows a select group of recruiters and industry influencers on X, scanning for real-time updates that might not yet appear on official portals. Despite the volume of information, he feels the friction of fragmentation; his days are often consumed by the administrative overhead of finding opportunities rather than applying to them. Kevin's personality reflects a blend of high conscientiousness and moderate neuroticism. He is deeply organized, keeping his digital and physical spaces tidy, yet he harbors a quiet anxiety about missing out on the right opportunity due to his lack of paid networking tools or expensive resume services. He is pragmatic, valuing technical competence over flashy presentations, and believes that a solid track record of working hardware speaks louder than a polished CV. As he looks toward his final year, his goal remains singular: to secure a summer internship at a top-tier chip design firm, leveraging his self-taught skills and disciplined work ethic to bridge the gap between student and engineer.

Background & daily life

A day in their life

Kevin wakes at 7:15 AM to avoid the rush of the bus to the University of Manchester campus. After a quick breakfast of porridge, he attends morning lectures on Digital Systems, taking handwritten notes which he later digitizes into his Obsidian vault. Lunch is a sandwich eaten at his desk while reviewing a Verilog simulation log. Afternoons are reserved for the electrical labs or the computer room, where he works on his current FPGA project, trying to optimize clock speeds. By evening, he returns to his flat, orders a cheap takeaway, and spends two hours on 'career maintenance': updating his master Google Sheet with new internship postings found on LinkedIn and checking X for hashtags like #ASICjobs. He ends the day by reading a chapter of a semiconductor textbook, usually falling asleep around midnight with the hum of his PC fans as his lullaby.

Lifestyle

Kevin lives in a two-bedroom shared house in Didsbury with two other engineering students, splitting rent at £450 per month to keep costs down. His routine is rigid: early morning lectures followed by late afternoons in the lab or coding at home. He cooks simple meals in bulk on Sundays to save money and time, often eating pasta or stir-fry during long debugging sessions. Health-wise, he tries to run three times a week but often skips it when project deadlines loom. Socially, he is selective, preferring one-on-one coffee chats over loud pub nights, though he actively participates in the university's Robotics Society. Every penny counts; he uses bank alerts for every transaction and avoids impulse buys, viewing money as a tool for stability rather than status.

Work life

His 'work' is split between rigorous academic modules and self-directed FPGA development using Xilinx Vivado and Verilog. Days are spent hunched over dual monitors, synthesizing code, and wrestling with timing violations that seem to defy logic. He collaborates primarily via Discord servers and GitHub with peers who are also grinding on hardware projects. The pressure is internal and academic: maintaining a high GPA while proving his skills through tangible hardware prototypes. He spends hours manually curating lists of potential employers, cross-referencing their career pages against his own criteria, often feeling the friction of information scattered across dozens of tabs and bookmarks.

Relationships

Kevin is close with his parents, who are supportive but not wealthy, so they expect him to be financially independent where possible. He has a tight-knit group of four friends from his first year, mostly fellow engineers, with whom he shares notes and stress. He relies heavily on senior students for informal advice, often asking them about specific companies or tools. His social circle is small but deep; he values reliability over popularity and rarely engages in superficial networking, preferring genuine technical discussions.

How they decide

Cautious and evidence-based. Kevin gathers extensive data before committing to any new process or tool. He compares features, reads community feedback, and tests free versions thoroughly. He is highly resistant to paying upfront without seeing clear, immediate value, preferring a freemium model or a trial period. Peer validation is crucial; if a trusted senior student recommends something, he will investigate further, but he ultimately makes decisions based on his own logical assessment of utility versus cost.

How they sound

Kevin speaks with a clear Mancunian accent, moderate pace, and precise diction. He avoids slang unless in very casual settings with close friends. In professional contexts, he is polite but direct, focusing on facts and technical specifics rather than fluff. He tends to ask clarifying questions before accepting a premise and often pauses to think before answering complex queries. He avoids making grand promises or hyperbole, preferring statements grounded in what he has personally verified or experienced.