Can you walk me through your development process, from a ticket or task to code on production?
How responsive are people to emails/Slack over the weekends and after 6pm?
How did your team come to use your current framework(s)?
Can you tell me about a time that the team has reorged?
What kind of diversity programs are there at the company?
Will I be working with anyone who is remote, or who works from home on a regular basis?
On a scale from 1 to it's-literally-the-worst, how much do you hate giving out your email address?
How often do you open up your inspector tool to bypass annoying shit on websites?
What will happen if you give me your email address?
Want more questions?
Get my full list of questions, and an update every week about engineering teams that are hiring.
Engineering-Driven
Customer Comes First
High Employee Retention
Committed to Personal Growth
Engages with Community
Open Source Contributor
Creative + Innovative
Uses Agile Methodologies
We build custom solutions for our clients. Thus, we need to understand their business and their pain points to build them a solution that will work for them. We work for a lot of smaller businesses or startups that are not yet widely known. Our bigger and more well-known clients are Bosch, Zurich, DA Direkt, SAP, and BASF.
How we communicate with our clients depends mostly on how the project is organised. If the client is part of our scrum team, engineers will communicate directly with the client. In more "traditionally managed" projects, communication is mostly channeled via PMs. When it comes to scrum, we do our meetings with the client in either our office or in theirs. Mostly, we try to rotate so that the client is regular visiting our offices as well. That seems to help to build trust in us when the client can "see" us work.
Since our marketing strategy is based on mouth to mouth propaganda, we make sure to deliver the best service to our clients.
Decentralized Internet and Developer Platform
New York, San Francisco, Hong Kong, & remote
Start-to-Finish Ownership
Customer Comes First
Engages with Community
Flexible Work Arrangements
Rapidly Growing Team
Committed to Personal Growth
Open Source Contributor
Impressive Team Members
We are an open-source project with over >7k community developers who contribute to our code. We have a Slack channel that has >4k members and we regularly interact with people in the channel. We actively seek feedback from the community, our customers, and view feedback as a necessary component in order to build a successful product.
15 Open Positions
Rapidly Growing Team
Cross-Department Collaboration
High Employee Retention
Committed to Personal Growth
Work/Life Balance
Eats Lunch Together
Safe Environment to Fail
Engages with Community
Yes, the company at large has high retention and no, we certainly can’t claim the same for our mobile team. After all, we’re a relatively new team and none of us have been here that long to begin with. That being said, we put a lot of attention in measuring engagement from our team members. We use Culture Amp to solicit honest feedback, capture the employee perspective, and use measurable results to identify areas of improvement and track our progress. We care a lot about making this a fantastic place to create, learn, and work and our numbers reflect it.
31 Open Positions
Customer Comes First
Data-Driven
High Quality Code Base
Work/Life Balance
High Employee Retention
Uses Agile Methodologies
Rapidly Growing Team
Continuous Delivery
Women sizes 14 and up are over 50% of the population of the US, yet on average they spend significantly less on fashion than their lower sized counterparts. The lack of product variety, poor/demeaning in-store experiences, and societal pressure all contribute to this. These are the problems we are solving for this customer every day at Dia. Every feature we build, every machine learning system we create, and every flow we optimize is aimed at improving the the customer experience. Engineers are fundamental to this process, and are expected to be looking at the data and thinking about the customer for each thing we build. We even style boxes for our customers as part of our onboarding!
Labor Automation Cloud Platform
New York, Toronto, and Lexington (just outside of Boston)
Work/Life Balance
Open Communication
Impressive Team Members
Safe Environment to Fail
Flexible Work Arrangements
Committed to Personal Growth
Uses Agile Methodologies
Team is Diverse
(By the way, our data team ensured that we sampled our key:values in randomized order so there would be no artificial clustering!)
Our engineers are organized into multiple agile teams. A product owner/manager handles the product research, defines and prioritizes feature stories, and communicates with customers, while the scrum team of engineers execute the lion’s share of the work. These teams are supported by the quality, design, data, and techops teams. To that end, each product owner ensures that efforts are aligned with business/customer values, with each sprint sized appropriately to that team based on its historical performance. Rarely do teams overcommit, enabling a us to run marathons over releases than burning out over sprints.
Work hours are relatively flexible with pre-agreed standup times and scrum meetings, dependent on the internal planning by the team. Working together remotely is standard fare as we’re empowered using modern collaboration software (JIRA, Zoom, Github, etc.). We have four offices (New York, Toronto, Long Island, Lexington) across two different countries (US and Canada) and a handful of entirely-remote contributors.
Flexible Work Arrangements
Data-Driven
Committed to Personal Growth
Continuous Feedback
Engages with Community
Flat Organization
We trust our employees and their judgment. While we expect you to be there for our daily scrums and weekly meetings, your work schedule is entirely up to you and your teammates. We try to keep things small. Our typical team consist of 4 developers and a product owner. We work at one project at a time.
You can work either from home or at our fully equipped office space in Gdynia. It’s all about preferences. Currently, one of our developers is working fully remotely. On the other hand, other team members prefer to be in the office every day.
1 Open Positions