Toronto, Ontario, Canada
Lucas De Medeiros
Software Developer
Building reliable software, automation, and DevOps workflows.
Experience
Automation Developer Co-op
Ontario Government | Gouvernement de l'Ontario · Toronto, Ontario, Canada · Hybrid
Jan 2025 – Aug 2025
- Migrated a legacy UFT/VBScript test suite to Selenium WebDriver (Java), refactoring script logic within the IBM Curam web framework.
- Developed and maintained automation scripts for the CPIN case management platform, building reusable components and structuring test flows around assigned modules.
- Integrated test execution into Azure DevOps CI/CD pipelines using Maven, enabling automated regression runs on build triggers.
- Collaborated with QA and development teams to verify bug fixes and feature changes, maintaining test coverage across iterative releases in a public sector environment.
Education
Toronto, Ontario, Canada
Seneca Polytechnic
Ontario College Advanced Diploma, Computer Programming & Analysis
Sep 2023 – 2026
Skills
Languages
Frameworks
Tools
Cloud
Licenses & Certifications
DevOps Professional Certificate by PagerDuty and LinkedIn
PagerDuty
Issued Aug 2025
Atlassian Agile Project Management Professional Certificate
Atlassian
Issued Aug 2025
Docker Foundations Professional Certificate
Docker, Inc
Issued Jul 2025
Microsoft Azure AI Essentials Professional Certificate by Microsoft and LinkedIn
Microsoft
Issued Jul 2025
Contact me
Under the Hood
Application architecture
Built with Next.js App Router, React, and TypeScript. Content is centralized in typed data objects so edits are traceable and low risk. The app is static-first, which keeps runtime complexity and infrastructure needs minimal.
Engineering setup
Local quality gates mirror CI: ESLint, TypeScript, and production build checks run before deploy. Asset handling is optimized for cacheability, and environment values are managed through platform secrets instead of hardcoded config. Goal is repeatable builds and predictable rollouts.
Delivery pipeline
Every PR gets automated validation, then ships to preview for review. Main branch is treated as release-ready: merge only after checks pass, then deploy to production. Failed checks block release, and each deploy is tied to a commit for quick rollback and debugging.