|
In my previous post in this series, I shared some context behind how I ventured out to start building an AI job search agent and journeyed into the land of crystallizing the difference between an app and an agent. This post provides another window into that journey.
The Presentation Layer I introduced the concept of an ARD (Agent Requirements Document/Documentation) - essentially a PRD but for AI agents. As I was writing the ARD for the job search agent, I started thinking about the details of the presentation layer. Given the need for user inputs (e.g. resume details and role preferences) and the need for a human-readable output (e.g. for suggested roles and companies), the design started shaping up much like an app fairly quickly. From my understanding of what AI Agents are, there are versions of AI agents that “can just do things” for the user. Given the right tools, access, and permissions, the agent can act on a user’s behalf and sometimes the output is a completed process. In the case of job searching, the output might be navigating all the way to the point of submitting an application - already filling in pertinent information and attaching the user’s resume. That sounds interesting - and has its benefits and challenges. However, I realized that what I set out to build was more of a discovery tool. Imagine: “Help me discover something” vs. “Help me do something”. In other words: “Show me something” [the app use case] vs. “Do something” [the agentic use case]. Sure, an AI agent could still “help me discover something” but the UI layer is still pertinent - for presentation purposes and also for interactivity. Manual Pieces of An Otherwise Automated Flow A job search is not necessarily a “set it and forget it” type of process in the way making an appointment or booking travel might be. Users will likely want to adjust preferences over time and will likely have updated resumes as time progresses (at least until their next great opportunity is secured!). The general analysis, search, and presentation process can run in an agentic fashion but making updates to the criteria used by that process still remains manual. Additionally, I wanted the user input interface and output surface to be presented side by side and I added details around this in the ARD. I think a typical agentic approach could work by presenting the results in a list or even by generating a new UI with each output (infra considerations aside). However, given the desired user experience and presentation modality, it became more and more apparent that an app was the better option for the time being. In summary, when considering what my job search tool would look like, it being an app rather than an agent became the brighter option. The Series Continues The story isn’t finished for now - I plan on delving into what an AI agent is in another post. Posting soon, Jewel – Extra Tidbits: In case you’re wondering about the status of the job search tool discussed above, I stopped work on it, for now, to focus on other things. If you’re currently job searching, feel free to leverage the process below. 1. Gather resume details that you want analyzed
2. Use an LLM to analyze the details
3. Iterate on the prompt if needed until you get a list of open roles with links. You might learn about a company you haven’t heard about before!
4. [Recommended] Keep track of companies that you’ve checked and the last date you checked their careers site for opportunities that might be a fit for your background and what you’re looking to do.
If you too are a Believer in Jesus Christ, remember that we can reverently pray about everything - including a job search - and ask Our Father for what we need in Jesus' Holy Name. I recommend that you pray over your job search. That will be better than any and all other processes I can recommend to you. Pray first (wisdom). Pray in the midst of the search (encouragement). Pray once you have your new great opportunity (thanksgiving). Keep praying. Scripture for Encouragement: 1 John 5:14; Luke 11:9-10
0 Comments
So exactly what is an “AI Agent”? Or maybe the quotation marks only need to be around “Agent” since I assume the AI part is implied when talking about agents in some circles. Also, some readers might be thinking ’you should have asked this question 3 years ago’ and others might be thinking ’thank you, I’m glad you brought this up’. I think that difference is exactly why this post and my question are both so timely.
Let me give you some more context. My professional career has largely (maybe 95.8%? :)) been in tech bridging business and technology. Throughout nine years of experience, I’ve wavered between what the mix looks like. Or if you want to continue with the bridge analogy - which piece of land I’m building the bridge from. Sometimes I’ve leaned more into the business side and sometimes the tech side. Lately, the two have been melding really nicely and I think the rise of the availability of tools for builders really helps with that. As such, I’ve finally ventured out to build! I built on an idea I had years ago and now have a working prototype that I got launched quickly given the assistance of an AI tool. I also ventured out to build an agent. In job searching, I built a kind of system involving using AI tools for resume analysis and searching for available roles that could be a potential match given my resume details. After running the loop several times then moving on to start documenting which companies I had taken a look at, the thought of using AI came to mind. It’s almost like programming. How do you know when it’s time to use recursion? Given the excitement and many, many posts and discussions about AI agents, I thought this would be a great opportunity to build an agent that could just run the loop for me. With this, the idea of “Agent Requirements Documentation” or an “Agent Requirements Document”, ARD for short, came up. It’s like a PRD but with specific details for tooling and inputs and outputs for the desired agent. It can also be used as a feeder into AI systems to speed up agent development. I started on the road to build an AI job search agent quite optimistically. Then, as my journey continued, I thought of the UI. Well, what would the interface look like? My original tracker is in Google Sheets. It’d be great to have some way for users to input details in a nice, clean UI then have the results presented similarly - in a nice, clean UI. This is around the time in the design process where I really started to think about what makes an AI agent an AI agent. When is something an agent vs. an app? If you’re wondering that too, stay tuned. I’m planning on writing at least a couple more posts along these lines - one walking through definitions of an “AI Agent” and another describing how my plans to build a job search agent resulted in something that looked more like an app. Before I conclude this post, I want to give all Honor and Glory to my Lord and Savior Jesus Christ. If you check out my other posts, you’ll see that it’s been a while since I’ve posted on this blog. A LOT has happened in my life over the past two years and God has kept me through it all. Not only has He kept me but He has also blessed me with ideas and encouragement in my journey as a technologist. This includes ideas described above around ARDs, using AI to automate the job search loop, and the ideas for this and other blog posts. All Glory to God. Thanks for reading! If you have any follow-up questions on AI Agents or my relationship with God, please feel free to reach out and contact me. Next post loading… Jewel Happy New Year!
2024 is here and I'm so grateful to have been able to spend time reflecting and looking forward. Something I've wanted to return to for some time is sharing some of the ideas, thoughts, and learnings I've gained as I've delved into new areas in my career. I have blogged before and I even started a podcast at one point. In recent months, my desire to 'return' to this type of sharing in these professional areas of my life has really grown. In considering the how, what, when, and where, I've returned here to this blog! The structure, name, location, etc., etc. of this blog may change but I'm starting this new chapter, here and now. Stay Tuned I have a number of post ideas planned out covering topics in tech and career journeying. Along these lines, do you have any questions or topics that you'd like to see me address? Let me know! Happy Tuesday and thanks for reading! Until the next post, Jewel |
AuthorThanks for visiting my blog! From Guyana to The Bahamas to Texas to New York City and The San Francisco Bay Area, it's easy to say that I've had many interesting and unique life experiences. Interesting and unique are also great descriptors for my career journey. Categories
All
Archives
March 2026
|