1

Technical Lead Manager Jobs (NOW HIRING)

Technical Lead Lewisville, TX Technical Lead position. This is a Call Center infrastructure. Other ... Management Roles and Responsibilities The Technical Manager will be responsible for performing the ...

The Technical Lead will support enterprise cybersecurity operations, security engineering, tool integration, risk management, and technical modernization efforts across a complex federal environment.

Technical Lead Location: Malvern, PA or Dallas, TX Work Type: Onsite / Hybrid Experience: 10+ Years ... Lead hands-on development of client-facing wealth management tools. * Build backend services using ...

Technical Lead Location: Alpharetta, GA (The technical lead should be able to lead a team and ... In addition, the individual must keep his/her manager well informed of status of development effort.

The Technical Lead will serve as the senior technical authority responsible for ensuring LMI ... Lead deployment and management of mission-critical applications within AWS and other cloud ...

Technical Lead (.NET) Position Overview We are seeking an experienced Technical Lead with strong ... Manage technical risks and proactively propose mitigation strategies. Mentor developers and promote ...

They will work closely with the Product Owners and IT Federal Project Manager (FPM) to fully ... Additionally, the Technical Lead will design and develop the system to set the standard for future ...

Showing results 21-40

Technical Lead Manager information

See salary details

$30K

$156.3K

$206K

How much do technical lead manager jobs pay per year?

As of Sep 13, 2026, the average yearly pay for technical lead manager in the United States is $156,348.00, according to ZipRecruiter salary data. Most workers in this role earn between $116,000.00 and $205,000.00 per year, depending on experience, location, and employer.

What is a technical lead manager?

A Technical Lead Manager (TLM) is a hybrid role that combines both technical leadership and people management responsibilities. TLMs are responsible for guiding the technical direction of a team while also overseeing the professional growth and performance of its members. They often balance hands-on engineering work, such as code reviews and architectural decisions, with managerial tasks like mentoring, hiring, and conducting performance evaluations. This role is crucial in ensuring that technical projects are delivered efficiently while maintaining a positive and productive team environment.

What does a technical lead manager do?

A Technical Lead Manager (TLM) typically splits their time between guiding the technical direction of projects and managing a team’s performance and growth. This dual focus means TLMs often participate in code reviews, architectural decisions, and problem-solving sessions, while also conducting one-on-ones, setting goals, and ensuring team alignment. Effective TLMs delegate appropriately, empower team members, and create an environment where both project delivery and professional development are prioritized. Balancing these aspects requires strong time management, clear communication, and the ability to shift between technical and people-centric tasks as needed.

What skills and qualifications are needed to be a technical lead manager?

To thrive as a Technical Lead Manager, you need a robust background in software development, systems architecture, and project management, often demonstrated by a degree in computer science or related field and several years of industry experience. Familiarity with development frameworks, cloud platforms, agile methodologies, and tools like Jira, Git, and CI/CD pipelines is typically required. Strong leadership, communication, and problem-solving skills set exceptional managers apart by enabling effective team guidance and stakeholder collaboration. These skills and qualities are crucial for delivering high-quality technical solutions while fostering team productivity and growth.

What is the difference between Technical Lead Manager vs Technical Project Manager?

AspectTechnical Lead ManagerTechnical Project Manager
Primary FocusLeading technical teams and overseeing technical deliveryManaging project scope, schedule, and resources
Required SkillsTechnical expertise, leadership, team managementProject planning, stakeholder communication, risk management
Work EnvironmentEngineering teams, product developmentCross-functional teams, client interactions
Common UsageTech companies, software development firmsIT consulting, enterprise project management

The Technical Lead Manager primarily focuses on leading technical teams and ensuring technical excellence, while the Technical Project Manager concentrates on planning, executing, and delivering projects on time and within scope. Both roles require strong communication skills, but their core responsibilities differ significantly in scope and focus.

What cities are hiring for Technical Lead Manager jobs?

Cities with the most Technical Lead Manager job openings:

What are the most commonly searched types of Technical Lead jobs?

The most popular types of Technical Lead jobs are:

What states have the most Technical Lead Manager jobs?

States with the most job openings for Technical Lead Manager jobs include:

What are popular job titles related to Technical Lead Manager jobs?

For Technical Lead Manager jobs, the most frequently searched job titles are:

Infographic showing various Technical Lead Manager job openings in the United States as of August 2026, with employment types broken down into 88% Full Time, 11% Part Time, and 1% Contract. Highlights an 80% Physical, 2% Hybrid, and 18% Remote job distribution, with an average salary of $156,348 per year, or $75.2 per hour.

Technical Lead Manager (Production Engineering)

Manhattan, NY • On-site

Other

Medical, Dental, Vision, Retirement, PTO

Posted 2 days ago

New


Job description

  • Production Engineering is Ramp’s infrastructure ownership layer. We exist to make Ramp faster, more reliable, and more scalable — and we do that by being embedded in the problems, not adjacent to them
  • Production Engineering is organized into teams — but we think about teams differently. Teams are mutable. We build them around what needs to be done, not around what we need to do given the teams we already have. The structure below reflects our current priorities; it will evolve as Ramp does
  • Right now, we operate across four areas:
  • Compute — the foundation everything runs on: container orchestration, networking, load balancing, edge infrastructure, and the deployment systems that get code from engineers’ laptops to production reliably and at scale
  • Storage — databases, caching, object storage, and the data infrastructure that underpins everything
  • Workflows & Messaging — the systems that power Ramp’s financial workflows and event-driven architecture
  • Internal Infrastructure — the platform that makes every builder at Ramp faster and more autonomous: observability, cost attribution, and CI/CD systems that give teams visibility into what they build and what it costs
  • Production Engineers at Ramp are full software engineers who happen to specialize in infrastructure. You write production code, you own systems end-to-end, and you drive technical outcomes across the organization — not just within your team
  • Build and operate critical infrastructure across Ramp’s compute, storage, messaging, and observability stack — owning the systems that handle real financial transactions at scale
  • Drive architectural change — not just flag problems. When you surface a reliability or scalability issue, you own the path forward: you propose the solution, find the owners across engineering, and stay in until it’s resolved
  • Partner with product teams at the design phase — reviewing architectures, embedding golden paths, and making it easy to build correctly the first time
  • Build Ramp’s next level of scale — you’ll be a hands‑on contributor to the most consequential infrastructure shift happening right now: our move to a cellular architecture, enabling Ramp to scale, reach international markets, operate in highly regulated and constrained environments (e.g. FedRAMP), and deliver on enterprise‑grade SLAs
  • Enable AI‑native engineering — as Ramp builds increasingly AI‑powered products, PE is the team that makes sure the platform can support them. You’ll proactively partner with product teams on AI infrastructure patterns, define the golden paths that turn one‑off solutions into reusable foundations, and stay ahead of emerging challenges before they become blockers
  • Build developer tooling and self‑service infrastructure — so that other teams can answer their own questions (cost, performance, reliability) without involving PE
  • Participate in on‑call rotation — and more importantly, use every incident as a signal to eliminate the root cause, not just resolve the symptom
  • Lead across the company — PE doesn’t just review designs or show up when called. We proactively initiate cross‑team architectural reviews, and we take full ownership of company‑wide reliability and scalability initiatives: identifying the problem, proposing the solution, aligning the stakeholders, and staying in until it’s done
Benefits
  • Comprehensive medical, dental, and vision insurance
  • One Medical Membership
  • 401(k) including an employer match
  • Unlimited PTO
  • Parental leave
  • Monthly wellness stipend
  • WFH stipend
  • Relocation support to move to NYC
  • Pet Insurance

We don’t hire for a checklist. We hire for the instincts that make someone exceptional on this teamYou are equally comfortable reading a database query plan, reviewing a system design doc, writing a Terraform module, and jumping into an incident at 2amYou move with urgency but without chaos. You know when to go fast and when to slow down and do it rightYou treat product teams as your users. You build for them, communicate with them proactively, and measure success by how much faster they can ship. But you’re also an owner — when something is broken or blocking, you don’t wait to be asked. We win when our customers winHands‑on experience with distributed systems at production scaleYou think in systems, not tasks. You understand that “fixing the bug” is step one; making it so the bug can’t happen again is the jobYou leave things better than you found them. Every system you touch, every process you encounter — you move it forward. Not always dramatically, but always directionally. You picked it up in a certain state; you leave it in a better one3+ years of software engineering management shipping high‑quality architectures for critical systemsExperience with at least one major cloud provider (AWS preferred)You can’t walk past something broken without wanting to fix it — and you don’t stop at the workaround. You find the root cause and eliminate the class of problemTrack record of leading technical projects end‑to‑end, including cross‑team coordinationFamiliarity with observability practices (SLOs, error budgets, alerting, dashboards)Comfortable using AI tooling and coding agents as part of your everyday engineering workflow — we expect our engineers to leverage these tools to move faster and think biggerStrong software engineering fundamentals — you write clean, well‑tested, production‑ready codeExperience with cellular or multi‑tenant architecture patternsPrior work on workflow orchestration systems (Temporal)Contributions to developer experience or internal platform toolingExperience in fintech, payments, or regulated industries (FedRAMP, SOC 2)

#J-18808-Ljbffr