We generally recommend that anyone who wants to apply for OpenQ reads all our articles on medium to understand our mentality. Start here and grab a coffee on a nice rainy Sunday. It will be exciting: https://medium.com/openqdev/introducing-openq-on-polygon-1b096f74e949

TL;DR OpenQ is a permissionless, GitHub-integrated, on-chain work platform tailored for software development feature bounties.

With OpenQ, ANYONE can mint and fund a bounty for ANY OPEN SOURCE ORGANIZATION from a GitHub Issue in seconds at https://app.openq.dev.

That means dApps underpinning DAOs, FOSS packages like Log4j, or any firm with an open source presence.

Contributors can then automagically claim their funds after a maintainer reviews and merges a pull request that completes the issue.

We’re a remote company that meets up IRL multiple times a year to hack/work together.
Our co-founders Andrew and Rick live in Austin, TX and Berlin, Germany. If you're in the area, you're sure to see them in a co-working space often.

It may seem funny that a Web 3 organization founded on alternative funding models for software development would be hiring fulltime developers.

It's like bootstrapping a compiler for a new programming language.

To bootstrap a compiler written in the language it's meant to compile, you must first write a compiler for the self-hosted compiler in another language 🤯.

What you will build with OpenQ is the bootstrap compiler for the future of work - starting with software development.

Eventually we intend to manage our entire payroll - from feature+bug bounties, streaming salaries to core developers, provision of invoices - on OpenQ itself. What you will be building is the accounting, governance and project management tools to make that possible, little by little.

At OpenQ we don't really distinguish between Senior, Mid-Level, Jedi, Level 6, Type 1A3B-Mid or whatever other categories exist to determine pay-levels at most tech companies and governments.

We don't eschew hierarchical engineering titles to be cool and alternative for it's own sake. It's just more efficient, and we all know these designations are often assigned arbitrarily and politicized to silence more junior voices, often to the detriment of the product.

Quality code can come from any person, with any number of years of experience, and even any skill level.

And what we put out at OpenQ is just that - quality code. Everything else but running code is words, and those are cheap.

If you want to say Senior Engineer or Chancellor Engineer, go for it! But have the GitHub history to back up the reputation 😉.

So with OpenQ's HR modus operandi elucidated, let's dig in to how you can put your code-God skills to good use building the future of online collaboration.

Note: All fulltime positions with OpenQ include generous salary, Employee Stock Ownership Plan, and a full benefits package.

Dear Hiring Managers,

If you are looking for:

– Golang, Python, NodeJS – React, Vue, Angular, React Native – PostgreSQL, Redis, MongoDB – GCP, AWS – Python, C++, Rust – ES6, SASS, or Webpack – Git and CI with TDD, BDD, DDD – Docker, Kubernetes

That’s not a full stack dev… That’s a whole engineering team #softwareengineering

• Some guy on LinkedIn that got a major ego boost the day he posted this

While we know that every dev's skills are multifaceted and that many features cross-cut across the stack, it's both unrealistic and inefficient to expect one person to truly have expertise across everything.

When something is everybody's responsibility, it is no ones responsibility. That is inefficient organizationally, and when the metaphorical shit hits the metaphorical fan, everyone starts pointing fingers.

That being said, we have regular skillshares (twice a week), encourage all our hires to shoot and write tutorials in which core devs share what they're working on with the rest of the team and community.

Anyone at any time is welcome to contribute their time to other parts of the stack! But you will OWN and be responsible for the quality of the part of the stack you will optimize in.

We are 100% transparent at all steps in the interview process.

Fill out this 5 minute form with your LinkedIn, GitHub, Twitter, etc. https://itzldldbwlt.typeform.com/to/m4ujIzU6

No pressure, we won't ask you to reverse a linked list or depth-first search a graph, so you can put away Cracking the Coding Interview.

This convo is to talk shop about your experience, your part of the stack, and to answer any questions you have about OpenQ and the team.

Because OpenQ is itself a contributor-to-core-dev pipeline of sorts, from bounty hunter to trusted inner circle, Step 3 involves completing a paid bounty in your area of expertise - blockchain, backend or frontend.

We've all had the take home coding challenge. This is different - you will actually be contributing the live OpenQ product.

OpenQ, like any developer friendly open source project, is optimized for rapid boot up and tear down. Your task will be to add some functionality.

This will require Docker and docker-compose just FYI :-)

In you as a person

• A curiosity-driven pragmatist who finds their answers in experimentation rather than speculation

• A humble soul who won't hesitate to DM questions to other team members and ask the community for help

For the Blockcahin + Smart Contract Engineer role in particular

• A smart dev passionate about Web 3 who understands why decentralization is valuable beyond the hype

• An empathetic engineer who realizes that the stack for most dApps extend well beyond just smart contracts, into supporting infrastructure like indexers, oracles, price feeds, decentralized hosting, traditional authentication, and much more

AKA The things we'll actually interview for to explore expertise

✅ Proficiency in Solidity best practices

✅ Great at writing and maintaing smart contract tests in JS, especially with frameworks like Hardhat, Truffle, dAppTools etc.

✅ A deep understanding of Ethereum standards like ERC20, ERC721/1155, and the OpenZeppelin contracts and contracts-upgradeable libraries

✅ L2 and/or sidechain experience (we are on Polygon but intend to rapidly expand to other EVM compliant networks)

✅ A thorough understanding of how oracles work (custom oracles, ChainLink, API3, and their relative strengths and weaknesses)

✅ Familiarity with multisignature execution of transactions, using hardware wallets, and the like

AKA The things it would be cool for you to already know, but if not, we'll teach you!

👌 Familiarity with open source and working with decentralized teams of contributors

👌 Has written and maintained subgraphs using The Graph

👌 Familiarity with Open Zeppelin Defender

👌 Understanding of low-level details of the EVM, like encoding/decoding transaction data, calls and delegatecalls, gas costs, opcodes, Yul assembly - the type of stuff you might find in the Ethereum yellow paper

👌 Interest+skills in Rust - we intend to migrate our containers running Node.js to more efficient and "decentralizable" WASM processes at earliest possibility

👌 Interest+skills in deploying microservices to Internet Computer

👌 Interest+skills in smart contract security and penetration testing

Yup, That's Me! DM. rickk#1128 on Discord.

In you as a person

• A curiosity-driven pragmatist who finds their answers in focused experimentation rather than idle speculation

• A humble soul who won't hesitate to DM questions to other team members and ask the community for help as needed

• An experienced Web 3 native or transplant who believes that dApp usability is the primary limiting factor in the mainstream adoption of this important technology, and wants to work towards correcting that for the benefit of society

For the Frontend Engineer role in particular

• A design pattern obsessed mind with ninja-level experience in React and/or other JavaScript frameworks

• A semi-perfectionist who notices when that button is just not-quite-right at this particular screen size and knows how to fix it

• A courageous soul willing to brave the depths of CSS to produce beautiful and maintainable code that promotes a beautiful and usable product

AKA The things we'll actually interview for to explore expertise

✅ Proficiency in React and/or other JavaScript frameworks

✅ Proficiency in frontend testing, both unit and integration

✅ Ability to query and optimize GraphQL

AKA The things it would be cool for you to already know, but if not, we'll teach you!

👌 Familiarity with open source and collaborating with decentralized teams of contributors

👌 Familiarity with Apollo Client

👌 Familiarity with GitHub's API

👌 Familiarity with Chrome extensions

👌 Understanding of OAuth 2 (it's how we integrate with GitHub, and soon other platforms)

Yup, That's Me! DM rickk#1128 on Discord.

🚧 Still thinking...🤔

AKA The things we'll actually interview for to explore expertise

✅ Proficiency in Node.js

✅ Ability to spin up and down MongoDB instances like a pro on a platform you'll decide on

✅ Ability to rapidly grok and integrate with third-party APIs, like GitHub, Notion, Trello and the like

✅ Familiarity with best practices in DevOps

AKA The things it would be cool for you to already know, but if not, we'll teach you!

👌 Familiarity with open source and working with decentralized teams of contributors

👌 Interest+skills in Rust - we intend to migrate our containers running Node.js to more efficient and "decentralizable" WASM processes at earliest possibility

👌 Kubernetes/Docker experience

👌 CircleCI experience

👌 Familiarity with decentralized

Yup, That's Me! DM rickk#1128 on Discord.