Skip to content
dc.
Back to selected work

Professional experience

Technical Leadership Across Web and Mobile Delivery

Establishing testing standards, code review, and automated release workflows at All-Win Software.

Technical leadershipAutomated testingCI/CD

2 min read

At a glance

Organization
All-Win Software
My role
Lead Software Engineer
Period
Aug 2022 — Aug 2025
delivery supported by shared engineering practices
Web + mobile

Based on professional experience documented in my CV. Internal implementation details are omitted.

Engineering delivery

  1. 01Design and review
  2. 02Automated tests
  3. 03Web and mobile releases

Conceptual workflow · All-Win Software

The context

At All-Win Software, I led engineering initiatives spanning backend, web, and mobile applications. The work involved Laravel, FastAPI, Node.js, React, Astro, SwiftUI, UIKit, and Flutter. My responsibility combined implementation with system design, code review, and delivery planning.

This breadth made engineering practices part of the job: a change needed to be understandable to reviewers, protected by useful tests, and practical to release on its target platform.

What I owned

  • Led backend, web, and mobile engineering initiatives.
  • Established unit, functional, and integration testing standards alongside code-quality practices.
  • Automated web and mobile release workflows using GitHub Actions and Bitbucket Pipelines.
  • Directed code reviews, system design discussions, and agile planning.

These responsibilities are documented in my CV. They describe my contribution; they do not imply that I built every application or delivery pipeline alone.

How the responsibilities connect

System design and review make a change’s intent visible to the team. Tests protect its behavior as implementation evolves. Release automation makes the steps between an approved change and a published application repeatable.

The useful connection is between these practices. A pipeline runs the checks the team has chosen; it cannot substitute for a clear design or a meaningful test. Likewise, a review process still needs a reliable path to release the work it approves.

Decisions and tradeoffs

Web and mobile releases have different build and distribution requirements. A shared quality standard can describe the behavior a change must protect while allowing each platform to keep appropriate build tools and release steps.

Automation also needs maintenance. Moving a manual step into CI makes it repeatable, but the team still needs to understand its inputs, failures, and ownership. These are engineering considerations behind the work, rather than a reconstruction of an unpublished internal pipeline.

The outcome and its scope

My CV records stronger testing and code-quality practices, more consistent technical decisions, and reduced manual deployment work through automated web and mobile releases. No team size, deployment-frequency baseline, or numerical productivity improvement is published here.

This experience shows how I contribute as a technical lead: hands-on engineering combined with practices that help others review, change, and deliver software.

05 Let’s connect

Good work starts
with a conversation.

Have a challenging engineering problem, a role in mind, or an idea worth exploring? I’d like to hear about it.

derian.cordoba@icloud.com

Based in Nicaragua · Working with international teams

Let’s talk

Send a short introduction

Have a role, a collaboration, or a technical challenge in mind? Share a little context to start the conversation.

Opportunities · Collaboration · Engineering

Prefer to write directly?

derian.cordoba@icloud.com

All fields are required.

Your name, email, and message are processed by Netlify Forms to deliver your inquiry. Please avoid confidential information.