Buildforce | Mobile Developer, All-Level Engineers | Austin, Texas | Full-Time | Remote (with option to come into office) | michael@buildforce.com or https://joinbuildforce.recruitee.com/
Buildforce is building a marketplace for construction tradespeople to get jobs with construction firms. We grew 10% week over week in 2021 and are off to an even better year in 2022.
You'll work in a small but rapidly growing team building product for workers, construction firms, and our internal users.
We're an AWS Typescript shop. On the FE, we're writing React/React Native. On the BE, we're Serverless with SST Framework.
We're hiring mobile engineers (React Native) and mid-level to senior engineers working mainly on the backend.
Buildforce is helping electricians find jobs in Texas. You'll have a huge impact on a business already growing at 10% every week since the beginning of 2021 and in the biggest industry vertical in the United States ($1.3 trillion a year in annual construction volume).
We're a full-stack typescript/javascript shop building React and React Native apps on AWS that talk to a GraphQL API. We're looking for great backend, mobile, and low code engineers.
Backend Engineer – We have a severlesss backend on AWS that uses SST framework. Our API is an Apollo GraphQL API. Some AWS services that we use are Lambas, RDS, Cognito, API Gateway, S3, Kinesis, and more.
https://joinbuildforce.recruitee.com/o/senior-backend-engine...
We’ve been using Retool for the past few months and I just want to say thanks. It’s saved us a slew of time and y’all are always responsive to any issues I’ve run into.
We've been using full Serverless for the past year with Serverless framework little to no issues. Sure, a single server would be a little bit quicker but that is my only major complaint.
I have not but my co-founder worked at Uber for 5+ years. He said they had engineers basically building whatever anyone wanted. He said they built their own Slack more or less just because they could.
It's sad, because if they would just travel the world (or look at the data) instead of building unnecesary infrastructure, they would realize how broken the Uber experience is in less developed countries.
Data quality issues, like missing tolls, intersection being different on Uber's map than in real life means that Uber is underpricing drivers, which leads to driver cancellations. It was very frustrating for me to start the whole process again mutiple times after waiting 5-10 minutes and try to haggle with the drivers all the time.
I think it's likely that they don't put much value in delivering a quality product in these markets, where the revenue is relative peanuts compared to first world countries. It's enough just to exist there and claim the territory for the brand. And they can always just blame the sub-par experience in these areas on bad infrastructure. Retaining talent by keeping their engineers happy with pet projects is probably much more important to the company.
All in on AWS for BE. Just about everything you need is there for free or close to free. Netlify for FE hosting just because it’s so easy to tie up to Github. Retool for ops. Metabase for BI. Seed for Serverless CI/CD.
What backend are you using for Metabase? Any chance you are using the same backend for Retool? I'm thinking about doing this with Snowflake as a backend.
I've been involved in a site that has over 10k pages and it worked fine. Sanity has a preview feature and Gatsby incremental builds are available now (which I haven't used yet) but should bring your build times down significantly.
We use Gatsby preview. It frustrates me that we are paying a lot of money for a substandard solution to a problem that shouldn't exist.
The same goes for Gatsby incremental builds. We don't want to run a web server, so instead we should pay to run a build server 24/7 so we can have a warm cache available when we need to build!?
The annoying part is that there is not reason a static site generator should have these limitations. Gatsby's entire revenue model is based on solving problems that only exist because of the bad architectural decisions in their open source product.
I disagree. I spent a few months with it and it was a bit of a nightmare. It fits certain use cases and AWS and others push it as a good use case for more than it should be.
Have geo data? Need a count? Need to look something up for your team member and you don't have time to setup BI tools? Want to query something differently because of design changes? The answer is pretty much no or you can but it'll take some extra thing for all of those.
We ended up picking up an Aurora Serverless and it is working just fine. We can quickly make changes as business cases change, our entire team can query it for now (until we have fancier tools on the biz end), and we are able to move much more quickly.
Yep, if you need aggregated data at all for operational purposes, Dynamo isn't a good choice. A lot of the hardship people have with Dynamo is not really understanding how to model their data correctly. If you don't design it correctly from the start, you are f*cked, and I sympathize with that.
I've enjoyed using Gatsby in a hybrid approach to combine marketing and a web app for MVPs. It's allowed me to get up and running quickly and haven't run into any major issues so far.
Buildforce is building a marketplace for construction tradespeople to get jobs with construction firms. We grew 10% week over week in 2021 and are off to an even better year in 2022.
You'll work in a small but rapidly growing team building product for workers, construction firms, and our internal users.
We're an AWS Typescript shop. On the FE, we're writing React/React Native. On the BE, we're Serverless with SST Framework.
We're hiring mobile engineers (React Native) and mid-level to senior engineers working mainly on the backend.
Reach out to me at michael@buildforce.com or view our jobs https://joinbuildforce.recruitee.com/.