Beyond the Bootcamp: Simone Hill, Vogue
Before Flatiron School, Simone Hill worked as an assistant editor at The Knot, “writing about all things weddings,” as she says.
Reading Time 7 mins
In our Beyond the Bootcamp series, we chat with members of our alumni community about their post-Flatiron career journeys. What new roles have they taken on? How did they get to where they are now? What advice do they have for new programmers following in their footsteps?
Before Flatiron School, Simone Hill worked as an assistant editor at The Knot, “writing about all things weddings,” as she says. She’s now leveraging her creative instincts in another way: as a front-end engineer at Vogue.
Learning to Code
While working as assistant editor at The Knot, Simone realized what she really loved about her job was the tech product and the platform – a tool that brides and couples could use to plan their weddings. But, according to Simone, “I didn’t know anything about how it was created or what would go into building something like that. So I had no technical background, but I really wanted to immerse myself in that and learn to build those things so I could have a skill that I could use to create tools, platforms, and apps like that myself.”
More than learning the technical content, Simone says the challenge was overcoming the scary feeling of diving into something completely different. That said, she quickly began to see parallels between writing and coding: “You have to construct an argument when you write any piece of content and really think through the flow of how a reader consumes it. You have to put yourself in that position a lot of times when you’re thinking through building a feature as an engineer because you have to consider: what’s that first interaction point? How do you get from that first interaction point and create the experience that the user expects? Or sometimes you want to create something that they don’t expect!”
Takeaway #1 – Simone’s advice for others starting on their coding journeys: “I would say just stick with it. It’s really challenging, and that never goes away. Even when you graduate from Flatiron School, even when you get your first job, even once you get a promotion in that job, there’s always going to be this feeling of, ‘should I be here? I’ve somehow tricked everyone up to this point. I’m way, way in over my head.’” One of Simone’s techniques for overcoming those feelings of imposter syndrome was to learn to ask questions. “You really cannot get anywhere in any field, but especially as an engineer, if you don’t open yourself up to being willing to ask a question,” she says. “And that can be really tough because when you’re starting out as an engineer, you don’t know what everyone thinks you’re supposed to know. In fact, actual preparedness is knowing what you don’t know and knowing the questions to ask to keep learning.”
The Flatiron School Experience
What Simone was seeking in a coding bootcamp wasn’t so different from what she wanted out of her undergraduate education. “I really enjoy the liberal arts experience in broadening problem solving skills as opposed to teaching someone a very specific tool,” she says. “I think one of the big critiques of a lot of bootcamps is that when this technology changes in five years, you’ll be left behind.” That wasn’t the case for Simone at Flatiron School: “I learned problem solving skills that I still use as an engineer and built a great base through which to continue learning and teaching myself as well.”
For Simone, the best part of the experience was how students presented their projects to the technical community. “I hate public speaking to this day,” she says, “but it was a really great way to force me to articulate technical ideas in front of an audience, and I think that was a really big benefit to have, especially when you think about going into job interviews and things like that – it really prepares you for that kind of experience.”
Simone’s biggest revelation at Flatiron School was proving to herself that she could push through her self-doubt and tackle new things. “I always had this sense of myself that I’m not a technical person, I don’t come from a logical mindset – I studied anthropology, and I was a writer – that those things weren’t me,” she says. “But it wasn’t true. Anyone, including me, can push themselves to learn to code.”
Takeaway #2 – Simone’s advice for prospective coding bootcamp students is to “definitely apply. You don’t know unless you apply.” But she also recommends teaching as a way to cement your learning. “Even if you don’t really know something that well, find somebody who knows a little bit less than you do and try to teach it to them,” she says. “You can get a lot of that at Flatiron because you’re working so closely with your peers. There might be a concept that clicked for you really quickly. Or even if it doesn’t, find somebody and try to explain it to them. Even if they already know it, it can still be a benefit to you and to the other person.”
Life at Vogue
The biggest surprise Simone encountered after starting her career at Vogue: some of the bigger challenges actually come once you’ve already passed the initial hurdle of learning to code. “I think Avi, while I was at Flatiron,” she remembers, “he told us that quote: ‘Make it work, make it right, ten make it fast.’” Simone’s challenge now that she knows how to code is to keep learning, to absorb the wealth of information out there, find what’s actually important, and bring it into her everyday work – while balancing that with getting things done. “Making things work in the way that you know that they will work versus really researching and trying something new,” she explains.
Takeaway #3 – Simone’s top tip for bootcamp grads seeking a job is to take the initiative to keep on learning and building after graduation. “Try out a new technology or a new language that you haven’t had experience with. Employers are really impressed when they see that you’ve gone beyond just what you learned in bootcamp to apply your learnings to something new.” she says. “I think they really appreciate seeing that this isn’t just about getting a job for you. This is a dedication, this is a passion. This is something that you really want to do and stick with. Because being an engineer, it’s a grind sometimes. That’s your everyday, that’s your day to day, and they want to make sure that you love it and you’re passionate about it, and it’s really what you care about. They want to see that you’re not looking for a job – you’re looking for a career.”
What’s next for Simone?
Learning to code and being a software engineer was a very intentional step for Simone, and development isn’t exactly where she plans to end up. “Ultimately I want to transition into a product facing role, lead a product team at a startup, or product at any number of companies,” she explains. “I think what really hooked me into my desire to learn to code and my love of technology is working on a tool and thinking of features, creating this story of who the user is, and what they do, and how they interact with the site, and how we fulfill their need for them with a piece of technology. So my first step was to learn to code and be a software engineer because I really felt like I had the perspective from the creative side and the user side, but I didn't have the understanding of how I would actually embark on building something.”
Ready to start your own programming journey? The best way to get started is our free Bootcamp Prep course. Stay tuned for more installments of “Beyond the Bootcamp”!
Posted by Flatiron School / March 27, 2017
Learn to Code Python: Free Lesson for Beginners
What is the difference between a data analyst and a data scientist?
While data analyst and data scientist roles attract similar types of creative and logical people, their roles do have stark differences. Here’s our breakdown of the lines between these often mixed up roles.