From Zero to SharePoint Hero: My Journey at Cambium Inc
Published: September 20, 2025 • 7 min read
The Beginning: When You Don't Know What You Don't Know
Picture this: I started my first day at Cambium Inc knowing absolutely nothing about SharePoint. Zero. Nada. But here's the thing about being a Computer Science student—you learn to embrace that feeling of "I have no idea what I'm doing, but I'm about to figure it out."
Cambium Inc is a multi-service consulting and engineering company with several service groups and departments working together on various engineering projects. My role? "Technology Adoption Support." Honestly, I wasn't even sure what that meant when I started, but it sounded like exactly the kind of challenge I was looking for.
Taking Ownership of My Learning
Although I didn't receive specific training tailored to my role, I quickly recognized that SharePoint was going to be crucial for my success. The company relied heavily on it, and here I was, completely clueless about this entire ecosystem.
So what did I do? I bought a course on Udemy with my own money. I wasn't about to let my lack of knowledge become a roadblock. The best part? The company reimbursed me for it afterward, which was a nice surprise and really showed me they valued proactive learning.
SharePoint - Sites, Permissions and many more
This newfound knowledge enabled me to assist the company in leveraging the services and features offered by SharePoint. I proceeded to create a SharePoint site called the "Cambium Academy." This platform served as a knowledge base, allowing the company to store training videos and documents containing standard procedures for various processes within the organization. It was constructed on SharePoint to harness its collaborative and document storage capabilities fully. Throughout this process, I acquired extensive experience in designing SharePoint sites and pages, implementing various permission levels for document libraries and other elements of SharePoint, and strategizing the allocation of these permissions to individuals or groups.
Lights, Camera, More SharePoint!
The Video Recording Adventure
Here's where things got interesting—and where I discovered I apparently had a hidden talent for making technology less scary for people. Video recording and content creation became this huge part of my job, and I was certain from the interview that this was something I'd have to do.
I started by recording a video explaining how to record videos using Microsoft Stream (very meta, right?). The company was all-in on keeping everything within the Microsoft ecosystem, which made sense once I understood the bigger picture.
Then came my pride and joy: the "Microsoft Teams Training Series." I had this crazy idea to make 60-second videos designed to help employees actually want to use Teams in their daily work life. I was determined to keep them short because, let's be real, nobody has time for 20-minute training videos when they're just trying to figure out how to share their screen. There's more to Teams than sharing screens though and I was stunned by how powerful it really is.
As the concepts got more complex, I had to expand to 90-second videos, but I stuck to that concise format. I used OBS Studio for recording, Clipchamp for editing, and Canva for designing thumbnails that would actually make people want to click on the videos.
The Art of Getting People to Actually Watch
But here's what I learned that they don't teach you in computer science classes: creating the content is only half the battle. Getting people to actually watch it? That's a whole different skill set.
I had to master the art of crafting messages that motivated people to click on those video links. This is where I got to inject my personality—including my admittedly questionable sense of humor—into emails and Teams posts. Turns out, being genuinely yourself in corporate communications gets people's attention way better than corporate speak.
By the end of my second term, I'd also created SharePoint training videos, though not as many as I would have liked due to time constraints. But quality over quantity, right?
Becoming the Automation Wizard
My First Real Power Automate Project
My introduction to Power Automate started small. Really small. I created a process where users could enter project names into a SharePoint list, and based on those entries, the system would automatically create folders and subfolders for each project in a specific document library. There were standard subfolders that needed to be generated for every single project, and doing this manually was driving everyone concerned crazy.
This little project opened my eyes to the possibilities of automation. I dove deep into online research, watched countless YouTube videos, and gradually built up my understanding of Power Automate. Knowledge is power, but applied knowledge? That's where the magic happens.
The Vacation Request System That Changed Everything
Armed with my newfound Power Automate knowledge, I tackled what became my biggest project: a comprehensive Vacation Request system using Power Automate, SharePoint, Teams, and Outlook.
The goal was ambitious but necessary: completely automate the vacation request submission and approval processes, streamline operations, and simplify communication about vacation requests. Before this system, vacation requests were this painful back-and-forth of emails and paper forms that would get lost or forgotten.
The new system allowed users to request forms directly through Teams, complete them right there, and automatically initiate the approval process. I used SharePoint lists as the database, which kept everything organized and searchable. Watching people go from dreading vacation requests to actually finding the process pleasant? That was incredibly satisfying.
Building Real Solutions for Real Problems
The Field Worker Application
During my second term, I got to work on something that felt like a real software development project: an application that enabled field workers to automatically collect data about their tasks, store it securely, and generate reports based on standard templates.
This project let me flex different muscles. I dove into database development using Dataverse, learned to construct application logic using Power Fx in Power Apps, and automated the whole process using Power Automate. It was like putting together a complex puzzle where every piece had to work perfectly with the others.
Mastering Forms and Surveys
Throughout my time at Cambium, I also became the go-to person for creating surveys and questionnaires. I learned about all the different methods within the Microsoft Ecosystem—Microsoft Forms, Polls, Polly, and more. Each had its own strengths and ideal use cases.
This knowledge made me valuable in an unexpected way: I could advise people on which tool to use based on their specific needs. Sometimes it's not about knowing how to use every tool, but knowing which tool is right for the job.
The Reality of Startup Life
Always Something New
Most of the time, tasks were assigned to me as problems arose. The company would recognize that something needed to be addressed, and I'd get pulled in to figure out a solution. This meant I consistently had a heavy workload, but honestly? I loved it.
It kept me occupied and provided endless learning opportunities. However, it also meant I had to constantly assess my to-do list and figure out which fires needed to be put out first. Communicating with my manager became crucial for prioritizing my responsibilities effectively.
Becoming the Go-To Person
The interesting thing about being the only person who could do certain things is that it forced me to absorb knowledge like a sponge. Everyone in the company relied on me for specific areas of expertise, and I always wanted to be ready with solutions when problems came up.
This taught me something valuable: you don't need to possess all-encompassing knowledge, and learning on the job is not just acceptable—it's essential. Technology moves too fast for anyone to know everything all the time.
What This Year Really Taught Me
The Power of "I Don't Know, But I Can Find Out"
My most commonly used phrase in meetings became "I don't know, but I can find out." At first, I thought this might make me look incompetent. Instead, it became my superpower. It showed I was honest about my limitations while being confident in my ability to learn and solve problems.
Skills Beyond Code
Working at Cambium taught me that success in tech isn't just about coding skills. I developed:
- Content creation abilities that make complex technology accessible
- Video editing skills that help communicate ideas effectively
- The ability to learn any tool if I set my mind to it
- Project prioritization in a fast-paced environment
- Cross-functional communication between technical and non-technical teams
The Microsoft Ecosystem Mastery
By the end of my year at Cambium, I had deep experience with SharePoint, Power Platform, Teams, Power Apps, Power Automate, and the entire Microsoft 365 suite. I could design workflows, automate processes, create training materials, and help others navigate these tools effectively.
Looking Back: A Year That Shaped My Career
My experience at Cambium Inc was transformative. It taught me that being willing to learn continuously is one of the most valuable skills in the IT field. It showed me that I could take ownership of my own learning journey and become an expert in areas I'd never heard of before.
The relationships I built, the problems I solved, and the confidence I gained during that year became the foundation for everything that followed in my career. Sometimes the best opportunities come disguised as things you've never done before.
This post is part of my "Professional Journey" series, where I share authentic experiences from my career path. Next up: my deep dive into AI Math training at Outlier.