Not trying to be snarky, but I'm not sure why this matters? Isn't the main value prop of a service like nango or Merge just the unified API and features around it (e.g. unified webhooks for events etc)? Can you help me understand why this is important?
Standard pre-built integrations are ok to get started. But rapidly customers ask for more integration capabilities, which are not supported by standard integrations. At this point, SaaS companies need to build custom integrations that fit exactly what they customers want.
elvex (https://www.elvex.ai/) | Senior Product Engineer | $150k-$210k USD equity, benefits | Remote (PST - AST preferred, but can make exceptions)
Mike here, the CTO at elvex. elvex is making generative AI accessible, useful and secure for enterprise teams. We’re helping non-technical users join what we truly believe is a revolution in computing. In the future elvex will power >50% of all AI apps inside a company.
Prior to elvex, our founding team (4 people currently) launched, scaled and sold Parse.ly to Automattic in their largest ever acquisition by cost and revenue (Automattic makes and maintains WordPress).
We’re looking to hire our next Senior Product Engineer. Senior Product Engineers are full-stack at elvex and are given a lot of autonomy to solve both customer and engineering-oriented problems directly.
If you join us, you’ll be employee number 5 overall and will have big impact on the trajectory of the company, culture and product. We are working with a host of very large B2B customers and solving real problems for them with our platform and looking to commercialize later in 2024.
You should be an expert in web app development with deep familiarity with one or more of: Django/Flask/FastAPI and React/Vue/Svelte. You should also love playing at the very edge of innovation as that’s where we are with generative AI at the moment. Is RAG the killer gen AI use case? Is the best UI we can do really just chat? How do we move beyond cool prototypes to production-scale use cases?
I'll admit "100% insecure" is perhaps a bit hyperbolic, but they are insecure from the standpoint that any other script executing on the page can examine the contents of either localStorage or sessionStorage and then try to perform a brute force attack.
The main assumption is just that you have a single API domain. The fact that the frontend and API may be on different domains doesn't impact this recommendation.
If the API tries to set an HTTPS-only session cookie on api.example.com, the client/browser will simply forward cookie that on every request (including requests made on behalf of a user like a frontend calling fetch()). You can try this yourself, or see it happening in the Github example linked in the post.
If you had backend APIs supported by different domains (api1.example.com and api2.example.com), things do get more troublesome. You could still configure the cookie domain for .example.com, but then you're sending the session cookie along with any request to any example.com subdomain.
For companies that you see on those boards, follow their social accounts and maybe the accounts of their founders/leadership. They'll often tweet about postings prior to them even going up on a job board.
Q: How do I make my resume attractive?
One of the most critical parts of remote cultures is being an effective communicator. Since you won't be in an office to bounce ideas around, you need to show that you can express your thoughts. Your resume itself will convey some of this, but if you have links to blog posts/essays that's great to see as well.
Aside from that, always good to see examples of work that you're proud of.
Q: Will I need a Visa if employed by a US company?
Not necessarily. If the company has a Canadian office, they'll likely take you on as a full time employee and pay all the regular benefits and payroll taxes for you. If they don't, you'll likely work as a contractor and will have to decide if you want to incorporate or be a sole proprietor. You do not require a Visa to be a Canadian working for a US company as a contractor.
You are correct that contractors have no insurance/benefits, but that's usually OK because you can negotiate higher wages as a contractor and pay for benefits yourself via something like Blue Cross (https://on.bluecross.ca/health-insurance/health-insurance-so...).
If you have a spouse, it's also possible you're covered under their plan so that's a good thing to check.
Regarding holidays/vacation, it's just something to negotiate as part of your arrangement. If you're "consulting" for one company, you're effectively a full-time employee and will likely have some level of vacation time built in to your contract.
In the USA... Given real estate prices in tech hubs, who can afford an office space anymore, let alone private offices! I imagine working from home will become the new normal. At least until the FCC allows ISPs to throttle Internet connection speeds so much that ISDN lines start looking attractive. Hopefully they make the phone company maintain those copper phone lines!
this fcc comment is so uninformed. getting rid of net neutrality will make service way better because you will be able to pay for a line with prioritized access for video conferencing and remote presence. net neutrality is what makes it impossible for individuals with a public isp connection to get the same quality as corporations with their own private networks.
>net neutrality is what makes it impossible for individuals with a public isp connection to get the same quality as corporations with their own private networks.
Right, its definitely not the ISP monopoly/duopoly
yep. all of those qos and traffic shaping features on routers don't actually do anything. that is why it should be illegal for public isps to use them. makes sense.
Yeah. I see a lot of replies here posting about remote work (which don't get me wrong is awesome!) but to me, that kind of misses the point. If you want an office, you generally like the idea of being able to interact with your coworkers in person. You just want privacy whenever you aren't interacting with people. Going full remote means that you rarely get that in person interaction if at all.
