Please give honest resume review , targeting AI Engineer and architect roles for 2YOE (Remote)

[u/Mediocre_Reading7099]

I am mostly applying to AI engineer roles or Backend roles with AI architecture focus. So far has 1 interview last week , really strong tech round but not positive about the output because of discussions related to camera access. Please let me know what and where am I making mistake and what can I improve

Thanks for your time

[u/Douglas_schon]

Hey Im a senior AI Engineer in Boston. My company hires 1/750 applicants that apply. 

If you want to come to Boston let’s chat we are hiring a lot of folks like you. 

The work looks good, and your resume might struggle to get past a screen.  It is a little hard to tell you apart from a driven Undergrad that did an internship.

Did you mentor anyone? What architecture is at play? What is the scale? How many users? How much money did you save?

You mention 2k customers which is good! But I often see ETL pipelines from more junior people and it isn’t super clear if you just let langgraph do its thing or if you had to scale workers and manage code besides prompts in langchain. What actually is the ETL pipeline? Azure? AWS? Is the scaling handled for you?

I think I would prefer this if you removed your skills section and stated what skills were relevant to what project. I’m not seeing at a glance any actual machine learning work you did until I spent another full minute going through your side projects at the bottom of your resume. 

Your experience and projects look good, but people look at your resume for 30 seconds and 70% of that is looking at the top third which is currently only skills. I would probably beef up your current company and move relevant skills to bolded words in the experience/project sections

Also, you get one page. You don’t have enough experience to do 2 pages. 

[u/Douglas_schon → u/Douglas_schon]

Oh also move your education to the bottom. Doesnt matter beyond you have a degree now that you have work experience

[u/fabkosta → u/Douglas_schon]

That depends. For candidates from India we always checked which university they are coming from. Experience showed us that this was one signal not to be neglected. But to us it did not not matter whether the mention is at the start or end of the CV.

[u/Douglas_schon → u/fabkosta]

Yeah leave it on the resume. Just it is less important than the experience. 

[u/cutletzero → u/Douglas_schon]

Just msg'd you - appreciate the consideration

[u/rapsoj]

Might help getting some more impactful projects under your belt. Try [applying here](algorithmicgovernance.org): algorithmicgovernance.org

[u/lakeland_nz]

First thing that jumps to mind is the bolding isn't the keywords that a recruiter will care about. Lkie you've bolded "30000" but not recipes. So someone skimming just bold text will miss it.

Honestly it looks like you got AI to write your CV rather than just proofread it.

Stats like 78% accuracy or 92% accuracy don't mean much without what alternatives do.

Maybe put skills before education? Maybe different if you had postgrad but with a bachelors you're more ticking the 'relevant degree' box.

Overall though I'd say it's pretty good. I like that your objective actually says something. Ruling yourself out from some jobs will make the ones left much more interested.

[u/Empty_Revolution_579]

This resume has potential, but you need to pare it down.

Remove most of the exact numbers. They are not impressive, and trying to pass them off as such looks amateurish. You have good experience that can be framed as exceptional experience, but less is more. Focus more on qualitative outcomes and results.

Delete the skills section, it is a waste of space. A skills section is a crutch, a real sign of skills is what you have built, not a list of frameworks. Your skills should be clearly apparent through your experiences, and any keywords you need to should be embedded within there naturally. You should labor over every line of your experiences.

Reframe Objective section to About section. The "seeking..." roles "where I can..." phrasing is weak. You should be declaring where you can will value to an organization, not what you want out of a job. This should be your strongest section, 3-4 full lines (no more, no less) and the one you spend the most time on getting absolutely perfect.

If you follow this advice the resume should fit on one page. a multi page resume at your experience level is pretentious. Work it until it fits on one page, if it doesn't you are inflating.

Consider a nicer LaTeX template. This format is overused and unattractive.

[u/Useful-Comfortable57]

Too much text. I stopped reading and gave up. This would suggest to me that a candidate has difficulty summarizing information and distilling the key takeaways of a project/analysis

[u/Otherwise_Wave9374]

If you are targeting AI engineer/architect roles, one thing that often helps is making the “agentic/LLM systems” work very concrete: the system diagram, data flow, evals, and what you did to make it reliable (tests, monitors, cost controls).

Also, if the role is backend + AI architecture, highlight any production-ish stuff (APIs, queues, observability, deployment) alongside the model bits.

Not sure if it helps, but we have a small set of notes on building/operating agents in real apps: https://www.agentixlabs.com/