Hi! This is all explained in our docs: https://skills.sh/docs/faq
158 karma · joined August 15, 2010
Location: SF Bay Area
Remote: Preferred, but not required
Willing to relocate: No
Technologies: AWS, Go, JavaScript, Python, Node.js, React, Ruby, Serverless
Skills: Executive leadership, technical architecture, engineering mentorship, people systems, product strategy, recruiting and hiring, org structure design, internal communications, growth, vendor management
Resume: https://www.linkedin.com/in/danielerickson/
Email: techwraithpdx@gmail.com
I was previously VP of Engineering at Eaze, CTO at Getable, an early engineer at Yammer and Storify, and ran a web application development agency for a few years. I'm just throwing this out there to break my bubble and widen the potential matches. See this thread on twitter for more about what I'm looking for: https://twitter.com/techwraith/status/1178738333490368513
Eaze's mission is to improve lives by providing safe, secure access to the highest quality cannabis products at the lowest prices with the utmost convenience. We are seeking passionate, talented and innovative leaders to join our world-class team and help shape history.
To learn more about who we are, our engineering culture, and whether this is the right place for you, read our Key Values profile: https://www.keyvalues.com/eaze
Here are our open roles:
- Senior Backend Engineer: https://jobs.lever.co/eaze/b3f8d324-afb9-4e06-9ac8-24e1c1bb7...
- Senior Frontend Engineer: https://jobs.lever.co/eaze/82e5d883-70fa-412f-b743-f7f63e4e7...
- Senior Infrastructure Engineer: https://jobs.lever.co/eaze/b98a0286-6dfa-45f6-9212-826b532c3...
- WordPress Engineer: https://jobs.lever.co/eaze/c90c5abd-3821-489f-bd59-c05d6a954...
Tech stack: Frontend: React / Redux. Backend: Node/.NET/C#. Infra: AWS, Terraform.
More at https://eaze.com/careers
In fact, if someone is too into their stack, we see that as a bad sign.
So I'd be super excited if you decided to apply :)
Also, we're growing fast enough that we're rarely comparing candidates. If we can hire both the apple and the orange (assuming both candidates are evaluated to be good for the role), we will.
Clear and respectful communication is one of the most important skills for an engineer to have.
If you read the second half of my answer in the article I go into the communication side of things. In my experience there are better ways to evaluate a candidate's emotional intelligence and social skills than asking them to code in front of someone.
You're 100% correct. We give our candidates the choice between working through a problem at the office (on the spot as you say) or doing a take home project asynchronously. Not everyone has the time to do homework, but not everyone wants to do an in person coding interview either. We try to stay flexible.
We believe that access to medical marijuana is a fundamental right for all people. That's why we build technology that connects people to doctors and dispensaries instantly from the comfort of home, so patients can get their medicine delivered quickly and safely.
We’re looking for passionate, talented, and innovative contributors to join our diverse, world-class team and help shape history. We’re serious about making a positive impact and improving the quality of life for both patients and employees.
* Senior Back End Engineer (C#/.NET and Node.js)
https://jobs.lever.co/eaze/b3f8d324-afb9-4e06-9ac8-24e1c1bb7...
The Role
As a back end engineer, you’ll help shape the platform that powers the Eaze web and mobile apps. We like to iterate quickly, so engineers are involved early in the product design process. Once we begin prototyping and moving towards release, you’ll own and ship your own code on infrastructure you help automate and maintain. You’ll be involved in each step of the process from design to deployment, including monitoring and scaling.
What We’re Looking For
Our core JSON API and many of our supporting tools are written in Javascript and C#, so having experience with Node.js or .NET is a plus. Have no fear if you’re not an expert in either of these—we love engineers who can rapidly learn the right language or tool in order to solve the problem at hand. Some of our ongoing challenges include real-time driver tracking and routing, dynamic product suggestions and of course scaling our system to accommodate our exponentially growing user base.
* Senior Mobile Engineer (iOS and Android)
https://jobs.lever.co/eaze/4ca30aac-4b71-4e79-97cb-53707f24b...
The Role
As our first mobile engineer, you'll be in on the ground floor of all of our mobile initiatives. We have two driver apps (one for Android and one for iOS), a tele-health app to get your doctors recommendation over video chat, and we're starting to explore consumer facing options for the marketplace itself.
What We're Looking For
We have a wide range of mobile apps on both of the main mobile platforms, so having experience with building applications for both iOS and Android is a plus. If you're stronger in one or the other, that's fine too - the team is growing quickly and we'll likely need to specialize soon. We're looking for someone who is a self starter with experience in all aspects of the mobile stack - data management, network, and UI.
We are changing the way the construction industry rents and manages equipment. Getable is a marketplace where contractors can find, rent, and manage equipment from local suppliers. We're the first to tackle this $41 billion market, and our customers love us. We've seen impressive growth over the past year, and have closed a series A funding round. Now, we need help taking this from an MVP to a industry leading product. Come join us as we enter our growth phase. We're a small company of twelve people with eight in the product team. We're building a diverse team, but we've all got one thing in common: we love building great things. We're always work to have an impact on our users, our team, and our product.
Our engineers use the latest in open source JavaScript tooling; Node.js, Browserify, npm, socket.io, PhoneGap, Docker, all help us build our realtime apps quickly. Atomify, our open source UI framework makes us nimble and simplifies the front-end development process. Our continuous integration and testing systems help us make sure that we're not sacrificing quality for development speed.
At Getable, we don't separate our engineers into front-end and back-end teams. It's all JavaScript here, so everyone is comfortable working on the whole stack. Product work is usually done in two to four week cycles by two to four people. We ship frequently, and we don't build things that won't be used.
We offer competitive salaries, meaningful equity, and great health, dental, and vision benefits.
Who we'd like to hire
We're looking for generalists who can go from working on an UI component on the client to building an API on the server and back again without missing a beat. We're looking for engineers who have experience building beautifully responsive single page applications. We strive for a culture of mentorship. Our senior engineers work with and help train more junior engineers to become the senior engineers we know they can be.
We're looking for both junior and senior level engineers.
If this sounds like you, email daniel@getable.com
We develop our applications using a modular approach on both the frontend and backend, using a modern, mostly open source JavaScript based stack: CouchDB, Node, Engine.io, Backbone, and responsive design.
Our frontend is based heavily on Atomic Design and Development, using an open source library we built called Atomify. We optimize for developer happiness and eliminate as many barriers to getting things on production as we can: we don't have any build steps, we have a live reloading component development workflow, and we have tests that run as you write your code.
Most of our apps are very frontend heavy, but our backend is all realtime. We share model code between the server and the client to make interacting with our data easy.
At the end of the day though, none of that is what makes us get out of bed in the morning. It all comes down to creating great feeling interactions to help our users get their jobs done.
Day to Day:
- Participate in the team's direction and come up with new ideas - Build modules for both the frontend and backend. We embrace open source and modularized development - Participate in and contribute to product discussions
Requirements:
- Have a passion for building easy to use apps for underserved users - Love to write small, well tested components that can be reused in many contexts - Have experience working on large JS codebases with a team of other highly skilled engineers - Be able to work on both the frontend and the backend - it's all JS
We provide:
- Meaningful equity - Better than average health plans - Backed by industry leading VCs - Opportunities to grow as a leader or individual contributor - Fun and smart coworkers
Sound like a good deal to you? Send an email to our CTO at daniel@getable.com
Getable is a small team (~10 people) working on changing the construction industry by helping contractors order and manage their rental equipment. We focus on producing high quality apps for three separate users: Contractors, Suppliers, and Getable itself. We develop our applications using a modular approach on both the frontend and backend, using a modern, mostly open source JavaScript based stack: CouchDB, Node, Engine.io, Backbone, and responsive design.
Our frontend is based heavily on Atomic Design and Development, using an open source library we built called Atomify. We optimize for developer happiness and eliminate as many barriers to getting things on production as we can: we don't have any build steps, we have a live reloading component development workflow, and we have tests that run as you write your code.
Most of our apps are very frontend heavy, but our backend is all realtime. We share model code between the server and the client to make interacting with our data easy. At the end of the day though, none of that is what makes us get out of bed in the morning. It all comes down to creating great feeling interactions to help our users get their jobs done.
Day to Day:
- Participate in the team's direction and come up with new ideas
- Build modules for both the frontend and backend. We embrace open source and modularized development
- Participate in and contribute to product discussions
Requirements:
- Have a passion for building easy to use apps for underserved users
- Love to write small, well tested components that can be reused in many contexts
- Have experience working on large JS codebases with a team of other highly skilled engineers
- Be able to work on both the frontend and the backend - it's all JS
We provide:
- Meaningful equity
- Better than average health plans
- Backed by industry leading VCs
- Opportunities to grow as a leader or individual contributor
- Fun and smart coworkers
Sound like a good deal to you? Apply here: https://angel.co/getable/jobs/30560-software-engineer or email daniel@getable.com
Backbone walks the line between framework and a collection of modules really well. It gives you just enough to be productive without being overly complex or restrictive. If you go the Backbone route, here's some pointers:
- Make sure you have a system in place for model management, having multiple models around for the same data can be a nightmare
- Backbone views are a bit too simple most of the time, you'll want to at least add a view hierarchy system and lifecycle events/methods.
- You can use the router for as much or as little as you'd like, don't feel like you have to have a new URL for every state in your app.
Yammer is using it for it's file uploads service.
It's got a great website and it's docs aren't bad either.
- "The SDK is available as an npm (Node Packaged Module)"
- "while keeping you from having to deal with threads, polling, timeouts, and event loops"
"npm" stands for "Node Package Manager", and Node.js definitely uses an event loop.
I'll definitely get some use out of this SDK though.
- Brand new Web site with extensive docs
- Removed models from geddy core, moved into Model project
- Removed utilities from geddy core, moved into Utilities project
- Removed router from geddy core, replaced with Barista
- Added view helpers
- Added model as a dependency
- Added utilities as a dependency
- Added barista as a dependency
- Added the geddy console command for CLI access to apps
- Added the geddy jake command to run Jake tasks in the app environment
- Added a ton of tests
- Fixed a ton of bugs