Now I use llms to help me research, outline, refine vocabulary and grade my work but also have stopped letting it speak for me. I’m much happier with the result.
Now I use llms to help me research, outline, refine vocabulary and grade my work but also have stopped letting it speak for me. I’m much happier with the result.
It's a bit of a stretch but MCP is to LLM enabled applications what REST is to web applications.
What was happening before was if you built tools using langchain, you'd have to rewrite them for crewai, cursor, etc. Now, we have a way to share tools, resources, and prompts with applications built using different frameworks.
Thanks xpe, I appreciate you jumping in here. I was struggling to find the words here and I think you did a wonderful job both championing the intent of the post as well as articulating why I found it difficult to engage. You've given me tools to use going forward.
Maybe this anticipates a future where AIs discover and consume these services automatically?
Of course, even if this isn't practically useful, it's cool and maybe will help this person to stand out, at least insofar as it demonstrated that Jake is a clever person who knows how to use MCP.
By connecting an assistant to a job searching api, a database, and context about myself I am able to create a prompt such as "find interesting jobs for jake. maybe something in the ai space?" and in a few minutes I can browse a curated list of potential job matches.
By connecting the assistant to text to speech and speech to text tools and context about myself I can provide a the job description in my prompt and request the assistant play the role of an interviewer. This has been much nicer than practicing in the mirror.
I think that for the next few weeks/months that a hiring team connecting to my mcp server will play out well for me but I think you're in the right ball park. It will be because I was able to show that I can extract value from technology.
Separate from the meta, and discussing only face value, the `candidate-info://website-text` has a bit of marketing puffery like we don't usually see on resumes. I'm wondering whether that's intended to influence the AI tool behavior.
As a simpler solution for many tech workers to get their info out there and easily AI-accessible, what about a plain static XML file Semantic Web-like markup of the pertinent resume information, in terms of some standard ontology. Which information you declare to be true. And then "AI" and other tools works from that? It could be under a `/.well-known/` URL, and anywhere else you can put or interchange an XML file.
I actually wrote the marketing for the humans. That site predates this ai native resume. My thinking is that by putting a little sell into my site I can show off another aspect of my skillset. I used to have a standard bio site with a portfolio but it was a wall of text and needed a refresher.
> As a simpler solution
llms.txt seems to work pretty well. I am sure there are ways to increase the quality of an llms.txt but I started by simply joining all the text data I already had together and asking an llm to make an llms.txt out of it. From there I've been "manually" editing it. Often with Claude's help.
> It could be under a `/.well-known/` URL
I am hoping we start to see a lot more use of this. We already have a pretty good set of tools to do discovery so let's use them.
Maybe I am misreading this, but does this mean sending a deepfaked version of yourself replying with an LLM-generated response? If I were the hiring manager and found out about this, you would not be invited to an interview.
Congrats on getting there for MCP resume before anyone else :)
I also find it an amazing judo-like usage of the way LLMs are so convincing to people with their confidence. By the time the recruiter realizes that the testimonial they read was a sort-of-close vector composite of the real ones given and the "vibe resume"d skills list they got was just not quite right, you'll have the job. It's not the jhgaylor's fault recruiters believe LLMs.
And honestly any professional recruiter or hiring agent who needs an AI, provided by the candidate no less(!), to interrogate (almost literally!) a resume is pretty just much asking for it.
I think even if no hiring manager ever connects to my mcp server I will still find plenty of value from this tool. I can connect hirebase.org and notion.com and my mcp and get claude to create a database of interesting jobs that might be a good fit for me. I can connect Speech to Text (and Text to Speech) and do mock interviews. I can import a job description and a couple of cover letters and get a customized letter for this job that gives me something other than a blank page to start with.
Location: Cary, MS
Remote: Yes
Willing to relocate: Yes
Technologies: AI Product Engineering, Data Driven Product Development, Kubernetes, AWS, Polyglot Programmer
Résumé/CV: https://jakegaylor.com
Email: jhgaylor@gmail.com