Original Summary

I recently got a take-home assignment for a job application: build a NotebookLM clone. AI coding tools were explicitly allowed, and I had quite a bit of freedom regarding the implementation. I started on October 12 and had a working prototype after roughly 2.5 hours. At that point, I probably could have focused on polishing the core functionality, recorded a quick demo, and called it a day. But I figured that since I was already building it, I might as well turn it into something I'd actually want to use and maintain. And that's where things got a little out of hand. :D Over the next few days, the project grew into ResearchBench , an open-source, browser-first research application built with SvelteKit and Rust/WebAssembly. It supports document processing, local semantic search and RAG, source-grounded Q&A with citations, summaries, study guides, and even AI-generated podcasts with two hosts. Documents and project data stay in the browser, while LLM features use a bring-your-own-key approach. Of course, once those features were working, I started thinking about everything else that could go wrong. So I added automated testing, security checks, documentation, localization, and a few more rounds of polishing. By the time I finished on October 16, the project had 635 passing tests across unit, Rust, end-to-end, and security testing. I also deployed a public demo, wrote a portfolio case study, and spent probably more time than necessary polishing the application. At some point, I realized I was no longer just finishing a take-home assignment but preparing an actual open-source release. :D To be transparent, I used AI coding agents extensively throughout development, as permitted by the assignment. My focus was on architecture, integration, reviewing the generated code, testing, and making sure the individual components actually worked together. This definitely wasn't four days of manually typing every line of code. The result is nowhere near full feature parity with NotebookLM, and there are still plenty of things I'd like to improve. But I'm pretty happy with how far it got in four days, especially considering that it started as a job application task. If anyone wants to have a look: GitHub: https://github.com/VikingOwl91/research-bench Live demo: https://research-bench.nachtigall.dev/ I submitted the assignment today, so I have no idea yet what the company thinks about it. Regardless of the outcome, I now have another open-source project that I'll probably keep working on. I'd love to hear what other developers think, especially regarding the architecture, UX, and potential improvements. Also, I'm starting to suspect I might have a slight problem with scope creep. :D   submitted by   /u/MrViking2k19 [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/16 11:16:52