By Matt AguiluzRevelry Alumni Signal flow is something I find endlessly fascinating. The process of receiving input, processing it, and returning output is relatively…
Software engineer content on the Revelry Blog: Navigate our lab notes by using the tag system.
So what was your path to Revelry? I have always had a deep understanding and positive relationship with technology. I started my journey back…
This is a complete guide to preparing for and landing a software engineer apprenticeship—that leads to a full-time job! If you want to pursue…
A doctor-turned-software engineer, Bob Weilbacher joined Revelry just a few months ago after a 20-year-long career in medicine.
Technical interviews are broken. We do case interviews in order to take candidates from hearing the scenario, to asking clarifying questions, to giving broad opinions and concepts, to specific architecture and programming tasks.
The hard part of this was recognizing the algebra beneath layers of domain-specific business rules.
Working in a team requires the members to all contribute their own set of knowledge to accomplish a goal. It’s unlikely that a team would be composed of members that share the same knowledge base. Stop worrying and love the bomb.
At its core, pairing is another useful strategy to work with your peers and get shit done. The best way to know what works for you is to take more opportunities to pair with others, think about what works and what doesn’t work, and continue to refine this skill set.
Instead of living in fear that you’re the one asking bad questions, consider that your questions will probably lead your team to deliver better outcomes.
Jason says, “Revelry has always been on my radar as a company that works for the community and hires amazing people.”