From: Felipe Ferreri Tonello <eu@felipetonello.com>
To: openembedded-devel@lists.openembedded.org,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: [JOB] Full-time position in California
Date: Tue, 19 Mar 2013 15:46:42 -0700 [thread overview]
Message-ID: <5148EAD2.9060304@felipetonello.com> (raw)
Hi,
I'm sorry for this off-topic. But I think it's a good thing for oe
developers in general.
I work for Cercacor Labs, and we are looking for a full-time yocto/oe
Linux Engineer.
About the company: We were medical device R&D company for Masimo. Now we
are developing out own medical device based on Linux. Here we develop
everything, since hardware, Linux kernel, middleware to multi-touch
applications.
Well.. The only issue is that due the time frame here we can't hire
anyone that requires H1B. So this person needs to be an American Citizen
or H1B holder.
I'm glad to provide you more information. Please contact me at
ftonello@cercacor.com.
BR,
Felipe
reply other threads:[~2013-03-19 23:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5148EAD2.9060304@felipetonello.com \
--to=eu@felipetonello.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox