Senior Developer Full time ENGLISH REQUIRED
Budget: $15 – $25 USD
Senior PHP Developer with deep Laravel experience and strong DevOps instincts — someone who thrives in agile teams and knows how to take a modern app from development to deployment, securely and efficiently.
You'll work with the TALL stack (Tailwind CSS, Alpine.js, Laravel, Livewire), Vue.js, PostgreSQL, and AWS, building and scaling multi-tenant applications. You’ll also take ownership of server management, CI/CD workflows, and automation that keeps development and deployment smooth, fast, and reliable.
Tech Stack & Tools :
Backend: PHP 8+, Laravel, Livewire, FilamentPHP
Frontend: Vue.js, Alpine.js, Tailwind CSS
Database: PostgreSQL
Cloud/DevOps: AWS, Docker, GitHub Actions, CI/CD pipelines
Workflow: Git, GitHub, PR-based development, Agile
What You Bring :
5+ years of professional PHP development, with expert-level Laravel knowledge
Strong experience with Livewire, Alpine.js, and FilamentPHP
Solid frontend capabilities with Vue.js and modern JavaScript
Hands-on experience with multi-tenancy
Deep understanding of PostgreSQL
Proven ability to manage Linux servers, configure NGINX, handle deployment pipelines
Comfortable working with AWS infrastructure (EC2, S3, etc.)
Experience setting up and maintaining CI/CD pipelines (GitHub Actions, etc.)
Familiarity with logging, monitoring, and alerting tools
FAQ ( COMMON QUESTIONS)
1) Can you provide more details on the specific scale and complexity of the multi-tenant applications?
The application integrates both e-commerce and auction functionalities, allowing customers to register, purchase items directly, or place bids on auction listings.
From a multi-tenant perspective, the system supports resellers who can create and manage their own independent storefronts. Each tenant can list products for direct sale or auction, with full control over their inventory and store settings. Additionally, tenants have the option to publish selected items to the main marketplace (our primary domain), giving their products greater visibility to a wider audience.
Technically, the system uses a schema-per-tenant model in PostgreSQL, which allows for strong data isolation, easier per-tenant customization, and scalable growth as the number of tenants increases.
2. What is the current size and structure of your existing codebase?
The current codebase includes core features such as cart functionality, an auction system, and integrated payment and shipping services. These components have been developed and are functional, but still require further testing, refinement, and optimization for production readiness.
The application follows a standard Laravel structure, adhering to Laravel’s conventions for routing, controllers, models, and services.
While the multi-tenant infrastructure is already in place (schema-per-tenant using PostgreSQL), tenant-specific feature integration is still in progress. Initially, features were being developed simultaneously for both the main domain and tenants, but we temporarily prioritized the main domain to accelerate its delivery.
3. What specific logging, monitoring, and alerting tools are currently in use or desired?
Currently, we do not have logging, monitoring, or alerting systems set up for the development environment, as we’re still in the early stages of implementation. However, for our existing live application, we are using Rollbar for real-time error tracking and logging. As the project matures, we plan to extend similar observability tools into the development and staging environments to improve debugging and system reliability.
4. Are there any specific security requirements or compliance standards that need to be met?
At this stage, there are no formal compliance requirements such as PCI DSS or GDPR that we are obligated to meet. However, we do follow common security best practices for Laravel applications, including CSRF protection, input validation, secure password hashing, and proper access control.
The project is not shared with any third parties, and all code contributions are managed internally through a private GitHub repository.
We use a pull request (PR) workflow where changes are submitted for review before being merged into main branches. This helps ensure code quality, maintain consistency, and catch potential security or logic issues early in the development cycle.
As the platform evolves and begins handling more sensitive data or scales to new regions, we plan to reassess and adopt any necessary security standards or compliance frameworks based on regulatory needs and user trust.
5. Can you provide further details on the expected daily responsibilities and team collaboration dynamics?
Daily responsibilities will revolve around feature development, bug fixing, code reviews, and maintaining the overall performance and stability of the application. You'll be working on both backend and frontend tasks, collaborating closely with the team to implement and improve functionality.
Our communication primarily takes place through Slack, where we discuss updates, raise blockers, and share quick feedback. While the team is small, we make it a priority to communicate daily to ensure we're aligned and responsive.
We also showcase progress one to two times per week, offering a chance to demo completed work, discuss any issues, and plan upcoming tasks. We follow a collaborative, open approach to feedback, with pull requests reviewed by peers to ensure high-quality code and thoughtful discussion.
You'll work with the TALL stack (Tailwind CSS, Alpine.js, Laravel, Livewire), Vue.js, PostgreSQL, and AWS, building and scaling multi-tenant applications. You’ll also take ownership of server management, CI/CD workflows, and automation that keeps development and deployment smooth, fast, and reliable.
Tech Stack & Tools :
Backend: PHP 8+, Laravel, Livewire, FilamentPHP
Frontend: Vue.js, Alpine.js, Tailwind CSS
Database: PostgreSQL
Cloud/DevOps: AWS, Docker, GitHub Actions, CI/CD pipelines
Workflow: Git, GitHub, PR-based development, Agile
What You Bring :
5+ years of professional PHP development, with expert-level Laravel knowledge
Strong experience with Livewire, Alpine.js, and FilamentPHP
Solid frontend capabilities with Vue.js and modern JavaScript
Hands-on experience with multi-tenancy
Deep understanding of PostgreSQL
Proven ability to manage Linux servers, configure NGINX, handle deployment pipelines
Comfortable working with AWS infrastructure (EC2, S3, etc.)
Experience setting up and maintaining CI/CD pipelines (GitHub Actions, etc.)
Familiarity with logging, monitoring, and alerting tools
FAQ ( COMMON QUESTIONS)
1) Can you provide more details on the specific scale and complexity of the multi-tenant applications?
The application integrates both e-commerce and auction functionalities, allowing customers to register, purchase items directly, or place bids on auction listings.
From a multi-tenant perspective, the system supports resellers who can create and manage their own independent storefronts. Each tenant can list products for direct sale or auction, with full control over their inventory and store settings. Additionally, tenants have the option to publish selected items to the main marketplace (our primary domain), giving their products greater visibility to a wider audience.
Technically, the system uses a schema-per-tenant model in PostgreSQL, which allows for strong data isolation, easier per-tenant customization, and scalable growth as the number of tenants increases.
2. What is the current size and structure of your existing codebase?
The current codebase includes core features such as cart functionality, an auction system, and integrated payment and shipping services. These components have been developed and are functional, but still require further testing, refinement, and optimization for production readiness.
The application follows a standard Laravel structure, adhering to Laravel’s conventions for routing, controllers, models, and services.
While the multi-tenant infrastructure is already in place (schema-per-tenant using PostgreSQL), tenant-specific feature integration is still in progress. Initially, features were being developed simultaneously for both the main domain and tenants, but we temporarily prioritized the main domain to accelerate its delivery.
3. What specific logging, monitoring, and alerting tools are currently in use or desired?
Currently, we do not have logging, monitoring, or alerting systems set up for the development environment, as we’re still in the early stages of implementation. However, for our existing live application, we are using Rollbar for real-time error tracking and logging. As the project matures, we plan to extend similar observability tools into the development and staging environments to improve debugging and system reliability.
4. Are there any specific security requirements or compliance standards that need to be met?
At this stage, there are no formal compliance requirements such as PCI DSS or GDPR that we are obligated to meet. However, we do follow common security best practices for Laravel applications, including CSRF protection, input validation, secure password hashing, and proper access control.
The project is not shared with any third parties, and all code contributions are managed internally through a private GitHub repository.
We use a pull request (PR) workflow where changes are submitted for review before being merged into main branches. This helps ensure code quality, maintain consistency, and catch potential security or logic issues early in the development cycle.
As the platform evolves and begins handling more sensitive data or scales to new regions, we plan to reassess and adopt any necessary security standards or compliance frameworks based on regulatory needs and user trust.
5. Can you provide further details on the expected daily responsibilities and team collaboration dynamics?
Daily responsibilities will revolve around feature development, bug fixing, code reviews, and maintaining the overall performance and stability of the application. You'll be working on both backend and frontend tasks, collaborating closely with the team to implement and improve functionality.
Our communication primarily takes place through Slack, where we discuss updates, raise blockers, and share quick feedback. While the team is small, we make it a priority to communicate daily to ensure we're aligned and responsive.
We also showcase progress one to two times per week, offering a chance to demo completed work, discuss any issues, and plan upcoming tasks. We follow a collaborative, open approach to feedback, with pull requests reviewed by peers to ensure high-quality code and thoughtful discussion.