I Got Tired of Losing to ATS Robots in the UAE Job Market, So I Built My Own Career Command Center

A developer built Interview Command Center, an open-source, self-hosted job-search tool that tracks applications across table, Kanban and timeline views, tailors CVs per job without inventing facts, and generates interview prep from job descriptions, round types and recorded weak spots. The tool runs on any OpenAI-compatible model, including Ollama, LM Studio, vLLM or hosted providers, or without AI at all, and includes browser-run coding challenges scored by AI on correctness, approach, verification, code quality and communication.

"I don't always apply for jobs. But when I do, I apply to 47 of them before lunch and hear back from zero." Let me be honest with you. Getting an interview in the UAE right now is hard. Not "a bit competitive" hard. "Your CV went into a black hole and the black hole didn't even send a rejection email" hard. This post is about how that frustration turned into a side project, and how that side project turned into the tool I now use every single day of my job search. If you're job hunting in the UAE or honestly anywhere in 2026 , you probably know this loop: CV final.pdf , CV final v2.pdf , CV final REAL this one.pdf ... "My spreadsheet of job applications had more tabs than my browser. And that's saying something." Here's the part nobody talks about. A lot of us build with AI now. Copilot, Claude, Cursor: they're part of how modern developers ship. That's fine. That's the job now. But then you sit in a system design round and the interviewer asks: "So, why did you choose a message queue here instead of a direct call?" And your brain goes: "...because the AI suggested it and it worked?" 😅 Being able to explain architecture, trade-offs and decisions out loud is a separate skill. And you can't build it by reading random "Top 50 Interview Questions" blog posts. You build it by practicing on the questions you actually get asked, and fixing the gaps you actually have. "Interviewer: Walk me through your architecture. Me: walks out of the room . Not what they meant, apparently." I didn't set out to build a product. I built it for myself, because I needed one place to: It's open source , self-hosted , and it works with whatever AI you have or none at all . 👉 GitHub: github.com/azadhmhd/interview-command-center https://github.com/azadhmhd/interview-command-center Here's everything it does. Table, Kanban and timeline views. Custom statuses, duplicate detection no more applying to the same role twice, oops , contacts, documents, which CV version went to which application , follow-up reminders, and you can import a job post straight from its URL. This is the one that saves me hours every week. "Auto Apply doesn't get tired, doesn't get sad, and doesn't refresh its inbox every 4 minutes. It's everything I aspire to be." Unlimited resumes and job-specific copies with the same design, a live A4 preview and PDF export. AI tailoring per job may only reword and reorder. It never invents facts. Your CV stays honest; it just speaks the JD's language. Every company gets its own sequence of rounds. You record: Paste your messy post-interview notes and it splits them into questions automatically. This is my answer to the "explain your architecture" problem. Give it the job description, round type, deadline, your CV and your recorded weak spots , and it builds: "Crash course" because that's exactly what happens to my confidence 2 days before an interview. Now at least it's a planned crash. Multi-stage problems in the style of modern AI-assisted coding interviews, plus pattern sections, in Python or JavaScript . Tests run in your browser, and an AI review scores you on correctness, approach, verification, code quality and communication . Yes, communication. Because "it works on my machine" is not an explanation. Full-text search across every interview you've ever done. If two companies ask the same question, it links to one entry. A spaced-repetition revision queue makes sure you don't forget what you learned the hard way. Rubric scoring on correctness, completeness, depth and clarity. Model answers stay hidden until you try first no cheating, I'm watching you . Retry and compare with your previous attempts. Milestones at 3, 2 and 1 day before the interview and on the day itself, with quiet hours, plus a prompt after the interview to capture what happened while it's still fresh. Use any OpenAI-compatible model Ollama, LM Studio, vLLM, hosted providers , or your existing Claude Code / Cursor subscription. No new subscription needed. Every question is marked as actually asked , public report , AI prediction or practice . Facts pulled from your CV stay "AI-inferred" until you confirm them. No hallucinated confidence. Self-hosted, multi-user workspaces, per-record sharing, audit log, export and account deletion. And with no AI configured at all , tracking, journaling, search, revision and scheduling still work. docker compose up and you're running. git clone https://github.com/azadhmhd/interview-command-center.git cd interview-command-center cp .env.example .env set APP ENCRYPTION KEY docker compose up -d --build Open http://localhost:3000 and you're in. I built this for my own job search, but I know I'm not the only one stuck in this loop. So: It's still under construction. It's in the "we'll get back to you" stage of its own hiring process. 😄 But with your feedback we can make it much better, and help each other land bigger opportunities and build better futures. "Rejection is just redirection. Usually towards another 'Apply Now' button." ⭐ If this sounds useful, star the repo, try it out and drop your thoughts in the comments or open an issue: 👉 github.com/azadhmhd/interview-command-center https://github.com/azadhmhd/interview-command-center Let's get hired. 💼 Are you job hunting in the UAE or the Gulf right now? What's the hardest part for you: getting the interview or surviving it? Tell me in the comments. 👇