Lisa MacCarrigan thinks about her career like a navigation app.
You know when you put an address into Google Maps and it shows you several different ways to get there? And how if you make an unexpected turn or miss an exit it’ll show you yet another way?
That framework has helped Lisa navigate some of the seemingly major career decisions—including a pivot from land use and environmental planning to coding—that led her to her current role as a front end software engineer at knowledge management software company Guru.
We sat down with Lisa to talk about the growth mindset behind her Google Maps metaphor, how she pursues new skills that help her at work and at life, and what advice she has for other engineers looking to find intellectual and job satisfaction in the ever-changing world of tech through continual learning.
Finding her kind of problem-solving
After college, Lisa started working in the field of land use and environmental planning and quickly realized that her favorite part of her job was using geospatial data to help make informed decisions.
“I continued to find myself falling into immersive flow states—like when you’re five years old and doing something and forgetting the world around you. Time wasn’t a thing. That would happen when I was working with data,” she says, smiling.
Lisa wanted to learn more, so she took a computer programming course at a local community college, as well other courses. She was soon convinced that her passion lay in programming, so she left her career in government to join a coding boot camp—and has been working happily as a developer ever since.
Learning on screen and on stage
When Lisa joined Guru as a front end software engineer, she’d worked in tech long enough to know what kinds of technical problems she wanted to get better at solving. She also knew she wanted to improve on certain soft skills, too, particularly listening, presenting, and collaboration.
So she signed up for a year of improv classes.
An unorthodox approach, perhaps, to improving on-the-job skills, but one that definitely worked. Lisa says she’s always had a dry sense of humor and a fondness for levity, but that diving into improv classes was a perfect mix of scary and comfortable that allowed her to work on what she’d set out to learn.
“I’ve woven my learnings into my daily work interactions,” says Lisa. She’s since identified four major skills from improv that map neatly onto her work in software development—active listening, support, trust, and collaboration—and encourages other engineers to follow suit.
But even for people for whom the prospect of soliciting audience prompts and acting out impromptu scenes is terrifying, Lisa believes that trying something new, whether it’s improv or pottery or boot camp, is worth it.
“Those experiences affirmed just how essential continual growth is, whether it’s derived through work or play,” she says. “Through continual learning, you’re constantly exposing yourself to new information, and with new information comes an increased awareness, and hopefully a deepened curiosity, which begets further learning and more curiosity.”
3 tips for other engineers to always be learning
1. Find a mentor with slightly more experience than you. Lisa suggests 2-3 years. “There’s a lot that you can learn from that person. And there’s also a lot that they can learn from you,” she says. “But most importantly, when you’re looking at someone two years ahead of you, they don’t have to reach too far back into their own experiences to know exactly where you’re at and what will help you grow.”
She also appreciates that Guru’s culture is built around pair programming from the very beginning. “You pair program when you’re new; you’ll pair program to get quickly onboarded and to understand, at a high level, the architecture and how all the pieces fit together,” she says. “But also when we’re stuck on things, we might tap a coworker and just say, ‘Hey, I’m really struggling in this area. I see that you’ve worked in this area.’ I really enjoy it, personally.”
2. Tackle problems that interest you—and stretch your skills. Lisa has done this at Guru by joining working groups that form to tackle specific problems.
Recently, she’s been doing that by contributing to Guru’s continuous integration pipeline (which deals with automating the integration of code changes into a shared code repository) in support of code quality and reporting initiatives. “I just raised my hand and I was like, I’ll take this piece and figure it out,” she says.
She’s also taking advantage of the book clubs and professional development budget that Guru grants to each employee for use on everything from conferences to coaching to courses to mentorship programs. Those training programs are especially useful to Lisa because of her non-traditional background, she says. “I’ve studied data structures and algorithms and discrete mathematics, to deepen my understanding, because they are foundational to Computer Science,” says Lisa.
3. Protect your deep work and focus time. Lisa loves that Guru’s status as a tech company focused on optimizing knowledge trickles down to how workflows and schedules are set up, too, noting that most team members in the tech org have a three-hour block in either the morning or afternoon for focused time. “You have the ability to immerse yourself in whatever you’re working on,” she says. Those blocks are actually when she does some of her best learning, says Lisa, because she has real-life examples to apply new concepts to: “If you encounter a new concept, don’t skip over it. Go right to the docs and read about it. It’s more likely to stick in that moment since it’s contextually relevant to what you’re working on,” she advises.
Lisa manages her growth with Guru’s engineering growth framework that includes multiple perspectives: a self-assessment, her manager’s assessment, peer reviews, biannual reviews, and biweekly 1:1s. The regularity helps keep her accountable, but it’s not why she keeps pushing to learn new things—that’s something more innate to who she is.
“I don’t lose the spark because I have a growth mindset,” she explains. “And with that mindset, I believe I can just keep going and learning and consequently, the spark just stays lit. “
Making learning a team sport
One of the things Lisa is working to learn right now is negotiation. “[Work] is constantly a negotiation,” she says. “Figuring out priorities, estimating how long tasks will take, and negotiating what will be included in the timeline and delivery.”
With her track record of learning what she sets out to get better at, we wouldn’t be surprised if Lisa negotiates her way into starting an improv group at Guru. “I think it could be a lot of fun when many of us are back in the Philadelphia office. I would be the natural person to get that conversation started,” she says.
And she’s got the perfect, tongue-in-cheek name for an improv team at a knowledge management platform: “Shoulder Tap.”
This content was originally published here.