We are a healthcare company working with AI in non-patient facing tasks. Looking for a US-based UI engineer to work on a per-project basis in collaboration with our design and product teams to build out our React app based on Figma designs.
==[Tasks and Deliverables]==
Develop a frontend UI based on Figma designs using React and Next.js.
Implement pre-built UI component libraries to ensure efficiency and consistency.
Translate the Figma designs into a proper design system in CSS.
Ensure seamless integration with backend APIs.
Collaborate with designers and backend engineers to optimize user experience.
Set up project structure, formatting, and best practices for scalable development.
==[Required Experience]==
Strong proficiency in React and Next.js.
Experience translating Figma designs into functional UIs.
Familiarity with component-based UI frameworks (e.g., Mantine, DaisyUI, Tailwind).
Understanding of best practices in frontend architecture and performance optimization.
==[Nice to Have]==
Some backend familiarity (basic Python/Django for minor adjustments).
Previous work on fast-paced startup MVP development.
Are you still looking for a freelance engineer for this project? If so, it sounds like my skillset aligns with what you're looking for.
I'm a US-based full-stack software developer with 8 years of experience building web applications. I'm experienced with Typescript, React, Next.js, Tailwind, and Python.
Let me know if you'd like to connect to discuss in more detail.
When Google transfers its IP that was created in the US to an overseas company "headquartered" in the Bahamas so that their subsidiary in Google Ireland can license the IP and not pay money to Google US, thereby avoiding US taxes, then Google Ireland certainly received benefit from the US government. This holds up so long as you believe that Google receives government benefit from US laws, regulations, and infrastructure, which I think they certainly do.
So it's not so much about forcing truly international companies to pay taxes in the US (though they should pay taxes if they are indeed subsidiaries making money from the work of a parent company when that parent company repatriates profits), it's more about exposing the legal-by-letter-but-not-by-spirit practices of companies that hide money generated in the US overseas.
This conversation took place yesterday at SemTech 2011. Ivan Hermann is with w3c. Kavi Goel is a product manager at Google who is on the Rich Snippets team. Others are identified in the document.
We're looking for a junior/mid level software engineer with an ability to work on front and back end code. We have a Rails/Javascript UI that uses a RESTful service built with Java (Spring, Hibernate, RESTlet) as its datastore.
Our team runs as closely to a startup as you can in the academic environment. We're responsible for building BioPortal: http://bioportal.bioontology.org. This isn't one of those research projects that produces a ton of theory but nothing usable. We're responsible for a full production environment that gets tens of millions of hits a month and have a full team of developers, including proper managers and even some QA (this is huge in academia). The project is well-funded by the NIH and we're halfway through year one of a five year grant.
You'll have a huge say in how things get implemented. We're not scared to incorporate new tech and definitely appreciate what people have to bring to the table. You'll be encouraged to get things done with minimal supervision, but everyone on the team is excited about talking through problems as needed.
Stanford Pros:
* Competitive compensation. Stanford likes to hire the best and we know we're competing with Google, Facebook, and everyone else. Salaries are competitive, obviously no access to options, bonuses, or profit-sharing :)
* Awesome benefits. This makes up for the lack of compensation to me. We get three weeks of vacation plus sick time plus PTO plus holidays. There's a two-week closure every December. Amazing health plans,. Free Caltrain and VTA. Alternative transit compensation. Healthy living incentives. Access to classes, gyms, libraries, and anything else the Stanford community has to offer.
* The work is incredibly meaningful and not profit-driven. Nothing wrong with profit, but if you're interested in just jumping into challenging work without worrying about money it can be a benefit.
* You work with people who are the best in the world at what they do.
* Travel opportunities for conferences on occasion.
If it gets really bad, won't the community just respond by having a monthly "Who's Offering" thread, much like we now have the monthly "Who's Hiring" thread?
Stanford, CA. Stanford Center for Biomedical Informatics Research, National Center for Biomedical Ontology.
We're hiring people interested in working with semantic web technologies, including RDF, OWL/OBO ontologies, triple stores, Protege, etc. The positions are mainly senior right now, possibly junior in the near future. Our main product is BioPortal, an ontology repository site with a RESTful API.
Stanford is an amazing place to work, great benefits, competitive salary, and the team here is top-notch (as you would expect). Feel free to ask questions (email in profile).
CloudApp can do this for screenshots or any file in the finder, plus copies a link to the clipboard: http://www.getcloudapp.com/ (not affiliated, just a very happy user)
Most people I know in the city have abandoned their cars. Zipcar has good penetration there but most people I know stick to public transit. I have friends that regularly do the trek from the Duboce Triangle to SF State without cars.
Public transit isn't as good as NYC or Chicago, but it's decent.
We are a healthcare company working with AI in non-patient facing tasks. Looking for a US-based UI engineer to work on a per-project basis in collaboration with our design and product teams to build out our React app based on Figma designs.
==[Tasks and Deliverables]==
Develop a frontend UI based on Figma designs using React and Next.js.
Implement pre-built UI component libraries to ensure efficiency and consistency.
Translate the Figma designs into a proper design system in CSS.
Ensure seamless integration with backend APIs.
Collaborate with designers and backend engineers to optimize user experience.
Set up project structure, formatting, and best practices for scalable development.
==[Required Experience]==
Strong proficiency in React and Next.js.
Experience translating Figma designs into functional UIs.
Familiarity with component-based UI frameworks (e.g., Mantine, DaisyUI, Tailwind).
Understanding of best practices in frontend architecture and performance optimization.
==[Nice to Have]==
Some backend familiarity (basic Python/Django for minor adjustments).
Previous work on fast-paced startup MVP development.