From: Ovidiu Deac <ovidiudeac@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [OSys PL Labs] 3 UI/UX Research Engineer Positions for Progr. Languages and Tools (Remote)
Date: Fri, 17 Sep 2021 14:16:44 +0300 [thread overview]
Message-ID: <CAKVsE7vMg8hxSY26v2KVkVr_ME-7MHCFFx_pgwMgHd525Bn4sg@mail.gmail.com> (raw)
In-Reply-To: <CACEStOgC5z6YOvzKDSnALewjrQvfTMRM+CrOTEN_X0qiHejWxQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2715 bytes --]
unsubscribe
On Tue, Aug 24, 2021 at 10:31 PM Nick Papoylias <npapoylias@gmail.com>
wrote:
> Dear colleagues,
>
> The newly founded PL (Programming Languages) research Group at OutSystems
> <https://outsystems.com/>
> has a goal of exploring the UI/UX frontier of Programming Tools.
>
> We are looking for 3 UI/UX Research Engineers for Programming Languages &
> Tools (Remote) to join our group. Please forward to anyone you think might
> be interested by our call:
>
> Europe/EMEA:
> https://www.outsystems.com/careers/job-detail/8a7887a87acffd16017b1cedb4930469/
>
> US/Americas:
> https://www.outsystems.com/careers/job-detail/8a7885a87b55f750017b7479ec9f365b/
>
> India/APAC:
> https://www.outsystems.com/careers/job-detail/8a7883a97ad004d8017b1011897d76de/
>
> Best Regards,
>
> Dr. Papoulias (@npapoylias <https://twitter.com/npapoylias>)
> *Director of Research **@OutSystems* <https://twitter.com/OutSystems>
>
> ==================================================
>
> *If you consider yourself (or aspire to be) a UI/UX expert with
> programming experience that wants to: “Boldly go where no programmer has
> gone before” don’t let any impostor syndrome stop you, apply to join us!
> What we are looking for in our research group -- first and foremost -- is
> explorers. Take a look at this short video to quickly learn more about
> OutSystems: https://youtu.be/0gx3hMMDOZI. <https://youtu.be/0gx3hMMDOZI.>*
>
>
>
> *Responsibilities:*
>
>
> ** Your base responsibility will be the development of research prototypes
> from an engineering perspective. Nevertheless, the research nature of these
> prototypes will almost always require you to either learn a new language, a
> new system or way of working. You will always be given time and guidance
> (bibliography, books and an engineering starting point) to do so. The
> director of the group will always be there to guide you with all aspects of
> your work.*
>
>
> ** Once this base responsibility is fulfilled your UI/UX experience and
> expertise will help us go even further. What can we add to a good prototype
> to bring aesthetics and usability to the mix ? What will make us smile
> every time we use it ?*
>
>
> ** When you become comfortable with the above responsibilities you can
> start proposing your own experiments to the team and guide our newest
> members through the whole R&D process.*
> ** Finally, according to the group’s needs you will be tasked to present
> our work to colleagues, internally or externally (to the wider industrial
> and academic community), participate in conferences, publications and in
> the general dissemination of our work.*
>
>
[-- Attachment #2: Type: text/html, Size: 4286 bytes --]
prev parent reply other threads:[~2021-09-17 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 19:31 Nick Papoylias
2021-09-17 11:16 ` Ovidiu Deac [this message]
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=CAKVsE7vMg8hxSY26v2KVkVr_ME-7MHCFFx_pgwMgHd525Bn4sg@mail.gmail.com \
--to=ovidiudeac@gmail.com \
--cc=caml-list@inria.fr \
/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