Services
Full-stack development,
from database to interface.
Some projects need one developer who can carry the work from the database to the interface, with the APIs, integrations and deploy pipeline in between. I do that end to end for smaller clients, and as the broader work that grows around a feature on larger teams.
When to bring me in
Full-stack work
across the whole product.
A platform split across too many systems
An e-sport coaching company ran on a backend, a standalone frontend application and a WordPress site. We rebuilt it as one product, so bookings, subscriptions and coach workflows ran through a single backend instead of patching gaps between systems.
Payments, queues and integrations
On the coaching platform, the Laravel backend handled payment integration and asynchronous job processing. At an insurer, slow work such as settlement runs, batch invoicing and reporting exports ran as queue jobs in the PHP services.
Back-office work stuck in legacy tools
When staff live in spreadsheets and an ageing host system, a replacement has to keep history and correctness intact. For a Danish insurance mutual, I worked across the PHP services and the Nuxt staff app that moved policy and billing work into one platform.
Hosting and deployments that need attention
For the coaching platform, I moved hosting to AWS in a multi-AZ VPC with RDS, S3, CloudFront and SQS, with Git hooks driving CI/CD. Deployments were automatic, and with queues and data off the app host, the application layer stayed stateless.
What you get
Web applications,
end to end.
The stacks in these cases - Laravel on PHP 7.4 for the coaching platform, Slim PHP and Nuxt 2 at the insurer - are what those engagements used. For new work, the stack depends on your team and what's already in place.
- Web applications from database to interface
- REST APIs, both client-facing and internal
- Payment integration and asynchronous job processing
- Integrations with finance systems and third-party services
- Relational data under migrations, reporting and exports
- Generated documents such as PDFs and letters from templates
- Cloud hosting, deploy pipelines and platform work
Cases
Full-stack work
in production.
- Product platform
E-sport coaching platform rebuilt to grow revenue without growing firefighting.
End-to-end rebuild so the team could onboard more players, run day-to-day operations reliably, and ship product changes with confidence. Laravel, Vue and AWS where it mattered for scale and cost.
A full-stack rebuild for an e-sport coaching company: a Laravel API with payments and queues, AWS hosting across multiple availability zones, Git-hook CI/CD and a server-rendered Nuxt customer app.
- Enterprise application
Policy and billing in one staff platform for a Danish insurance mutual.
Long-term contract on Slim PHP services and a Nuxt 2 staff app for memberships, tariffs, invoicing, settlement and reporting, replacing legacy back-office tooling the team could no longer extend safely.
Long-term work for a Danish insurance mutual across Slim PHP services and a Nuxt 2 staff application: domain logic, reporting exports and integrations, plus billing and policy lifecycle features.
"What really struck me was Emil's agility and persistence when going towards the goal. He could see problems in finding too many shortcuts, but had no problems with digging down into the "source"."
Michal Dobroczynski
Freelance Linux DevOps
How it works
From a first message
to launch and after.
Share the context
Tell me what you're building, who it's for and what timeline you're working toward. Stack preferences, design constraints and links to a repo, Figma file or existing product all help.
Agree on the setup
I work on an hourly rate and I'm transparent about it before we start. For scoped work, you get an honest hour estimate tied to a clearly defined brief, so you know what you're committing to upfront.
Work inside your workflow
I join your Slack, follow your Git workflow, attend your standups and fit into your existing processes, whether the team is a startup or a large enterprise.
Launch and keep going
I don't disappear after deployment. Most of my clients keep me on for maintenance, iterations and new features, and some partnerships have been running for 4-8 years.
FAQ
Hiring a
full-stack developer.
Yes. On the coaching platform I rebuilt the Laravel backend, the Nuxt frontend and the AWS setup. At the insurer I worked in both the Slim PHP services and the Nuxt staff app.
Yes. On the coaching platform I started by maintaining the existing software suite and shipping incremental features, before we agreed on a full rebuild in mid-2020.
The backend work in my case studies is PHP: Laravel on the coaching platform and Slim at the insurer. I also work with Node.js, PostgreSQL, Redis and Docker, and with hosting on AWS and Azure.
Yes, when it's part of the job. On larger teams it's often part of the broader work that grows around a feature: deploy pipelines, scripting and third-party wiring. For the coaching platform, I set up the AWS hosting and the Git-hook CI/CD.
Both. For smaller teams and focused builds, I often own a project A-Z with a defined scope. For larger organizations, I embed in your team for the long term.
Related services
Other ways
I can help.
Frontend development
Frontend architecture, product UI and component libraries, when most of the work is in the interface.
Vue & Nuxt development
Framework-specific work on Vue and Nuxt applications, from component frameworks to rendering strategy.
Looking for
the right developer?
Whether you're ready to start or just exploring your options, feel free to reach out. No commitment, no pressure.
I usually respond within 2 hours.