Target Role
Position: System or Software Vehicle Integration Engineer
Salary: £53,000 - £68,000
2/10
Not Suitable
Job Description
**Job Title:** System or Software Vehicle Integration Engineer **Salary:** £53,000 - £68,000 **Location:** **Job Description:** Product Engineering is centred on innovation and creativity. From advanced driver assistance systems to developing the future of electric propulsion, the opportunities to create exceptional experiences for the future of motoring are wide-ranging. You'll work alongside industry experts to drive product strategy, manage programs, analyse performance, and lead transformation initiatives. Exceptional careers that bring world-renowned vehicles to life start here. Are you ready to take your software expertise out of the lab and onto the road? We're pushing the boundaries of what's possible in assisted and automated driving. As an ADAS Software Vehicle Integration Engineer, you'll be at the heart of this transformation — integrating, testing, and refining the software that powers our most advanced driver assistance features. This is a hands-on, high-impact role where you'll work across embedded systems, vehicle platforms, and global teams to bring new features to life. From debugging in real vehicles to collaborating with architects and engineers across the business, you'll play a key role in delivering safe, intelligent, and seamless driving experiences. Expect variety, complexity, and frequent international travel as you help shape the future of mobility. **What to Expect:** Deliver real-world impact by integrating and validating ADAS software across embedded and vehicle systems. - Lead the integration of new ADAS software into embedded ECUs and full vehicle environments, ensuring smooth bring-up and functionality - Validate customer-facing ADAS features through end-to-end system testing and real-world vehicle trials - Act as the technical lead for issue resolution, using triage, root cause analysis, and hands-on debugging to solve complex software and system problems - Implement software fixes and enhancements directly within the ADAS software stack to improve performance and reliability - Support cross-functional teams by investigating software issues and providing expert-level technical insight - Collaborate with architects and subject matter experts to align integration efforts with system-level design and long-term platform goals **What You'll Need:** Bring your hands-on software skills, systems thinking, and problem-solving mindset to deliver next-gen driving technology. - Strong programming experience in C/C++ and MATLAB/Simulink, with a focus on embedded systems and control software - Proficiency with automotive tools and platforms, including CANoe, CAPL, GIT, JIRA, and basic Linux/QNX commands - Experience in ADAS software development and integration, ideally across domains such as cruising, parking, or active safety - Solid understanding of software architecture and middleware, including IPC mechanisms and system-level design - Proven ability to debug and resolve issues in both HIL and real vehicle environments - Willingness and ability to travel internationally, supporting integration and testing activities across global markets including the US, China, India, and Europe **Benefits:** This role is rewarding in more ways than one. On top of our core offering, you'll do extraordinary work with amazing people. In addition, you can expect a wide range of benefits: - Discounted car purchase (open to family members, too) - A 52 week maternity leave policy and a 4 week paternity leave policy. Other parental leave policies are available - A competitive pension - A company performance-related bonus - An employee learning scheme providing funding for education, training and other activities which support the development of personal skills and promote lifelong learning - Access to open, employee-led support and social networks - Comprehensive Life Assurance and Income Protection policies
CV Preview (Content Assessed)
Candidate
Summary
SmarterCV is built differently. Instead of generating a generic CV on your behalf, our AI analyses your experience against real job descriptions and asks you the right questions - helping you uncover and articulate what you've actually done, not what sounds good on paper. Every suggestion is grounded in your real experience. SmarterCV will never fabricate a skill you don't have or upgrade a role you didn't hold. What it will do is help you present your genuine experience more strategically, so that when you walk into an interview, you can stand behind every word on your CV. The result is a CV you feel confident submitting - and a job application you can be proud of.
Skills
Technology: CSS; Excel; Google Sheets; HTML; JavaScript; Jira; Power BI; Python; SQL
Specialisations: AGILE Project Management; Budget Management; Project Management; Project Risk; Stakeholder Management
Experience
Director — SmarterCV
Jul 2023 - Present
- Designed and architected a scalable, data-driven web-based application platform, supporting an initial user base of 1000+ users and planning for future growth to 10,000+ users.
- Managed the full software development lifecycle for SmarterCV.com, coordinating with multiple stakeholders and delivering the platform within project timelines.
- Delivered a scalable web platform using PRINCE2 methodology, managing £50k budget across 3 project phases and coordinating 5 stakeholders to achieve 100% on-time delivery.
- Created responsive front-end design using HTML, CSS and JavaScript, ensuring cross-browser compatibility and improving user experience across desktop and mobile devices.
- Designed and implemented SQL database architecture to store 2,300+ user profiles and project data, optimizing query performance by 40% and enabling real-time analytics dashboards for stakeholder reporting.
Software Lead — Major Car Company
Sep 2024 - Sep 2024
- Project managed a 2-week Python training initiative for 15+ software apprentices, defining scope, timeline, and deliverables with heads of software and software quality stakeholders.
- Delivered the training project on schedule and within budget, coordinating with multiple departments and ensuring all learning objectives were met within the allocated timeframe.
- Facilitated daily stand-ups and weekly progress reviews with training participants, managing project risks and escalating technical challenges to senior stakeholders.
- Tracked project progress using Excel spreadsheets, monitoring completion rates and reporting KPIs to leadership including training effectiveness and participant engagement.
- Managed stakeholder expectations and communications, presenting project updates to heads of software and software quality, and ensuring clear project direction.
Software Lead — Major Car Company
Apr 2024 - Jul 2024
- Project managed a 3-month fast-paced initiative with 3 other engineers to produce a mechanical solution for CFD validation image processing techniques, delivering on time and within budget.
- Developed work breakdown structures (WBS) and network diagrams to map dependencies and streamline project execution, ensuring clear project direction and milestone tracking.
- Applied Agile project management methodologies, facilitating daily stand-ups, sprint planning, and retrospectives to ensure iterative development and adaptability.
- Led critical design review processes, integrating feedback from cross-functional teams and managing stakeholder expectations to refine CFD validation techniques.
- Delivered persuasive presentations to stakeholders, communicating technical and business impacts and reporting project KPIs to leadership.
- Managed external supplier relationships, overseeing procurement and integration of essential components while maintaining vendor performance standards.
- Tracked project budgets using Excel, ensuring cost-efficient resource allocation and forecasting variances to maintain financial control.
- Created earned value graphs to monitor project progress and assess performance metrics, reporting project health to senior management.
Project Manager — University Research Project
Apr 2022 - Jun 2022
- Project managed a cross-functional research project to predict and forecast energy demand for Ireland, managing project scope, timeline, and deliverables while presenting findings to 150+ stakeholders.
- Coordinated data analysis and modeling activities across multiple workstreams, building a Python model to forecast energy usage and ensuring project milestones were met on schedule.
- Managed vendor and technology research, evaluating 8+ renewable energy sources and coordinating analysis across pricing, location, capacity, storage, risk, and reliability factors.
- Facilitated decision-making processes by implementing statistical models, evaluating 15+ different factors and presenting recommendations to project stakeholders.
- Delivered project outcomes including a professional report and business case, managing stakeholder expectations and ensuring clear communication of findings to 150+ students.
Project Manager — University Motosport Team
Sep 2020 - Jul 2022
- Delivered a Python software solution to predict EV battery architecture and performance, reducing research and development costs by £4,000 from a £15,000 budget and improving decision-making accuracy.
- Led a manufacturing project plan with clear schedules, budgets and work packages, coordinating orders with 15+ suppliers across a 12-month timeline and managing vendor relationships through sponsorship agreements.
- Facilitated Agile ceremonies including 2-week sprints, sprint planning, and retrospectives for 22 team members, improving project delivery and maintaining team alignment.
- Tracked project budgets using Excel and earned value analysis, forecasting variances and reporting financial performance to stakeholders through monthly reviews.
- Managed RAID logs documenting risks, issues, and decisions, escalating critical items to senior management and maintaining project control across 4 monthly review meetings.
- Coordinated cross-functional teams of 22 engineers and 15+ sponsored partners, ensuring clear communication and delivering the full vehicle mechanical plan on schedule.
- Directed the design and build of a carbon-fibre vehicle body, completing testing on schedule and staying within the £15,000 budget through effective resource management.
Job Description Keywords Extracted
Tier 1: Critical Requirements
ADAS software integration
C/C++ programming
Embedded systems
ECU integration
Vehicle integration and testing
MATLAB/Simulink
CANoe / CAPL
Root cause analysis and debugging
HIL (Hardware-in-the-Loop) testing
Real vehicle testing and trials
Tier 2: Important Requirements
Software architecture and middleware
IPC mechanisms
GIT version control
JIRA
Linux / QNX
System-level design
Cross-functional collaboration
International travel for integration and testing
ADAS domains (cruising, parking, active safety)
Triage and issue resolution
Tier 3: Desirable Requirements
Automotive embedded software development
Control software
Global team collaboration (US, China, India, Europe)
Software fixes and enhancements within ADAS stack
Stakeholder and architect collaboration
Experience Timeline Analysis:
The candidate has approximately 3-4 years of experience since graduating in June 2022. The two 'Major Car Company' entries are very short (1 month and 3 months respectively) and their relationship to each other is unclear — if these are graduate scheme rotations, they should be presented as such. The SmarterCV Director role has been running since July 2023 concurrently with the car company roles, which is credible as a side project. There are no unexplained gaps. However, the overall experience timeline raises a question: the candidate graduated in June 2022 but the first professional role listed starts in April 2024 — what was the candidate doing between June 2022 and April 2024? This 22-month gap is significant and needs to be accounted for on the CV. Was this the period when SmarterCV was being built, or was there other employment during this time?
Overall Suitability for Role
This is currently a Not Suitable profile for the ADAS Software Vehicle Integration Engineer role, with an overall relevance score of 2/10. The fundamental issue is not a lack of potential — a Mechanical Engineering MEng with Formula Student experience and software development capability is a credible starting point for an automotive software engineering career. The problem is that the CV as currently presented is a project manager's profile, not a software engineer's. The tier 1 critical requirements — C/C++, MATLAB/Simulink, embedded systems, ECU integration, ADAS experience, CANoe/CAPL — are either absent from the CV entirely or buried under project management framing. Before this application can be credibly submitted, the candidate needs to answer a fundamental question: do you have the technical skills this role requires (C/C++, MATLAB/Simulink, embedded systems experience) but have simply not presented them, or are these genuinely absent from your background? If the former, the CV needs a complete rebuild around the engineering content. If the latter, this role is likely 2-3 years of targeted technical experience away from being a realistic application. The most important immediate action is to clarify what technical engineering work was actually performed at the Major Car Company and during Formula Student — these are the two most likely sources of relevant technical content that may be hidden behind the project management framing.
Key Strengths
- MEng in Mechanical Engineering provides a relevant academic foundation for an automotive engineering role, and Formula Student participation signals genuine automotive engineering interest and hands-on vehicle development experience
- JIRA is listed and directly named in the JD's required tools
- Python programming capability demonstrated across multiple projects (SmarterCV platform, Formula Student battery model, university energy model) — Python is a useful scripting and analysis language in automotive engineering contexts
- Cross-functional team collaboration and stakeholder communication demonstrated across multiple roles — relevant to the JD's requirement for working across global teams and with architects and subject matter experts
- Agile methodology experience in technical team contexts is a soft-skill positive for the JD's collaborative engineering environment
Critical Gaps
- C/C++ is entirely absent from the CV — this is the primary programming language for the role and is a tier 1 critical requirement; without it, the application is very unlikely to pass the initial sift
- MATLAB/Simulink is entirely absent — this is explicitly required and is the standard tool for control systems and ADAS modelling; given the MEng background, this is a surprising omission that needs immediate clarification
- No ADAS experience of any kind — ADAS software integration is the core function of the role and there is no evidence of any ADAS domain knowledge (cruising, parking, active safety) anywhere in the CV
- No embedded systems or ECU integration experience evidenced — the JD requires hands-on experience integrating software into embedded ECUs and real vehicle environments; the CV shows only web development and project management
- CANoe, CAPL, and Linux/QNX are all absent — these are named tier 2 requirements and their absence, combined with the C/C++ and MATLAB gaps, suggests the candidate may not have the core technical toolkit for this role
- The CV is framed almost entirely as a project manager profile — the majority of bullets across all experiences describe project management activities (WBS, earned value, RAID logs, budget tracking, stakeholder presentations) rather than hands-on software engineering
Recommendations to Strengthen Your Application
- Answer the critical question first: do you have C/C++ and MATLAB/Simulink experience? Check your MEng modules, Formula Student work, and car company role. If yes, these must be added to your technologies list and evidenced in your experience bullets immediately — without them, this application will not pass the initial sift regardless of how well the rest of the CV is written.
- Clarify the nature of your 'Major Car Company' roles — the two 'Software Lead' entries describe training delivery and project management, not software engineering. If these were graduate scheme rotations, were there other rotations involving actual software engineering work (embedded systems, ECU work, ADAS testing, vehicle integration)? If so, this experience needs to be surfaced and should become the centrepiece of your CV for this application.
- Rebuild your experience bullets around engineering and technical content, not project management. Remove or drastically condense all project management artefacts (WBS, earned value graphs, RAID logs, budget tracking, sprint ceremonies) across all experience entries — these are actively harming your application by positioning you as a project manager rather than a software engineer.
- Reframe the Formula Student experience as your strongest automotive engineering credential — expand the Python battery model with technical detail, add any embedded systems or CAN bus work, and rename the role from 'Project Manager' to reflect the engineering contribution. Formula Student is well-recognised by automotive employers and is currently underutilised.
- If C/C++ and MATLAB/Simulink are genuinely absent from your background, consider whether a more junior automotive software engineering role (Graduate Software Engineer or Junior Embedded Systems Engineer at £30-40k) would be a more realistic entry point, allowing you to build the embedded systems and ADAS experience this role requires before targeting senior integration engineer positions.
- Rewrite the summary entirely — replace the SmarterCV product description with a professional engineering profile that leads with your MEng, automotive context (Formula Student, major car company), and strongest technical credentials. Include the target job title or close equivalent.
Professional Summary Assessment
Professional Summary
Score: 1/10
Alignment:
There is no alignment between the current summary and the ADAS Software Vehicle Integration Engineer role. The summary is the SmarterCV product description — it describes the platform's value proposition, not the candidate's professional background.
Gaps:The summary contains no professional content whatsoever. It does not reference the candidate's name, engineering background, technical skills, programming languages, automotive experience, or any of the tier 1 or tier 2 requirements for this role. It needs to be completely replaced with a professional summary tailored to this application.
Questions - Missing JD Requirements:
ADAS software integration and embedded systems
Your summary needs to be written from scratch for this role. Based on your experience, do you have any direct ADAS, embedded systems, or automotive software integration experience? Your CV shows a Mechanical Engineering MEng, Formula Student involvement, and software work at a major car company — do any of these involve embedded systems, ECU work, or vehicle software? The answer to this question should anchor your summary.
C/C++ and MATLAB/Simulink
The JD requires strong C/C++ and MATLAB/Simulink experience. Your technologies list doesn't include either. Do you have experience with C, C++, or MATLAB/Simulink — from your degree, Formula Student, or your car company role? These are tier 1 critical requirements and need to appear in your summary and technologies list if you have them.
Automotive software and vehicle integration
You list 'Major Car Company' as an employer. What did you actually do there in a software context? Your current bullets describe training delivery and project management — but the job title is 'Software Lead'. Did you do any hands-on software engineering, vehicle integration, or ADAS work at this company? If so, this is the most important content to surface for this application.
Recommendation: Reframe
Replace the entire summary with a professional profile tailored to the ADAS Software Vehicle Integration Engineer role. A strong summary for this application should: (1) open with your engineering background and software expertise — Mechanical Engineering MEng, software development experience, automotive context, (2) reference your strongest technical credentials relevant to the JD (C/C++, MATLAB/Simulink, embedded systems if applicable), (3) mention automotive or vehicle context — Formula Student and the major car company role are both relevant signals, (4) reference problem-solving, systems thinking, and cross-functional collaboration, (5) include the target job title or close equivalent. Keep to 3-5 lines, no first person, no marketing language.
Technologies Assessment
Technologies
Score: 2/10
Alignment:
Questions - Reframing Opportunities:
JIRA is the only technology in your list that appears directly in the JD's required tools. Python has some relevance as a scripting and analysis language in automotive engineering contexts, and SQL/data tools show analytical capability. HTML, CSS, and JavaScript demonstrate software development experience, which is a general positive signal.
Gaps:The JD's tier 1 and tier 2 technology requirements are almost entirely absent from your list. C/C++ is the primary programming language required — not listed. MATLAB/Simulink is explicitly required — not listed. CANoe and CAPL are named automotive tools — not listed. Linux/QNX is required — not listed. GIT is required — not listed. Excel, Google Sheets, Power BI, CSS, and HTML are not relevant to an embedded automotive software role and add noise. Your technologies list as it stands reads as a web development and project management toolkit, not an embedded systems engineering toolkit.
Questions - Missing JD Requirements:
C/C++
C and C++ are the primary programming languages for this role. Do you have any experience with C or C++ — from your MEng, Formula Student, or your car company role? Even university-level C++ from control systems or embedded modules would be worth listing. If you have used C++ in any professional or academic context, it must appear on your CV for this application.
MATLAB/Simulink
MATLAB/Simulink is explicitly required and is the standard tool for control systems and ADAS modelling in automotive engineering. Given your Mechanical Engineering MEng, it would be unusual not to have used MATLAB. Did you use MATLAB or Simulink during your degree — for example in control systems, dynamics, or simulation modules? Did you use it in Formula Student for battery performance modelling? If so, add it immediately.
CANoe / CAPL
CANoe is the standard automotive network analysis tool used for ECU testing and vehicle integration. CAPL is the scripting language used within CANoe. Do you have any experience with CANoe or CAPL — from your car company role, Formula Student, or any other automotive context? If not, this is a significant gap for this specific role.
GIT
GIT is listed as a required tool. Do you use GIT for version control in your SmarterCV project or any other software work? If so, add it to your technologies list — it's a direct match to a named JD requirement.
Linux / QNX
Linux command-line proficiency is required, and QNX is a real-time operating system used in automotive embedded systems. Do you have any Linux experience — even basic command-line use from your degree, SmarterCV development, or your car company role? If so, add it. QNX experience would be a strong differentiator but is less commonly held at this level.
Python
Python is not in the JD's named tools but is widely used in automotive engineering for data analysis, test automation, and scripting. You have Python experience from your SmarterCV platform and your Formula Student battery model. Can you frame your Python experience in terms of engineering analysis and modelling rather than web development? For example, your Formula Student Python model for EV battery performance is directly relevant to an automotive engineering context.
Recommendation: Reframe
Your technologies list needs a near-complete rebuild for this application. (1) Remove HTML, CSS, Excel, Google Sheets, and Power BI — these are not relevant to an embedded automotive software role. (2) Add C/C++ if you have any experience — this is the single most important missing technology. (3) Add MATLAB/Simulink if you used it during your MEng or Formula Student — almost certain given your degree. (4) Add GIT if you use it for SmarterCV or any other project. (5) Add Linux if you have any command-line experience. (6) Add CANoe/CAPL if you have any automotive network tool experience. (7) Keep JIRA and Python. The goal is a technologies list that reads as an embedded automotive software engineer's toolkit, not a web developer's.
Specialisations Assessment
Specialisations
Score: 2/10
Alignment:
Questions - Reframing Opportunities:
Agile Project Management and Stakeholder Management have some relevance — the JD mentions cross-functional collaboration and working with architects and subject matter experts. Project Management broadly shows an ability to coordinate complex work. These are soft-skill adjacencies rather than technical matches.
Gaps:None of your specialisations address the tier 1 or tier 2 technical requirements of this role. ADAS software integration, embedded systems, vehicle integration and testing, root cause analysis, debugging, software architecture, and control software are all absent. Budget Management and Project Risk are not relevant to a hands-on software integration engineering role. Your specialisations list reads as a project manager's profile, not a software integration engineer's.
Questions - Missing JD Requirements:
Embedded systems and control software
The JD requires hands-on embedded systems experience. Do you have any specialisation in embedded software, control systems, or real-time systems — from your MEng, Formula Student, or your car company role? If so, this should replace the project management specialisations as your lead technical credential.
ADAS software integration and testing
ADAS integration is the core function of this role. Do you have any experience with ADAS systems, driver assistance features, or vehicle software integration — even at a system-level understanding from your car company role? If so, this is the most important specialisation to add.
Root cause analysis and debugging
The JD specifically requires proven ability to debug and resolve issues in HIL and real vehicle environments. Do you have a specialisation in systematic debugging, root cause analysis, or fault investigation? Even from your SmarterCV development or Formula Student work, structured problem-solving and debugging experience is worth naming.
AGILE Project Management
Agile is relevant to the JD's cross-functional team context but is a soft-skill match rather than a technical one. For a software integration engineering role, 'Agile software development' or 'Agile in embedded software teams' would be a stronger framing than 'Agile Project Management'. Did your car company role involve Agile ceremonies within a software engineering team context — sprint planning, code reviews, integration testing cycles? If so, reframe this as a software engineering practice rather than a project management one.
Recommendation: Reframe
Your specialisations list needs to be rebuilt around technical engineering credentials rather than project management skills. Remove Budget Management and Project Risk entirely — these are irrelevant to a software integration engineering role. Replace with technical specialisations that reflect your actual engineering capability: embedded systems, control software, vehicle systems, ADAS (if applicable), debugging and root cause analysis, software integration and testing. If you genuinely don't have these specialisations, be honest about what you do have — but the current list actively misrepresents your profile for this role.
Experience Assessments
Experience 1: Director — SmarterCV
Score: 2/10
Alignment:
Questions - Reframing Opportunities:
Building a web platform from scratch demonstrates software development capability and systems thinking — both general positives for a software engineering role. Designing and implementing SQL database architecture and building a scalable platform shows end-to-end software ownership. JIRA is mentioned in the JD and you have used it. The platform architecture work shows some system design thinking.
Gaps:This is a web application built with HTML, CSS, JavaScript, and SQL — none of which are relevant to embedded automotive software engineering. There is no C/C++, no MATLAB/Simulink, no embedded systems, no ECU integration, no vehicle testing, and no automotive context. The role title 'Director' and the project management framing (PRINCE2, budget management, stakeholder coordination) positions you as a business owner and project manager rather than a hands-on software engineer. The JD requires someone who debugs in real vehicles and integrates software into embedded ECUs — this experience provides no evidence of that capability.
Questions - Missing JD Requirements:
Embedded systems and C/C++
Your SmarterCV platform is built in web technologies. Did you make any architectural decisions involving embedded-style constraints — for example, memory management, real-time processing, or performance-critical code? If not, this experience is unlikely to bridge the embedded systems gap for this role.
GIT version control
You are building a software platform — do you use GIT for version control in this project? If so, add GIT to your technologies list and mention it in this experience entry. It's a named JD requirement and you almost certainly use it.
Designed and architected a scalable, data-driven web-based application platform, supporting an initial user base of 1000+ users and planning for future growth to 10,000+ users
You made architectural decisions for scalability and system design. For a software integration engineering role, the architecture and system design thinking is more relevant than the web technology stack. Can you describe the architectural decisions you made — for example, how you structured the system for scalability, what design patterns you used, how you handled data flow between components? System-level thinking is a tier 2 requirement for this role.
Designed and implemented SQL database architecture to store 2,300+ user profiles and project data, optimizing query performance by 40% and enabling real-time analytics dashboards
The 40% query performance optimisation is a strong engineering signal — it shows you can identify a performance problem, analyse it, and implement a fix. This problem-solving and optimisation mindset is relevant to the JD's root cause analysis and issue resolution requirements. Can you describe what you did to achieve the 40% improvement? The method matters more than the number for an engineering audience.
Recommendation: Condense
Condense this experience to 2-3 bullets focused on the software engineering aspects rather than the project management and business framing. Keep: (1) the system architecture and design work — frame it as technical system design, (2) any performance optimisation or debugging work, (3) GIT usage if applicable. Remove: PRINCE2 methodology, budget management, stakeholder coordination, and the 'Director' framing — these position you as a project manager, not a software engineer. The role title 'Director' may also raise questions about seniority expectations — consider whether 'Founder / Software Engineer' better represents the technical nature of the work for this application.
Experience 2: Software Lead — Major Car Company
Score: 2/10
Alignment:
Questions - Reframing Opportunities:
Questions - Other Experience:
The job title 'Software Lead' at a major car company is a strong signal for this application — it suggests automotive software context. The role is at a relevant employer. Facilitating Agile ceremonies shows familiarity with software team practices.
Gaps:The content of this experience describes training delivery and project management, not software engineering. There is no C/C++, no embedded systems, no ECU work, no vehicle integration, no ADAS, no debugging, and no automotive software development. The bullets read as a training coordinator and project manager role, not a software lead. This is a one-month experience (September 2024) which is very short and may raise questions. The disconnect between the title 'Software Lead' and the described activities (training delivery, Excel tracking, stakeholder presentations) is significant and may undermine credibility.
Questions - Missing JD Requirements:
ADAS software integration and embedded systems
Your title is 'Software Lead' at a major car company — but the bullets describe a training delivery project. Did you do any hands-on software engineering work at this company outside of this training initiative? For example, did you work on embedded software, ECU integration, ADAS features, or vehicle testing in any other capacity during your time there? If so, this is the most important experience to surface for this application — even if it was a separate rotation or project.
C/C++ or MATLAB/Simulink
As a 'Software Lead' at a major automotive company, did you write or review any C/C++ or MATLAB/Simulink code — even in a supporting or reviewing capacity? If so, this needs to be in your bullets. The JD requires hands-on programming experience in these languages and your current bullets show no programming at all.
CANoe / CAPL or automotive tools
During your time at this car company, did you have any exposure to automotive engineering tools such as CANoe, CAPL, DOORS, or any ECU diagnostic tools — even in a learning or observational capacity? Any genuine exposure to these tools is worth mentioning for this application.
Software Lead
Your job title is 'Software Lead' but the bullets describe training delivery and project management. This creates a credibility risk — a recruiter reading 'Software Lead' at a major car company will expect software engineering content and will be confused or disappointed by training coordination bullets. Can you clarify: what was the actual nature of your role at this company? Was this a graduate scheme rotation, a specific project assignment, or a permanent role? Understanding the full scope of your time there is essential to presenting it accurately and credibly.
Facilitated daily stand-ups and weekly progress reviews with training participants, managing project risks and escalating technical challenges to senior stakeholders
This bullet describes project management of a training programme. For a software integration engineering role, this provides no technical evidence. Is there any software engineering work you did during this period that isn't currently captured in your bullets — for example, developing the Python training materials, writing code for the training exercises, or any technical work alongside the project management?
You have two separate 'Software Lead' entries at the same 'Major Car Company' — one in September 2024 (1 month) and one April–July 2024 (3 months). Were these part of a graduate scheme or structured rotation programme? If so, presenting them as rotations within a single graduate scheme entry (similar to how Rolls-Royce graduate schemes are typically presented) would be clearer and more credible than two separate short-tenure 'Software Lead' roles. What was the overall structure of your time at this company?
Recommendation: Reframe
This experience needs significant reframing. (1) Clarify the nature of the role — if this was a graduate scheme rotation, present it as such. (2) Replace the training delivery and project management bullets with any actual software engineering work performed. (3) If the only work done in this rotation was training delivery, condense to 1-2 lines and focus on the software engineering content taught (Python, OOP, software quality) rather than the project management of the training. (4) The title 'Software Lead' for a training delivery role is misleading — consider whether a more accurate title (e.g. 'Graduate Software Engineer' or 'E&T Graduate Scheme — Software Training') better represents the work. Credibility is at risk if the title and content don't match.
Experience 3: Software Lead — Major Car Company
Score: 2/10
Alignment:
Questions - Reframing Opportunities:
This experience demonstrates Agile project management in a technical engineering environment, cross-functional team leadership, and stakeholder communication — all soft-skill adjacencies to the JD's collaboration and communication requirements. The CFD validation context shows engineering domain familiarity. Managing a team of engineers through a technical project shows some technical leadership capability.
Gaps:This is a project management role for a mechanical/CFD engineering project, not a software integration role. There is no C/C++, no embedded systems, no ECU work, no ADAS, no vehicle software, and no automotive software development. The bullets are almost entirely project management artefacts (WBS, network diagrams, earned value graphs, sprint planning, budget tracking) with no software engineering content. The 3-month duration and the project management framing means this adds limited technical credibility for a software integration engineering role.
Questions - Missing JD Requirements:
Software engineering and technical contribution
You managed a team of engineers on a CFD validation project — but did you personally write any code or software as part of this project? For example, did you write any Python scripts for image processing, data analysis, or automation? If so, this technical contribution is more relevant to the JD than the project management activities and should be surfaced.
MATLAB/Simulink or C/C++
CFD validation work in an automotive engineering context sometimes involves MATLAB for post-processing or analysis. Did you use MATLAB or any other engineering analysis tool during this project? If so, add it.
Project managed a 3-month fast-paced initiative with 3 other engineers to produce a mechanical solution for CFD validation image processing techniques
The phrase 'mechanical solution for CFD validation image processing' is technically interesting but opaque. What did the solution actually do and what software or engineering tools were involved? If there was a software component to this work — for example, image processing algorithms, data pipelines, or analysis scripts — that technical content is far more relevant to this application than the project management framing.
Applied Agile project management methodologies, facilitating daily stand-ups, sprint planning, and retrospectives
Agile ceremonies are relevant context but not a technical differentiator for a software integration engineering role. Can you reframe to describe what the Agile process was delivering — what software or engineering outputs were being iterated on? The output matters more than the process for this application.
Recommendation: Condense
Condense to 1-2 bullets maximum, focusing on any technical engineering or software content rather than project management process. If there was no hands-on software engineering in this rotation, a single line acknowledging the project context is sufficient. Remove all project management artefacts (WBS, network diagrams, earned value graphs, budget tracking, supplier management) — these position you as a project manager and are irrelevant to a software integration engineering role. The space saved is better used expanding any genuine automotive software engineering experience.
Experience 4: Project Manager — University Research Project
Score: 2/10
Alignment:
Questions - Reframing Opportunities:
Building a Python model to forecast energy demand shows programming capability and analytical thinking. The modelling work demonstrates some quantitative engineering skills. Managing a complex multi-variable analysis across 8+ energy sources shows systems thinking. Presenting to 150+ stakeholders demonstrates communication capability.
Gaps:This is a university research project in energy demand forecasting — entirely unrelated to automotive embedded software, ADAS, vehicle integration, or any of the tier 1 or tier 2 JD requirements. There is no C/C++, no embedded systems, no automotive context, no ECU work, and no vehicle testing. The project management framing (scope, timeline, deliverables, stakeholder management) adds no technical engineering value for this role.
Questions - Missing JD Requirements:
Python for engineering analysis
You built a Python model for energy demand forecasting. Can you describe the technical complexity of the model — what algorithms or methods did you use, how large was the dataset, and what engineering or statistical techniques were applied? Python modelling capability is a transferable skill for automotive data analysis and test automation, even if the domain is different.
Coordinated data analysis and modeling activities across multiple workstreams, building a Python model to forecast energy usage
The Python modelling work is the most technically relevant aspect of this experience. Can you expand on the technical details of the model — what methods, what data, what outputs? The project management framing around it ('coordinated activities', 'managed workstreams') adds noise for a software engineering application. Lead with the technical work.
Recommendation: Condense
Condense to 1 bullet focused exclusively on the Python modelling work — describe the technical approach and the engineering problem being solved. Remove all project management content (scope management, stakeholder presentations, vendor research coordination). This experience is from 2022 and is a university project — it should occupy minimal space on a CV targeting a £53-68k senior engineering role. The Python model is the only element worth retaining.
Experience 5: Project Manager — University Motosport Team
Score: 5/10
Alignment:
Questions - Reframing Opportunities:
This is your most relevant experience for this role. Delivering a Python software solution to predict EV battery architecture and performance is directly relevant to automotive engineering and demonstrates software capability in a vehicle context. The Formula Student competition is well-recognised in the automotive industry and signals genuine engineering passion and hands-on vehicle development experience. Coordinating 22 engineers and 15+ suppliers across a 12-month timeline shows the cross-functional collaboration the JD requires. The carbon-fibre vehicle body design and build demonstrates hands-on vehicle engineering. The EV battery performance modelling is directly adjacent to the automotive propulsion and ADAS domains the JD references.
Gaps:The role is framed as Project Manager rather than Software Engineer, which undersells the technical engineering contribution. The Python battery model is the most relevant element but is described in a single bullet alongside budget and supplier management. There is no C/C++, no embedded systems, no ECU work, no ADAS, and no vehicle software integration. The Formula Student context is academic/extracurricular rather than professional. The project management framing (RAID logs, earned value analysis, sprint ceremonies, budget tracking) dominates the bullets and obscures the engineering work.
Questions - Missing JD Requirements:
C/C++ or embedded systems
Formula Student teams often develop embedded software for vehicle control systems, data acquisition, and motor controllers. Did your team write any embedded C or C++ code — for example for the motor controller, battery management system, or data logging? If so, this is the most important technical experience to surface for this application.
MATLAB/Simulink
Formula Student vehicle development frequently uses MATLAB/Simulink for vehicle dynamics modelling, control system design, and simulation. Did you use MATLAB or Simulink during your Formula Student work — for example for the battery performance model, vehicle dynamics, or any control system? If so, add it to your technologies list and mention it here.
CANoe or automotive network tools
Formula Student electric vehicles use CAN bus for communication between ECUs and control systems. Did your team use any CAN bus tools or network analysis tools — even basic CAN logging or monitoring? Any exposure to automotive network protocols (CAN, LIN, Ethernet) is relevant for this role.
Embedded ECU or vehicle software
Did your Formula Student team use any off-the-shelf ECUs or motor controllers that required configuration or software integration — for example, Motec, Bosch, or similar? Even configuring or integrating a commercial ECU demonstrates vehicle software integration awareness.
Delivered a Python software solution to predict EV battery architecture and performance, reducing research and development costs by £4,000 from a £15,000 budget and improving decision-making accuracy
This is your strongest bullet for this application. Can you expand on the technical detail? What did the model actually do — what inputs, what algorithms, what outputs? How did it predict battery architecture and performance — was it a physics-based model, a data-driven model, or a simulation? The technical depth of this work is more impressive than the cost saving for an engineering audience. Also, 'improving decision-making accuracy' is vague — what decisions did it inform and what was the outcome?
Directed the design and build of a carbon-fibre vehicle body, completing testing on schedule and staying within the £15,000 budget
You directed the design and build of a vehicle body — this is hands-on vehicle engineering. Did this involve any software tools for design (CAD), simulation (FEA, CFD), or testing data analysis? If so, name the tools. For an automotive engineering role, the vehicle engineering context is a strong signal and deserves more technical detail.
Facilitated Agile ceremonies including 2-week sprints, sprint planning, and retrospectives for 22 team members
Agile ceremonies for a Formula Student team is an unusual and interesting approach. Was this applied to the software development work specifically — for example, iterating on the battery model or vehicle control software? If so, framing this as Agile software development practice in a vehicle engineering context is more relevant than generic project management.
Recommendation: Reframe
This is your most relevant experience and needs to be reframed to lead with the engineering and software content rather than project management. (1) Expand the Python battery model bullet significantly — add technical detail about the model's approach, inputs, and outputs. (2) Add any embedded systems, C/C++, MATLAB/Simulink, or CAN bus experience from Formula Student — this could be the most important missing content on your entire CV. (3) Reframe the role title from 'Project Manager' to something that reflects the engineering contribution — 'Software and Systems Engineer' or 'Technical Lead' if accurate. (4) Condense or remove the project management artefacts (RAID logs, earned value analysis, sprint ceremonies, budget tracking) — keep only what shows engineering and technical capability. (5) The vehicle body design and build bullet is a strong automotive engineering signal — expand on the technical tools and methods used.
Qualifications Assessment
Qualifications
Score: 6/10
Alignment:
Questions - Reframing Opportunities:
A Masters in Mechanical Engineering (MEng) is a strong academic foundation for an automotive software integration engineering role. Mechanical Engineering degrees at Liverpool typically include control systems, dynamics, thermodynamics, and programming modules — all relevant to the JD's embedded systems and control software requirements. Competing in UK Formula Student for two years is a highly relevant signal for an automotive engineering role — it demonstrates hands-on vehicle development experience and is well-recognised by automotive employers. The A-Level profile (Maths A, Physics B) shows a strong quantitative foundation appropriate for engineering.
Gaps:The degree is Mechanical Engineering, not Computer Science or Software Engineering — which means the software engineering credibility rests entirely on your work experience and project work. No grade is listed for the MEng, which is a notable omission — if you achieved a First or 2:1, this should be stated prominently. No relevant certifications are listed (e.g. functional safety, AUTOSAR, MATLAB certification). The Formula Student detail is minimal — 'competed for two years' tells the reader nothing about what you actually did technically.
Questions - Missing JD Requirements:
Programming and software engineering foundation
Did your MEng include programming modules — particularly in C, C++, or MATLAB/Simulink? Mechanical Engineering degrees at most UK universities include at least one programming module and often control systems using MATLAB. If so, name these modules in your qualifications entry — they provide academic evidence of the tier 1 technical requirements.
Control systems and embedded systems
Did your MEng include control systems, mechatronics, or embedded systems modules? These are directly relevant to the JD's embedded systems and control software requirements and would strengthen the academic foundation for this application.
MEng grade
Your MEng grade is not listed. What grade did you achieve? A First or 2:1 from Liverpool in Mechanical Engineering is a strong credential for a £53-68k engineering role and should be stated clearly.
Competed in the UK Formula Student competition for two years
Formula Student is a significant and well-recognised automotive engineering credential — but 'competed for two years' tells the reader nothing about your technical contribution. What did you actually do in Formula Student beyond project management? Did you design any systems, write any software, work on the powertrain or electronics, or contribute to vehicle dynamics? The technical contribution is what matters for this application, not the competition participation itself.
A Levels — High School
Your A-Level institution is listed as 'High School' rather than the actual school name. For a professional CV, the institution name should be included. Is there a reason you've anonymised this? If it's a privacy preference, that's fine — but if not, the actual school name adds credibility and completeness.
Recommendation: Reframe
Strengthen your qualifications section by: (1) adding your MEng grade — this is a significant omission if you achieved a First or 2:1, (2) adding relevant modules from your MEng, particularly programming (C/C++, MATLAB), control systems, dynamics, and any embedded or mechatronics content, (3) expanding the Formula Student entry to describe your technical contribution rather than just competition participation — what systems did you work on, what software did you write, what engineering problems did you solve, (4) consider adding the actual school name for your A-Levels. Your MEng from Liverpool with Formula Student experience is a genuinely strong foundation for an automotive engineering role — make sure the qualifications section communicates this clearly.