Francisco Giraldo
Results-oriented Senior Backend Engineer with a solid foundation in software architecture, design patterns, and clean coding principles. Experienced in building scalable, maintainable, and high-performance backend systems using modern PHP frameworks and best practices. Proficient in designing robust APIs, integrating third-party services, and improving system reliability through monitoring and automated testing. Strong collaborator who thrives in cross-functional teams, driving innovative solutions that enhance product functionality and user experience. Eager to contribute to forward-thinking organizations by leveraging deep backend expertise to solve complex technical challenges and deliver business value.
Currently Interested In
Object Oriented Programming, Clean Code, Design Patterns, SOLID - DRY - KISS Principels, Domain Driven Design, Test Driven Development, Event Driven Programming, REST APIs.
Work Experience (Last 5 years)
Senior Backend Engineer
Design, build and maintain the LanguageTool's website.
- Develop the backend part of new features, or modifying existing ones.
- Collaboration with the frontend developers to create API endpoints using Laravel.
- Checking monitoring tools like Sentry and Graylog to fix issues and bugs.
- Integrate 3rd party APIs like Recurly and Fastspring
- Setup Amplitude experiments
- Making sure the new features are working correctly in Production
Techonologies:
- PHP
- OOP
- Laravel
- Rest API
- MySQL
- Docker
- GIT
- PHPUnit
- Sentry
- Graylog
- Amplitude
- GTM
Senior Backend Engineer
Design, build and maintain the Scribbr's backend system.
- Design and develop the backend part of new features, or modifying existing ones.
- By using scalable and performant backend solutions with the use of tools like RabbitMQ, Crons and Redis
- Collaboration with the frontend developers to create API endpoints using Symfony.
- Checking monitoring tools like Sentry and AWS Cloudwatch to fix issues and bugs.
- Integrate 3rd party APIs like Asana, Adyen, Mailchimp, Wise, Aspose, Trustpilot, Turnitin
- Making sure the new features are working correctly in Production
Techonologies:
- PHP
- OOP
- DDD
- CQRS
- Distributed apps
- Symfony
- Rest API
- MySQL
- Docker
- GIT
- PHPUnit
- AWS
- RabbitMQ
- Redis
- Sentry
PHP backend Developer
Fast paced startup with a global e-commerce platform with millions of users. The company is working on scaling the platform by moving the main WordPress website to microservices written with Laravel. Started initially fixing bugs and improving features of the web application. Later joined the Supply team which was in charge of the functionality to add the products to the the site.
- Contributed to scale the company's existing system by leveraging functionality into microservices.
- Contributed to improve the internal operations system by creating and improving existing processes.
- Investigated and solved production issues/bugs by debuging and using logs.
Techonologies:
- PHP
- OOP
- Laravel
- SQL
- Docker
- GIT
- PHPUnit
- Javascript
- AWS
- Algolia
- Redis
- RabbitMQ
- Metabase
- Continous Integration
Project Highlights
Integrate Amplitude experiments in the LanguateTool website
Setup the PHP and JS Amplitude SDK to be able to run backend and frontend experiments.
An amplitude experiment is a test that compares different versions of a digital experience (like a webpage or app feature) to see which one performs better based on user behavior. Its benefits include data-driven decisions, improved user engagement, and higher conversion rates.
Improve user's document deletion in the Scribbr webapp
Scribbr backend system deleted the documents uploaded by users using a cronjob. This was consuming a lot of CPU resource so this process was improved by setting an expiry date to the S3 buckets. The a AWS lambda function would be trigger on deletion and call an endpoint to Scribbr's system to further do any deletion logic.
Create Scribbr's financial journals
Created complex SQL queries to fetch the financial data. And coded a OOP design to manage the data and the financial rules in order to create the journals. The design was easy to extend as new rules or changes to the journals were added.