Tracking 100,000+ career sites
Senior Information Technology Jobs
This list tracks 100K+ company job sources and updates hourly with senior information technology roles across IT management, systems, technical support, service delivery, security, and enterprise technology.
Openings may be titled senior systems engineer, IT manager or director, service-delivery manager, enterprise applications leader, technical-support lead, infrastructure manager, technology-risk professional, or IT transformation leader. Work can include operating networks and endpoints, managing identity and enterprise systems, leading support, overseeing vendors and budgets, improving service processes, governing security and risk, or delivering modernization programs. Financial services, healthcare, manufacturing, consulting, government, and software employers differ in scale, regulatory pressure, legacy systems, and service expectations. Judge seniority through the business criticality and breadth of systems owned, decision authority, budget and vendor responsibility, escalation duties, and the size and structure of the team. A senior engineer may remain an expert individual contributor, while a director may be evaluated on operating performance, workforce planning, governance, and executive communication.
Map the operating model before comparing tool lists. Establish which systems and users the team supports, whether services are run internally or with vendors, and whether the remit is operations, support, governance, applications, or transformation. Note which service levels, budgets, and security or business risks sit with the position. Then review required platforms, certifications, clearance, on-call expectations, service-management practices, regulatory knowledge, budget responsibility, and team resources at the source. Any described assessment can guide preparation for troubleshooting, architecture, service, incident, vendor, or change-management scenarios. Employer, location, industry, compensation, and sponsorship filters can reduce the inventory. Compare disclosed pay and bonuses with call burden, workplace and travel requirements, and the condition of the environment being inherited.
Browsing and filtering are free. A free account can save IT roles, record application progress, and provide Copilot for selected forms. Keep the systems boundary and service expectations in the application record, with the source posting as the final check.





- today
Lightning AISenior Application Security Engineer - AI and Machine Learning$180k - $220kSeattle, WA$180k - $220ktoday - today
AuctaneSenior Security Engineer$75k - $83kBarcelona, Spain$75k - $83ktoday - today
Stanley 1913Information Security Senior Manager$150k - $170kSeattle, WA$150k - $170ktoday - today
CapgeminiConsultante / Consultant Senior Cybersécurité GRCAix-en-Provence, FranceNot listedtoday - today
AgodaSenior Systems Engineer - Contact Center TechnologyGurugram, IndiaNot listedtoday - today
DoctolibSenior Corporate Security Engineer - IT SecurityParis, FranceNot listedtoday - today
True AnomalySenior Embedded Security Engineer - Flight Software$145k - $235kLong Beach, CA$145k - $235ktoday - today
ZooxSenior IT Engineer - Audio Visual$151k - $181kFoster City, CA$151k - $181ktoday - today
GuidewireSenior Product Security EngineerRemote in IrelandNot listedtoday - today
AvnetSenior SAP Basis Consultant - Technical AdministrationPoing, GermanyNot listedtoday - today
HUBSenior Endpoint Engineer$130k - $155kChicago, IL$130k - $155ktoday - today
ReachSenior Staff Security ResearcherSan Francisco, CANot listedtoday - today
KLA CorporationSenior IT Business Systems Analyst - Multiple Teams$137.8k - $234.3kMilpitas, CA$137.8k - $234.3ktoday - today
Verra MobilitySenior Manager - Category Manager - Information TechnologyMesa, AZNot listedtoday - today
JustworksSenior IT Support Engineer$121k - $151kNew York, NY$121k - $151ktoday - today
Verra MobilitySenior Cybersecurity EngineerMesa, AZNot listedtoday - today
AxonSenior Security Operations Engineer 2$148.5k - $237.6kSeattle, WA$148.5k - $237.6ktoday - today
AxonSenior Security Operations Engineer 2Scottsdale, AZNot listedtoday - today
AxonSenior Security Operations Engineer 2$148.5k - $237.6kBoston, MA$148.5k - $237.6ktoday - today
Verra MobilitySenior Information Security Analyst - Security Ops & RiskMelbourne VIC, AustraliaNot listedtoday - today
General MotorsSenior Product Cybersecurity Engineer - Product Security Incident Response Team - PSIRTWarren, MINot listedtoday - today
General MotorsSenior Cybersecurity Incident AnalystWarren, MINot listedtoday - today
AbbottSenior SAP Application Analyst$78k - $156kMadison, WI$78k - $156ktoday - today
General MotorsSenior RTP Analyst - Global SAP CoEWarren, MINot listedtoday - today
General MotorsSenior Product Cybersecurity Engineer - Product Security ValidationWarren, MINot listedtoday
Explore More
Related Job Lists
Curated lists closely related to this one — similar roles, industries, and locations.
Senior Cybersecurity Jobs
Built from a 20M+ job database and updated hourly, this list surfaces senior cybersecurity roles across security engineering, architecture, operations, consulting, and cyber risk. Titles can include senior security engineer, cybersecurity architect, cloud or application security engineer, detection engineer, incident responder, security operations lead, security consultant, governance or cyber-risk manager, and security engineering director. The underlying work spans preventive controls, threat detection, incident response, architecture reviews, vulnerability management, identity, compliance, and security strategy. Team placement can shape the job: some postings describe close work with engineering, while others center on operations, risk, assurance, or client advice. Advisory positions may add deliverables and recommendations for several stakeholder groups. Seniority is reflected in authority over risk decisions, ownership during incidents, scope of systems protected, influence on architecture, and responsibility for mentoring or managing teams. Separate technical specialist and principal roles from governance or people-leadership positions, even when their titles use similar security language. Classify the function as engineering, operations, incident response, architecture, advisory work, assurance, or governance. That choice determines whether cloud and security tools, threat expertise, certifications, policy knowledge, or stakeholder influence should carry the most weight. Identify the assets and users being protected, the decisions the role can make, and who accepts residual risk. Next verify clearance requirements, on-call duties, travel, management scope, and reporting line in the original posting. If technical scenarios, architecture reviews, incident walkthroughs, or risk discussions are named, prepare evidence for those steps rather than assuming a universal security interview. Company, location, industry, compensation, and sponsorship filters can narrow the set. Consider pay with call burden, onsite constraints, team maturity, and authority to change systems; confirm authorization and residency language at the source. The list is free to browse and filter. A free account is optional for saved cybersecurity roles, application tracking, and Copilot. A short note on security domain and operating responsibility makes later comparisons clearer.
Senior DevOps and Infrastructure Jobs
This list is updated hourly from 100K+ company job sources and surfaces senior DevOps and infrastructure roles across CI/CD, SRE, platform engineering, systems, networks, databases, and observability. Openings may be labeled senior DevOps engineer, site reliability engineer, platform engineer, infrastructure engineer, systems or network engineer, database administrator, production engineer, or infrastructure lead. Responsibilities can include deployment automation, internal developer platforms, Kubernetes operations, network and database reliability, monitoring, capacity planning, incident response, and modernization of core systems. The balance between software development, platform enablement, and direct operations varies by team and should be clear in the source description. Some postings measure the role through developer adoption and delivery speed; others focus on availability, recovery, capacity, or safe change. Seniority is reflected in production ownership, architectural judgment, incident command, automation depth, and the ability to reduce recurring operational work. Staff and principal roles may set technical direction without direct reports; managers and operations leaders can add staffing, service-level, and escalation responsibilities. Production responsibility is the most useful starting point. Determine whether the engineer owns services, a shared platform, networks, databases, or an operating process, and how much of the work is software development versus administration. Then verify the cloud and operating environment, coding and infrastructure-as-code tools, container stack, observability systems, security or clearance needs, on-call rotation, and role during high-severity incidents. Look for evidence of who sets service objectives, approves risky changes, and follows remediation work after an incident. A disclosed interview plan may call for coding, systems design, troubleshooting, or incident examples; tailor preparation to the ownership described. Compare pay with call frequency, remote-access limits, and platform maturity. Company, location, compensation, and sponsorship filters refine the list, while the original posting controls authorization and workplace requirements. The list remains free to browse and filter. An optional free account keeps saved infrastructure roles and application progress together and offers Copilot for selected forms. Revisit any saved posting before applying.
Senior Cloud Engineer Jobs
Updated hourly from a 20M+ job database, this list surfaces senior cloud engineer roles across AWS, Azure, Google Cloud, platform engineering, migration, security, and reliability. Openings can include senior or principal cloud engineer, cloud architect, cloud platform engineer, infrastructure engineer, site reliability engineer, cloud security engineer, and engineering manager. Day-to-day work may involve designing landing zones and network boundaries, migrating applications, codifying infrastructure, operating Kubernetes, improving observability and resilience, controlling cloud cost, or setting security and governance standards. Some roles focus on a shared internal platform; others are tied to a particular product, migration, security program, or operating environment. Migration-led work may have defined transition milestones, while platform ownership continues through capacity, incident, and lifecycle decisions. Seniority depends on the systems and failure modes owned, autonomy in architecture decisions, incident leadership, and influence across development, security, and operations teams. Staff or principal openings may lead through expertise, while management roles can add staffing, service-health, and roadmap responsibilities. A useful first split is architecture and migration work versus ongoing platform and reliability ownership. From there, compare the required cloud provider with the broader networking, security, automation, and distributed-systems knowledge the role expects. The source posting should clarify infrastructure-as-code tools, container or serverless environment, certification or clearance requirements, travel, workplace terms, and whether production support includes an on-call rotation. Determine whether the team consumes an existing cloud foundation or owns the controls and services other teams depend on. If an interview format is described, prepare system-design, troubleshooting, automation, security, or incident examples appropriate to that platform boundary. Employer, location, compensation, and sponsorship filters can narrow results, but authorization and remote-work conditions should be confirmed in the original listing. No account is needed to browse or filter. A free account can hold saved cloud roles and application stages, with Copilot available for forms you choose to complete. Keep provider and on-call details attached to the relevant role.
Explore our FAQ section to learn more.
Senior IT work exists anywhere an organization runs a large internal technology environment. Recognizable employers to research include IBM, Cisco, Microsoft, Accenture, Deloitte, JPMorgan Chase, UnitedHealth Group, Walmart, and major universities and hospital systems. Technology vendors and consultancies hire for cloud, network, workplace, and client infrastructure roles. Banks, healthcare organizations, and retailers need internal teams for identity, devices, business applications, and resilient operations. Titles vary more than the work, so search systems engineer, infrastructure engineer, IT architect, network engineer, and enterprise technology alongside senior IT. Verify current openings and required credentials on each employer's own careers site.
Mid-level administrators often own defined systems and handle routine changes, support, and maintenance independently. Senior IT professionals are expected to make decisions that affect several systems or teams. They design migrations, set access and recovery standards, handle difficult incidents, evaluate vendors, and explain risk to leaders who may not be technical. The difference is judgment and scope rather than years alone. A senior candidate should be able to describe why a change was necessary, which alternatives were rejected, how disruption was controlled, and what happened after launch. Mentoring and escalation ownership are common even when the position has no direct reports.
Start with the operational problem and quantify the result where the numbers are honest. Useful examples include reducing ticket volume, shortening account provisioning, improving recovery time, automating patching, completing a cloud migration, closing audit findings, or cutting recurring software costs. Name the environment and tools, but do not let a product list replace the story. Explain your own role when a vendor or larger project team did part of the work. Senior hiring managers look for changes that remained reliable after rollout, so mention documentation, monitoring, training, or controls you put in place. Avoid claiming ownership of an organization-wide result you only supported.
The useful certification is the one that matches the work you want and appears in real postings for it. Advanced cloud credentials can help with architecture or migration roles, while networking and security certifications matter for those specialties. Service-management credentials may carry weight in large enterprises and consultancies. At senior level, a certificate rarely outweighs evidence that you designed, migrated, secured, or recovered a production environment. It can still help when you are moving into a new specialty or when a consulting employer needs certified staff for partner requirements. Check expiration, renewal work, and employer demand before paying for an exam.
Most combine troubleshooting with architecture and communication. You may be given an outage, access problem, failed migration, or security incident and asked what you would check first. Expect questions about networks, operating systems, identity, cloud services, backups, monitoring, and change control at the depth required by the role. Some employers add a practical lab or scripting task. Senior candidates are also tested on judgment: when to escalate, how to limit business disruption, and how to communicate uncertainty during an incident. Prepare examples where your first theory was wrong, because the correction often shows more skill than a perfectly tidy success story.
Ask how often the rotation comes around, how many alerts the last person received, and which events truly require a response at night. Find out whether senior staff are the first line or the escalation point, whether weekend maintenance is routine, and whether the company provides extra pay or recovery time. The most important question is whether the team can fix recurring causes during normal hours. A quiet rotation with good automation is different from a schedule that looks light only because people absorb constant interruptions. Also ask which vendors or business teams must be contacted during an incident and who has authority to stop a risky change.
Yes, particularly in cloud architecture, networks, security, identity, enterprise applications, and infrastructure automation. Individual contributors can advance by owning larger environments, defining standards, leading difficult migrations, reviewing designs, and becoming the escalation point for problems that cross teams. Titles may include lead, architect, principal, or senior specialist. The path is less consistent than in software engineering, so ask for the written career ladder and examples of people promoted through it. Confirm whether technical leaders receive authority and compensation comparable to managers. If the only next step is supervising a service desk or operations team, the employer may not have a genuine senior technical track.
Commercial employers can sponsor qualified IT professionals, but policies differ sharply by company and position. Large consultancies, technology vendors, banks, and healthcare organizations are more likely to have established immigration processes than small internal IT departments. Some client contracts, government systems, or positions requiring access to classified information impose citizenship or clearance requirements that ordinary corporate IT jobs do not. Current authorization and future sponsorship are separate questions, so describe both accurately. An H-1B transfer may be handled differently from a new petition. Confirm the policy with recruiting and seek qualified immigration advice for your circumstances.