Frontend
ReactTypeScriptJavaScriptHTMLCSS
Back to careers
Engineering · Open role
Frontend Engineer
Build fast, accessible, beautiful experiences that help millions of developers learn, practice, build, and grow.
frontend.tsx
01const platform = {
02 learn: true,
03 practice: true,
04 build: true,
05 openSource: true,
06 impact: "global",
07}
08▌
Build at scaleReal users. Real impact.
RoleFrontend Engineer
LevelMid / Senior
Work modelRemote-first
FocusDeveloper Education
The opportunity
Build the frontend developers actually want to use.
CodeHarborHub is building an open-source ecosystem where developers can learn concepts, follow roadmaps, practice problems, build projects, and contribute to the community.
As a Frontend Engineer, you will help turn that vision into fast, accessible, reliable, and enjoyable products. You will work on user-facing experiences where frontend engineering directly affects how people learn.
This is not a role where you only implement predefined designs. You will have opportunities to influence component architecture, interaction patterns, performance, developer experience, and product decisions.
Your impact
Turn complex technology into simple learning experiences.
From interactive tutorials to dashboards, roadmaps, challenges, and developer tools — your work will directly shape the learning experience.
01Product ownership
∞Learning opportunities
What you'll do
Own meaningful frontend engineering work.
You will contribute across the product lifecycle — from architecture and implementation to performance, quality, and iteration.
01
Build and maintain polished, accessible, responsive interfaces for CodeHarborHub.
02
Develop reusable React and TypeScript components that can scale across the platform.
03
Translate product requirements, designs, and ideas into production-ready experiences.
04
Work closely with backend, content, community, and product contributors.
05
Improve frontend performance, Core Web Vitals, SEO, and overall user experience.
06
Write maintainable, testable, and well-documented frontend code.
07
Review pull requests and contribute constructive technical feedback.
08
Identify technical debt and continuously improve frontend architecture.
09
Build interactive learning experiences including roadmaps, practice systems, dashboards, and developer tools.
10
Contribute to open-source projects and help establish engineering standards.
Required
What you should bring
- Strong understanding of HTML, CSS, and modern JavaScript.
- Practical experience with React and TypeScript.
- Understanding of responsive design and accessibility.
- Experience working with Git and GitHub-based workflows.
- Ability to consume REST APIs and work with asynchronous data.
- Understanding of component-based architecture and reusable UI patterns.
- Ability to debug frontend issues independently.
- Good understanding of browser fundamentals and web performance.
- Ability to communicate technical ideas clearly.
- A strong learning mindset and willingness to contribute in an open-source environment.
Bonus
Great if you also have
- Experience with Next.js or Docusaurus.
- Experience with Tailwind CSS or CSS Modules.
- Experience with Framer Motion or other animation libraries.
- Experience with Supabase or PostgreSQL-backed applications.
- Knowledge of testing with Vitest, Jest, Playwright, or Cypress.
- Experience with CI/CD and GitHub Actions.
- Open-source contributions or experience maintaining public repositories.
- Understanding of SEO, structured data, and Core Web Vitals.
Our stack
Technologies you'll work with.
You don't need to know everything on day one. Strong fundamentals and the ability to learn matter more than checking every box.
UI & UX
CSS ModulesTailwind CSSResponsive UIAccessibility
Engineering
GitGitHubCode ReviewCI/CD
Platform
DocusaurusSupabaseREST APIsGitHub Pages
How we work
Engineering is more than writing code.
We look for people who care about the outcome, the users, and the people they build with.
Think in systems
Build reusable solutions instead of solving the same problem repeatedly.
Care about users
Good engineering should make difficult technology easier to understand and use.
Build in the open
Share knowledge, review code, document decisions, and help the community grow.
Own your work
Take responsibility from the first idea through production and continuous improvement.
Hiring process
A practical, transparent process.
We want to understand how you think and build — not make you memorize algorithms for the sake of an interview.
01
Application review
We review your application, projects, GitHub activity, and relevant experience.
02
Intro conversation
A short conversation about your background, interests, expectations, and why you want to work with us.
03
Technical discussion
We discuss frontend fundamentals, architecture, debugging, accessibility, performance, and real-world engineering decisions.
04
Practical challenge
You may be asked to solve a focused frontend problem or improve a small interface. We care about your approach, not just the final output.
05
Team conversation
Meet contributors and discuss collaboration, ownership, communication, and how you work in an open-source environment.
06
Decision
We share the next steps, expectations, and role details clearly.
Questions
Before you apply.
A few answers to common questions about the role and our hiring process.
The role is designed around remote collaboration. Final working arrangements depend on the specific opportunity and team requirements.
Professional experience is valuable, but it is not the only signal we consider. Strong personal projects, internships, open-source contributions, and demonstrated problem-solving can also be meaningful.
Yes. If you can demonstrate strong frontend fundamentals and the ability to build real projects, you can apply. Internship opportunities may be a better fit depending on your experience level.
No. You should be strong in the core frontend technologies. Familiarity with the rest of the stack is helpful, but we expect engineers to learn new tools when needed.
Absolutely. Open-source contributions can demonstrate practical engineering ability, collaboration, communication, code quality, and ownership.
Include your resume or profile, GitHub profile, portfolio if available, relevant projects, and a short explanation of why this role interests you.
Ready to build?
Your next commit could help thousands of developers.
If this role sounds like you, we'd love to see what you've built. Show us your projects, your thinking, and what you want to build next.
Don't have a traditional resume? Your GitHub, portfolio, and open-source work can tell us a lot.