Abel Sayago Email & Phone Number

London, England, United Kingdom

Trainee Detective Constable on the direct-entry path towards Detective Constable.My experience on the program was an initial period of learning at University, followed by 6 weeks working on a Response Team (attending 999 calls), followed by 2 months of working as a Detective on the Criminal Investigation Department.Responsibilities:• Work with victims: listen to the allegations, identify if an offence has been committed, take statements that can be admitted to court, support them throughout the reporting process, throughout the investigation and in court processes.• Investigate impartially and with an open mind: create an investigation strategy, gather evidence, build a case to present to the Crown Prosecution Service (CPS) and eventually to the courts.• Work with suspects: explain the allegations made against them, conduct arrests, conduct a post arrest search, present the detainee to the custody suite and communicate the circumstances of the arrest.• Conduct suspect interviews following PEACE: create an interview plan following the known evidence, ask appropriate questions during the interview (open, non-leading, 5WH questions and confirmatory questions) to establish the suspects account of the events, challenge the accounts with the available evidence.• Retain information: ensure the IT systems are correctly updated throughout the investigation after every step, write arrests and search statements, report any stop and search, report any interaction with a child.• Work with vulnerable people: be able to identify vulnerable people and what might make them vulnerable, understand how their vulnerability might cause them to be a victim or perpetrator of crime, adapt my communication, body language and stance appropriately, ensure the person's safety and change the circumstances if necessary.• Know the relevant criminal law both for police powers to act legally and for criminal offences to to identify them and cover all points to prove when preparing cases.

London, England, United Kingdom

Tasked with the technical onboarding of Digital Service Providers (DSP, like Spotify) into the organisation.The MLC was created as part of the US Music Modernisation Act (MMA) tasked with the processing and distributing digital mechanical royalties in the US. Every DSP operating on the US was legally required to work with The MLC, the majority required to report the usage of music on their platforms and pay royalties. As a new organisation, there was no existing relationships and no technical solutions, every DSP required onboarding.Responsibilities• Understand the regulations: the services contemplated in the legislation, how royalties need to be calculated and operational timetables.• Work with the software supplier: agree on requirement documents, set priorities and ensure legal compliance.• Develop usage files formats: work within DDEX to enhance their Digital Sales Report format to support new requirements, develop a bespoke alternative simpler format.• Identify, onboard and liaise with DSPs: establish contact, work 1-on-1 with DSPs to understand their service and technical challenges, explain the new legislation and file formats, help with he implementation and assist with a test process to ensure compliance.• Lead open webinars to explain the new legislative framework and how The MLC will fulfil its obligations.• Work with the DSPs on the processing of the "historically unmatched data", this is all the data that under the previous legal framework, the DSPs were unable to identify the copyright owners of the mechanical rights.Achievements• Onboarded 30+ DSPs that report their music usage monthly to The MLC.• Developed 3 files formats for the delivery of usage files following the requirements of the legislation within the short timeframe required by the legislation to start operations.• Enabled the deliver of the "historically unmatched data" for the biggest 5 DSPs operating in the US.

London, England, United Kingdom

Responsible for the technical oversight of the Copyright team and the Usage Ingestion team while leading the Usage Processing team.The Copyright team processed non-digital royalties files coming from AMRA's partners societies, as well as well as ingested member's repertoire into the system. The Usage Ingestion team received the usage files from consumer music services through different protocols (like SFTP or AWS S3), funnelled them into the Usage Processing pipeline, and archived them.Responsibilities• Ensure inter-compatibility across teams: review architecture and design and ensure quality across the entire function.• Take part on AMRA's strategic decisions: participate on how to evolve the vision and set business objective and goals.• Analyse the feasibility of business goals: break down into deliverables and set time frames and resources needed.• Translate business objectives into technical objectives: set-up function-wide objectives and teams OKRs, work out priorities and distribute workload.• Liaise with stakeholders on delivery: adapt according to the circumstances, balance delivery with tech debt, ensure the teams are able to deliver to a high quality standard without stakeholder pressure.• Build, grow and maintain the team: decide teams' composition, hire new employees, set salaries and communicate rises and promotions to team members.• Drive function-wide events and off-sites.Achievements• Divided the Usage Processing team into two teams after the scope of the team became unmanageable by a single scrum team, creating the Usage Ingestion Team.• Unified the objectives of the different teams that were pulling in different directions into a unified common goal, ensuring the synergy across the different functions.• Fixed previous incompatibilities existing in the system into a unified pipeline able to process the data efficiently.• Moved the business from a chaotic start-stop 3-monthly cycle of data processing to a continuous delivery of data.

London, England, United Kingdom

Team Lead of the Usage Processing team. Developed, built and maintained AMRA's digital music usage processing pipeline.The pipeline processed the usage coming from consumer music services (like Spotify) end to end: it ingests the usage files; matches the metadata against the repertoire; calculates the percentage of the usage due to AMRA; applies the terms of each licence with the service; calculates the money to be invoiced; generates a file to send back to each service and generates royalties to be paid to AMRA’s members.Responsibilities• Develop and design the system's architecture and ensure its quality.• Make risk assessments, navigate dependencies and build mitigation strategies.• Ensure team delivery: set OKRs and liaise delivery with stakeholders, develop yearly roadmaps together with the product team and communicate to the team.• Build and grow the team: screen CVs, lead interviews and ensure a positive onboarding experience.• Manage team personal development: set out individual OKRs, make development plans, do 1on1s, mentor and guide on performance, push for promotions.• Collaborate with other areas of the organisation, like product and QA, to ensure the efficient functioning of the team.• Set team working practices: coding style, standards of quality, agile methodology, peer review process.• Drive team ceremonies: stand-up, backlog refinement, sprint planning and retrospective.• Represent AMRA at DDEX: work with the other DDEX members to build the specification for DDEX DSR, a file format for the transmission of usage data between entities in the music industry.Achievements• Rebuilt an inherited, inefficient and unscalable Oracle-based system into a high performing pipeline able to process 1T+ transactions a quarter from 15+ music providers across 150+ different territories without a change of technology or an increase in cost.• Built a highly configurable music metadata matching platform to replace the existing Oracle-based solution.

London, England, United Kingdom

Senior Software Engineer at KTech/AMRA, working on the development, maintenance and execution of the digital music usage processing pipeline.Recently bought by Kobalt Music, AMRA was the first global digital music collection society, collecting money directly from consumer music services (like Spotify and Apple Music) for AMRA's members globally.Responsibilities:• Run the IT Operations function: maintain the correct operation of the internal software, deploy new versions of the software, identify any potential problems and raise them with the development team.• Support the business on the use of the internal software: teach the business how to use the tools developed by the tech department, understand the requirements for new functionality, identify bugs and explain to the development team.• Handle the music services monthly distributions into the system: receive the usage files through different protocols (like SFTP or AWS S3), ingest them into a common path into the usage processing pipeline, and archive them for long term storage.

London, England, United Kingdom

Software Engineer at Kobalt Music Group. Working within the dev team on the internal administration software used by the admin team at the organisation to run the operations of the company.The system was a monolithic Java swing application with a Tomcat based backend running over an Oracle database, with the business logic mixed between the database itself written in PL/SQL, the Java backend and the Java frontend.Responsibilities:• Design, develop and test new features as they are requested, spec'ed and assigned to me: work full stack, from the changes to the database up to the UI changes.• Prioritise and manage my own time: work on my own list of issues while integrating into the team's schedules and development priorities.• Train new team members: explain the system, how the architecture works and provide help and guidance with their first issues, offer assistance and support when I have more experience.• Support the admin team: work on tickets opened by the admin team, explain new functionality, clarify functions, identify and report bugs.• Work on urgent requests that require changing data in production: judge the feasibility of the request and the impact on the system, plan the change, issue the change and ensure the stability of the system.Achievements:• Created, designed and maintained the marketing budgeting subsystem within the application.• Created, designed and maintained the physical stock control subsystem within the application.

Seville, Andalusia, Spain

Junior Software Developer on a 2-month long part-time placement at Genera Mobile developing interactive storybooks for iOS.After winning an iOS development contest at my university I was offered a placement at Genera Mobile to work on their content store for iPhone and iPad called TouchyBooks developing interactive storybooks.Responsibilities:• Develop interactive storybooks based on the assets and story provided: work on each of the scene of the story, decide on what would animate and how and the gestures and touches that would trigger the animation.• Code the storybook using the already existing storybook engine.Achievements:• Identified and fixed a memory leek on the storybooks engine that was limiting the amount of elements available to place on each scene.

Seville, Andalusia, Spain

Writer on the Spanish online publication AppleWeblog.Worked independently publishing 2 articles a day as part of a larger team covering Apple News, analysis and opinion pieces in Spanish.Responsibilities:• Decide what to write about ensuring consistency with the editorial line and avoiding overlap with other writers.• Write articles raging from covering news, to analysis of hardware and accessories, to software guides to opinion pieces.• Seek collaboration with brands for product analysis.• Provide extended coverage during Apple related event days.

Seville, Andalusia, Spain

Member of Wesser's Seville team of recruiters working in getting people to become members of different charities and to donate monthly.Worked as a street level recruiter on three different campaigns for three different organisations: Red Cross Spain, WWF/Adena and Spanish Association Against Cancer (known in Spanish as AECC). Posted in a different area of Seville city center every day as part of a team of 6.Responsibilities:• Work with the rest of the team and decide how best to split the team across the coverage area.• Decide who to try to stop to have a conversation.• Talk to the people that stopped to convince them to join the charity.• Know the details of the charity to be able to answer any questions.• Fill in recruitment form of behalf of new members.