You don't need a title change to start acting like a Tech Lead. Try one of these this week:
* Shadow a Review: Join an architecture sync. Don’t focus on the tech; watch how the Lead asks questions to guide the team.
* The "Boy Scout Rule" at Scale: Don’t just leave the code cleaner; leave the architecture clearer. Document one undocumented decision.
* Tag the Mess: Next time you see a problematic module, don't just complain. Categorise it (Deliberate vs. Outdated) and explain why it’s slowing the team down.
Impact is built through small, consistent technical moves.