The software development team at Gynger approaches everything with intention — and that includes team members’ time.
Will Hogben, director of software engineering, gave the example of keeping set meeting schedules for software engineers.
“Not much alters the meeting schedule we have set,” Hogben said. “Even if we are having issues, those meetings still occur.”
The idea is not to make the team more rigid, but to protect everyone’s time.
“If you are on call, it is possible some issue could come up that could take time away from your regular development work,” Hogben said. “If anything becomes large, we adjust the sprint by moving some tickets to other people or to the next sprint.”
Noteworthy Perks at Gynger
- Continuing education available during work hours
- Paid industry certifications
- Unlimited vacation policy
- Company equity
- Performance bonus
- Pay transparency
- Mean gender pay gap below 10 percent
Respecting the time and hard work that team members put into each product milestone is part of the team culture. Built In saw this when interviewing Varun Sridhar, a product lead, in 2023.
“We are one team marching towards the same goal,” Sridhar noted. At the time, the team was still scaling the young startup and was intentional in making sustainable hiring decisions and designing the product in consistent proof-of-concept steps.
Now, Gynger is expanding its CFO-focused product suite and bringing on product and engineering team members with the same intention and care as when the company started.
To give applicants a preview of what a day-to-day as an engineer at Gynger might look like, Built In asked Hogben to share a walkthrough of his daily schedule.
Gynger is the first B2B payments and embedded financing solution for buyers and sellers of technology.
7:00 a.m.
Most days I wake up around 7 a.m. This allows me to be up in time for 7:30 a.m. meetings, which is the best time to meet with the New York team and the Israel team without waking the West Coast team up too early. I make coffee and a protein shake and walk the dog. Then I check Slack for any overnight errors or emergency issues that might need attention. If it’s Monday or Thursday, I sync with the team. If we are not doing a sync, I settle into whatever tickets I’m currently working on.
7:30 a.m.
Most meetings for me on the West Coast start at 7:30 a.m. This includes our two weekly team syncs, our design meetings, which happen every other Wednesday, and our retro, which is every other Tuesday. After those meetings, I might have one-on-one meetings with members on my team or something similar.
9:00 a.m.
I review any new PRs, check Slack for any new issues or emergency items and then usually begin development around 9 a.m. Then for the most part of the day, I am free to develop on my own unless someone needs help or I need to sync with someone about a ticket.
Most of my midday work is spent in heads-down development after about 9 a.m.
Noon
I usually take a 30-minute to one-hour lunch around noon, then back to development.
1:00 p.m.
Most days I sign off around 3 p.m., which is when most of the East Coast team is also done working. Before I leave, I check Slack and make sure nothing else pressing has come up, review any new PRs and then usually go do some sort of exercise.
3:00 p.m.
Sign off.
