Relative to the local job market, we are ethnically and geographically diverse. There is always room for improvement. With various programs, internships, and hiring initiatives, I think we will continue to reach our D&I goals.
There are always new challenges to work on and tech debt to fix. We have been around for a while, but the company is relatively small. This means there are unique challenges you wouldn't usually be exposed to due to constraints that exist in larger organizations.
The culture is humble and drives us to make the best product possible for our community. An example of this is our engineering on-call process. When there is a page, 90+% of the time, other department team members will jump in if they are familiar with the problem. You rarely feel alone when you are on-call. If you do, ask and, someone will jump in to help!
We are fully remote, with options for localized in-person meetups. I do not participate in localized meetups, but the opportunity is there for the more extroverted individual. Before, I have never experienced a company with humility and cooperation while being 100% remote. I find that positively unique.
The employees who are here clearly have a sense of ownership of the product. They care to reduce tech debt. They care to research to make the following product better than the last. They care to defend what they think is right. It is part of our value for Bias for Considered Action, which propels us to do the right thing for our community.
Sometimes it feels like there is a lack of focus on what the product is (or what part is most important). There will always be a feeling of this while we continue the "innovation flywheel," but it could be better managed from a people perspective. In addition,
As many employees of fully remote jobs find, you need to find your groove in terms of getting work done and responding to external requests. When Slack is your main form of communication, it is easy for anyone to attempt to get your attention at any time of the day. I think this could even be noted as a positive in that you will be forced to grow in your interpersonal skills in addition to your technical skills being expanded.
There is a lot to do, so you must prioritize your time accordingly. Again, not so much a negative, but if you want a job where you clock in and out without any sense of ownership or passion, this is not the place for you. We passionately want the best for our community and our teammates. Doing it right sometimes means taking the long road instead of the shortcut.
Focus. Discontinue the products that are not helpful to the company financially or are hurting (confusing) the community. Be willing to make a few people unhappy to move the company and the community forward.
"Die for oneself." "Oneself" is the community, and by "dying," I mean that we should be giving everything or sacrificing. Docker, Inc. should invest more into the community. We have support, hub-feedback, the public roadmap, Docker Forums, etc. Those need to be bustling places where the community feels like they are talking with employees at Docker, not only other community members or to a wall. I believe we are working on this in the higher management levels, and some individuals engage with the community more.
With that said, it is still essential to mark community engagement as a critical objective of success at Docker, Inc.
Had an email discussion with a recruiter, and scheduled a phone screen. They called me after the agreed time, and after a short call discussing my experience, they suggested they wanted to move me forward to the next step of the process. I never he
I applied via website. They came back to me after around two weeks with time slots to arrange an interview to discuss the role. Then during the 30 mins instead of the role discussion it was a technical screening with recruiter and online coding wit
First a recruiter screen, then two technical interviews including a coding challenge, then a cultural/behavioral interview. Then another call with the recruiter to re-align and to get me updated on the process.
Had an email discussion with a recruiter, and scheduled a phone screen. They called me after the agreed time, and after a short call discussing my experience, they suggested they wanted to move me forward to the next step of the process. I never he
I applied via website. They came back to me after around two weeks with time slots to arrange an interview to discuss the role. Then during the 30 mins instead of the role discussion it was a technical screening with recruiter and online coding wit
First a recruiter screen, then two technical interviews including a coding challenge, then a cultural/behavioral interview. Then another call with the recruiter to re-align and to get me updated on the process.