Make software eng job desc more opinionated and add time leverage in …

…our values (airbytehq#1987)

docs/career-and-open-positions/senior-software-engineer.md

@@ -1,48 +1,63 @@
 # Senior Software Engineer
 
-## **About Airbyte**
+Join [Airbyte's](https://airbyte.io/) small, but growing, engineering team. We are backed by the world's [top investors](https://docs.airbyte.io/career-and-open-positions#our-investors). 
 
-[Airbyte](https://airbyte.io/) is the upcoming [open-source](https://github.com/airbytehq/airbyte) standard for EL\(T\). We enable data teams to replicate data from applications, APIs, and databases to data warehouses, lakes, and other destinations. We believe open-source is the only approach that can solve the problem of data integration. It allows us to cover the long tail of integrations while enabling teams to adapt pre-built connectors to their needs.
+You will spend your time solving one of the most complex and unsolved problem with data: Access. We're on a mission to allow anyone to access data, wherever it is, and make it available into the system of their choice.
 
-Airbyte is remote friendly, with most of the team based in the Bay Area. We’re fully open as a company. Our [company handbook](https://docs.airbyte.io/company-handbook), [culture & values](https://docs.airbyte.io/company-handbook/culture-and-values), [strategy](https://docs.airbyte.io/company-handbook/strategy) and [roadmap](https://docs.airbyte.io/roadmap) are open to all.
+We are passionate about data, open source, our community and scale! 
 
-We're a seed-stage company backed by some of the world's [top investors](https://docs.airbyte.io/career-and-open-positions#our-investors) and believe in product-led growth, where we build something awesome and let our product bring the users, rather than an outbound sales engine with cold calls.
+We love Java, Python, Node, K8s, Docker... but in the end, it doesn't matter: we just want to build the best product.
 
-## **Responsibilities**
 
-We are looking for an engineer who is passionate about data, open source and scale. You will be working with other engineers to design and build the future standard of data integration.
+## **About you**
 
-As an early member of our engineering team, you will play a significant role in shaping the future of Airbyte: product, team culture, process, and everything in between. You’ll take ownership of mission-critical work across all levels of the stack: building and scaling our core platform including execution, configuration, scheduling, integration with data ecosystem \(DBT, Airflow, Spark, K8s...\), monitoring, APIs, deployment, build system and more. You will also scale our connector infrastructure to provide an amazing Developer Experience \(DX\) to our contributors and new members of the team.
-
-Today, our stack is composed of several technologies: Java, Python, Docker, Typescript/React, K8s...
-
-As part of a high-growth startup, you will also have the opportunity to collaborate closely with company leaders, users, partners, and non-engineering parts of the business. Every Airbyte engineer plays a critical role in shaping the future of our product, team, and culture.
-
-If you love taking the lead on ambitious projects, having lots of latitude, and working in a high velocity team, this may be just the role for you.
+* Have attention to detail and bias for action.
+* Are a prolific communicator, and thrive in uncertainty.
+* Are passionate about data, big data, open source and... DATA.
+* Want to help & support users solve their problems.
+* Are looking to work in a fast-paced environment, solving fundamental industry problem.
+* Are comfortable working remotely.
 
 ## **Requirements**
 
-* 3+ years of experience
-* Self-directed and work with minimal supervision
-* Proficiency in at least one programming language: we don’t mind which one
-* Passion for data and solving a fundamental industry problem
-* Excited about working on Open Source and in the open
+* 3+ years of backend engineering work experience.
+* Self-directed and work with minimal supervision.
+* Proficiency writing production-quality code, preferably in Java, Kotlin or Python.
+* Familiarity with scalability.
+* Excellent communication skills.
 * You share [our values](https://docs.airbyte.io/company-handbook/culture-and-values)
 
+## **Great-to-haves**
+
+* Experience with AWS / GCP / Azure.
+* Experience working with huge data sets.
+* Experience with open source development.
+
 ## **Location**
 
 Wherever you want!
 
-## **We provide**
+## **Perks!!!**
 
+* Work with great people
 * Unlimited PTO
 * Remote friendly
 * Equipment stipend
-* For countries where it applies: Health Insurance, Retirement \(401k, etc\)
+* Weekly team events
+* For countries where it applies: 
+  * Health Insurance 
+  * Retirement \(401k, etc\)
+
+## **This is how we think**
+We are an open company, we are opinionated and public about how we think!
+* Our [company handbook](https://docs.airbyte.io/company-handbook),
+* Our [culture & values](https://docs.airbyte.io/company-handbook/culture-and-values),
+* Our [strategy](https://docs.airbyte.io/company-handbook/strategy),
+* Our [roadmap](https://docs.airbyte.io/roadmap),
+* The [future of data integration](https://airbyte.io/articles/data-engineering-thoughts/why-the-future-of-etl-is-not-elt-but-el/)
 
 ## **Applying**
 
 Email us at [[email protected]](mailto:[email protected]) with a link to your LinkedIn / Resume / GitHub \(optional\).
 
-You don't need to include a cover letter, but just a paragraph about how you found us and what makes you a great person to join our founding team!
-
+Don't send a cover letter, your resume will speak for you!

docs/company-handbook/culture-and-values.md

@@ -1,5 +1,7 @@
 # Culture and Values
 
+Culture & values are not a pretty words on a wall. They are the dimensions by which we hire, we promote, and we demote.   
+
 We hope the handbook will help you better understand how it feels to work with us as a colleague, a client, a partner or a member of our open source community.
 
 We also believe that a company culture needs to be opinionated to be effective and attract the right people. It cannot be right for every person, or it would mean we don’t have a culture. And that’s perfectly fine. We will continue to iterate and refine our values along the way.
@@ -11,21 +13,26 @@ Here are the values we deeply believe in:
 We’re huge believers in “Diversity in counsel, unity in action.” Several heads are always better than one head to solve any problem. The more diverse the views, the more enlightened the decision will be. This entails several things:
 
 * For any collaboration to be fruitful, we need **full transparency**. Any missing information is a risk. 
-* **Any opinion or concern needs to be shared**. Saying “I knew it would turn out like this…” is not acceptable if you didn’t share your view beforehand. 
+* **Any opinion or concern needs to be shared**. Saying “I knew it would turn out like this…” is not acceptable if you didn't share your view beforehand. 
 * We always share our challenges: **bad news must travel faster than good news.**
 
-However, “unity in action” means for us that **we don’t believe in consensus**, and that even if you don’t believe in the decision that was made, you still need to commit to the decision, so you give it a chance to succeed. We think about consensus as diluted solutions.
+However, “unity in action” means for us that **we don’t believe in consensus**, and that even if you don’t believe in the decision that was made, you must commit to it and give it a chance to succeed. Consensus results in diluted solutions.
 
 ## **Humility and Maximizing Growth**
 
 Candid collaboration can’t work without humility. Humility means that you’re open minded towards others’ opinions, and let others speak their minds, whatever their role.
 
-Leaving ego at the door means you should not defend a point just to win an argument. We are a team **in search of truth, not in search of winning points**.
+Leaving ego at the door means you don't defend a point just to win an argument. We are a team **in search of truth, not in search of winning points**.
 
 We prioritize **progress over perfection**. We are thankful towards errors of action, provided we learn and get better.
 
 We should **never pull rank**. If you have to remind someone of your position, you're doing something wrong. Explain the reasons for your decision, and respect everyone irrespective of their function.
 
+We **leverage our time**, and we enable others to leverage their time:
+- We stay away from low impact tasks. If they exist, we question their existence, and we kill them, we automate them or we externalize them. 
+- We are never a blocker. We respond to ALL communications (internal or external) within 12h.
+- We stay critical about past decisions and existing processes ("Is this meeting really useful?") .
+
 ## **Being Intentional and Owning the Outcome**
 
 We always want to stay mindful about the projects we are working on, and why we are working on them. We need to understand the value we expect to bring, the audience we want to address, and the metrics we want to impact.
@@ -45,4 +52,3 @@ All of this can only work if you can feel comfortable being vulnerable with your
 **Address behavior, not people.** For constructive feedback to work, it should not be tied to the individual.
 
 **Don't let others fail, if you can help.** We succeed together. We keep an eye out for others who may be struggling or stuck, and see how we can provide assistance when needed.
-