#Crack Devlog #10

What new??

• finally i deployed the mvp, you can check the project out i will provide demo link……
• finally made a frontend, used figma to design it (timelapsed).
• connected it using flask.
• and deployed on Render

What next??

• well add some more roles and then fix some bugs.
• then ship it

Crack devlog #9

what new?

• well i completed designing frontend on figma
• wrote code for it and it is a bit different but yea still good as this is my first full stack software project i have ever built.
• frontend designed on figma is the first image.
• after the 2 images are errors i faced when tried to write the code .
• and the last when after when i took help of claude it is looking cool.

what next?

• ahh… will implement flask i guess

Crack devlog #8

What new?

• Started working on frontend.

Frontend

• So the color theme i choose was purple and golden.
• Dark mode by default.
• Minimalistic.
• Glassmorphism.

What next?

• Will soon implement Flask in backend and connect the frontend.
• Also provide demo link so that you can try it out, well the project still at max will take up to ~5 days to finish.

Crack devlog #7

What new?

• Implemented a dynamic interview engine for asking question.
• Using OOP .
• So if you saw my previous devlog i implemented an interview session engine using OOP, that engine handles the interview session starting and finishing, sending answers of the question to the AI and then receives the evaluation in JSON format which then also the engine parses to convert it into a report.
  Well right now i implemented another engine using OOP to make the interview more dynamic.

The newly implemented engine.

• So basically i implemented an dynamic interview session engine to make it feel like real interview.

What does that engine do?

• Well that engine is basically asking question, but if you have read my previous devlogs, what we implemented first was that user will be asked the role, difficulty and number questions.
• But…… that was just a prototype!!
• Well i made the engine more smarter.
• So basically now the user has to choose the role, then the difficulty and number of questions will be decided by this engine.
• So the questions will start from easy, after every question the engine makes an average of the scores of every questions asked, then it decides whether to level the difficulty or not, if not then it will ask you a few more questions, if the average score will increase to be eligible for next difficulty, the engine will automatically increases the difficulty , the same goes for difficulty medium, hard and scenario based questions too………

Crack Devlog #6

What new?

• Backend is almost finished.
• The prompt is being sent successfully. Prompt
• The data received from Claude Sonnet - 5 is parsed and converted into a report successfully (as you can see in the images).

What next?

• Still this milestone is huge i guess that only ~37% of the Crack is completed.
• Will finish backend soon .
• Will start working on Frontend after the backend finishes.
• The color theme for the frontend of Crack will be Purple and White, also Gold on some parts (very minimal).
• Will make it aesthetic and minimalistic with glassmorphism .
• Also deciding to add more features and more roles so this project might reach ~100+ hours easily.

Sad news!! 😭

Since in my previous devlogs i was mentioning that I will use Claude Sonnet - 5 , well now I will use ChatGPT , because i got $10 AI grant from Stardance from my another project HCAI (check it out ) so i decided to use Claude Sonnet - 5 but i don’t know why but the card i got from HCB was declining, i contacted HCB and they told me that it is the problem with Anthropic, reimbursement wasn’t viable because of $25 Fees (as i am not from USA), the fees itself is more than my $10 AI grant so i decided upon using it for ChatGPT will use Terra model I guess……………

Crack Devlog #5

What is done so far?

• Well my project was at pause since I started it in between my python course, but like now the course is completed so I am back.
• I have made and completed the Interview engine by using OOP .
• I have implemented time tracking system inside the engine.
• Also successfully implemented the answer tracking system, which corresponds to the question asked in the engine.
• Also it records time taken for each question and time taken for the whole interview.

What next?

• So what I will build next is a system for sending the prompt to AI for evaluation .
• Then with the data received I will convert it to scores, graphs and charts; will create a full analysis.
• I will use Claude Sonnet 5 , since it’s one of the strength is detailed and nice explanations, so it fits well for my evaluation and suggestions report.
• For testing I will use Hack Club’s AI API keys , then will shift to Anthropic’s AI API keys , lets hope that my another project named “HCAI” get ratings fulfilled since its been almost a week, but haven’t got no rating at all .
• If it gets rated before “Crack” (which I think will be rated by the time ) then I will buy $10 credits of Anthropic and will use it in my project .

Crack Devlog #4

• well i have completed Interview Engine v1.

• it asks for a specific role, topic and no. of questions.

• and then according to the role, topic and no. of question it pulls questions randomly from topic inside the roles database stored in json files.

• will make it more dynamic by starting from easy question and then increasing difficulty to medium and then to hard, then comes scenario based questions, where the user will be asked real world problems to solve, only if they can answer hard questions very well.

• after making engine more dynamic i will add more roles to it, it has right now 9 full roles.

Crack Devlog #3

–> hmm……yo!
–> well nothing interesting but completed 4 roles.

–> i also got an idea that i might also add practical or scenario based questions, since thats where real thinking is required. according to my plan questions will be asked from easy and then if the answer is correct then the difficulty will increase from easy to medium and then to hard also if answered very well.
–> if the user can answer hard questions easily then the difficulty levels up to scenario based questions, where user will be asked practical or scenario based questions, like real world problems which he/she needs to answer.
–> then the report of their interview will be created by AI, accordingly how they answered the question
–> if the user was not able to answer easy/medium/hard difficulty questions correctly then the interview will stop at that difficulty level and the report will be handed to them accordingly by AI.

Crack Devlog #2
–>hmm……….
–> Well, I have been working on this project for like 3-4 days, have completed the software engineer database, and will soon end the backend developer database.
What am i making??
–> i am making an ai interview coach, which asks the questions that can be asked in an actual CS job interview.
–> it starts with easy questions , and then increases the difficulty according to the performance of the user.
–> after the interview ends, it creates a full-fledged report of the user highlighting strong and weak points and also give overall rating out of 100, and also suggest what and how to improve the answer.

Crack Devlog #1

well…………
it’s been almost 2 days i have been working on a project called Crack🥀 so that you can crack your interviews easily .

idea is pretty simple:
–> the user can select an option from the list of CS roles for ex. Software Engineer, Data Scientist, DevOps etc.
–> the user will be asked few questions on the roles or option they selected (just like in job interviews).
–> number and difficulty of questions will depend on how user will answer the question.
–> after the interview is over, the AI will create a full fledged report of the answers given by the users, and will be given score with report on how they performed.

as of now:
–> i have created i guess approx. 5% of the database.
–> a working prototype which pulls question from the database according to the user input.
–> UI is still on terminal 🥀 .
–> not very user friendly or dynamic but a working prototype which i will further improve and polish.

what’s next?:
–> write the database, at least completing 7-8% of it.
–> make the code more dynamic.

how will it work?:
–> well i will use APIs to get the report from an AI.