Most guides about AI and job searching are theoretical. "AI will change how we find jobs." "The future of hiring is conversational." Lots of hand-waving, not a lot of showing.
This is the opposite. This is what it actually looks like to run a job search through a single conversation with Claude, connected to Remoet via MCP (Model Context Protocol). I'm going to walk you through each step with real interactions you can replicate today. Think of it as a single-conversation workflow: profile, discovery, shortlist curation, and application tracking, all without leaving your AI agent.
If you haven't set up MCP yet, our setup guide for Claude, Cursor, and Windsurf will get you connected in about five minutes.
Why This Is Different From AIApply, Jobright, and Auto-Apply Tools
I want to address the elephant in the room before we start. There's a whole category of AI job search tools that promise to auto-apply to hundreds of jobs for you. Jobright, AIApply, LazyApply, and others. They optimize for volume.
The problem with volume-based auto-apply is that it doesn't work. Quality-focused AI agents achieve 4-8% interview rates compared to roughly 0.1% for volume-based auto-apply tools. Spraying 500 generic applications gets you filtered out by the same ATS systems these tools claim to beat.
What we're doing here is fundamentally different. Remoet is an MCP server for job search, which means your AI agent has real tools to research companies, evaluate fit, build a shortlist, and track what happens. It's conversational job search: you talk to Claude, Claude uses Remoet's MCP tools, and together you build a targeted pipeline. Companies on Remoet are pre-filtered by real tech stack data, not keywords. When you search for "TypeScript and Node.js," you're matching against actual technology data that companies have listed, not scraping job descriptions for mentions of the word "Node."
That distinction matters. Let me show you how it works.
Step 1: Connect and Check Your Profile
The first thing to do after connecting is see where you stand. Open Claude and say:
"Show me my profile."
The agent pulls your complete developer profile from Remoet: your summary, skills, work experience, education, projects, and any gaps. If you're starting fresh, most fields will be empty.
Here's what Claude might come back with:
"Your profile is mostly empty. You have no summary, no skills listed, no work experience entries, and no projects. Your profile won't be competitive without at least a summary, skills, and some work history."
This isn't a canned response. The agent is reading your actual data and evaluating what's missing. On a traditional job board, you'd have to notice these gaps yourself by staring at blank form fields. Claude tells you upfront.
Step 2: Build Out Your Profile Through Conversation
Now you fill in the gaps, but instead of tabbing through form fields, you just talk:
"Update my summary to say I'm a senior full-stack developer with 6 years of experience building web applications with TypeScript, React, Node.js, and PostgreSQL. I'm based in Berlin and looking for fully remote roles."
The agent updates your summary. Next:
"Add a work experience entry. I worked at Acme Corp from January 2022 to March 2025 as a Senior Software Engineer. I led the migration of their monolithic PHP backend to Node.js microservices, reduced API response times by 40%, and mentored a team of 3 junior developers."
One conversational message instead of filling out 6 form fields. Keep going:
"Add TypeScript, React, Node.js, PostgreSQL, and Docker to my skills."
You can layer in education, projects, whatever you want. The point is that building a complete profile through conversation takes maybe 10 minutes. Through forms, it takes 30 to 45 minutes because you're context-switching between fields, formatting text, and fighting with date pickers. I've done it both ways. The conversation approach isn't just faster, it's less draining.
Step 3: Find Companies That Match Your Stack
Now you search. This is where MCP changes everything compared to manual browsing.
"Find remote companies that use TypeScript and Node.js."
The agent searches Remoet's company catalogue and returns results ranked by relevance to your query. It's matching against real tech stack data that companies have listed, not keyword-scraping job descriptions. That's a meaningful difference. When a company says they use Node.js on Remoet, they actually use Node.js.
You'll get a list like:
"Found 47 companies matching TypeScript and Node.js. Here are the top results: [Company A] (TypeScript, Node.js, React, PostgreSQL, 12 open jobs), [Company B] (TypeScript, Node.js, Go, 8 open jobs), [Company C] (TypeScript, Node.js, AWS, 5 open jobs)..."
Already better than scrolling through 200 generic listings. But you can refine further:
"Which of those also use PostgreSQL?"
"Show me more details about Company A. What do they build?"
Claude pulls the full listing profile for any company you're curious about: their description, tech stack, perks, URLs, and how many open jobs they have right now. This is the conversational part. You're not clicking through pages. You're having a back-and-forth that narrows down your options naturally.
Step 4: Star the Companies You Care About
Once you've found companies that genuinely match your background, star them:
"Star Company A and Company C."
Stars on Remoet aren't passive bookmarks. They feed your personalized job dashboard. Every company you star adds their job postings to your feed. This is your curated pipeline, and it only works well if you're selective.
Claude knows this. If you try to star a company whose stack doesn't overlap with your skills, it'll flag it:
"Company X primarily uses Rust and Go. Your profile lists TypeScript and Node.js with no Rust or Go experience. Starring this company would add their jobs to your feed, but you may not be qualified for most of them. Want to star it anyway?"
That kind of judgment call is something a traditional UI simply can't make. The agent is cross-referencing your profile with the company's tech stack in real time.
Step 5: Check Your Job Feed
After starring companies, you've got a personalized feed. Check it:
"Show me jobs from my starred companies."
The agent pulls active job listings from all the companies you've starred. You can filter further:
"Show me only senior-level roles."
"Any of these that mention remote with no location restrictions?"
You're having a conversation with your job feed instead of scrolling through it. The difference sounds small but it changes how you engage with the information. You actually read and evaluate instead of skim and forget.
Step 6: Save Jobs and Take Notes
When something catches your eye, save it:
"Save the Senior Full-Stack Engineer role at Company A."
Then add context so future-you remembers why:
"Add a note: their stack is a near-perfect match, they have an engineering blog I like, and the role mentions working on their new API platform which is exactly what I did at Acme Corp."
This is your private CRM. Three weeks from now, when you're comparing five companies and trying to remember which one excited you and why, these notes are invaluable. And because you're adding them in the moment through conversation, the friction is zero compared to maintaining a spreadsheet. I've tried the spreadsheet approach. It lasts about four days before you stop updating it.
Step 7: Get the Application URL and Apply on the Company Site
This is the step most "AI job search" content gets wrong, so I want to be explicit about it.
Almost every job on Remoet is scraped from an external careers page. When you tell your agent you want to apply, the agent's job is to hand you the application URL, not to submit anything on your behalf. You click through, you fill out the company's form on their site, you hit submit. The application happens in the company's system, not in Remoet.
"I'm ready to apply to the Senior Full-Stack Engineer role at Company A. Give me the application URL and anything I should know before I go."
The agent surfaces the URL, the role description, the company's tech stack, and any notes you've already attached. If your profile has gaps that would be obvious on a CV, the agent flags them:
"Your profile has no projects listed. Companies in this stack often look for portfolio links. Want to add a project before you apply?"
You decide. Then you go apply on the company site like you always have.
The exception: A small slice of jobs on Remoet are internal, posted directly by companies through Remoet's partner system. For those, the agent can submit end-to-end. The agent will know which type a job is and will tell you:
"This role is an internal job. I can submit your application through Remoet using your profile, or you can apply via the company URL. Which do you want?"
For the vast majority of roles, the answer is "I'll apply on the company site." That's not a failure of the agent, it's the honest shape of an internet where most jobs live on external ATSs. What the agent gives you is everything around the apply click: discovery, evaluation, notes, tracking. Application submission, for most jobs, is still on you.
Step 8: Track Everything
Once you've applied (externally or internally), log it so it's part of your tracked pipeline:
"I just applied to the Senior Full-Stack Engineer role at Company A. Add it as an application with today's date and a note that I sent it through their site."
Now it's in the pipeline. Ask for status across applications any time:
"Show me all my applications."
The agent pulls your full application list with statuses, dates, and any events you've logged. For internal applications, the agent also surfaces real status events from the company side (submitted, viewed, interview scheduled, offer received).
For a specific company:
"What's the status of my application at Company A?"
"Show me the event history for that application."
You can also add notes to applications over time:
"Add a note to my Company A application: had a first-round call, the interviewer mentioned they're expanding the platform team."
Everything stays attached to the application. When you check back next week, all the context is there. No more digging through email threads trying to reconstruct timelines.
Step 9: Weekly Check-Ins
The real power of this workflow isn't the initial setup. It's the ongoing maintenance. Once your agent is connected, weekly check-ins take about five minutes:
"Anything new from my starred companies this week?"
The agent checks your digest and shows new job postings from your starred companies. You scan the list, save anything interesting, and move on. Compare that to the old workflow: open 5 job board tabs, search each one, scroll through results, try to remember what you already saw last week.
"Any updates on my applications?"
Quick status check across your pipeline. No dashboard required.
The Full Loop
Here's the complete workflow:
Connect your AI agent to Remoet via MCP (one-time setup)
Audit your profile and fill in gaps through conversation
Search for companies by tech stack
Star companies that match your background
Browse your personalized job feed
Save interesting roles with notes
Get the application URL and apply on the company's site (or have the agent submit internally for the small slice of partner-posted roles)
Log and track applications, status, and notes over time
Repeat steps 5 through 8 weekly
Total time: about half an hour to get from zero to a curated pipeline with your first application sent. After that, maybe 5 minutes a week to stay on top of everything.
On a traditional job board, the initial setup takes hours, and weekly maintenance takes 30 to 60 minutes of browsing, filtering, and clicking. The agent compresses all of that into conversation. It's not magic. It's just a better interface for the same work, with you still doing the apply click on the company site for most roles.
Frequently Asked Questions
Can I do all of this with the free plan?
Yep. Remoet's free tier includes 30 MCP requests per day, which is enough for a full search-star-pipeline session. You can star up to 10 companies and have unlimited access to your profile, applications, and saved jobs. If you're running multiple intensive sessions per day, you might want to upgrade, but most people find the free tier covers their weekly workflow just fine.
What if I want to use the website for some steps?
Everything's synced. Star a company through Claude and it shows up on the website. Save a job on the website and your agent can see it. Use whichever interface feels right for each step. Some people prefer the website for browsing job descriptions and the agent for searching and tracking. Whatever works for you.
Does the agent remember my previous conversations?
Claude has access to your Remoet data (profile, stars, applications, saved jobs, notes) across all sessions. Your data persists regardless of which conversation you're in. What Claude doesn't remember is the conversation itself from a previous session, but since all the important state is stored in Remoet, that rarely matters. Your notes are your memory.
Can I use a different AI agent than Claude?
Yes. Any MCP-compatible agent works: Cursor, Windsurf, Cline, and others all support MCP. The experience is similar across clients, though some handle multi-step tool calls more smoothly than others. I've found Claude to be the most reliable for complex workflows, but Cursor is great if you're already in it for coding and want to job search from the same window.
So the agent doesn't actually submit my applications?
For the vast majority of roles, no. Almost every job on Remoet is scraped from a company's external careers page, and the actual application form lives on that company's site. The agent hands you the URL and the context. You click submit on the company's site. That is the honest shape of the workflow and any tool that claims otherwise is either lying or is restricted to a tiny in-network slice. For the small slice of internal jobs (companies posting directly through Remoet's partner system), the agent CAN submit end-to-end using your profile, and it will tell you when that option exists. Either way, you log and track every application through your agent so the pipeline stays in one place.
