From EHS Practitioner to EHS IT Leader: A Field Fuide to Making the Transition

Every time I share a job posting for an EHS systems or data role on LinkedIn, my DMs light up. EHS specialists, managers, directors, even a VP, all asking the same thing: "How do I make this transition? Where do I even start?"

The demand for these roles is real. And it's accelerating. When I first started out, I was lucky to see one job posting for this type of role every six months. Now I see at least one every few weeks. The market is catching up to what forward-thinking companies already know: you need people who understand both EHS and the digital systems that support it.

So I sat down and answered the questions I get asked most often. What I've learned is that this transition isn't a straight line, and there's no single right way to do it. But there are patterns. There are skills that matter more than others. And there are misconceptions that hold people back.

My hope is that you walk away with clarity on whether this role is for you, and a sense of where to start.

I've spent the last decade making this transition myself and helping others do the same. Safety intern. Safety specialist. EHS consultant. Project manager. System admin. And most importantly: the in-house EHS Systems and Data leader navigating system management, collaborating with stakeholders across IT, Risk, People and Operations.

I've seen and lived this transition from EHS practitioner to EHS IT leader from a lot of angles. And now, one of the things I like doing is helping EHS professionals figure out how to make this same move.

What Does a Day in the Life Look Like?

Let me paint a picture of what you're actually signing up for.

Coming in, you're likely going to be responsible for managing the EHS team's software platform. That might mean selecting a new system, optimizing what you already have, or fixing something that's been broken for years.

You're likely going to wake up to Slacks, MS Teams pings and emails asking things like:

• "Hey, can we change this form?"
• "I'm not able to get data out of this report."
• "We need to submit this quarterly board report by end of day."
• "I've been playing around with [Random System] and I'm wondering if you can help me."

You'll likely also become the EHS IT service desk, even for tools you don't technically own. It's a lot of problem-solving. It's a lot of customer service. And you need a mindset that doesn't mind being contacted constantly. EHS professionals are no stranger to this, so likely there is no concern there.

If you have a method to funnel those requests in a way that creates feedback loops for the people asking, that's the smartest thing you can do early on. It shows them you're listening and there to support, but also that you have work priorities to stay on top of. No one wants their ticket going into a black hole, so find what works for you to manage the back-and-forth conversation (and it keeps an audit trail).

On any given day, you might also be:

• Meeting with cross-functional stakeholders
• Running training sessions on the system
• Updating user and admin documentation
• Working with data engineering teams and analysts
• Documenting and visualizing processes, workflows and dependencies
• Upskilling on a new tool the company just procured

This is why it's important to read job descriptions carefully to understand what tools you'll be working with and what's expected of you. If that's not listed, ask in the interview.

At the management level, add to that:

• Managing budgets and going through budget approval processes
• Understanding what systems are being used across the department, how they connect (or don't), and what should be consolidated
• Writing business justifications and ROI statements for executive leadership
• Monthly, quarterly, and yearly goal setting and work prioritization
• People management (if you're lucky enough to have a team or a contractor/consultant supporting you)

You really become the go-to person and the filter for everything EHS technology, systems and data.

A lot of your work depends on other people.

This is the part people underestimate. You're not going to be doing everything yourself. A lot of what you need to deliver is dependent on other teams. Maybe you need your data engineering team to build a pipeline. Maybe you need the integrations team to connect your EHS system to HR. Maybe you need IT to provision access or security to sign off on a vendor. Maybe you need EHS to show up to the workshop for requirements gathering and provide their input so they can be documented for configuration.

Your job is to project manage across all of it. Keep people moving. Follow up on what you need. Track dependencies. Know who's responsible for what and when it's due.

And here's the soft skill that matters most: you need to be someone people actually want to work with. You're all on the same side. Being clear, organized, and respectful of people's time goes a long way. We've all worked with someone who creates chaos in every inbox they touch. Don't be that person. Document the action items, set agreed upon timelines and communicate clearly.

You cannot be a "yes" person all the time.

People should know they can come to you with any issue, and you're going to listen and digest it. But that doesn't mean you automatically go make the change.

This is the biggest difference between a generic IT service desk person managing EHS tech and an actual EHS person in this role: you're more likely going to understand the pros, the cons, the trade-offs, and the risk associated with any changes you make in your tech stack. Being able to clearly communicate that information matters.

Having some form of a steering committee or a system power user group to run things through is a good best practice. Emotions and politics can get in the way, so being comfortable standing your ground while maintaining empathy is important. You'll work with difficult personalities. Technology frustrates people when it doesn't work, and learning how to manage that without taking it personally is part of the job.

The Technical Bar Is Lower Than You Think

The biggest misconception I hear from EHS professionals? That you need to be deeply technical or know how to code. You don't.

If you're going to learn one thing, learn SQL. Python is a bonus. But coding is much less of a barrier than it used to be thanks to AI.

But here's what you do need: technical fluency.

It helps to understand where technology can be applied to EHS processes. Where can automation reduce manual work? Where can integrations eliminate double entry? Where can AI help surface insights faster? You don't need to build these solutions. But seeing the opportunities and knowing what to ask for is part of the value you bring.

You'll want to understand how fast the technology landscape is changing. AI is accelerating everything. The tools that exist today didn't exist ten years ago, and the tools that will exist in one, two and five years will make today's look archaic. Staying aware of these shifts and trends is important.

Your domain knowledge is your competitive advantage.

This is why IT people often struggle in these roles. I've seen it over and over again in my consulting work. They have the technical skillset, but they lack the domain knowledge. They don't know what a Job Safety Analysis is. They don't understand why OSHA recordkeeping matters. They don't understand the severity of the risks of the operation and its impact on human lives and the environment. They can't speak the language of the department they serve.

You can. You're the translator who can sit with an EHS manager or Ops Leader, understand their workflow needs, and explain it to IT or a software vendor in a way they can actually build. That skill is rare and incredibly valuable.

Domain knowledge is around 60% of the job at the start. The technical piece closer to 40%. And even as the balance shifts over time, you're not leaving EHS behind. You're becoming a bridge between EHS and IT. You're expanding your toolkit, not abandoning your domain.

The real technical requirement is having the aptitude and willingness to learn, even outside your 9-to-5. You're not going to check every box on the job description. But that's not a reason to skip the application.

Is This Role for You?

Before we get into what you need, let's make sure this is the right fit. Answer honestly:

1. Do you enjoy problem-solving more than being in the field? These roles are heavy on troubleshooting, system design, technical translation and working through challenges. If you don't like being on a computer for a lot of your work week, that's okay. This might not be your path. It's vital to be hands on with your users and team, but the nature of the job is going to put you at a desk more than field work will.

2. Are you the person people come to when something's broken? If coworkers already ping you with "hey, do you know how to fix this?" or "can you pull this data for me?", you're already doing parts of this job. Hone in on that.

3. Do you find yourself thinking "there has to be a better way" when doing manual work? If repetitive tasks frustrate you and you're always looking for ways to automate or streamline, that's a sign.

4. Are you comfortable being the bridge between EHS and IT? You'll spend a lot of time translating between groups who don't speak the same language. If that sounds exhausting rather than interesting, reconsider.

5. Are you willing to learn on your own time? The technical skills can be learned. But you do have to want it. If you're only interested because of the perceived higher salary, this role will burn you out. You're going to be more of an IT person than a boots-on-the-ground EHS person. Make sure you're ready for that shift.

If you answered yes to most of these, keep reading.

What You Actually Need to Make This Transition

One of the most common questions I get is: "What certification should I get?"

Here's the thing: there isn't one magic certification. I wish I could point you to a single credential that would open every door, but this transition is more nuanced than that. What actually matters is a mix of EHS domain knowledge, technical skills, and the people-centered abilities that let you bridge two worlds.

I've seen this pattern hold true from entry-level roles to director positions, across every client engagement and every person I've helped make this transition. The formula is consistent, even if the path to get there looks different for everyone.

Here's what tends to matter most, organized by category:

Software and Systems Experience

Hands-on experience beyond just being an input user. Whether it's Cority, Gensuite, Intelex, Enablon, ISN, SafetyCulture, EHSInsight, Avetta, Origami Risk, or any of the other 50+ platforms out there, if you've done anything other than basic data entry, highlight it. Ran a requirements workshop? Configured a workflow? Set up a form? Troubleshot permissions? Trained end users? That counts. Put it on your resume, that experience is your launching pad.

And this extends beyond EHS software. HRIS systems, asset management platforms, ERPs. Being comfortable navigating different tech stacks is a major advantage. If you've touched one or two of these platforms and started to see how they work behind the scenes, you can probably get up to speed on a new one within three months. They all have a learning curve, but the patterns transfer.

One thing to know: the level of hands-on work can vary widely. Some roles will have you deep in technical configuration work every day. Building forms, setting up workflows, managing permissions, troubleshooting integrations. Other roles are much more vendor-managed. You're the business owner, but the vendor or a consultant does most of the technical build. You're coordinating, testing, and providing requirements, not configuring.

Every platform and tech stack is different. Every company is different in how they operate. Be prepared for a balanced mix depending on what the company has and how they've structured the role. Read the job description carefully and ask about this in the interview so you know what to expect.

Configuration literacy. Knowing how fields, forms, tables, roles, and automations work in modern platforms helps you make informed decisions and push back when needed.

Automation and AI awareness. Understanding what's possible with workflow automation, no-code tools, integrations, and AI lets you design smarter systems. You don't need to build these things, but knowing what to ask for matters. And it definitely helps if you can get your hands dirty.

Data

Data fluency. Familiarity with the basic terminology that shows up in job descriptions will serve you well. What's an API? How do integrations work? What's a data pipeline? What's a data warehouse? How are the databases configured? How does AI enhance or impact all of these things? It's very likely you don't need to be the one building them. But you need to know who does and being able to talk about them intelligently opens doors.

Data analytics skills. This goes a bit beyond fluency. Being comfortable with basic SQL, generating dashboards, building reports, and tracking metrics is important. More importantly, being able to speak to the "so what" and the "why" behind the numbers. What KPIs is your leadership team asking for? How do they think that data is getting to them? What decisions do they need to make with this data?

Data governance fundamentals. Maintaining taxonomies, owners, validations, naming rules, and clean data. Without governance, systems eventually break, and using AI on your data will be impossible.

People and Process Skills

A customer service mindset. You're going to be the IT help desk for EHS, even when the issue isn't technically your problem. People will come to you when they can't log in, need a report, or want data you don't control. Staying positive and pointing them in the right direction matters. In many of these roles, you'll be the single point of contact.

Change management skills. Driving adoption, communication, user training, and behavioral change. Most system failures are people problems, not tech problems.

Requirements gathering skills. Asking the right questions, mapping workflows, and translating work-as-done reality into clear technical requirements.

Vendor management skills. Working with cybersecurity, IT, legal, procurement, and software vendors. Negotiating scope, clarifying requirements, and holding teams accountable. This becomes even more important as AI gets integrated into platforms.

Project management skills. Developing digital strategy across multiple workstreams. Managing timelines, risks, dependencies, deliverables, and stakeholders. Keeping the boat afloat and maintaining accountability.

Domain Foundation

Systems thinking. Understanding how incidents, hazards, controls, training, and operations connect helps you design workflows and data models that reflect real work. This is where your EHS background becomes your competitive advantage.

If you've spent years in EHS, you already have this. The work now is making it visible. When you're building a project portfolio or talking through your experience in an interview, map out the connections. Show how you traced an incident back to a training gap but that training completion dates mean nothing if you're not tracking competency against task requirements. Explain how you redesigned a hazard assessment process because the old one didn't reflect how work actually gets done on the floor. Show that you recognize that automating escalation of corrective actions creates noise, not accountability if it's not tied back to goals.

Here's what I want you to take away from this: you likely already have more of these skills than you realize. The self-assessment is the first step. Figure out which ones you need to work on and start there. It's not about checking every box before you apply.

And read the job descriptions. They'll tell you exactly what to learn. The market is pretty transparent about what it needs.

What Does the Market Actually Want?

I share a lot of job postings on LinkedIn related to these roles, and I track the patterns across them. Here's what companies are actually asking for:

EHS IT Manager at a cloud infrastructure company ($122K-$179K)

• 7+ years in EHS
• Tech-savvy in EHS data reporting
• Customer-centric (you will be the single POC)
• Strong cross-functional skills
• Global experience preferred

EHS Data and AI Analyst at a manufacturing facility ($75K-$95K)

• Data analytics and reporting (Power BI, Tableau, Python, R, SQL)
• Comfort with AI and machine-learning models
• Managing EHS platforms including system admin, training, reporting, workflow building, process optimization
• Cross-functional collaboration with Operations and Continuous Improvement Teams
• Deep analytical mindset AND EHS domain expertise

EHS&T Systems Specialist at a mining services company

• EHS systems administration across multiple platforms
• Data analytics and reporting (Excel, Power BI preferred)
• System configuration, workflows, user training, and troubleshooting
• Understanding of OSHA, MSHA, EPA, and ISO standards
• Cross-functional collaboration with IT and EHS leadership
• Change management skills

EHS Systems Manager at a global enterprise (capped at $203K)

• Leading enterprise software projects
• Translating between EHS teams and digital groups
• Optimizing systems to reduce admin burden for people on the shop floor
• Database management and backend system architecture
• Business Intelligence tools like Power BI and Tableau
• API integrations

See the pattern? Every single one of these roles wants domain expertise, systems experience, data skills, and the ability to work across functions. That's the formula. Once you see it, you can reverse-engineer your development path.

Let's Talk About Money

According to the National Safety Council's Safety+Health Salary Survey for 2025, less than 20% of EHS professionals are making over $150K. That salary range is typically reserved for Director and VP roles.

As you can see above, salaries for EHS systems and data roles have a wide range, but they're typically on the higher end for EHS positions. The difference? It's an IT systems role. It demands a different type of technical expertise and therefore, a larger salary band. Roles that blend EHS domain expertise with technology skills are being compensated in a completely different bracket.

If you've been thinking about upskilling in systems, data, or AI, here is your green light. The organizations investing in digital transformation need people who can do both, and the money reflects it.

Where to Start (And How to Build Proof Without Going Back to School)

Do you need a coding bootcamp or a degree? No. And I say that as someone who learned most of this on the job.

If you're considering a paid bootcamp, especially if you're unemployed, I'd encourage you to think carefully about that investment. Your time might be better spent building portfolio projects that show what you can do.

If anything, invest in your EHS credentials. A CSP, ASP, or CIH will be far more valuable than a generic data cert. Your domain credibility is what will set you apart from IT candidates.

Start with what you have access to.

1. Automate a manual process. Chemical approval workflows, inspection checklists, incident follow-ups. Use Power Automate/Power BI, Google Apps Script, or even Jira if your team has access. Maybe you have a chemical approval process that requires a bunch of emails and Slacks back and forth. Build something that takes that friction out.

2. Build dashboards with real or dummy data. Show you can take raw data and turn it into something decision-makers can use. Shift the narrative from lagging indicators to leading indicators. You can even have ChatGPT, Gemini, or Claude generate a project for you if you need dummy data.

3. Improve how leadership gets their data. If someone's pulling reports manually, fix it. If the data is messy, clean it up and visualize it better. This is the kind of work that gets noticed internally and translates directly to your resume. Create a mock deck for an EHS leadership team.

4. Become a power user or system admin for your EHS software. If your company has an EHS platform, ask to get involved, try to get access to the admin side in a demo environment. Learn how permissions work. Volunteer to configure a new form or workflow. This hands-on experience is exactly what hiring managers are looking for.

5. Consider freelance or independent consulting. If you have some prior experience and the capacity, taking on small consulting projects can accelerate your learning fast. You'll get exposure to different platforms, different client problems, and real-world implementation challenges. It's not for everyone, but if you have the bandwidth, it's a way to build credibility and a portfolio at the same time.

These projects prove you can think like a systems person, not just an EHS person.

How to Showcase Your Learning

LinkedIn.

Build in public. Post about what you're learning. Share the automation project you completed. Write about the dashboard you built. EHS professionals are forever learners, so no one will think it's weird that you're upskilling.

Update your LinkedIn headline to reflect the role you want, not just the one you have. Your company doesn't need to be in your headline. That space is yours.

Recruiters live on LinkedIn. I found my last industry job because someone reached out to me. This is still a very niche space, and there aren't a lot of qualified people. Make yourself visible.

Even if you're doing internal work, anything you can repurpose into a LinkedIn post, a Substack blog, or a blog article, wherever you feel safe sharing that information, do it. Remember not to post any company data openly. You can share about your experience: the problem you had, the process you thought through, what you executed and what the results were.

Don't go too deep into one skill at the expense of breadth. You don't need to become a SQL expert before you apply. You need to be conversant across multiple areas.

Don't wait until you feel ready. Apply as soon as you have a few bullets on your resume that tie EHS experience to technical skills. Apply early. Get feedback. Adjust.

IT people apply to these jobs even when they don't know what EHS stands for. You should too. Apply to get interview experience. If you don't get the role, ask why. That's how you learn where to focus.

Commit to the time investment. Realistically, if you're serious about this transition, plan to spend 5 to 10 hours per week learning and building. Use free resources. Build portfolio projects. Share your learning.

It takes time, but it's doable. And remember: you already have the domain expertise. That's the hardest part to teach. You're more qualified than you think.

How I Made This Transition

I started as a safety coordinator in oil and gas, moved into environmental consulting, and realized our project workflows were painfully slow. I advocated for a mobile checklist app so I could audit 100+ oil wellheads in a week and have the data immediately available.

That curiosity led me to a consulting firm that specialized in EHS systems. I learned system administration, project management, and stakeholder communication. But the real breakthrough came when I moved in-house to industry.

That's where I learned the soft skills that matter: who to talk to for budget approval, how to navigate IT and HR systems, how to balance what EHS needs with what operations can actually use. Figuring out who the right person is to talk to, whether that's the people systems team, the data analytics team, the IT team that provisions permissions, or the operations team that needs access to the data within the EHS tool. All of that was deeply learned when I made that transition to industry. I was in the weeds and I was directly responsible for the impact that systems and data had on our larger EHS management system.

Now I run a consulting firm doing that same work at scale across a dozen high-risk industries. The need is out there.

If you want to accelerate your learning and land a role, consider one of the three "trifecta" career opportunities:

1. Industry (in-house at a company). This is where you learn the soft skills and internal politics. Budget approvals. Stakeholder management. Balancing competing priorities. Getting really hands-on across multiple tools.

2. Vendor (working directly for Cority, VelocityEHS, Enablon, or a startup). You'll go deep on one platform and learn how software companies think about product development and implementation.

3. Consulting (think ERM, Trinity, Jacobs, All4, JS Held, boutique firms, independent consulting). You'll get exposure to multiple platforms and client problems fast. You might start entry-level, but you'll learn the breadth of the market quickly.

Each path teaches you something different. You might have to start entry-level, but you'll get exposure that compounds over time.

What About People Who Think They're Too Senior to Pivot?

Let me be honest: any career transition is hard. You might take a step back on the org chart. You might feel like you're starting over in some ways. That's worth acknowledging.

But the work itself is challenging, rewarding, and constantly evolving. I'm part of the data community now. I go to data happy hours and talk to engineers, analysts, and scientists who work in healthcare, marketing, finance. The tech world is fun, and we're in the middle of a massive shift with AI and automation.

Combine that with how fast EHS and regulatory compliance are changing, and you're in a dual lane of forever learning. It's not boring or a dead end.

If that sounds exciting to you, the transition is worth it.

Where Is This Space Headed?

This is a growing niche within our domain, and it's exciting to see companies valuing the importance of it. The need is high and validated talent is low. I see this every day in my client work and in the market data I track.

I predict roles like EHS AI Automation Specialist, Director of EHS AI Systems, and VP of EHS Technology will become commonplace in the next 5 to 10 years. This will become a central leadership role as technology evolves and AI becomes integral to the way we do work.

If you get in now, you're positioning yourself for a career trajectory that doesn't exist yet for most EHS professionals.

A Final Note

I started writing this because I kept having the same conversations over and over. And I realized that if this many people are asking, there's probably a whole lot more who are wondering the same thing but haven't reached out yet.

This transition is doable. And honestly, I think more EHS professionals should be making it. The work matters, the demand is there, and you already have the foundation. You just need to build on it.

If you have questions about this transition, the job market or the candidate pool for these roles, leave them in the comments. I'd love to hear from you.

If you currently serve or have served in an EHS Systems/Data/IT/Platforms role, I'd love to hear about how your experience got you there.

P.S. I'm putting together a free career roadmap for EHS professionals looking to break into systems and data roles. It will include a structured learning path based on your experience level, curated resources, and portfolio project ideas you can start immediately. If you want it when it's ready, sign up here to get on the waitlist.