Engineering Manager
Adaeze
she/her“Welcome in. Adaeze, EM. I'll mostly be the one keeping us aligned, and I'll be honest with you about where you are. Ping me anytime.”
The team
Eleven engineers, and none of them agree.
Every role you would find on a real engineering team. Each has a name, a voice, and an opinion about your code. Rosa wants the query plan, Aleks reads for security, Maya asks what “done” means. Learning who to go to for what is itself part of the job.
01
Leadership
They set direction, hold the line, and unblock you when something is stuck.
Tech Lead
Maya
she/her“Hey. Maya, tech lead. If a piece of work is unclear or in flight, that's a me-question. We'll figure it out together.”
Staff Engineer
Lars
he/him“Lars. Staff. I'm quiet most of the week. When I do chime in, it's usually because something will hurt us a year from now.”
02
Product & design
They shape what gets built, who it is for, and how it should feel.
Product Manager
Naledi
she/her“Naledi, PM. I'll keep asking who this is for. You'll get tired of it. Then you'll start asking it yourself, and we'll both be happier.”
Product Designer
Mei
she/her“Mei, design. I'll be in your DMs about flows. Bring me sketches, even bad ones. Especially bad ones.”
03
Engineering Core
Web, services, data, infra: the people writing what runs in production.
Senior Backend Engineer
Tunde
he/him“Tunde, backend. I'll be the one asking what happens when this fails. Don't take it personally. It's how I read systems.”
Senior Frontend Engineer
Ravi
he/him“Ravi, frontend. I'll have opinions on what the user actually sees and clicks. Most of them are useful. Some are pedantic. You'll learn to tell which.”
Senior Database Engineer
Rosa
she/her“Rosa, data. Bring me schema changes before, not after. I'm patient with people who haven't done much SQL. Less patient with people who pretend they have.”
Platform Engineer
Yusuf
he/him“Yusuf, platform. I care about how things ship and what wakes someone up at 3am. Ping me before the deploy, not after.”
04
Quality & security
Tests, hardening, edge cases. They pressure-test the work before it ships.
Security Engineer
Aleks
he/him“Aleks, security. I'll be the one asking who else can do this. Not because I distrust the team. Because the internet distrusts the team.”
QA Engineer
Farah
she/her“Farah, quality. I'll be the one asking what happens when the user does the thing we told them not to. Nothing personal.”
That is your team. The twelfth seat is empty.
Bring a repository or start from a template. Adaeze runs the first conversation, and every review after it lands in a GitHub history that is yours.