Project Type: One-time project with potential ongoing work
Experience Level: Expert / Senior Laravel Developer
Industry: Field Services, SaaS Platforms
Client: Field Services Network (www.FieldServicesNetwork.com)
Project Overview
Field Services Network is seeking a highly experienced Senior Laravel Developer to architect, develop, and deploy a custom URL-routing and service-linking platform similar to the functionality offered by ServURL.com. This new service will be integrated directly into our existing Laravel application and will eventually be offered as a subscription-based SaaS product for outside users.
We currently utilize ServURL.com within FieldServicesNetwork.com, and the goal of this project is to build our own internal version of that service. The new system must remain fully compatible with how ServURL is being used today, ensuring a seamless transition with zero disruption for our users.
What We Need Built
We are looking for a developer who can deliver a scalable, secure, and feature-rich Laravel-based service with capabilities including (but not limited to):
Core Requirements
Build a ServURL-style service within our Laravel infrastructure
Must seamlessly replace or mirror the current ServURL.com functionality used inside FieldServicesNetwork.com
Ability to generate, manage, and route service URLs for field agents and external clients
API-ready architecture for integrations
Multi-tenant structure to support external users
Subscription-based access (Stripe or equivalent)
Dashboard for users to create, manage, and track their URLs
Logging, analytics, and usage reporting features
Role-based access control and strong authentication
Clean, maintainable, well-documented code following Laravel best practices
You inherit a large Laravel 10 codebase where features are scattered across the UI. We want every capability consolidated into tabs under a single Work Order. How do you refactor without breaking production?
What models, relationships, and services would you expect to orbit a Work Order in a service marketplace like FSN?
How do you prevent illegal state transitions in a Work Order lifecycle?
How would you expose Work Order functionality in tabs without creating a giant controller or God model?
Explain how you would implement escrow-style payments with milestone releases in Laravel.
What database tables are required for a marketplace-grade payment system?
How would you design a multi-tenant URL-routing service inside an existing Laravel app?
How do you replace an external service (ServURL) without breaking existing users?
What parts of a service marketplace will fail first under scale?
What should never be synchronous in a Laravel marketplace?
What are the highest security risks in a contractor marketplace?
How do you secure webhooks in Laravel?
If you disagreed with the product direction, how would you handle it?
What would you refactor first in a messy Laravel app—and why?
Describe a production outage you caused and how you fixed it.
This is a mission-critical project and we are looking for a top-tier expert. If you are an architect-level Laravel developer who understands how to build scalable SaaS infrastructures and enjoys working with complex routing logic and subscription models, we want to hear from you.
...