Free scoping read. A written assessment of your manuscript in two business days, at no cost.

Start one

UI/UX designer

Pubrica is looking for an experienced and talented UI designer to design and shape unique, user-centric products and experiences. The ideal candidate will have experience working in agile teams, with developers, UX designers and copywriters. You will be able to make deliberate design decisions and to translate any given user-experience journey into a smooth and intuitive interaction.
Job description:
  • Three or more years of experience and proven track record.
  • Strong portfolio to be presented and defended during interview.
  • Hands-on experience creating wireframes, prototypes, storyboards, user flows, etc.
  • Experience using tools such as Photoshop, Sketch, Illustrator, InVision, UXPin, Quartz.
  • Understanding of basic front-end languages: HTML5, CSS3 Javascript.
  • Creative ideas with problem solving mindset.
  • Experience working in an agile/scrum development process.
  • Be open to receiving objective criticism and improving upon it.
Reach Us:

Designing for researchers who arrive with a deadline

Visitors to Pubrica are usually researchers, clinicians or company teams who need a specific service, often under time pressure and frequently working in English as a second language. Many visit on a phone between clinical or lab duties. Good design for this audience reduces effort: clear routes from a question to the relevant service, forms that ask only for what is needed, and content laid out so that a busy person can find the answer quickly. Interfaces a designer here would work on include, for example, service and sample pages, enquiry and order forms, and pages presenting technical documents such as journal comparison reports.

Trust, clarity and confidentiality in the interface

Researchers are being asked to share unpublished work, so the interface has to earn trust. Practical design choices include stating plainly what happens after a file is uploaded, showing who will see it, making confidentiality and service terms easy to find, and avoiding dark patterns such as pre-ticked consent boxes or hidden costs. Error messages should explain what went wrong and how to fix it. Each step of an order or enquiry flow should show where the user is and what comes next.

Content-heavy pages pose a different challenge. Sample documents, tables of journal metrics and long academic articles need typography, spacing and hierarchy that keep them readable on small screens. The sample work page is a good example of material that depends on careful layout.

Accessibility and responsive behaviour

The posting emphasises fundamental principles such as colour theory and visual weight. These connect directly with accessibility: the Web Content Accessibility Guidelines (WCAG) 2.2 set expectations for colour contrast, visible focus states, target sizes, keyboard operation and text alternatives. Designing to these from the start costs far less than retrofitting them. Responsive behaviour should be planned, not left to chance, with layouts tested at narrow widths, tables that adapt or scroll sensibly and forms that work with on-screen keyboards and autofill.

A working process from research to developer handoff

  1. Understand: review analytics, enquiry patterns and feedback from client-facing staff to identify where users struggle.
  2. Map: document user flows for key tasks, such as finding a service, requesting a quote or downloading a sample.
  3. Sketch and wireframe: explore layouts at low fidelity before committing to visual detail.
  4. Prototype and test: build clickable prototypes and observe a few representative users completing tasks.
  5. Specify: hand over annotated designs with states, spacing and behaviour, and keep the style guide current.
  6. Review: check the built result against the design with developers and adjust where needed.

This role works closely with web developers, copywriters and UX colleagues, as the description notes; see the web developer executive post for the development side of that partnership.

Keeping a style guide that scales

The description lists style guides among the tools this role creates and uses. For a site with many service pages, sample documents and articles, a shared component library prevents drift: consistent buttons, form fields, tables, callouts and typographic scales mean new pages can be built quickly and look like part of the same site. Documenting each component's states, spacing, accessibility notes and intended use helps developers and content teams apply it correctly. Reviewing the guide regularly, and removing components that are no longer used, keeps it trustworthy.

Preparing a portfolio you can defend

The essential duties ask for a strong portfolio to be presented and defended at interview. The most persuasive case studies show the problem, the constraints, the options considered, the evidence used to choose between them and the result, not only the final screens. Include at least one example involving forms or multi-step flows, and one involving dense content. Be ready to explain a decision that changed after testing or criticism.

Apply through the APPLY NOW button, which opens Pubrica's application form, and include a link to your portfolio along with your CV.

Get a free quote

Regulations

Check your project against this rule

  1. 1Your work
  2. 2Your details
  3. 3Send
What do you need?

Material you send is held under signed confidentiality, with access limited to the assigned team and encrypted transfer. It is not used to train anything and is not passed to third-party tools. Ask for the agreement before you send anything you would rather cover first.