126 to 150 of 364 Figma Jobs

Python, RESTful APIs, and microservices architecture. Strong Front End development experience using Nextjs/React/Typescript, with familiarity in wireframing tools (eg, Figma). Hands-on experience in building distributed systems with messaging technologies such as RabbitMQ or Kafka. Proficient with caching techniques and tools (eg, Redis, Protobuf). ...

environment. Proven experience designing digital products with measurable impact. A solid understanding of user-centred design, accessibility, and responsive design principles. Strong proficiency in Figma and familiarity with common prototyping tools. Excellent communication, collaboration, and storytelling skills - you'll often be the bridge between design and engineering. Comfortable working autonomously ...

well-defined acceptance criteria, and clear prioritisation Experience of using Agile tooling to support team delivery e.g. Jira Experience of using design tools e.g. Figma to make Mock-ups to communicate concepts to the development team or Stakeholders A good understanding of the front-to-back trade lifecycle, including client ...

well-defined acceptance criteria, and clear prioritisation Experience of using Agile tooling to support team delivery e.g. Jira Experience of using design tools e.g. Figma to make Mock-ups to communicate concepts to the development team or Stakeholders A good understanding of the front-to-back trade lifecycle, including client ...

Agile, C4, UML , TOGAF , Microsoft Well-Architected Framework , design patterns . Experience using modern tools in support of delivery: e.g. Azure DevOps, LeanIX , Lucidchart , Figma, Balsamiq, M365. Excellent understanding of public cloud hosted infrastructure and application integrations. Experience in building Minimal Viable Products (MVP) and working with product teams. Experience ...

Ability to think strategically about the entire customer journey while also being highly skilled at hands-on execution, from writing copy to reviewing Figma mockups. Communication & Influence: Exceptional communication skills (written and verbal) with a knack for simplifying complex concepts and the ability to influence and align stakeholders across product ...

Ability to think strategically about the entire customer journey while also being highly skilled at hands-on execution, from writing copy to reviewing Figma mockups. Communication & Influence: Exceptional communication skills (written and verbal) with a knack for simplifying complex concepts and the ability to influence and align stakeholders across product ...

Agile, C4, UML , TOGAF , Microsoft Well-Architected Framework , design patterns . Experience using modern tools in support of delivery: e.g. Azure DevOps, LeanIX , Lucidchart , Figma, Balsamiq, M365. Excellent understanding of public cloud hosted infrastructure and application integrations. Experience in building Minimal Viable Products (MVP) and working with product teams. Experience ...

Shopify apps (e.g. Node.js, PHP, or similar) Experience with unit testing in a front-end context Comfortable working with design tools such as Figma Prior experience in a digital agency environment, handling multiple clients/projects concurrently ...

back-end? That would make our team even more complementary. We expect a solid foundation in React with TypeScript, .NET Core (Entity Framework), PostgreSQL, Figma, and the main design principles. Do you have experience beyond that? Great. If not, no worries. We have a strong team ready ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...

always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used actual logic and data. My changes cascaded throughout the app for comprehensive critique ...