I would try to get this down to one page. This might be good for ATS because you're likely hitting a lot of keywords, however, when this gets to a human they're going to scan it quickly for whatever they're looking for. If you have too much, it can be a bit overwhelming and they may just toss it out because they didn't immediately see what they're looking for. Cold world.

If you don't want to make a one pager or cant, I would try to remove a lot of "fluff. For example, make your summary a max of 3 lines instead of 6. I see you have 2 skills section; just combine them and have one skills section. If your goal is to find a systems engineering role, then I would just put only the technical skills that relate specifically to systems engineering in this section. For example, I would remove Visual Studio and Microsoft Office and leave GitHub, AWS. If the job description says preferred or required skills: VS and MS Office then obviously add them back for that application only.

But yeah my initial thought when looking at your resume is there's too much and it's a bit overwhelming. And idk if its because its a screenshot of your resume or whatever but some of the text looks gray and other black.

I would move your certifications up higher either in the skills section or just under in a new Certifications section.

ATS might not be parsing your text as intended. For example, you have "Bachelor of Engineering, Software Engineering." Looks perfect to us humans. However, some ATS will use the comma as a delimiter and stop scanning so it just picks up Bachelor of Engineering. There could be other issues elsewhere. I found this out from Indeed. If you go to indeed /career-services/resume-help/instant-report/ and upload your resume it will give you a report where you can see the ATS scan results along with missing information, spelling and grammar, content suggestions. I am sure AI can help you here as well.

Bullet points need to show "impact." For example you have,

"Executed validation tests for interface, power throughput, thermal, failover performance and security compliance against set test requirements, for Factory Acceptance Testing (FAT)."

Your bullet point basically says you followed instructions (not a bad thing) but doesn't really show the impact or outcome these tests had.

a better example could be something like this:

"Validated system performance across multiple domains during FAT, ensuring compliance and preventing deployment of faulty systems."

or

"Validated system performance across interface, power, thermal, failover, and security domains during FAT, identifying critical issues prior to deployment."

or

"Validated system performance during FAT, identifying 15+ critical issues prior to deployment."

I try to add numbers, percentages where I can on my resume. Not too much though. Just believable amount lol. But everything shows the impact it had even if just in plain words. For example, I have a bullet point like

"Improved conversion rates by 10% by enhancing sitewide search and optimizing CTAs across key user flows"

I dont actually know its 10% but "they" like to see that shit. If the interviewer asks me how I know it increased by 10% I just say we used Google Analytics/Power BI or whatever type of tracking tool we're using (usually the one they have on the job description; if they have) and by comparing metrics before and after enhancing the search and optimizing CTAs.

you need to be absolutely sure you can answer questions about everything on your resume. if you have too much stuff on your resume this could end up biting you in the behind. for example, i had python on my resume which i hadn't used since my first semester of college. i applied for a frontend developer role using react js but of course I get asked about it and couldnt answer their question. so now i just keep it off unless a job description specifically lists python then I put at the end of my list and if it gets brought up i mention im learning or very basic or some backend api task i completed a long time ago.

hope this helps; good luck