You'll be the first front-end engineer and employee #6 at an incredibly fast growing FinTech. We're backed by the founders of Skype, Zoopla, Lovefilm and already have our second £2M round lined up after only 12 months since the company's inception.
Thanks a lot for the shoutout, bh13731. The sunset of Parse and the rise of GraphQL was indeed one of the reasons for us to start working on Graphcool. We have a lot of customers who migrated from Parse to our platform which was a good usability benchmark for us.
In general GraphQL provides many advantages over a traditional REST like API provided by most BaaS. It frees you from the need for proprietary SDKs and reduces vendor lock-in.
The way you phrased it almost seem sarcastic in the context of this thread, although i think you are actually recommending them :)
They offer a interesting product but i think at this moment it has the exact same problem that Parse had (my other comment in this thread), you don't have access to the raw data, hope they will do that in the future (provide direct access to the source database), it will certainly be a more interesting/flexible service
Hi ruslan_talpa, I'm one of the founders of Graphcool. Thanks a lot for your feedback. You're totally right: Not having direct access to YOUR data is one of the main concerns about BaaS which we'll address at its core over the coming months.
I'd be very keen on hearing your experience getting started building something on Graphcool!
Thanks for the support! If you have some time, would love for you to check out Scaphold as well. With the latest release of our custom logic workflows, we're feature-complete and can handle real workloads that require advanced permissioning, real-time subscriptions, performance monitoring, and more.
Hey, so the reason for the viewer is due to the Relay spec. It's a standard that was developed at facebook that provides some best practices in terms of schema design but I understand liking the simpler schema especially if you use Apollo and not Relay. We've thought of providing a non-relay schema for this reason as well but have yet to get around to it. Thanks for the feedback.
I'm not a recruiter but we tried to hire someone who needed an H1-B/J1 visa and it was truly awful. We went through trying to make it work/expedite the process but there was nothing to be done. He was awarded the visa and we would have still had to wait another 4 or 5 months till they could actually start.
I'm usually quite proud of the United States but it was baffling to me how challenging this was. We have a highly qualified person, who has an employer looking to pay them, of which they will have taxes going to the United States, you've already vetted them as being okay, and yet it's still going to take nearly half a year for you to allow them to come work here.
It makes me wonder what the hell people do all everyday at the government.
To answer your question, I don't think anyone, especially a recrutier, can make the process easier.
You'll be the first front-end engineer and employee #6 at an incredibly fast growing FinTech. We're backed by the founders of Skype, Zoopla, Lovefilm and already have our second £2M round lined up after only 12 months since the company's inception.
Read more: https://meetcleo.recruiterbox.com/jobs/fk0mqjn/