Laravel Developer Resume
2.00/5 (Submit Your Rating)
SUMMARY
- While my hats have changed over the years, I have always written software and studied new ways of approaching problems.
- My latest position was delivering solutions on a tightknit remote first team.
PROFESSIONAL EXPERIENCE
Laravel Developer
Confidential
Responsibilities:
- Transforming legacy tool developed in Lotus Notes to modern PHP framework on Linux servers migrating to AWS.
- Integrating Kendo UI with Laravel on PostgreSQL Db using Apache.
- Documenting system environments, installing debugging tools, use of MVVC framework, creating document export functionality, supporting the testers with deployment to testing/UAT/Demo environments, using git and Bitbucket, running brownbags for fellow programmers on framework tools.
Network Support
Confidential
Responsibilities:
- Maintaining a highly visible website (itdashboard.gov) using Drupal for Office of the Federal Chief Information Officer (OFCIO) on a remote first team doing PHP, JavaScript, HTML, CSS, and MySQL development on centOS Linux servers using Apache. Writing and editing bash scripts to automate parts of the deployment process were also my responsibility.
- Updates to Drupal were handled using Drush in order to bring updates into version control. Business logic for handling data on the site was written in a custom Drupal module.
- My role, also, included regular baselining of the codebase for each 2 week sprint. The team used Jenkins for Continuous Integration (CI) and Selenium (JAVA framework) for regression testing, and git for version control. So, I have to be able to switch between PHP, JAVA, and bash scripting on a moment’s notice.
- The team used Agile Scrum for project management and the cadence was Daily Stand Ups in the morning, with mornings and afternoons for writing code.
- While on the project we migrated from HighCharts to using d3 for graphical display of data.
- The site was both an internal and external tool for the government. Data was uploaded, validated against business rules and format, and processed for management use and display.
- A major part of the project was coordinating with the Electronic Capital Planning and Investment Control (eCPIC) community. Schema changes were a regular occurrence as reporting rules started to migrate to reflect the Technology Business Management (TBM) model and priorities changed.
Software Engineer
Confidential
Responsibilities:
- The team I worked on developed applications for the USAID Bureau for Economic Growth, Education and Environment.
- These applications served back office functions such as managing staff, travel assignments, office space, operational strategies, and portfolio (contracts, grants, activities) management.
- Applications were developed on a LAMP stack using HTML, CSS, Javascript and JQuery.
- We prided ourselves on our close contact with users during development which leads to much better products.
- The time we spent with users was the primary reason our products got the positive feedback that they did.
- We built products with a focus on improving work and information flows.