WeframeTech Backend Hiring Task 📝
Walkthrough of task
https://youtu.be/8E_d_671zbI?si=J5i-7rK6nEIYb2iR
Deadline: Before 6 PM IST on the 30th.
🔥 Backend Developer Recruitment Task – Advanced
Payload CMS Challenge (Duration: 1 Day)
🎯 Objective:
Build a Dynamic Workflow Management System inside Payload CMS where users can
create, assign, and track multi-stage approval workflows for any collection (e.g., Blog,
Product, Deal, Document) dynamically via the Admin UI. This must be fully reusable and
support unlimited nested workflows.
Don’t worry if you’ve never heard of Payload CMS before. It’s a free, open-source
Node.js headless CMS that you can explore at https://payloadcms.com. It’s
developer-friendly, highly customizable, and can even be deployed on Vercel at no cost.
We’re not expecting you to be an expert — in fact, that’s the point. This task is intentionally
designed to push you outside your comfort zone. We want to see how you approach
something new and unfamiliar, how quickly you can adapt, and how well you can navigate
a modern tech stack without handholding.
This isn’t about copying a project off GitHub or submitting a shiny portfolio piece. It’s
about showing us what you’re really capable of when you’re thrown into the deep end. How
you problem-solve. How you learn. How you build under pressure. We’re not here to judge
you by a polished CV — we want to see your mindset, your grit, and your resourcefulness in
action.
So yes, this task might frustrate you. It might make you Google a lot. It might force you to
rethink things. But that’s exactly why we’ve assigned it. Because that’s what real work
looks like.
If you're truly serious about growth, and if you want to prove you're more than just
another developer with a portfolio full of templates — this is your shot. Step up. Show
us what you’ve got.
Good luck — we’re rooting for you. But more importantly, we’re watching closely.
🧩 Business Context:
The client is a mid-sized enterprise that wants to build internal tools for document approvals
(e.g., Legal Contracts, Product Specs, Blog Posts, etc.). They want to use Payload CMS for
its flexibility and TypeScript-first API.
🚀 Getting Started from Scratch
New to Payload CMS? No problem! Visit https://payloadcms.com and thoroughly read their
documentation to understand installation, setup, and core concepts. Start with their "Getting
Started" guide to install Payload locally using Node.js. Learn about collections, hooks,
plugins, and admin customization. Study their deployment guides for platforms like Vercel.
Understand authentication, access control, and custom components. This foundation is
crucial for building the dynamic workflow system. Don't skip the docs - they're your roadmap
to success!
🧪 Core Challenge Requirements:
1. ✅ Dynamic Workflow Engine (Core Complexity)
● Admins should be able to create workflows (collection: workflows) with any
number of steps.
● Each step should:
○ Be assigned to a user role or specific user
○ Have conditions (e.g., field value checks like “amount > 10000”)
○ Have step type: approval, review, sign-off, or comment-only
● Steps must be evaluated and triggered automatically on document save or
update.
● Workflows should be attachable to any existing collection (Blog, Product,
Contract, etc.)
✅ Bonus: Support conditional branching between steps based on the previous outcome.
2. 🛠️ Dynamic Injection into Admin UI
● Add a tab or collapsible area in each relevant collection's edit view:
○ Displays current workflow progress
○ Shows logs: who approved, when, outcome, comments
○ Enable inline actions for roles/users (approve/reject/comment)
3. ⚙️ Audit Trail Collection (workflowLogs)
● Create a separate collection workflowLogs that records:
○ Workflow ID
○ Affected document ID & collection
○ Step ID
○ User, action, timestamp, optional comment
● Make this immutable. Logs must never be editable.
4. 🔌 Custom Plugin (Non-Admin Triggered Logic)
● Write a Payload plugin (or hook-based system) that:
○ Triggers the appropriate workflow engine when any watched collection is
created/updated.
○ Evaluates which step is due next.
○ Sends custom email notification (simulate with console logs).
○ Enforces permission-based step locking.
✅ Bonus: Allow setting SLAs per step (in hours) and auto-escalate if overdue.
5. 🚀 Provide APIs
● Provide 2 custom REST APIs:
1. POST /workflows/trigger – manually trigger workflow on a document
2. GET /workflows/status/:docId – return workflow and step status for
given document
🧪 Constraints:
● Do not use 3rd-party workflow libraries.
● Do not hardcode collection names – system must be dynamic.
● You must use Payload v2+, TypeScript, and express-based plugins/hooks only.
● UI changes must be done using Payload’s admin.components override system.
🎓 Submission Expectations (Private)
Please submit the following in a private GitHub repository (do not share it publicly or on
social platforms such as LinkedIn):
What to include:
1. Codebase
A working Payload CMS project with seed data for two collections:
● Blog
● Contract
2. README with:
● Setup instructions (step-by-step installation and running)
● Brief explanation of the architecture (file/folder structure, plugin logic)
● Sample workflows (examples of how workflows work)
● Demo credentials (for both admin and reviewer roles)
● Deployment guide (how to deploy to Vercel or other platforms)
3. 🚨 MANDATORY: Loom Walkthrough Video
CRITICAL SUBMISSION REQUIREMENT:
Your Loom video submission MUST include:
✅ Your face must be visible throughout the video (camera on)
✅ Proper task overview and demonstration (2-3 minutes minimum)
✅ Clear explanation of your approach and architecture
✅ Live demonstration of all features working
✅ Screen recording of the admin interface and workflow system
⚠️ REJECTION CRITERIA:
● Video without your face visible = AUTOMATIC REJECTION
● Video without proper task overview = AUTOMATIC REJECTION
● Video that's just screen recording without explanation = AUTOMATIC REJECTION
● Generic or rushed walkthrough = AUTOMATIC REJECTION
What to cover in your Loom video:
1. Introduction (with your face visible)
2. Architecture explanation (show your code structure)
3. Live demo (create a workflow, assign it, test approval process)
4. Technical challenges you faced and how you solved them
5. Bonus features you implemented (if any)
6. Deployment demonstration (show it working live)
Important Notes:
● Keep the repository private.
● Do not share this project on LinkedIn or any social media platforms.
● Please grant repo access to: majhisambit2@gmail.com
🧠 Evaluation Criteria:
🔧 Architecture & modularity
🔄 Reusability & dynamic config
●
🔒 Security & role-based access
●
⚙️ Payload-specific expertise
●
🧩 Problem-solving under constraint
●
🎥 Quality of Loom presentation and explanation
●
●
📚 Recommended Learning Path
Day 1 Preparation:
1. Morning (2-3 hours): Set up Payload locally, go through basic tutorials
2. Afternoon (2-3 hours): Study collections, hooks, and plugins documentation
3. Evening (1-2 hours): Plan your architecture and approach
Development Day:
1. Early Morning: Set up project structure and basic collections
2. Morning: Implement workflow engine core logic
3. Afternoon: Build admin UI components and integration
4. Late Afternoon: Implement APIs and testing
5. Evening: Create Loom video and finalize submission
Submit your assignment here
https://forms.gle/qXAR7amswc3bbT1eA
🚀 Why Join Us at WeFrametech?
At WeFrametech, we're a fully remote company working with global clients and building
digital products using the latest technologies. We're not just another dev shop — we focus
on creating solutions that actually matter, used by millions of people across the world.
We're a young, dynamic team that values creativity, accountability, and integrity above all
else. We believe great teams are built on trust and ownership, not just skillsets.
If you're looking for a place where your work has real impact and you're constantly learning
and growing — you'll love it here.
🌟 What to Expect When You Join weframetech:
🚀 Real-World Impact Build production-ready products that reach millions of users, from
startups to billion-dollar companies.
🌍 Global Exposure Work directly with international clients, giving you real-world
experience with diverse teams, cultures, and markets.
🛠 Work with Cutting-Edge Tech From Jamstack and serverless to AI and commerce
ecosystems, you'll always be working with modern, high-demand tools.
💬 Open & Transparent Culture Weekly team calls, feedback loops, and async
communication — we keep things clear and collaborative.
🌱 Career Growth & Ownership You'll be given real responsibilities from Day 1, and a path
to grow into leadership or specialization roles.
🌴 100% Remote & Flexible Work from anywhere, on your schedule. We care about
results, not time clocks.
🤝 A Team That Actually Cares We're here to support each other, push boundaries, and
have fun doing it.
🎉 Young, Driven & Fun Culture No corporate BS. Just a passionate team building cool
things and solving real problems.
🧘 Mental Wellness & Balance We're serious about work-life balance and maintaining a
healthy, respectful work environment.
About The company: https://weframetech.com/ (Weframetech Solutions PVT Ltd)
LinkedIn: https://www.linkedin.com/company/weframetechcom
Best regards,
Vipul Uthaiah
CSO, Weframe Tech
