Leading Engineering Teams Without Leaving the Code
Tech lead is not a meeting-only job. How I balance delivery, mentoring, and staying hands-on across healthcare, ERP, and product builds.
I lead engineering teams and mentor developers — and I still review PRs, sketch architecture, and unblock hard bugs. That is intentional. Teams trust leaders who remember what production feels like.
**Set clarity, not chaos.** Every sprint should have one visible outcome and one owner. As tech lead and PM, I translate executive goals into tickets developers can finish without guessing.
**Mentor in public, correct in private.** Junior engineers grow when code reviews explain why — patterns, security, performance — not just "change this." I pair on hard problems instead of taking them over unless the deadline demands it.
**Protect focus.** Context switching kills quality. I shield teams from vague stakeholder pings by enforcing briefs and office hours for questions.
**Document decisions.** Architecture notes, ADRs, and README updates are how you scale past five people. Future you — and future hires — will thank you.
**Ship demos early.** Stakeholders calibrate on working software, not slides. Everlast ERP modules and nutrition internal tools moved faster when ops saw their workflow live, even rough.
**Hire for curiosity and communication.** Stack can be taught. Judgment and clear writing are harder.
**Know when to code and when to delegate.** If I am the bottleneck on every task, I failed as a lead. If I never touch code, I lose technical respect. Balance is daily work.
This model is what I offer as fractional lead engagements — own the outcome, mentor the team, stay accountable to the codebase.
If you are a developer following me on LinkedIn: ask for feedback on something specific. If you are a founder: ask whether you need a builder, a consultant, or a hands-on lead. The answer changes the engagement model.
Tags: Team LeadMentoringTech LeadAgileSoftware EngineeringYoussef GeorgeLeadershipProduct DeliveryCairoRemote Teams