Redesigned GroupMe profiles.
Profile components, mini-profiles and swipe navigation on iOS.
Luisa Santo / iOS engineer
I build iOS apps
at Microsoft.
I work on GroupMe. Previously, I built iOS features for Microsoft Teams and contributed to the Peacock app launch.
Swift, Objective-C and UIKit.
Selected product experienceGroupMeMicrosoft TeamsPeacockSky
01 / Selected work
What I've
worked on.
The problem, my contribution, and the implementation choices for each project.
Streaming chat summaries.
Incremental responses, caching and failure handling in the iOS client.
Teams post-meeting architecture.
Separating legacy controller logic into Swift components and view models.
Alongside feature work
Tests, accessibility
and mentoring.
I build test infrastructure, fix accessibility issues, and help interns plan, implement and explain their work.
63
UI tests authored
Reusable automation for GroupMe's iOS suite.
17
Accessibility issues addressed
VoiceOver behavior, headings, states and contrast.
02
Interns mentored
Architecture, implementation, review and communicating impact.
02 / Experience
Work and
project experience.
Microsoft, the Peacock launch, and the move from backend engineering to iOS at Talkdesk.
2024 - present
GroupMe
Consumer iOS & AI experiences
Profiles, streaming AI experiences, chat UI and the testing and measurement behind them.
2022 - 2024
Microsoft Teams
iOS architecture & product engineering
Meeting-related experiences, legacy modernization, privacy-sensitive behavior and automation.
2021 - 2022
Teams & Skype for Business
Developer support
Technical ownership of developer scenarios across EMEA, shared knowledge and collaboration with product engineering.
Apr 2020 - Mar 2021
Peacock
iOS Developer
Contributed to the iPhone and iPad app launch, including the highlights section and movie/show details UI in Swift and UIKit.
May 2019 - Apr 2020
Talkdesk
Software Engineer
Contributed to a Ruby microservice, then moved to iOS work on push notifications and Interface Builder. Helped onboard new iOS engineers.
Current Microsoft title: Member of Technical Staff.
Other experience
Taught app development with App Inventor at Girls Code (2018-2020) and block-based programming at Happy Code (2018-2019).
Additional project work involving Sky and Comcast.
Education
Instituto Superior Técnico
MEng, Artificial Intelligence (2020); BEng, Computer and Information Sciences (2018).
Recent AI coursework
- Generative AI for Software DevelopmentDeepLearning.AI / Aug 2026
- AI Code ReviewDeepLearning.AI / Aug 2026
- MCP: Build Rich-Context AI Apps with AnthropicDeepLearning.AI / Jul 2026
- AI Prompting for EveryoneDeepLearning.AI / Jul 2026
Research background
Research and
early projects.
Speech-to-text for archives and space-mission design. The Alpbach programme was organised by FFG and co-sponsored by ESA.
Research internship
Speech-to-text for CERN's archives
Evaluated speech-to-text tools for CERN's archives, comparing feasibility and limitations.
Research details on LinkedInAlpbach Summer School / 2015
JANOS mission concept
Contributed to a preliminary space-mission concept studying gravity's effect on quantum systems. Team Blue received the programme's Best Technical Case recognition.
Read the programme report View the Team Blue photograph on ESAPhoto credit: FFG/Summer School Alpbach/MA Jakob. Photograph hosted by ESA.
AI-assisted engineering
How I direct
AI-assisted work.
Clear requirements, useful context and checks on the result. The tools help with the work; they do not decide what is true or ready to publish.
Make the brief testable
Specify the goal, existing behavior, constraints and acceptance criteria. Call out missing evidence before asking an agent to implement a solution.
Give agents the right context
Use Copilot CLI and MCP connections to bring code, design and issue context into the task. Keep private sources out of public deliverables.
Verify the result
Compare changes with the sources and existing patterns. Require build, test and accessibility checks, and keep publication decisions with the human.
A public example brief
Illustrative example based on this portfolio workflow, not a verbatim internal prompt.
Goal: Create a clear portfolio for an iOS engineer. Evidence: Use supplied sources. Separate individual contributions from product-wide outcomes. Constraints: Keep the repository private. Do not deploy or publish company-confidential material. Acceptance: A static build, keyboard navigation, no mobile overflow and a working CV download. Review: Report source gaps, run the checks and ask before changing publication scope.
Recommendations
People I've worked with.
“Her proactive approach and eagerness to contribute more to the business made her an invaluable team member.”
“I reviewed many of her pull requests and was impressed by her openness to feedback”
“Luisa played a key role in helping ramp up new engineers by creating valuable technical content on development topics.”
“Her patience and ability to explain complex concepts made my learning experience smooth and rewarding.”
Selected excerpts from professional recommendations. Full recommendations on LinkedIn
03 / How I work
Code, reviews
and a bit about me.
Much of my work is in existing codebases: separating responsibilities, tracing state changes, and checking what happens when a request fails.
I also review code and mentor interns. I help them plan components, work through feedback, and explain their technical decisions.
Outside work, I like fantasy books and retro objects.
Read my CV