Experience layer
Build intuitive learning, practice, project, dashboard, and community experiences.
Build the systems behind a developer learning platform — from beautiful interfaces and APIs to databases, authentication, infrastructure, and everything in between.
CodeHarborHub is building an open-source ecosystem where developers can learn, practice, build projects, explore roadmaps, and collaborate with other developers.
As a Full Stack Engineer, you will work across the entire product surface. One day you might build a React learning experience. Another day you could design an API, improve a database query, implement authentication, or troubleshoot a production issue.
The goal is not simply to add more features. The goal is to build a platform that is fast, reliable, maintainable, secure, and genuinely useful to developers at different stages of their careers.
You will have meaningful influence over technical decisions and the opportunity to work on systems that connect education, open source, community, and developer tooling.
Our engineers work across product boundaries. You should be comfortable understanding how the different layers connect.
Build intuitive learning, practice, project, dashboard, and community experiences.
Connect product experiences through clean APIs, authentication, business logic, and integrations.
Design reliable data models for users, learning progress, projects, contributions, and platform activity.
Keep the platform deployable, observable, secure, and reliable as usage grows.
You will have responsibility beyond implementation — from technical thinking to production quality.
Design and build end-to-end product features across the frontend, backend, database, and API layers.
Develop scalable React and TypeScript interfaces for learning, practice, projects, dashboards, and community experiences.
Build reliable backend services, REST APIs, authentication flows, and data-driven application features.
Design clean database schemas and efficient queries for application data and user workflows.
Integrate third-party services and APIs while keeping security, reliability, and maintainability in mind.
Collaborate with frontend engineers, designers, technical writers, community contributors, and product stakeholders.
Own features from technical design and implementation through testing, deployment, monitoring, and iteration.
Review pull requests, improve engineering standards, and contribute to architectural decisions.
Investigate production issues, debug across the stack, and improve application performance.
Contribute to the open-source ecosystem and help make CodeHarborHub easier for other developers to build on.
The stack can evolve. Strong engineering fundamentals matter more than knowing a particular framework.
Good architecture is important. Good engineering judgment is even more important.
Understand how a feature moves from interface to API, database, infrastructure, and back to the user.
Treat authentication, authorization, validation, secrets, and user data as core engineering concerns.
Choose practical architecture that solves the real problem without unnecessary complexity.
Communicate decisions, review code thoughtfully, document important context, and make contributors successful.
Our process focuses on practical engineering, architecture, communication, and problem solving.
We review your experience, GitHub activity, portfolio, projects, and relevant technical work.
A short discussion about your background, interests, engineering experience, and what you want to build.
We explore frontend, backend, APIs, databases, security, architecture, debugging, and engineering trade-offs.
You may work through a realistic feature or debugging problem covering multiple parts of the stack.
We discuss how you would design, scale, secure, test, and evolve a real product feature.
We talk about collaboration, ownership, communication, open source, and how you work with other engineers.
We share the outcome and next steps clearly, including expectations for the role.
A few things worth knowing about the role and our engineering environment.
The role is designed around remote-first collaboration. Specific working arrangements can depend on the opportunity and team requirements.
You should be comfortable working across the stack, but we do not expect every engineer to have identical depth everywhere. Strong fundamentals, practical experience, and the ability to learn are important.
The platform can use Node.js-based services, REST APIs, and Supabase/PostgreSQL depending on the product area. The exact stack can evolve as the platform grows.
Yes. You should understand relational data modeling, SQL fundamentals, relationships, indexes at a conceptual level, and how application code interacts with persistent data.
This particular position is intended for engineers who already have meaningful full-stack project experience. If you are earlier in your journey, internships and contributor opportunities may be a better starting point.
Yes. Open-source work is especially relevant because our engineering culture values public collaboration, code review, documentation, ownership, and community contribution.
If you enjoy moving between interfaces, APIs, databases, and architecture — and want your work to have a real impact on developers — we'd love to hear from you.