- Technical Lead responsibilities
- Responsible for technical architecture for multiple work streams
- Responsible for owning and leading technical discussions with the client
- Has a bigger scale and big-picture knowledge awareness and ownership. I.e. owns architecture patterns, practices, and principles not limited to Salesforce core only, but touching all the different clouds, integration, security, data, and DevOps
- Contributes towards Practice Development within Globant
- Able to work across multiple projects simultaneously
- Primarily focuses on design activities, but can either transition into a Tech Lead role or reduce assignment on a project, depending on the engagement and program
Communication
- Able to communicate clearly and concisely in verbal and written fashion
- Explain technical concepts to a non-technical audience
- Adapts communication to the audience
- Able to challenge the client and justify their own viewpoint
- Able to lead difficult conversations with the client
- Can influence clients' architects and decision makers on the best approaches to (not limited): principles, patterns, investment, tools, licenses
Presentation
- Leads the design of client-facing presentations and delegates ownership of elements of the presentation to team members
- Able to present in an organized, coherent fashion and adapt their presentation style to their audience
- Able to present in client-facing sessions such as Design Authorities, providing explicit rationale for design decisions and responding to the client challenges
- Able to respond to feedback and tailor messaging
- Audience can range from technical people to C-level stakeholders, a wider scale than a Technical Lead
Collaboration
- Establishes a collaborative environment with the team and client
- Leads and delegates tasks in an assertive and effective way, while not neglecting the review and assurance processes
Leadership
- Is a role model for junior team members and provides mentorship
- Defines roles
📌 Salesforce Architect (Pune)
🏢 Globant
📍 Pune