Intermediate Software Developer (Frontend) - Pine Hosting (Remote)

About Pine Hosting

Pine Hosting runs game servers for players and communities: Minecraft, Rust, ARK, Palworld, Project Zomboid, FiveM, Hytale and many more. We don’t resell someone else’s control panel. We build and maintain our own.

At the center is the Pine Game Panel, our own fork of Pterodactyl that we have built far beyond the original. It handles one-click modpack and plugin installs, a template shop, Minecraft version switching, Steam Workshop collections, DDoS protection management, subdomains and AI-assisted log analysis. Around it sit our Astro website, our WHMCS billing platform, Discord bots and a set of internal tools.

The role

We’re hiring an intermediate software developer whose main focus is the frontend. You’ll own the user interfaces our customers touch every day. That means features in the React panel, pages on the Astro website, and the PHP and HTML templates behind our billing and other systems.

This isn’t a junior role. You should be able to take a feature from an issue to a reviewed pull request with little hand-holding. You should also be able to read code you didn’t write and know when to ask a question.

Backend experience is a real plus but not required. If you’re strong on the frontend and want to grow into full-stack work, we’ll train you on our PHP/Laravel backend and the systems around it.

What you’ll work on

Most of your time goes to the first two areas. The rest grows as you do.

• Pine Game Panel (React, TypeScript, Tailwind CSS, styled-components, easy-peasy, React Router; Laravel API): build and polish customer features such as the file manager, console, backups, schedules, mod and plugin installers, template shop and game-specific settings screens
• Website (Astro, TypeScript, Tailwind CSS 4): product and game pages, pricing, tools and blog; keep it fast, accessible and SEO-friendly
• Billing and client area (WHMCS: PHP, Smarty templates, HTML/CSS/JS): customize the client area, order flow and email templates; write hooks
• Internal tools (React + Vite; ASP.NET Core): admin dashboards for staff, such as product data, sponsorships and hardware planning
• Panel backend, as you grow (PHP 8.2+, Laravel 12, MySQL, Redis, queues): API endpoints, services, background jobs, tests

On the panel, there is also modernization work ahead. Planned items include moving off twin.macro to plain Tailwind, upgrading React and Tailwind, and reworking layouts to be truly responsive. If you enjoy leaving a codebase better than you found it, there’s plenty to do.

What we’re looking for

• Around 2–4 years of professional or equivalent real-world frontend experience, with shipped work you can show us
• Strong React and TypeScript: hooks, component design, state management, and talking to REST APIs
• Solid HTML and CSS fundamentals, with Tailwind CSS experience; responsive layouts, accessibility and cross-browser quirks shouldn’t scare you
• Comfort with plain PHP and server-rendered HTML templates, since not everything we run is a single-page app
• Day-to-day Git: branches, pull requests, rebasing, and taking code review well
• Debugging skills: browser dev tools, network inspection, and reading a stack trace in a language you’re less familiar with
• Clear written communication in English; much of our work is async through issues and PR reviews

Bonus points

None of these are required. Each one helps, and backend experience helps most.

• Backend / full-stack: Laravel or another PHP framework, MySQL, Redis, queues and background jobs, writing tests (PHPUnit, Jest, Playwright)
• Astro or other static and hybrid site frameworks, plus web performance and SEO work
• WHMCS or other billing and client-area customization
• Real-time UIs: WebSockets and streaming data, such as live consoles and resource graphs
• Other languages in our stack: Go (our Wings daemon), C#/.NET (internal tools), Node.js (Discord bots)
• Infrastructure basics: Linux, Docker, nginx, CI pipelines
• Game servers: you’ve run or modded Minecraft, Rust or similar, so you know what our customers are trying to do

How we work

• Work starts from an issue, goes onto a feature branch, and lands through a pull request that a senior developer reviews
• Merged changes deploy automatically to a staging environment, so you test against the real thing before a versioned production release
• Small team, real ownership: what you build is in front of customers within days, not quarters
• Mentoring t…