Are you passionate about building elegant, high-performance digital experiences? Do you thrive in a modern PHP ecosystem and love working with clean architecture, scalable hosting, and robust infrastructure? We’re looking for a Craft CMS Developer to join our team and help deliver powerful, secure, and beautifully engineered web platforms. If you’re confident working across PHP, databases, web servers, and cloud environments — this could be your next big move. What You’ll Be Working With Craft CMS is a modern PHP/Composer application running on a standard LAMP or LEMP stack, with MySQL or PostgreSQL as the database backend. You’ll be hands‑on across the full stack environment. Runtime & Language PHP 8.0.2+ (8.2+ preferred) Database (One Of) MySQL 5.7.8+ (InnoDB required) MariaDB 10.4+ Web Server (One Of) Apache 2.4+ with mod_rewrite Core PHP Extensions Required bcmath, ctype, curl, dom, fileinfo, gd or imagick (for image handling), iconv, intl, json, mbstring, openssl, pcre, pdo, reflection, spl, zip PHP Configuration Recommendations upload_max_filesize and post_max_size aligned with upload requirements You don’t just deploy — you fine‑tune for performance and reliability. Bonus Points For Experience With Redis or Memcached (caching & session storage) SSL/TLS implementation (HTTPS) Node.js, npm, and Vite (Craft 4+ asset bundling) Queue drivers (database or Redis) for background jobs like image transforms and emails Cloud hosting platforms such as AWS, DigitalOcean, Render, or Craft‑optimized hosting like Servd Infrastructure & Hosting You should be comfortable deploying and managing applications in: Linux-based environments (Ubuntu, Debian, CentOS) is most common Cloud-first architectures The ideal candidate should understand what it takes to run secure, performant, and maintainable systems in the real world. What We’re Looking For You’re more than someone who “installs Craft.” You understand the ecosystem — from Composer dependency management to database performance tuning, server configuration, background job queues, and caching strategy. #J-18808-Ljbffr