Launching today
Staffcoder
Build like a real engineer
73 followers
Build like a real engineer
73 followers
Staffcoder is a hands-on coding platform where developers practice real engineering work instead of algorithm puzzles. Choose from 1000+ challenges across 39 learning paths, covering React, Next.js, Django, Spring Boot, Docker, Kubernetes, AI agents, and more. Every challenge runs in a full browser IDE with a real terminal, file system, and live preview, so there is nothing to install. Pick a stack, open a challenge, and build. Free to start.
Free Options
Launch Team / Built With
Dropbox SignSimple, secure eSignatures for the way your team works.
Promoted
Hi everyone,
I'm Shashank, maker of Staffcoder, and I'm really excited to share it with you today.
Staffcoder is a place to practice coding the way you actually work on the job: inside real frameworks, with real tools.
Here's how it works:
Pick a stack, like React, Next.js, Django, Spring Boot, Docker, Kubernetes, or AI agents
Open a challenge
Solve it in a full browser IDE with a real terminal, file system, and live preview
There's nothing to install. Just open a challenge and start coding.
Right now there are 1000+ challenges across 40+ learning paths, covering frontend, backend, fullstack, mobile, DevOps, data, QA, and AI engineering. It's free to start.
Thanks for checking us out.
@shashank21j Does the browser-based terminal support complex projects, or are there any limitations ?
@dipanshu_kushwaha5 Yes, Full IDE in the browser with agentic + AI chat, each in its own container. Only real limit is container cost, which is on us. We keep adding new multi-service projects. Try one: https://www.staffcoder.com/paths
@shashank21j Kudos on the launch. How does one get started? How did you come up and create the challenges?
Thanks @swati_paliwal In order to get started one can create their lifetime free account which gives 1 hour of free usage per week along with some AI credits to try out. Pro plans costs 10$ a month which includes 1$ of AI credits. Every skill is divided into modules, each module has a video to learn from and some challenges to advance to the next module.
About the challenges I have 13 years of experience making/curating content in coding, software engineering domains which helped companies like hackerrank in their hiring tests. I always had the dream to put the same challenges out to the community and hence staffcoder. Right now all our content is educational in nature and hence easy to implement. We'll be soon launching out compete and practice sections for more experienced audience.
For more you can email to me directly shashank[at]staffcoder[dot]com
The puzzle grind never matched the work I did on the job, so this one clicks. I'd sooner practice something that behaves like a real task and find where I'm rusty. Bookmarking it shashank ;)
@amine_aziz_alaoui Thank you your feedback means a lot :). Remember to solve the golden challenges to finish a module faster. Soon we'll be launching compete section for more advanced users :)
Congrats, Shashank and team! Learning React in a real project with a terminal and preview feels a lot closer to the work people will actually do.
Thank you @oleksii_sekundant means a lot. :) I hope we're able to make learning a lot more engaging and enjoyable.
Building and learning in a real-world environment is what makes Staffcoder special. Excited to see it live! 🚀
Really excited to be part of building Staffcoder. Great to finally see it live!
Are you planning to add more Docker and Kubernetes challenges?
"real engineering work instead of algorithm puzzles" is the pitch that makes me want to know how grading works, since that's exactly what's hard about moving past algorithm puzzles. a two-sum problem has one right answer a test suite can check. a Kubernetes deployment or a React component usually has several reasonable ways to do it, and the bad ones often still pass a basic test and only show their cost later, in debugging or at scale. is the grading rubric checking for specific implementation patterns, or just that the end state works, because those give pretty different signals about whether someone actually built it the way a senior engineer would