Creative Technologist
Nymbus · Jacksonville, FL · 3 wk ago
RemoteRemoteOTHR$65k–$80k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Nymbus" description, then "The Opportunity", then "What You Will Own", then "What You Will Bring", then "How We Work", then "Compensation and Benefits". We must not repeat job title. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Hiring at Nymbus" etc? That's EEO and legal; remove. Also remove "Ready to join? ...". Also remove "Actual compensation will be determined..." duplicates.
We need to preserve all substantive information. So include About Nymbus description, The Opportunity description, What You Will Own (list of duties), What You Will Bring (required qualifications, preferred qualifications), How We Work (remote-first description), Compensation and Benefits (salary range, benefits list). Ensure we don't create sections with filler. All sections have content.
We must not include Pay/Schedule/Benefits unless posting actually states them. It does state compensation and benefits, so include Benefits section. No schedule mentioned, so omit Schedule. Pay: they gave base salary range, so we can include Pay section? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They gave example headings. We can use Pay for salary range. Benefits for benefits list. Or combine into Compensation and Benefits. But they said include a section ONLY when posting has real, specific content for it. The posting includes base salary range and benefits. So we could have Pay and Benefits separate. However they gave example headings; we can use Pay and Benefits. Let's do Pay (Pay
) with p containing base salary range and note about bonus/equity. Benefits (Benefits
) with ul list.
We also need About the role? The posting has "About Nymbus" and "The Opportunity". Could treat "About Nymbus" as About the role? But they said do NOT repeat the job title as a heading. We can use About Nymbus as a heading? They said use for section headings (e.g. About the role, Responsibilities...). So we can use About Nymbus as heading. Or "About the role" is generic; but we have specific content about Nymbus. Use About Nymbus.
The Opportunity could be Responsibilities? But they have separate "What You Will Own" which is responsibilities. So we could map: About Nymbus -> About the role; The Opportunity -> maybe Overview? But we can just use The Opportunity as heading. However they gave example headings; we can use any heading as long as it's . Probably fine to use The Opportunity.
What You Will Own -> Responsibilities.
What You Will Bring -> Requirements (or Qualifications). We'll use Requirements.
How We Work -> maybe Skills? But it's about remote work culture. Could be Skills? Better to use How We Work as heading.
Compensation and Benefits -> we split Pay and Benefits.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content.
About Nymbus paragraph: "Nymbus is a high-growth fintech company, 'Built to Move,' empowering banks and financial institutions to transform faster, compete smarter, and deliver greater value in today's digital marketplace. At Nymbus, we're revolutionizing banking technology. Our award-winning modern core platform and cloud-based solutions help financial institutions modernize, scale, and succeed. As part of our team, you won't just be part of a tech revolution; you'll be at the forefront of it, driving innovation and delivering exceptional client experiences. Nymbus is building the next generation of fintech platforms, and that takes people who are ready to challenge convention, move with purpose, and reimagine what's possible. We operate with an AI-first mindset across our business, continuously improving how we work, and the value we deliver to our clients. We want our partners to be thrilled about the possibilities we are creating together and the lasting impact our collaboration will bring to the industry and consumers. The journey to growth begins with doing something different. And that journey starts with the great people who make Nymbus. We challenge the status quo, question assumptions, and work together to turn bold ideas into meaningful progress."
The Opportunity paragraph: "We're hiring a Creative Technologist who can take a client site from Figma to production and keep it running after launch. You'll direct AI tooling to generate components and pages, own the pipeline that ships them, and manage the CMS each client uses to update their content. Most of the code will be generated with Kiro and Figma-to-code tools. Your job is to direct those tools, review what they produce, and decide what's ready to go live. You'll be on the Brand & Creative team, working directly with the designers on each client brand. Client site work currently runs through a shared engineering sprint schedule, and this role moves design, build, and upkeep onto one team. You'll also be the quality check between approved creative and the live site. You're not expected to write client copy, but you should understand how a marketing site is supposed to read and behave, and catch when hierarchy, content, calls to action, responsive behavior, or implementation does not look right. Our Creative team works across US and European time zones, so expect some early mornings or late afternoons. You'll work with our Dev Services team on architecture and security standards."
What You Will Own: bullet list:
- Development
- Turn approved Figma designs into production-ready components and pages using Kiro and Figma-to-code tooling.
- Review, test, and fix AI-generated code before it merges.
- Build a shared component library as the foundation for new client sites.
- Keep design tokens code-owned and on-brand for each client.
- Ensure forms, calls to action, confirmation states, links, and lead-capture journeys work correctly from both a technical and user-experience perspective.
- Deployment
- Own the pipeline from Git to Tina Cloud CMS: branching, pull request review, build verification, and publish where the client sites currently live while helping us navigate the transition to AWS.
- Keep builds reliable and troubleshoot them when they fail.
- Write down release standards the rest of the team can follow.
- Maintenance
- Run the draft, preview, publish, and rebuild cycle so client content updates go live cleanly.
- Define which fields clients can edit, and keep layout and design code-owned.
- Act as the technical point of contact for client site requests, alongside the creative lead on each account.
- Monitor and improve site performance, Core Web Vitals, image delivery, and production reliability.
- Maintain page metadata, redirects, canonical URLs, sitemap behavior, analytics and approved tracking integrations.
- Other duties as assigned.
What You Will Bring:
Required Qualifications:
- 2+ years building and shipping production websites.
- Production experience directing AI coding tools (Kiro, Cursor, Claude Code, or similar), and a good sense of when their output needs rework.
- Fluency with Git-based workflows: branching, PRs, code review, conflict resolution.
- Experience with modern static site frameworks.
- Experience with a headless CMS, including content modeling.
- Practical AWS experience: Amplify, S3, and CloudFront to provision and troubleshoot.
- Working knowledge of web accessibility standards (WCAG 2.2 AA). Our clients are banks, and some of our brands are built accessibility-first.
- Strong visual and web judgment: able to spot when typography, spacing, responsive behavior, imagery, content hierarchy, or interaction does not match the approved design or simply does not feel production-ready.
- Clear communication with designers, clients, and engineers who don't share your context.
Preferred Qualifications:
- Figma-to-code tooling experience (Figma Dev Mode, Builder.io, Anima, or similar).
- Design token systems such as Style Dictionary.
- Financial services, regulated industry, or agency experience.
- A design background, or a portfolio that shows both the design and the build.
How We Work:
- Nymbus is a remote-first company. Success in our remote environment requires self-motivation, initiative, and strong personal accountability.
- Team members are expected to manage their priorities independently, communicate proactively, remain responsive, and participate on camera during virtual meetings.
- A strong remote culture requires intentional effort from everyone.
- We expect team members to engage in our global community, proactively build relationships, participate actively in team and company conversations, seek opportunities to collaborate, and take shared ownership of creating a connected and inclusive remote community including showing up on camera.
Compensation and Benefits:
- Base salary range: $65,000 to $80,000 annually
- Annual cash bonus and equity eligibility, if applicable.
- Remote Work Environment
- Health, dental, and vision insurance, including HSA/FSA/DCA
- 401(k) plan
- Flexible time-off and company holidays
- Additional paid volunteer day
- Supplemental Insurance Programs, including voluntary Life, Accident, Critical Illness, Pet Insurance
- Employee Assistance Programs [EAP]
- Wellness programs
- Growth and development programs
- Actual compensation will be determined based on relevant experience, skills, role scope, and location.
We need to avoid duplication: "Actual compensation will be determined..." appears twice; we should keep only once.
We need to remove boilerplate: "Hiring at Nymbus", "As an AI-first company..." etc. Also remove "Nymbus is an equal opportunity employer..." etc. Also remove "Ready to join? ..." etc.
Now produce HTML.
Structure:
About Nymbus
... (the paragraph)
The Opportunity
... (the paragraph)
Responsibilities
- Development
- Turn approved Figma designs into production-ready components and pages using Kiro and Figma-to-code tooling.
- Review, test, and fix AI-generated code before it merges.
- Build a shared component library as the foundation for new client sites.
- Keep design tokens code-owned and on-brand for each client.
- Ensure forms, calls to action, confirmation states, links, and lead-capture journeys work correctly from both a technical and user-experience perspective.
- Deployment
- Own the pipeline from Git to Tina Cloud CMS: branching, pull request review, build verification, and publish where the client sites currently live while helping us navigate the transition to AWS.
- Keep builds reliable and troubleshoot them when they fail.
- Write down release standards the rest of the team can follow.
- Maintenance
- Run the draft, preview, publish, and rebuild cycle so client content updates go live cleanly.
- Define which fields clients can edit, and keep layout and design code-owned.
- Act as the technical point of contact for client site requests, alongside the creative lead on each account.
- Monitor and improve site performance, Core Web Vitals, image delivery, and production reliability.
- Maintain page metadata, redirects, canonical URLs, sitemap behavior, analytics and approved tracking integrations.
- Other duties as assigned.
Requirements
Required Qualifications
- 2+ years building and shipping production websites.
- Production experience directing AI coding tools (Kiro, Cursor, Claude Code, or similar), and a good sense of when their output needs rework.
- Fluency with Git-based workflows: branching, PRs, code review,
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Hiring at Nymbus" etc? That's EEO and legal; remove. Also remove "Ready to join? ...". Also remove "Actual compensation will be determined..." duplicates. We need to preserve all substantive information. So include About Nymbus description, The Opportunity description, What You Will Own (list of duties), What You Will Bring (required qualifications, preferred qualifications), How We Work (remote-first description), Compensation and Benefits (salary range, benefits list). Ensure we don't create sections with filler. All sections have content. We must not include Pay/Schedule/Benefits unless posting actually states them. It does state compensation and benefits, so include Benefits section. No schedule mentioned, so omit Schedule. Pay: they gave base salary range, so we can include Pay section? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They gave example headings. We can use Pay for salary range. Benefits for benefits list. Or combine into Compensation and Benefits. But they said include a section ONLY when posting has real, specific content for it. The posting includes base salary range and benefits. So we could have Pay and Benefits separate. However they gave example headings; we can use Pay and Benefits. Let's do Pay (Pay
) with p containing base salary range and note about bonus/equity. Benefits (Benefits
) with ul list.
We also need About the role? The posting has "About Nymbus" and "The Opportunity". Could treat "About Nymbus" as About the role? But they said do NOT repeat the job title as a heading. We can use About Nymbus as a heading? They said use for section headings (e.g. About the role, Responsibilities...). So we can use About Nymbus as heading. Or "About the role" is generic; but we have specific content about Nymbus. Use About Nymbus.
The Opportunity could be Responsibilities? But they have separate "What You Will Own" which is responsibilities. So we could map: About Nymbus -> About the role; The Opportunity -> maybe Overview? But we can just use The Opportunity as heading. However they gave example headings; we can use any heading as long as it's . Probably fine to use The Opportunity.
What You Will Own -> Responsibilities.
What You Will Bring -> Requirements (or Qualifications). We'll use Requirements.
How We Work -> maybe Skills? But it's about remote work culture. Could be Skills? Better to use How We Work as heading.
Compensation and Benefits -> we split Pay and Benefits.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content.
About Nymbus paragraph: "Nymbus is a high-growth fintech company, 'Built to Move,' empowering banks and financial institutions to transform faster, compete smarter, and deliver greater value in today's digital marketplace. At Nymbus, we're revolutionizing banking technology. Our award-winning modern core platform and cloud-based solutions help financial institutions modernize, scale, and succeed. As part of our team, you won't just be part of a tech revolution; you'll be at the forefront of it, driving innovation and delivering exceptional client experiences. Nymbus is building the next generation of fintech platforms, and that takes people who are ready to challenge convention, move with purpose, and reimagine what's possible. We operate with an AI-first mindset across our business, continuously improving how we work, and the value we deliver to our clients. We want our partners to be thrilled about the possibilities we are creating together and the lasting impact our collaboration will bring to the industry and consumers. The journey to growth begins with doing something different. And that journey starts with the great people who make Nymbus. We challenge the status quo, question assumptions, and work together to turn bold ideas into meaningful progress."
The Opportunity paragraph: "We're hiring a Creative Technologist who can take a client site from Figma to production and keep it running after launch. You'll direct AI tooling to generate components and pages, own the pipeline that ships them, and manage the CMS each client uses to update their content. Most of the code will be generated with Kiro and Figma-to-code tools. Your job is to direct those tools, review what they produce, and decide what's ready to go live. You'll be on the Brand & Creative team, working directly with the designers on each client brand. Client site work currently runs through a shared engineering sprint schedule, and this role moves design, build, and upkeep onto one team. You'll also be the quality check between approved creative and the live site. You're not expected to write client copy, but you should understand how a marketing site is supposed to read and behave, and catch when hierarchy, content, calls to action, responsive behavior, or implementation does not look right. Our Creative team works across US and European time zones, so expect some early mornings or late afternoons. You'll work with our Dev Services team on architecture and security standards."
What You Will Own: bullet list:
- Development
- Turn approved Figma designs into production-ready components and pages using Kiro and Figma-to-code tooling.
- Review, test, and fix AI-generated code before it merges.
- Build a shared component library as the foundation for new client sites.
- Keep design tokens code-owned and on-brand for each client.
- Ensure forms, calls to action, confirmation states, links, and lead-capture journeys work correctly from both a technical and user-experience perspective.
- Deployment
- Own the pipeline from Git to Tina Cloud CMS: branching, pull request review, build verification, and publish where the client sites currently live while helping us navigate the transition to AWS.
- Keep builds reliable and troubleshoot them when they fail.
- Write down release standards the rest of the team can follow.
- Maintenance
- Run the draft, preview, publish, and rebuild cycle so client content updates go live cleanly.
- Define which fields clients can edit, and keep layout and design code-owned.
- Act as the technical point of contact for client site requests, alongside the creative lead on each account.
- Monitor and improve site performance, Core Web Vitals, image delivery, and production reliability.
- Maintain page metadata, redirects, canonical URLs, sitemap behavior, analytics and approved tracking integrations.
- Other duties as assigned.
What You Will Bring:
Required Qualifications:
- 2+ years building and shipping production websites.
- Production experience directing AI coding tools (Kiro, Cursor, Claude Code, or similar), and a good sense of when their output needs rework.
- Fluency with Git-based workflows: branching, PRs, code review, conflict resolution.
- Experience with modern static site frameworks.
- Experience with a headless CMS, including content modeling.
- Practical AWS experience: Amplify, S3, and CloudFront to provision and troubleshoot.
- Working knowledge of web accessibility standards (WCAG 2.2 AA). Our clients are banks, and some of our brands are built accessibility-first.
- Strong visual and web judgment: able to spot when typography, spacing, responsive behavior, imagery, content hierarchy, or interaction does not match the approved design or simply does not feel production-ready.
- Clear communication with designers, clients, and engineers who don't share your context.
Preferred Qualifications:
- Figma-to-code tooling experience (Figma Dev Mode, Builder.io, Anima, or similar).
- Design token systems such as Style Dictionary.
- Financial services, regulated industry, or agency experience.
- A design background, or a portfolio that shows both the design and the build.
How We Work:
- Nymbus is a remote-first company. Success in our remote environment requires self-motivation, initiative, and strong personal accountability.
- Team members are expected to manage their priorities independently, communicate proactively, remain responsive, and participate on camera during virtual meetings.
- A strong remote culture requires intentional effort from everyone.
- We expect team members to engage in our global community, proactively build relationships, participate actively in team and company conversations, seek opportunities to collaborate, and take shared ownership of creating a connected and inclusive remote community including showing up on camera.
Compensation and Benefits:
- Base salary range: $65,000 to $80,000 annually
- Annual cash bonus and equity eligibility, if applicable.
- Remote Work Environment
- Health, dental, and vision insurance, including HSA/FSA/DCA
- 401(k) plan
- Flexible time-off and company holidays
- Additional paid volunteer day
- Supplemental Insurance Programs, including voluntary Life, Accident, Critical Illness, Pet Insurance
- Employee Assistance Programs [EAP]
- Wellness programs
- Growth and development programs
- Actual compensation will be determined based on relevant experience, skills, role scope, and location.
We need to avoid duplication: "Actual compensation will be determined..." appears twice; we should keep only once.
We need to remove boilerplate: "Hiring at Nymbus", "As an AI-first company..." etc. Also remove "Nymbus is an equal opportunity employer..." etc. Also remove "Ready to join? ..." etc.
Now produce HTML.
Structure:
About Nymbus
. Probably fine to use The Opportunity.
What You Will Own -> Responsibilities.
What You Will Bring -> Requirements (or Qualifications). We'll use Requirements.
How We Work -> maybe Skills? But it's about remote work culture. Could be Skills? Better to use How We Work as heading.
Compensation and Benefits -> we split Pay and Benefits.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content.
About Nymbus paragraph: "Nymbus is a high-growth fintech company, 'Built to Move,' empowering banks and financial institutions to transform faster, compete smarter, and deliver greater value in today's digital marketplace. At Nymbus, we're revolutionizing banking technology. Our award-winning modern core platform and cloud-based solutions help financial institutions modernize, scale, and succeed. As part of our team, you won't just be part of a tech revolution; you'll be at the forefront of it, driving innovation and delivering exceptional client experiences. Nymbus is building the next generation of fintech platforms, and that takes people who are ready to challenge convention, move with purpose, and reimagine what's possible. We operate with an AI-first mindset across our business, continuously improving how we work, and the value we deliver to our clients. We want our partners to be thrilled about the possibilities we are creating together and the lasting impact our collaboration will bring to the industry and consumers. The journey to growth begins with doing something different. And that journey starts with the great people who make Nymbus. We challenge the status quo, question assumptions, and work together to turn bold ideas into meaningful progress."
The Opportunity paragraph: "We're hiring a Creative Technologist who can take a client site from Figma to production and keep it running after launch. You'll direct AI tooling to generate components and pages, own the pipeline that ships them, and manage the CMS each client uses to update their content. Most of the code will be generated with Kiro and Figma-to-code tools. Your job is to direct those tools, review what they produce, and decide what's ready to go live. You'll be on the Brand & Creative team, working directly with the designers on each client brand. Client site work currently runs through a shared engineering sprint schedule, and this role moves design, build, and upkeep onto one team. You'll also be the quality check between approved creative and the live site. You're not expected to write client copy, but you should understand how a marketing site is supposed to read and behave, and catch when hierarchy, content, calls to action, responsive behavior, or implementation does not look right. Our Creative team works across US and European time zones, so expect some early mornings or late afternoons. You'll work with our Dev Services team on architecture and security standards."
What You Will Own: bullet list:
- Development
- Turn approved Figma designs into production-ready components and pages using Kiro and Figma-to-code tooling.
- Review, test, and fix AI-generated code before it merges.
- Build a shared component library as the foundation for new client sites.
- Keep design tokens code-owned and on-brand for each client.
- Ensure forms, calls to action, confirmation states, links, and lead-capture journeys work correctly from both a technical and user-experience perspective.
- Deployment
- Own the pipeline from Git to Tina Cloud CMS: branching, pull request review, build verification, and publish where the client sites currently live while helping us navigate the transition to AWS.
- Keep builds reliable and troubleshoot them when they fail.
- Write down release standards the rest of the team can follow.
- Maintenance
- Run the draft, preview, publish, and rebuild cycle so client content updates go live cleanly.
- Define which fields clients can edit, and keep layout and design code-owned.
- Act as the technical point of contact for client site requests, alongside the creative lead on each account.
- Monitor and improve site performance, Core Web Vitals, image delivery, and production reliability.
- Maintain page metadata, redirects, canonical URLs, sitemap behavior, analytics and approved tracking integrations.
- Other duties as assigned.
What You Will Bring:
Required Qualifications:
- 2+ years building and shipping production websites.
- Production experience directing AI coding tools (Kiro, Cursor, Claude Code, or similar), and a good sense of when their output needs rework.
- Fluency with Git-based workflows: branching, PRs, code review, conflict resolution.
- Experience with modern static site frameworks.
- Experience with a headless CMS, including content modeling.
- Practical AWS experience: Amplify, S3, and CloudFront to provision and troubleshoot.
- Working knowledge of web accessibility standards (WCAG 2.2 AA). Our clients are banks, and some of our brands are built accessibility-first.
- Strong visual and web judgment: able to spot when typography, spacing, responsive behavior, imagery, content hierarchy, or interaction does not match the approved design or simply does not feel production-ready.
- Clear communication with designers, clients, and engineers who don't share your context.
Preferred Qualifications:
- Figma-to-code tooling experience (Figma Dev Mode, Builder.io, Anima, or similar).
- Design token systems such as Style Dictionary.
- Financial services, regulated industry, or agency experience.
- A design background, or a portfolio that shows both the design and the build.
How We Work:
- Nymbus is a remote-first company. Success in our remote environment requires self-motivation, initiative, and strong personal accountability.
- Team members are expected to manage their priorities independently, communicate proactively, remain responsive, and participate on camera during virtual meetings.
- A strong remote culture requires intentional effort from everyone.
- We expect team members to engage in our global community, proactively build relationships, participate actively in team and company conversations, seek opportunities to collaborate, and take shared ownership of creating a connected and inclusive remote community including showing up on camera.
Compensation and Benefits:
- Base salary range: $65,000 to $80,000 annually
- Annual cash bonus and equity eligibility, if applicable.
- Remote Work Environment
- Health, dental, and vision insurance, including HSA/FSA/DCA
- 401(k) plan
- Flexible time-off and company holidays
- Additional paid volunteer day
- Supplemental Insurance Programs, including voluntary Life, Accident, Critical Illness, Pet Insurance
- Employee Assistance Programs [EAP]
- Wellness programs
- Growth and development programs
- Actual compensation will be determined based on relevant experience, skills, role scope, and location.
We need to avoid duplication: "Actual compensation will be determined..." appears twice; we should keep only once.
We need to remove boilerplate: "Hiring at Nymbus", "As an AI-first company..." etc. Also remove "Nymbus is an equal opportunity employer..." etc. Also remove "Ready to join? ..." etc.
Now produce HTML.
Structure:
About Nymbus
... (the paragraph)
The Opportunity
... (the paragraph)
Responsibilities
- Development
- Turn approved Figma designs into production-ready components and pages using Kiro and Figma-to-code tooling.
- Review, test, and fix AI-generated code before it merges.
- Build a shared component library as the foundation for new client sites.
- Keep design tokens code-owned and on-brand for each client.
- Ensure forms, calls to action, confirmation states, links, and lead-capture journeys work correctly from both a technical and user-experience perspective.
- Deployment
- Own the pipeline from Git to Tina Cloud CMS: branching, pull request review, build verification, and publish where the client sites currently live while helping us navigate the transition to AWS.
- Keep builds reliable and troubleshoot them when they fail.
- Write down release standards the rest of the team can follow.
- Maintenance
- Run the draft, preview, publish, and rebuild cycle so client content updates go live cleanly.
- Define which fields clients can edit, and keep layout and design code-owned.
- Act as the technical point of contact for client site requests, alongside the creative lead on each account.
- Monitor and improve site performance, Core Web Vitals, image delivery, and production reliability.
- Maintain page metadata, redirects, canonical URLs, sitemap behavior, analytics and approved tracking integrations.
- Other duties as assigned.
Requirements
Required Qualifications
- 2+ years building and shipping production websites.
- Production experience directing AI coding tools (Kiro, Cursor, Claude Code, or similar), and a good sense of when their output needs rework.
- Fluency with Git-based workflows: branching, PRs, code review,