this should go first since its your most recent exp

again any outcomes here you can mention? how many people used this? what problem did it solve?

if you can be a bit more specific here that'd be better, this sounds a bit general. i.e what performance issues? what outcome did your recommendations have?

formatting here is kind of confusing, but i assume its cause you worked at the same place on two different teams. i'd say just have two headers like

Cyber Security Analyst<br /> Statistics Canada - Incident Response Team<br /> .....<br /> Cyber Security Analyst<br /> Statistics Canada - Endpoint Protection Team .....

also do this is descending order (newest first)

if you can free up room by shortening the skills section and add another project that would be beneficial

should this not be Calgary, AB?

i'd say keep this more concise, no need for a summary. just keep the technical skills and maybe split them up into languages, frameworks, developer tools.

i assume there are other technologies used here than just Figma?

you can probably just combine these two

try to use stronger action verbs than Compared, maybe something like Analyzed, Evaluated. also you can rephrase this to sound more impactful like what the AI suggestion says here. even if you don't have a metric for time saved, it still sounds better if you rephrase to something like "Analyzed ...., enabling project leads to make data-driven decisions..."

split this up into sections like Languages, Frameworks, Developer Tools, etc.

if you can add a metric here that would be good, e.g. reduction in latency

can you be more specific? "supporting technology needs" isn't really clear

can you elaborate on this?

mention what technologies you used for this

try to add % of code coverage, # of tests written, or any metrics to back this up

i'd move certs to it's own section below experience or below skills

this is how you annotate

yeah ur ngmi bro

Quantify the number of users or sessions tracked to demonstrate the app's usage and impact.

Include user adoption rates or feedback to illustrate the bot's effectiveness and popularity.

Clarify the potential financial impact or risk reduction achieved through this AI agent's alerts.

Add metrics on how many resumes were improved or user satisfaction ratings to demonstrate impact.

Highlight a specific contribution or idea that led to a significant improvement in team performance.

Specify the user engagement metrics or feedback received post-redesign to showcase impact.

Quantify the decision-making improvements or time saved for executives due to the dashboards.

Consider rephrasing to emphasize how this tool improved support response times or user experience.

Add a specific example of a critical bug found to highlight the importance of your contributions.

Clarify the impact by stating how this improved efficiency or employee satisfaction beyond just time saved.

Highlight any specific contributions or outcomes from these meetings to showcase teamwork impact.

Add user metrics or feedback to demonstrate the app's effectiveness or popularity.

Explain the significance of these alerts—how they improve decision-making or risk management.

Provide the original hosting cost for a clearer picture of the savings achieved.

Mention specific metrics, like the number of resumes improved or user engagement rates.

Be more specific about the user experience improvements or feedback received post-redesign.

Quantify the time or efficiency gained by eliminating these spreadsheets to highlight the impact.

Include the previous setup time for context; this enhances the impact of the achievement.

Clarify what 'coverage' refers to—unit tests, code coverage, etc.—for better understanding.

Specify the impact of time saved on overall productivity or cost savings for the company.

Mention any user adoption rates or feedback to highlight the application's success and relevance.

Consider adding user engagement metrics or feedback to demonstrate the bot's effectiveness.

Clarify the potential impact of this AI agent on decision-making or risk management for stakeholders.

Consider specifying the previous hosting costs to give a clearer picture of the savings achieved.

Include metrics on how many resumes were improved or the average improvement rate to show effectiveness.

Highlight any specific contributions or outcomes from these meetings to demonstrate leadership.

Use active verbs like 'improved' or 'enhanced' to convey a stronger impact.

Quantify the time saved for executives to highlight the efficiency gained through your work.

Clarify how this time saving directly benefits project timelines or resource allocation.

Specify the baseline coverage percentage to give context to the improvement achieved.

Consider rephrasing to emphasize the impact of the automation on employee productivity and morale.

🔧 Mention any user feedback or metrics that demonstrate the app's success.

🔧 Specify how this bot improved user experience or efficiency.

🔧 Clarify the potential business impact or use case for this AI agent.

📝 Remove extra space before the comma after PHP and ensure consistent spacing throughout.

💪 Great initiative; consider mentioning any user engagement metrics to showcase success.

💡 Include user metrics or feedback to demonstrate the app's effectiveness or popularity.

🔧 Specify the impact of dashboards on decision-making or efficiency to enhance this bullet.

💪 Comprehensive skill set; consider prioritizing skills relevant to the job you are applying for.

🔧 Consider adding the date of certification to provide context on your qualifications.

📝 Add spaces after commas for consistency in project formatting (e.g., AWS (Lambda, DynamoDB, S3)).

💡 Consider highlighting specific contributions or outcomes from scrum participation for added impact.

💪 Excellent use of metrics to showcase efficiency gains; maintain this focus on results.

💪 Quantified achievement effectively demonstrates impact; continue this practice throughout.

💪 Strong GPA reflects academic excellence; consider adding relevant coursework to highlight skills.

🔧 Add specific technologies used or methodologies applied to enhance technical depth.

💪 Unique project showcases initiative and technical skills; ensure all projects highlight similar impact.

💪 Certification adds credibility; consider adding more certifications or relevant training if available.

💡 Consider listing courses relevant to desired job roles to enhance alignment with job descriptions.

📝 Remove extra spaces and ensure consistent punctuation for a cleaner look.

🔧 Clarify the impact of this feature on user experience or efficiency for better context.

💡 Consider emphasizing specific contributions or outcomes from scrum meetings to highlight teamwork.

💪 Excellent use of metrics to illustrate efficiency improvements; maintain this level of detail.

💪 Quantified achievement effectively showcases impact; continue this trend in all experience descriptions.

💪 Strong GPA demonstrates academic excellence; consider adding relevant coursework to highlight skills.

yup its so over

your ur ngmi bro 🥀

what % accuracy?

how many users?

another example of a bullet you can add metrics to. Something like "Processed $500K (or however much) in real estate-related invoices, ensuring accurate record-keeping and streamlining financial tracking for internal operations". this is roughly the format your bullets should be in

try to list some technologies, metrics, etc. be more specific than large-scale. how many records (approx.), 5K? 50K? what kind of data migration are we talking about, on-prem to cloud? one db to another? Try and make all these bullets in the format: Accomplished X through Y resulting in Z.

work exp should be in descending order, have your most recent work exp at the top

split this up into more clear sections, i.e.

Programming Languages: Python, Java, C

Design Tools: AutoCAD, SolidWorks...

This section is more just about including key words, you dont really need to write out your skills in full sentences

first note is that you want to try and get this resume down to one page, ill highlight spots where you can clean things up and save space.

keep font size consistent with experience, skills, and other headers.

try and quantify this as well in terms of how much you improved this.

action statement-ify this more. something like "Led the research and design of Dalhousie FSAE's first functional undertray."

what tuning software?

another opportunity to quantify information. how much in costs? if the number is not that big, try using a percentage, like ....reducing costs by X%

Try to use some quantifiable information here. You can make 'multiple weeks of downtime' stand out by specifying the amount of weeks, or for a bigger number, use the number of hours, like 100+ hours

can just be 'Experience'

same thing here, you can just list the skills and then in your experience/projects mention how you demonstrated these skills.

no need for a summary here, just list skills like: Programming Languages: C, Python, MATLAB

nothing else to say for this section really. looks great 👍

good improvement on the action statements. the last thing i can say is really try and get some numbers in here if possible. it's hard to quantify information and remember exactly what you did, but it stands out between just plain words.

can split this into Languages, Frameworks/Libraries, and Developer Tools for easier readability.

don't be afraid to exaggerate on your bullets a little bit, you can probably add another bullet talking about streamlining data from csv files. even if it's just importing a csv as a game, really emphasize how useful this feature is

if you received some sort of certificate for this, add a certifications section to your resume instead, and then mention how you used Python for this role

don't rly need to specify personal project here, consider replacing this with the tech stack instead. same for other projects

i recommend you keep the game jam project since hackathon projects check off a lot of benchmarks. collaboratively working on code, working in fast-paced environment, playing different roles in a team , etc...

be more specific here again and action statement-ify. i found this pretty helpful: https://www.linkedin.com/posts/kshitijdhyani_job-resume-softwaredevelopment-activity-7091234601506918400-vUiE/?utm_source=share&utm_medium=member_android although completely different projects, just realized i stole the name for one of my projects from this guys resume lmao.

action statement-ify this more. Developed X sign-up pages using SAP UI5, ensuring responsiveness across all devices and .... something along the lines of that. if you handled auth for these pages you could also mention that. Implemented secure user authentication using .... you get the point

same thing as the Python one, if you received any certification add it as a seperate section.

again be more specific here, what front-end and back-end frameworks/tools?

try quantifying some information here, and be more specific. how many products? how many clients? what programming languages and frameworks?

can just be "Experience"

although they told us to include this for 8890, you don't need a resume section for this. a simple (Co-Op) after your Bachelor of Computer Science is fine. they can infer the rest like what term you're in, that you're looking for a summer position, etc.

since you have technical experience, consider adding it above your projects section.

if this is preventing you from a one-page resume, this would be a section you can get rid of. unfortunately if the volunteer experience is non-technical, it likely will not help out much. However, a Leadership section can be a strong addition, where you can include things like "Student Captain from 2019-2020...". if you can fit that in then that's great, i think you get the point i'm trying to make about getting everything on one page.

for your experience section, just stick with one header, you don't need relevant and other. to condense your resume as much as possible, focus on your technical experiences. if you have room left over, add the statistics canada one as well, but you probably can get rid of the GMV role.

this would be an example of a bullet you can remove to shorten things up.

good action statements on your projects. if possible, condense some of the bullets so that you can get your content into a one-page resume.

you don't really need a section for soft skills like collaboration, time management, etc. although they are important for a resume, you already have action statements like "collaborated closely ...." which demonstrates that you possess that skill.

testing annotation

you can probably condense these two into one in like 'Developed a Full-Stack web app using Node.js and PostgreSQL, addressing the absence of online booking platforms for baseball fields in the HRM'

you could rephrase slightly to fit this better into action statement format like 'Collaborated in a team of X developers to build ....'

you dont really need to specify full stack although it's a good key word to have for ATS, should be fine to just mention it on your field manager project.

although they told us to add this in the 8890 course, you dont really need a line about co-op status, a simple (Co-Op) after the Bachelor's of Computer Science should be fine. they can usually infer the rest (what year your in, that you want a summer term co-op, etc..)

i'd put the link to your portfolio in the header instead.

make sure to use strong action statements here (accomplished X through Y resulting in Z). instead of saying 'i used', you could rephrase to something along the lines of 'Developed the front-end of a JSON compiler, implementing lexical, syntactic, and semantic analysis, ensuring proper error handling and recovery'.

this can be condensed as well.

unnecessary description. these two lines can be condensed into one.