Reddit Developer Builds a Text-Message Job-Hunting Agent: Can Conversational AI Reshape Job Search?

As general-purpose personal AI assistants continue to proliferate, one Reddit developer has set his sights on a vertical niche—job hunting. The agent he built runs directly on iMessage and WhatsApp, letting users complete the entire flow from building a profile and discovering companies to submitting applications on their behalf, all via text message. The project has sparked a thought-provoking question in the community: are job seekers really willing to hand "finding a job" over to an AI in a chat window?

From General Assistant to Vertical Agent: The Entry Point into Job Search

The developer noted that the rise of general-purpose personal agents like instinct, muse, and dots got him thinking: could there be a vertical agent focused on a single use case? He zeroed in on two directions—finance and careers—and ultimately chose to build in the career space.

That judgment has a real basis. Job hunting is a long, repetitive, and highly personalized process: understanding one's own background, filtering for matching companies, judging hiring signals, and writing and submitting materials—each step consumes significant energy. General assistants tend to stop at "answering questions," whereas the value of a vertical agent lies in stringing this sequence of actions into an automated chain. From a product design standpoint, putting the entry point in a messaging app rather than a standalone app lowers the barrier to use—users don't need to download another app; they just state their needs as if texting a friend.

This "zero-install, conversation-as-a-service" approach aligns with the current trend of AI agents evolving from tools into "delegable proxies": what users hand over is the task, not the steps.

The core difference between a "general-purpose personal agent" and a "vertical agent" lies in task boundaries and degree of autonomy. General agents (such as instinct, muse, and dots mentioned in the article) typically focus on broad capabilities like open-ended Q&A, calendar management, and information retrieval, with the design goal of covering as many everyday scenarios as possible—so they often only deliver "one step"—answering a question or completing a single retrieval. Vertical agents, by contrast, narrow their capabilities onto a single workflow, allowing them to execute multiple actions with side effects in a chain—for example, reading a user's resume, calling recruiting data sources, and automatically sending application emails. This "delegated agent" means users give up not just operational steps but also part of their decision-making authority and outward representation, which is why the demands for reliability, revocability, and permission boundaries far exceed those of general assistants. Vertical scenarios are easier to land precisely because the workflow is relatively fixed and success criteria are clear, making it feasible for the agent to be useful within a limited scope.

What It Can Actually Do: A Closed Loop from Profile to Auto-Application

According to the original post, the agent's core capabilities cover several key stages of job hunting.

• Understanding personal profiles and preferences: Collecting user background information through conversation and conducting deep research to form a candidate profile usable for matching.
• Discovering target companies: Not only based on user preferences but also seeking dynamic clues like "hiring signals" to help filter for companies more likely to be in hiring mode.
• Outreach and application on behalf: The agent proactively contacts these companies and submits applications on the user's behalf.
• Extended career services: Including seeking warm intros from founders, interview preparation, resume creation, and more.

Taken together, it aims to be not just a "job finder" but a career agent covering the entire job-hunting lifecycle. The introduction of "hiring signals" is a key differentiator—traditional job boards rely on already-posted positions, whereas hiring signals may come from earlier signs such as company expansion, funding, or team changes, theoretically enabling timelier applications. However, the quality of auto-applications, matching precision, and whether it creates "spray-and-pray" information noise still depend on how deeply the agent understands the user's profile and how restrained its recommendation logic is.

"Hiring signal" is an analytical concept in recruiting that refers to signs a company is expanding or adding headcount even before formally posting a job. Common sources include funding announcements, rapid team growth on LinkedIn, hiring activity for executives or key roles, product line expansion, and office space leasing. Compared with posted positions on job boards, hiring signals usually appear earlier, theoretically allowing candidates to reach employers before a role goes public and avoid competing against a flood of applications. But they also suffer from high noise and uncertain inference: funding doesn't equal hiring, and headcount growth may target specific functions. Therefore, hiring signals are better used as a basis for ranking and prioritizing candidate companies rather than directly equating to "there's an opening to apply for," and actual effectiveness depends heavily on the quality of the agent's signal sources and filtering logic.

Why Choose iMessage and WhatsApp

Putting the agent on messaging channels rather than building a standalone product is the project's most distinctive product decision.

The advantages are intuitive: reach-and-use immediately, no need to register a new account, conversational interaction that feels natural, and seamless integration into users' daily communication flow. For a task like job hunting that requires repeatedly confirming preferences and syncing progress at any time, the asynchronous nature of texting is actually well-suited—users can reply with a few messages during their commute or in spare moments while the agent pushes things forward in the background.

But this also brings boundary issues. Job hunting involves sensitive data such as resumes, identity information, and salary expectations. On third-party communication platforms, users' concerns about privacy and authorization tend to be higher. In addition, the texting interface is less expressive than a purpose-built UI when presenting structured information like job lists and interview schedules. These limitations mean that while texting is light enough as an entry point, complex decision-making steps may still need a more complete view to support them.

Deploying an agent on third-party communication platforms like iMessage and WhatsApp is essentially borrowing their "communication-as-a-platform" distribution dividend. These apps already have built-in account systems, push notifications, end-to-end encryption, and cross-device sync, so developers can reach users without building their own app—a technical prerequisite for "zero-install, conversation-as-a-service" to work. But the cost is that data sovereignty and capability ceilings are constrained by the platform: on one hand, sensitive information such as resumes, identity, and salary expectations passes through third-party servers, raising authorization and compliance risks; on the other hand, platform review policies for bot accounts and automated messages may tighten at any time, and rich interactions (such as job cards, interview calendars, and file previews) are limited. Therefore, such solutions are better suited as lightweight entry points, while complex decisions and document management often still need to flow back to a proprietary web or app interface.

An Unresolved Question: Would You Use It?

At the end of the original post, the developer posed a direct question to the community: if you were looking for a job, would you use an agent like this?

There's no standard answer, but it highlights the core tension facing vertical job-hunting agents. Supporters would argue that delegating repetitive applications and initial screening to AI can significantly save time, especially during the broad-net phase of job hunting; the cautious would worry that auto-applying weakens the job seeker's control over every communication, and job hunting is precisely an occasion that relies heavily on personal judgment and authentic expression.

From a broader perspective, this project is a small experiment in personal agents moving toward verticalization. It tests two things: the extent to which a conversational entry point can carry a complete task flow, and whether users are willing to hand over the authority to "communicate externally on their behalf" to AI. The answers to these two questions may be more worth watching than how far this agent itself goes.

If you're interested in job-hunting automation or vertical agents, you might want to try the original post and give feedback—after all, what products like this need most for iteration is real usage data from actual job seekers.

One-line Summary

A developer puts a job-hunting agent inside iMessage and WhatsApp to test whether a conversational entry point can carry a full auto-application workflow.

Paragraph Summary

Inspired by general-purpose personal agents, a Reddit developer chose job hunting as a vertical scenario and built an agent that runs on iMessage and WhatsApp. By texting, users can complete a closed loop: building a personal profile, discovering target companies based on hiring signals, and having the agent reach out and apply on their behalf, with additional services like warm intros, interview prep, and resume creation. Putting the entry point on messaging channels lowers the barrier to use and fits the "zero-install, conversation-as-a-service" trend, but it also raises boundary issues around privacy, authorization, and structured information presentation. The article ultimately returns to a core tension: whether job seekers are willing to hand over the authority to communicate externally on their behalf to AI. This is both a small experiment in vertical agents and a feasibility test of whether a conversational entry point can carry a complete task flow.