Knowledge
I threw myself into the work, listened closely, and burned it into memory. That’s how you learn, you know?
struct Skills {
let management = "Managing a development team following SCRUM principles"
let coordination = "Actively coordinating across multiple technical areas"
let decisions = "Direct ownership over product decisions and definition phases"
let crossFunctionalWork = "Close collaboration with other areas (Android, Web, Backend, Product, Design)"
}
struct Tech {
let languages: [String] = ["Flutter", "Dart", "Swift"]
let reactiveProgramming: [String] = ["SwiftUI", "Async/Await", "Provider"]
let architecture: [String] = ["BLoC", "VIPER", "MVVM"]
let codeModularization: Any?
let pushNotifications: Any?
let testing: [String] = ["Unit Test", "TDD"]
let ci/cd: [String] = ["fastlane", "Firebase", "Analytics", "Github Actions"]
let others: [String] = ["Jira", "TestFlight", "Gitflow", "SCRUM"]
}
Experience
Being part of the Gibobs team has been one of the most significant, challenging, and rewarding experiences of my professional and personal life. I joined the startup when there were fewer than 20 people in the entire company, and it has been growing non-stop ever since.
Initially I was the iOS Technical Director, building the application from scratch and guiding it through every phase of evolution. I later took ownership of the entire mobile area, which marked the turning point where we decided to migrate our native apps to Flutter.
That level of responsibility allowed me to develop strong decision-making skills — both around the technologies we adopted and the people involved. It was also a huge leap forward in terms of organizational skills, managing methodologies like SCRUM and Kanban, as well as product thinking, given how closely I worked with stakeholders on the product’s direction.
Resources
