Last active
May 4, 2026 03:01
-
-
Save wahengchang/d3d726bbaf6ca4a93370a379b088ab22 to your computer and use it in GitHub Desktop.
New Hire Test Assignment
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # New Hire Test Assignment | |
| Hey π | |
| Thanks for taking the time. We're a small studio team, so we don't really care about job titles β what we care about is whether you can **learn fast, build stuff, and get shit done**. | |
| This little assignment is how we figure that out. | |
| --- | |
| ## The Deal | |
| - β° **Deadline:** 7 days from when you receive this | |
| - π΅ **Compensation:** A small thank-you fee for your time, if you complete it | |
| - π¦ **Delivery:** Everything goes on GitHub (public or private repo, just give us access) | |
| That's it. No tricks. | |
| --- | |
| ## What We're Looking At | |
| We're not grading you on perfection. We want to see: | |
| - How you **learn** something new when you don't already know it | |
| - How you **build** when no one's holding your hand | |
| - How you **ship** β actually finishing and making it usable | |
| If you can deliver the two things below, you're done. No bonus points for over-engineering. | |
| --- | |
| ## What To Build | |
| ### 1. A Runnable Blog System (Web App) | |
| A simple blog with **3 pages**: | |
| - **List page** β shows all posts | |
| - **Post detail page** β shows a single post | |
| - **Tag page** β shows all posts under a given tag | |
| **No design required.** Plain text with `<a>` links is totally fine. We don't care how it looks β we care that it works. | |
| **The real goal:** an AI agent should be able to **clone, install, run the server, and cron the script from #2 β with zero human intervention.** (Some light human setup for *this* assignment is acceptable, but the closer to fully automatic, the better.) | |
| So when you build it, keep asking yourself: *"Could Claude / Cursor / an agent do this end-to-end on a fresh machine?"* | |
| **Requirements:** | |
| - Clean `README` with copy-pasteable commands (`git clone` β install β run β done) | |
| - No hidden manual steps (no "now go click this button in some dashboard" unless absolutely necessary β and if so, document it clearly) | |
| - Bonus if you **deploy it** to Cloudflare / Vercel / Netlify / wherever you're comfortable. Send us the live URL. | |
| Stack is your choice. Use whatever you're fastest in. | |
| ### 2. A "Find & Publish Next Article" Script | |
| One script (or one markdown workflow file) that: | |
| - Finds / generates the next article (you decide how β this is just a test, we're not strict about the source or method) | |
| - Tags it | |
| - Publishes it to the blog system from #1 | |
| **Requirements:** | |
| - Must be **one command to run**. Either a single script, or a markdown file we can follow / paste into something like Claude / ChatGPT / n8n / whatever. | |
| - Don't overthink it. Show us your approach to wiring things together. | |
| --- | |
| ## Ground Rules | |
| - Use any tools, libraries, frameworks, or AI assistants you want. We don't care *how* you build it β we care that it works. | |
| - If you get stuck, ask. We'd rather you ask than guess silently for 3 days. | |
| - If you can't finish everything, ship what you have and tell us what's left. We respect honesty more than excuses. | |
| --- | |
| ## Submission | |
| When you're done, send us: | |
| 1. **GitHub repo link** (with a clear README) | |
| 2. **Live URL** if deployed | |
| 3. A short note (a few sentences is fine) on: | |
| - What you'd improve if you had another week | |
| - Anything you learned along the way | |
| --- | |
| Good luck β looking forward to seeing what you build. π |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment