---
# System prepended metadata

title: SDK Tech Lead Responsibilites

---

# SDK Tech Lead Responsibilites
_Working draft. Bullets are pretty vague right now. We can specify to make more specific._


- Ensure quality of software delivered by team
    - Reviewing PRs in depth
    - Documenting designs, decisions, etc.
    - Be the guiding force around code quality standards, definition of done, etc.
    - Maintain vision for full lifecycle of products and observability.
- Determine future project requirements and realistic plans to implement
	- Work with product on timeline estimations and tracking
	- I (Charlie) have been approaching this work as trying to translate the higher-level stuff into actual actionable work. Like, there's a rough design and product doc, but it's my job to take those and create a clear and documented (diagram + tickets) plan
- Motivate and inspire team to ask questions and voice concerns
    - Lead by example
- Keep up to date with latest industry trends and best practices
- Delegating and defining work items for the team
- Guide team through technical challenges
	- Drive team consensus on solutions
	- Explicitly solicit ideas, feedback, and opinion from team-members
- Act is primary point of contact for issues related to the platform
- Work with EMs/PMs to triage and prioritize work (feature requests, SISPs, etc.)
- Work with and mentor teammembers on growth areas
    - Meet with them periodically to talk technical goals, interests?
    - Assist with brag doc work?
    - Hold a standing office-hours type time that is available to folks but otherwise a focus-time for us?
- Help push back on external requests
    - Support peers in learning when/how, but also backing them up when they do
    - "Shield" team from wasting time on high level technical conversations / circles that are currently non-actionable
