Welcome to the Snyder Tech Field Guide—our living handbook for how we work together. This guide is crowd-sourced by our team and evolves as we learn and grow. Think of it as the collected wisdom of everyone who's been here before you.
At first glance, we might seem organized. Look closer, and you'll discover a healthy amount of chaos. But there's purpose in all of it. We've found that embracing change—rather than resisting it—leads to better outcomes.
Your First Day
Starting a new job can be overwhelming. Here's what to expect and how to hit the ground running.
Getting Set Up
- You'll receive access to our core systems within your first hour
- Your manager will schedule a welcome call to walk through priorities
- Take time to explore our internal documentation—there's a lot of it
- Don't worry about knowing everything immediately; we expect a learning curve
Your First Week
- Meet with your team members—async introductions are fine
- Complete required training modules at your own pace
- Start small: pick up a minor task to get familiar with our workflow
- Ask questions freely—there are no dumb questions here
How We Work
We're a distributed team across multiple time zones. This shapes everything about how we communicate and collaborate.
Async by Default
Most communication happens asynchronously. We write things down, share context generously, and don't expect immediate responses. This respects everyone's time and focus.
Documentation Over Meetings
Before scheduling a meeting, ask: "Could this be a document?" Written communication creates a record, includes more people, and can be referenced later.
Overlap Hours
We maintain a few hours of overlap between regions for real-time collaboration. Sync meetings, when needed, happen during these windows.
Trust & Autonomy
We hire capable people and give them room to work. You don't need to ask permission for most things—just keep your team informed.
Our Structure
We're intentionally flat. Titles exist for external clarity, but internally, what matters is what you do—not what you're called.
There's no rigid hierarchy. Teams form around projects. People take on leadership roles as needed, then step back when the work is done. Your influence comes from your contributions, not your position.
Teams
Small, cross-functional groups that own specific areas. Teams have autonomy to make decisions about their domain.
Leads
People who coordinate work and help remove blockers. They're guides, not gatekeepers. Leading is a responsibility, not a rank.
Guilds
Communities of practice around specific skills (e.g., frontend, DevOps). Guilds share knowledge and maintain standards across teams.
Communication Tools
We use several tools, each with a specific purpose. Use the right tool for the message.
Slack
Quick questions, casual conversation, real-time coordination. Ephemeral by design—important decisions should be documented elsewhere.
Documentation
Decisions, processes, and anything that needs to last. If it's important, write it down where others can find it.
External communication and formal notices. Rarely used internally—we prefer more immediate channels.
Video Calls
Complex discussions, relationship building, and when async isn't working. Use sparingly and record for those who can't attend.
The Snyder Creed
These are the principles we try to live by:
We are always learning. The technology landscape evolves constantly, and so do we. Yesterday's best practice is tomorrow's technical debt. Stay curious.
We build sustainably. Quick wins that create long-term problems aren't wins. We choose solutions we'll be proud of a year from now.
We communicate openly. Information hoarding creates silos. Share context, document decisions, and default to transparency.
We own our work. Shipping is just the beginning. We support what we build and fix what we break.
This is a marathon, not a sprint. We're building for the long term—our careers, our company, and our impact. Pace yourself.
Getting Help
Stuck? That's normal. Here's how to get unstuck:
Search First
Chances are someone's asked before. Check our docs, Slack history, and existing issues.
Ask in Public
Post questions in team channels, not DMs. Others might have the same question or useful context.
Reach Out
If you're still stuck after 30 minutes, ask someone directly. We'd rather help than have you spin.
Welcome Aboard
This guide will never be complete—and that's by design. As you learn things that should be here, add them. As things change, update them. This is your guide now too.
We're glad you're here.