Senior Frontend Engineer
Kepler Group
About the role
We are looking for a Senior Frontend Engineer to own the user-facing surface of a visually polished, client-demo-ready application built in React, Next.js, and TypeScript, bridging the gap between a non-tokenized Figma UI kit and a coded Storybook component library. You will build and document missing components natively into the existing design system, consume REST APIs to present complex data-dense UI states clearly, and use AI-assisted development tools including Claude Code with the critical judgment to push back on shortcuts that compromise long-term maintainability.
What you will do
- UI Development: Build a visually polished, demo-ready front-end using Kepler's mesh-ts React framework, React, Next.js, and TypeScript.
- Component Library Contribution: Identify gaps between the Figma UI kit and the coded Storybook, then build and document the missing components natively into the existing library.
- API Integration: Consume REST APIs and present complex, synthesized data (creator insights, AI-generated scores) clearly and performantly.
- Design Partnership: Work with design to resolve the non-tokenized Figma kit into consistent, reusable coded primitives.
- AI-Accelerated Implementation: Use Claude Code (pointed at AWS Bedrock) to move fast during implementation — while critically evaluating AI-generated output and pushing back when it isn't the right long-term solution.
- Stakeholder Alignment: Drive conversations directly with client engineers and designers to clarify both functional and non-functional requirements, rather than defaulting to whatever "just works" in the short term.
- Synchronous Collaboration: Work daily alongside client engineers over Slack and Google Meet.
Must Haves
- 5–7 years of frontend software development experience.
- Strong TypeScript and React proficiency, including Next.js — with a demonstrated discipline of no lazy
anyusage and genuine comfort with a strictly typed codebase. - Demonstrated ability to deliver visually polished, demo-quality interfaces — strong eye for detail, spacing, and interaction feel, not just functional correctness.
- Experience contributing to or maintaining a shared component library / design system, including Storybook.
- Comfortable translating Figma designs into code, including when the source designs are not tokenized and require judgment to systematize.
- Solid experience consuming REST APIs and handling complex, data-dense UI states (loading, partial data, large result sets).
- High comfort level working entirely in a Mac/Linux terminal environment (Bash, Makefiles), including modern JS tooling (bun or comparable).
- Practical, hands-on use of AI-assisted development tools, paired with the critical judgment to challenge AI output when it compromises long-term maintainability.
- Strong soft skills (mandatory, not a bonus): the ability to hold and defend a technical opinion — challenging a stakeholder's or a designer's proposed "quick fix" with sound reasoning in pursuit of a solution that scales and is maintainable long-term, while still being pragmatic enough to ship.
Nice to haves
- Experience with bun specifically, or with non-default JS runtimes/package managers.
- Design-token systems and theming architecture experience.
- Data-visualization experience (charts, dashboards, analytics-heavy interfaces).
- Enough Python familiarity to read backend code and reason about API contracts.
- Familiarity with Auth0 or front-end authorization/permission-gated UI patterns.
Perks
- Growth without limits: build your skills through mentorship, internal TechTalks, challenging projects, and a dedicated annual learning budget
- Competitive compensation: get recognition that reflects your skills and impact, with regular performance and compensation reviews
- Flexibility: work 100% remotely with flexible hours that support focus, autonomy, and a healthy work rhythm
- Meaningful, modern projects: build impactful products using modern technologies alongside global teams and leading brands
- Collaborative culture: join a supportive environment with zero micromanagement where ideas are welcomed and contributions are recognized
- Well-being & support: access local well-being programs and people-focused support tailored to your location
Didn’t find the perfect fit?
Subscribe to get notified about new roles that match your skills and interests.
Hiring process timeline
We designed our hiring process to be fast, transparent, and convenient — so you always know what to expect and can move through the steps without unnecessary delays.
A quick note
After applying, keep an eye on your inbox — including your spam folder. Occasionally, emails from our hiring platform, LaunchPod, may land there.
Tell us about yourself
Submit a short application form.
Pass a quick test
Pass a 30’- 60’ test.
Record a short video
Introduce yourself on video to fast-track your application process.
Meet our team
Once you pass the video review, grab a spot on our calendar for a technical interview.
Get an offer
Welcome to AgileEngine!
Have any questions?
What is the work format and schedule?
We are a remote-first company, so all our positions are remote. Schedules are flexible, but the main requirement is to have an overlap with your client’s schedule to ensure smooth collaboration. Specific details depend on the project and are discussed during the interview process.
What level of English is required?
We look for Upper-Intermediate (B2) proficiency or higher. Since you will be collaborating with international teams and global clients (including Fortune 500 companies), English is a part of your daily work.
Does AgileEngine provide work equipment?
It depends on your location. We provide equipment in Ukraine, Poland, Argentina, Colombia, Mexico, Brazil, Guatemala, Portugal, Spain, and India. In the USA, equipment is usually provided by the client; otherwise, you will be expected to use your own setup.
What opportunities for professional growth do you offer?
We support continuous growth through personalized development paths tailored to each expert. Also, you can expect:
- An annual learning and development budget
- Internal workshops, tech talks, and mentorship programs
- Opportunities to switch projects or grow into new roles over time
What does a typical team look like, and what tools do you use?
Teams vary by project, but you’ll usually work with a mix of experts across different fields, along with a delivery or project manager who supports collaboration and onboarding.
For day-to-day work, teams commonly use tools like Jira and Google Workspace, along with communication platforms such as Google Chat. Depending on the client, you may also work with Slack, Confluence, Notion, or similar tools.
Need help?
Want more details? See full FAQ
If something doesn’t work or you have questions regarding your application process, drop us a line.