Roles
Shipping software takes more than developers. These are the roles we staff and recruit for across a project, from planning through production, and what each one protects you from.
Portraits and names are illustrative of each role.
Plan
Decide what to build, in what order, and how you will know it worked.
Mei Lin Tavares
Product Owner
Singapore
Owns the backlog and decides what gets built next. Without one person making those calls, teams build features nobody asked for and miss the ones that matter.
Lucía Montenar
Business Analyst
Mexico City, Mexico
Turns how your business actually works into clear, testable requirements. Most rework traces back to a requirement that was vague or wrong, and this role catches it before code is written.
Prika Nameen
Senior Project Manager
Bengaluru, India
Keeps scope, budget, and schedule honest and visible. You always know where the project stands, what it will cost, and what is at risk.
Nur Aisyah Halim
Delivery Manager
Kuala Lumpur, Malaysia
Clears blockers between teams, vendors, and stakeholders so work keeps moving. Releases slip when nobody owns the hand-offs; this role owns them.
Callum Brennagh
Scrum Master
Dublin, Ireland
Runs the planning, check-ins, and retrospectives that keep a remote team in sync. Good process is what makes a distributed team predictable.
Talia Ressler
Engineering Manager
Tel Aviv, Israel
Hires, coaches, and sets standards for the engineers on your project. Code quality over the long run depends on who is on the team and how they are held to account.
Design
Shape the system and the experience before the expensive part starts.
Kenji Arimoto
Solutions Architect
Osaka, Japan
Designs how the pieces of your system fit together and connect to other tools. Early architecture choices are the hardest and most expensive to change later.
Arjun Velakkar
Technical Lead
Pune, India
Turns the architecture into day-to-day technical decisions and reviews the team's code. Keeps a growing codebase consistent instead of a patchwork.
Hana Seoyun
UX Designer
Seoul, South Korea
Maps how real people will use your product and tests it with them before it is built. Usability problems cost a fraction to fix on paper compared to in code.
Yuna Kasahara
UI Designer
Tokyo, Japan
Designs the screens, components, and visual system your users see. A consistent interface looks trustworthy and is faster for engineers to build.
Build
Write the software, from the database to the screen.
Marcus Adeyemi
Senior Software Engineer
Lagos, Nigeria
Builds the hardest parts of the system and mentors the rest of the team. Senior judgment is what keeps an MVP from turning into something you have to rebuild.
Daniel Okawa-Reyes
Frontend Engineer
Vancouver, Canada
Builds the Angular interfaces your customers click, type, and tap. This is the part of your product people see, so speed and polish here shape first impressions.
Jae-won Parkhill
Backend Engineer
Busan, South Korea
Builds the .NET services, APIs, and business logic behind the screens. Security, data integrity, and performance are decided here.
Imani Brookes
Full-Stack Developer
Austin, United States
Works across the interface, the services, and the database. On a small team, one engineer who can carry a feature end to end ships faster with fewer hand-offs.
Ezra Kaplowitz
Database Administrator
New York, United States
Designs, tunes, and protects your SQL Server data, including backups and recovery. Your data usually outlives the application, so it needs its own care.
Test
Prove it works before your customers find out it doesn't.
Siobhan Carrow
QA Lead
Edinburgh, United Kingdom
Plans what gets tested and signs off on release quality. Defects caught before release are far cheaper than ones your customers report.
Erik Lindqvale
QA Automation Engineer
Stockholm, Sweden
Writes automated tests that run on every change. They let the team ship often without breaking what already works.
Release and operate
Ship safely, keep it running, and know about problems first.
Rafael Quintero
Release Manager
Bogotá, Colombia
Schedules and coordinates releases, including rollback plans. Releases become routine instead of risky late-night events.
Karim Haddadin
DevOps Engineer
Amman, Jordan
Builds the Azure pipelines and infrastructure that take code from commit to production. Automated deployment removes the manual steps where mistakes happen.
Astrid Halvorsen
Site Reliability Engineer
Oslo, Norway
Monitors uptime and performance and leads the response when something breaks. You hear about problems from alerts, not from your customers.