Prospective Teammate Site
Dear Prospective Teammate,
We're excited to begin the process of working with you to figure out whether you'd like to join the Chain.io team and if we're a great fit for you. Everyone's time is incredibly valuable so we've put together this site to help explain a bit about our company, culture, and hiring process. This way, we can spend our face to face time really getting to know each other instead of getting bogged down in administrative details.
One of the things that we really value is learning, and this process is definitely part of that. If you have any feedback during or after the process, we're excited to hear about it.
Our hiring process consists of several interviews which each have a specific focus. Depending on the role, we may do all, or just a subset of these interviews. Since, we value your time and understand how inconvenient the interviewing process can be, we normally try to do all interviews via a phone call and one visit to our office.
We do a few different kinds of interviews, and depending on the role, we may squeeze some of these together or add a little more.
- Initial Screen - A conversation to help understand your goals, make sure you understand the job, and determine if there's a good fit. This is a great time to ask questions about anything in this site.
- Culture and Product - A conversation to explain a little bit about our culture and the product we sell. We'll also ask questions about how you like to work and how you interact with other people inside and outside of the company. This is a good time for questions about "what we do" and "how we do it".
- Technical - A conversation to discuss the specifics of the job itself and your qualifications. For developers, this will be the initial conversation about things like programming languages and frameworks. For a sales role, this would be where we talk about your approach to winning new business. For accounting, words like General Ledger might be used, and so on.
- Teammate / Hiring Manager Time - Time with the hiring manager and any other teammates who might be involved in the hiring process to have a more wide ranging conversation about the job, your background, and anything else that might come up. This is a more free-form conversation where we work together to figure out if Chain.io is right for you and vice versa.
Interviews: What to Expect
Interviewing is naturally stressful. At Chain.io, we try to minimize unneeded stress so people can make good decisions. From our perspective, the goal of the interviews is to help understand who you are and how you might work with the team, not to grill you and make you uncomfortable. Here are a few things that should help you prepare.
- We're Casual: There's a 99.999% chance that someone you interview with will be in jeans. There's a 92.81% chance that someone will be in a t-shirt. (There's an 87.58% chance that those stats are made up, but you get the idea.) You don't need to wear business attire. Wear whatever makes you comfortable. If dressing up gives you extra confidence, go for it. If dressing down makes you more relaxed, that's cool too. We have so many important things to worry about, so we promise we won't spend time discussing your outfit.
- We're Nice: The first principle in our corporate culture is "Nice" and we mean it. Nobody is going to grill you. We believe that the best hiring process is a collaboration between you and our team so we can all understand whether everyone would benefit from working together. We wouldn't jeopardize that partnership by being rude or aggressive. It's just not in our DNA.
- We Will Ask You Solve Problems (but we won't ask you to write code): We are interested to learn about the approach you take to solving problems, so we will probably ask you to explain the approach that you'd take to a hypothetical problem. Depending on the role, that problem may be a customer service issue, a bit of technical architecture, or a sales role-play. For development roles, this might involve drawing a flowchart or diagram, but it will not involve writing code on a whiteboard (or our cool Jamboard). We're much more interested in hearing how you'd attack a problem than in the specifics of the technical details.
- We Hope You'll Ask Questions: We find the best interviews are two way conversations, and we don't have a script to walk through. If you have questions or want to understand more about something, please ask.
Coordinating The Details
During the hiring process, we'll assign a lead who will be your main point of contact. If you have questions, scheduling conflicts, get lost, or have any other issues, you can work directly with this person. They are there to help you. If you are working with a recruiter, then we may funnel some of that communication through the recruiter.
We generally aim for the hiring process to take around 2 weeks from initial contact to final decision. This may vary depending on circumstances. We generally plan for about a week to get the interviews done and another week of follow up and decision making. Depending on the complexity of the role, this may stretch out over a longer period.
We believe in continuous improvement, and our hiring process is no exception. After we've completed the process, we may ask you for some candid feedback on how we did. We really appreciate your feedback, but we also understand if you're not comfortable sharing. We will ask for this feedback after process is done, so you know it won't impact our decision in any way.
Our culture is based on three principles:
We are nice people who enjoy our work. When we interact with other people, we have a pleasant demeanor and treat them with respect. We understand that people may disagree, and we work to resolve those disagreements based on facts and reason. We do not see business as a winner take all proposition. We actively seek out opportunities to find win-win solutions for our clients, partners, and other companies in our ecosystem.
We aim to make our products accessible to our clients with a minimum level of effort. Where we have a choice between a big word and a small one, we use the small one. If we can spend extra time reducing a process from two steps to one, we will. If a one-page contract will suffice, we will deliver it. Our products and services solve real problems for our clients, and they shine on their own. We do not need to use jargon and complexity to make them seem more impressive.
Our clients hire us to deliver high-quality products and services. We accomplish this by working in a professional and workmanlike manner. We are good stewards of our clients' and our internal resources including time and money; however, we do not take shortcuts that might sacrifice quality. We rely on documented, repeatable processes to help us deliver consistent outcomes for our clients.
We express this principle to our clients through our actions. We do what we say we are going to do. We present solutions that are well formed and thoughtfully executed. We do the unseen work that precipitates high-quality solutions like unit testing, code reviews, project management, and security audits.
Work Day / Work Hours
We don't have a set workday; however, a lot of the work we do involves team collaboration. To help coordinate this, we ask that you be available from 10-4 Eastern time on weekdays and that you also try to keep meetings inside this window.
We ask that everyone target a 35-40 hour work week. Everyone can track their own time, and you don't need to report the specific hours that you work, only your days off. If you find yourself working more than 40 hours on a consistent basis, we will have a conversation to figure out how to better balance your workload.
Time to recharge is critical. None of us work well when we're burnt out. When you take time, we expect you to really take it. No email, no calls, no stress.
We have a hard floor, soft ceiling approach to time off. Everyone is required to take at least 10 non-holiday work days off per year; no exceptions. That's the hard floor. We ask that everyone try to keep their total days off at or under 20 days. If you have a special opportunity that's going to put you a little over, go ahead. If you have a special opportunity that is going to put you more than 10 days over, please have a conversation with Brian first.
Whenever possible, try to give everyone at least 2 weeks notice if you're going to take more than one consecutive day off. This will help us plan our collaborative better.
- Why the hard floor? Rest and recuperation are important. We're in this for the long haul, and burnout is not in anyone's best interest.
- Why the soft ceiling? We have a lot to do, and to accomplish our goals, we need people to do the work.
What We Do
At Chain.io we enjoy using technology and process
to make supply chain integrations faster, more reliable, and easier to manage.
☝That's a complicated sentence, so let's break it down...
First and foremost, we aim to have a pleasant and supportive culture here at Chain.io. This is captured in our brand guidelines of "Nice, Accessible, and Professional". In a fast paced environment, its easy to forget that everyone we work with (co-workers, partners, and clients) are all human beings. When we remember that everyone is generally trying to do the best they can, it's easier to practice empathy. When we are empathetic and considerate, then business results will follow.
Supply Chain Integration
For our purposes, a "Supply Chain Integration" is any point where teams repeatedly exchange information to further a supply chain related process.
The teams we're talking about are often separate companies (like a Shipper and Carrier), but they may be internal parties (like a Distribution Center and Accounting Department).
The teams exchange information repeatedly. We're not interested in solving one time communications. We're looking for data that is exchanged either on a regular schedule (hourly, daily, monthly, etc) or as part of every transaction (like a Shipment Status Notification, or Purchase Order).
Note carefully that the definition does not include any preference for technology. In the current state, teams may be communicating by email, spreadsheet, phone, EDI, XML, APIs, paper documents through the mail, or something we've never heard of.
Technology & Process
We are a technology company. We believe that applying advanced technology solutions to the mechanisms that supply chain partners use to communicate with each other is critical to continued global economic growth. We actively develop technology solutions to practical business problems related to supply chain integrations. For example, the Chain.io Platform provides a centralized hub for companies to communicate and share heterogeneous information in a consistent way.
In business, technology itself is rarely the solution to any problem. Without a consistent and effective set of processes to implement, maintain, and enhance, the technology will never reach its full potential. To that end, we aim to apply consistent, measured business processes both internally and with our partners and clients.
Internal processes include things like:
- Employee on-boarding
- OKR planning
- Code release & deployment
External processes include things like:
- Client integration project management
- EDI support & incident management
- Sales to implementation hand off
Faster, More Reliable, and Easier To Manage
We aim to reduce the friction for our clients when they want to bring on new trading partners. A client should never turn down a good business opportunity because it's too hard to exchange information. We do this by applying the technology inherent to the Chain.io Platform and by supporting our clients with professional services based on measured, repeatable project management processes.
We also aim to have a high performing system. We should be able to scale to millions of transactions while measuring and maintaining the performance of the system within our established SLA targets.
When a customer chooses Chain.io, she should be confident that both our technology and processes will deliver results that match our promises. Our professional services team should deliver projects faster than if the client had attempted the project without us. We should execute our processes consistently and repeatably and be able to report on the results. Our technology should be available and running and acceptable speeds 24x365. Transactions submitted should behave in the way that is explained in our documentation, and there should not be unpredictable side effects. We must not lose or corrupt our clients' data.
Easier To Manage
Bringing on new clients and executing their projects is only half of the battle. Our aim is to be a part of our clients' supply chain on an ongoing basis. During normal operations, our clients and internal teams should have the consistent and simple visibility to the status of their long running transactions and the health of our environment. When something is not right (regardless of fault), we should be able to quickly guide our clients to a resolution. Our technology should provide visibility to the problem and be an active partner with our people and our clients' teams in resolving the issues.
Some Final Words
We know that deciding to join a new company is a huge decision. We hope this information will help us get started on the right foot. We value your thoughts and contributions throughout this process, and we hope this page helped you understand a bit more about us and what we do. We'll see you at the interview!