Candidate: Shibmohan Paul
Deadline: 12pm, January 14 2026
The Brief
You’re launching a fictional open-source tool called “CodeSnap” that lets developers take beautiful screenshots of their code.
Think: A tool that makes code snippets look polished and shareable for documentation, social media, or presentations.
Target Audience: Python developers, JavaScript developers, and technical content creators who share code snippets online.
What We Need From You
Part 1: Design Deliverables
Create the following three assets:
1. Instagram Post
Format: Carousel OR single post (your choice) Include: Visual + Caption Goal: Announce CodeSnap to the developer community 2. Twitter/X Post (GIF)
Format: Single post with GIF Include: Tweet copy + Visual Goal: Drive awareness and clicks 3. Landing Page Hero Section
Format: Mockup of the hero section only Include: Headline, subheadline, visual treatment, CTA Goal: Convert visitors in the first 3 seconds Important: All three pieces should feel cohesive but platform-appropriate. Developers should immediately understand what CodeSnap does and why they’d want it.
Part 2: Communication Deliverables (REQUIRED)
This is equally important as the design work. We want to understand your thought process and communication style.
1. Design Rationale Document
Write a brief explanation covering:
Audience Understanding: How did you think about developers as your audience? What makes them different from other audiences you’ve designed for? Visual Decisions: Why did you choose this color palette, typography, and overall style? What were you trying to communicate? Platform Strategy: Why did you design the Instagram, Twitter, and landing page differently (or similarly)? Key Message: What’s the one thing you want people to remember about CodeSnap after seeing your designs? 2. Feedback Response
Imagine your design lead gives you this feedback on your Instagram post:
“This looks great, but I’m worried the visual style might be too playful for our developer audience. They tend to prefer minimal, clean aesthetics. Can you explain your thinking here, and would you change anything based on this feedback?”
Write your response to this feedback. Show us how you:
Explain your design decisions Handle constructive criticism
Submission Guidelines
Deadline: 12pm, January 14, 2026
Format:
Share ONE link with everything organized (Figma, Google Drive, PDF, Notion, whatever works best) Make sure we can view without requesting access All 3 design assets (clearly labeled) Design Rationale Document
Next Steps
If your assignment demonstrates strong fit, we’ll schedule a follow-up call to:
Review your work together Discuss your design rationale in more detail Continue the interview conversation Answer any questions you have about VideoDB Questions?
Feel free to reach out at shivani@spext.co if anything is unclear. We want you to do your best work.
Looking forward to seeing what you create AND how you explain it!
Team VideoDB