Breaking into tech looks glamorous from the outside. Big logos. Big salaries. Big ideas. But when you’re actually standing at the edge—no network, no roadmap, no clear signal you belong—it can feel overwhelming fast.
I know, because I’ve lived it. Starting from scratch in a fast-moving, often exclusive industry forces you to answer tough questions early: Where do I fit? Who do I learn from? And how do I survive long enough to grow?
What I learned the hard way is this: talent matters, but support systems matter more. With the right communities, clear markers for growth, and a mindset built around learning—not perfection—you can build a career in tech that’s both successful and deeply fulfilling.
Find your communities early—and hold onto them
Everything changed for me at a hackathon while I was a student at Broward College. The event was organized by Code2040, and it flipped a switch I didn’t know existed. For the first time, I saw how technology could be used to solve problems facing underrepresented communities—and how my own background wasn’t a liability, but an asset.
More importantly, Code2040 connected me to people. Mentors. Peers. Builders who looked like me and spoke honestly about navigating tech spaces that weren’t designed with us in mind. That sense of belonging is powerful. It’s also fragile if you don’t protect it.
Later, I joined Hack.Diversity and NSBE, the National Society of Black Engineers. Being surrounded by Black and Brown technologists who shared the same hunger and grit created a level of camaraderie that’s hard to replicate elsewhere. You’re not just learning skills—you’re watching people one or two steps ahead of you win. That proximity makes success feel attainable.
These communities did more than prepare me technically. They equipped me to navigate the unspoken realities of being Black in tech: microaggressions, imposter syndrome, the pressure to overperform in rooms where you’re often the only one. That preparation mattered when I landed at Snap Inc.—first as an intern, then full time.
Once inside, I didn’t just ship code. I helped lead initiatives aimed at making products more inclusive for underrepresented users. Ironically—or maybe predictably—those efforts made the product better for everyone.
Set career plans with “buoys,” not fantasies
Tech careers rarely move in straight lines. That’s why you need what I call buoys—visible markers that help you stay oriented when things get messy. Buoys can be people, roles, or milestones that show you what’s possible.
Some of the most impactful buoys in my journey weren’t executives or celebrities. They were peers just a year or two ahead of me. Their advice was practical. Their wins felt reachable. Their mistakes felt familiar.
Then there were the more distant buoys—the ones further out in the water. Tammarrian Rogers, director of engineering at Snap Inc., was one of those for me. She embodied the leadership and technical excellence I aspired to reach, and her guidance helped me think long-term instead of job-to-job.
Here’s the key: don’t admire your buoys quietly. Reach out.
As an intern at Snap, I DM’d Evan Spiegel—yes, the CEO—on HipChat, back before Slack took over. I wanted feedback on an app idea I was building. He set up time. That conversation shaped how I approached future projects, including Inclusive Camera, which I later pitched directly to him.
Age doesn’t limit impact. Access does. And access often starts with asking.
Examples of career “buoys” to identify early
| Type of Buoy | What It Represents | Why It Matters |
|---|---|---|
| Peer Buoy | Someone 1–2 years ahead | Makes success feel achievable |
| Mentor Buoy | Experienced leader | Provides long-term perspective |
| Skill Buoy | A core technical skill | Anchors career direction |
| Role Buoy | A specific job title | Clarifies next steps |
Treasure your time to learn—before the stakes rise
Early career is the cheapest time you’ll ever have to make mistakes. Use it.
I wish I had spent more time early on exploring machine learning and product design. Those skills became essential later, but learning them under pressure is a different game. Once expectations rise, learning becomes more targeted, more rushed, and more strategic.
If you’re just starting out, go beyond your assigned tasks. Learn languages you don’t “need” yet. Attend meetups. Read design docs. Break things in side projects. This kind of exploration builds intuition, and intuition compounds.
According to workforce data from the U.S. Department of Labor (https://www.dol.gov), early-career skill accumulation has a measurable impact on long-term earnings and mobility. That’s not motivational talk—it’s structural reality.
Learn to fail fast—but do it with intention
At Snap, speed wasn’t optional. Ideas moved fast. Experiments failed faster. The difference between people who stalled and people who grew was how they handled failure.
Failing fast isn’t about being careless. It’s about recognizing what’s not working and adjusting before sunk costs pile up. Bad code. Weak pitches. Features users ignore. These aren’t career-enders unless you ignore the lesson.
The real skill is extraction: What went wrong? Why? What changes next time?
In tech, resources are finite—time, budget, attention. Companies expect you to grow quickly. Learning how to pivot thoughtfully, without ego, is one of the most valuable skills you can develop as an engineer or product leader.
Be unmovable about your values when job searching
When I was choosing between full-time offers after graduating, I felt stuck. Both options looked good on paper. So I called Tammarrian.
She asked one question: “What are your values?”
That forced clarity. I wrote them down—impactful work, a real commitment to diversity and inclusion, and visible growth paths. When I measured both companies against those values, the answer was obvious. Snap aligned. The other didn’t.
Values aren’t soft. They’re strategic. Research from the U.S. Equal Employment Opportunity Commission (https://www.eeoc.gov) consistently shows that inclusive workplaces retain talent longer and perform better. Choosing alignment early protects you from burnout later.
Set boundaries. Decide what you won’t tolerate. Early compromises have long shadows.
The throughline that matters
Community will carry you when confidence dips. Buoys will guide you when direction blurs. Learning will compound when titles don’t. And failure—handled well—will accelerate everything.
Tech doesn’t need you to be perfect. It needs you to be intentional.
Stay curious. Stay anchored. And remember: your background isn’t something to overcome. It’s part of what makes your work matter.
FAQs
1. What are the biggest challenges when breaking into the tech industry?
Many newcomers struggle with lack of access, limited professional networks, unclear career paths, and the pressure to prove themselves in environments where they may feel underrepresented.
2. Why are communities like Hack.Diversity, Code2040, and NSBE important for early-career talent?
These communities provide mentorship, technical preparation, emotional support, and representation—helping early-career professionals navigate both the technical and cultural realities of working in tech.
3. How can mentorship accelerate a tech career?
Mentorship offers guidance, perspective, and access to networks. Mentors help mentees avoid common pitfalls, build confidence, and make informed decisions at critical career moments.
4. What does it mean to “fail fast” in tech?
Failing fast means quickly identifying what isn’t working, learning from mistakes, and adjusting course without fear or ego—allowing for faster growth and better outcomes.
5. Why are personal values important when choosing a tech job?
Your values shape your long-term satisfaction and growth. Choosing companies that align with your beliefs around impact, inclusion, and development helps prevent burnout and supports sustained success.
