What we will be building? π
- Online CV https://nikola-mitic.dev/cv/patient21
- Blog / Tweet like interface https://nikola-mitic.dev/tiny_thoughts
- Chat interface to let people chat to your CV https://nikola-mitic.dev/ai_clone_interview/chat
- And finally audio interface to give your CV voice and let people talk to your CV https://nikola-mitic.dev/ai_clone_interview/talk
Entire source code:
Preamble
It's the year 2024 and tech word is going crazy. Somehow you find yourself in a need for a new job. You start applying for jobs. And you keep applying, and you apply some more, and more, and even more.
But that right job offers does not come!
And you start asking yourself what are you doing wrong, and how can you optimise your job search, since by now your figure it out it is a numbers game! As market is saturated with us developers (especially us web frontend developers).
This is where I am at the moment, and where I was for the past 2 years.
There is much I can say about this topic, and hopefully help others, as well as get off my chest all the unfairness going around job market at the moment. But I won't.
Instead I want to share what help me optimise and reduce the amount of interviews I am having which otherwise should not even happen as they bring no job opportunities.
Simply put I want to clear out all the processes which are not a match, while also increasing amount of processes which are more likely to be a match.
By now you already experiences automatic CV filtering, where some sort of AI will scan your CV and you would be marked as match or not. You might not like it, I know I do not, but it makes sense. I wanted to do the same with companies.
Ex coworker of mine, said.
This is like playing uno reverse card on companies using AI to filter our job applications, we should just let their AI bots talk to our AI bots.
To make it clear, that was never a goal. But it does sounds funny. Tech interviews are known to be ridiculously long. 6 rounds seems to be the norms nowadays. So let's do some basic math (the only one I know), if you have 10 interviews a week (which has been a norm for me), and half of it is first round where they ask basic questions, and if one interview as such lasts 30 minutes, you just save yourself 7.5 hours per week! You got almost a full work day back.
Not too bad!
Solution is rather simple:
Have an AI be aware of you resume, build a simple chat interface, where hiring managers and recruiters can ask questions which they usually asked on first initial calls.
Before we start
I won't be explaining line by line, after all how you do things is up to you. However, I will explain the concept, give you the blueprint, give you detailed solution to a common problems you will encounter and share the whole repo to the relevant code for guidance.
I believe you can learn a lot and have fun in the process.
Prerequisites
- For the concept itself nothing, you do not even need to be a developer. If you are not a developer and fail to understand, it is up to me! I did a bad job explaining it.
- For implementation you can choose your own stack, I went with
- NextJS with TS - For CV implementation
- Tailwind CSS - For styling
- Node JS - For the one and only BE service we will be writing
- Llamaindex TS - To easy out working with LLM
- Open AI api - For both LLM and embedding model
- Groq API - For LLM, optimal, but at the time of writing it is free
- Eleven labs API - For voice cloning and streaming
- Hygraph - For content hosting
- Vercel - For deployment CV hosting / deployment
- Renderer for Node JS service hosting / deployment
But wait how much will I have to pay for this? πΈ
Almost nothing! Except for Open AI all of the tools have generous free tiers, limits you will hardly surpass, considering that this is your online CV it really should not be getting a tone of visitors
β€οΈIf you would like to stay it touch please feel free to connectβ€οΈ
Top comments (0)