Position :: Technical Lead
Location :: Houston, TX( Hybrid- 2 days onsite)
Type :: Contract
Must Have:
LinkedIn with a picture
8+ years of professional software development experience.
2+ years leading a development team as a technical lead, team lead, or equivalent.
7+ years of hands-on experience with C# and .NET.
Strong experience with Angular.
Production experience building and hosting applications on Azure.
Proven experience building and running CI/CD and release pipelines.
Summar
The Senior Technical Lead leads custom software development at Bigge. The team builds and maintains the internal platforms behind crane dispatch, asset management, field service, and pricing, and the integrations that connect them to Dynamics 365, Salesforce, and other enterprise systems. This is a hands-on technical management role, roughly 60% hands-on technical work (building, code review, CI/CD, and releases) and 40% team leadership (sprints, priorities, and stakeholders). You report to the Director of Engineering and partner with the Principal Engineer, who sets architecture and technical direction for the organization. You own delivery: sprint execution, code quality, testing, releases, and the team’s day-to-day work.
Key Responsibilities
Technical Leadership and Delivery
• Lead a team of software developers. Set daily priorities, unblock work, and hold the team to consistent standards for code quality, testing, and documentation.
• Run Agile sprints end to end: planning, standups, reviews, and retrospectives. Keep the backlog groomed and sprint commitments realistic.
• Write user stories and technical tasks in Azure DevOps from discovery sessions with stakeholders.
• Partner with the Principal Architect on architecture decisions and technical standards and turn those decisions into executable work.
• Stay hands-on: build features, review code, and step into critical fixes.
• Harden reliability and release discipline on critical internal platforms under active operational load, reducing production risk and single points of knowledge.
• Use AI-assisted development tools in delivery and set the standards for how the team uses them, including review and testing of AI-generated code.
• Make sure work is tested before it ships, with unit, integration, and regression coverage matched to the risk of the change.
Stakeholder and Cross-Functional
• Serve as a technical point of contact for stakeholders on the team’s work.
• Triage incoming requests. Step back from implementation to determine whether an issue is a defect in existing behavior or a request for new capability and route it to the right path.
• Work across Engineering teams, including Salesforce and ERP, and with Infrastructure on changes that span multiple systems.
• Explain technical tradeoffs, risks, and timelines to leadership in plain language.
• Take direction and feedback from leadership and adjust plans as priorities change.
Release and DevOps
• Own CI/CD and release pipelines, including build, test, and deployment automation across environments.
• Run release management: release planning, go/no-go readiness, deployment, and rollback.
• Write and send release communications so stakeholders know what changed, when, and what it means for them.
• Monitor production health after releases and drive root-cause fixes for recurring issues.
Integration and Platform
• Build and maintain integrations using Azure Logic Apps, Power Automate, and REST APIs across Dynamics 365, Salesforce, and third-party systems, in line with architecture and standards set with the Principal Engineer.
• Oversee Azure-hosted applications and services, including App Service and Functions, in coordination with the infrastructure team.
• Support Power Apps solutions as part of the broader Microsoft platform.
What Success Looks Like
• Sprints deliver what they commit to, on a predictable cadence.
• Releases ship on schedule with fewer production defects and rollbacks.
• Automated test coverage gates every deploy, and recurring production defects and security debt drop steadily.
• Stakeholders know what is shipping, when, and what changed.
• Bugs and feature requests get separated early and routed to the right path.
• A team that writes tested, consistent, maintainable code without constant oversight.
• A close working partnership with the Principal Engineer and the rest of Engineering.
Contact Information
Email: himanshu.yadav@anviktek.com
Click the email address to contact the job poster directly.