Location: Tbilisi, Remote/Tbilisi
Workplace: remote
Tabby creates financial freedom in the way people shop, earn and save by reshaping their relationship with money. Over 25 million users choose Tabby to stay in control of their spending and make the most out of their money.
The company’s flagship offering allows shoppers to split their payments online and in-store with no interest or fees. Over 70,000 global brands and small businesses, including Amazon, Noon, IKEA, and SHEIN use Tabby to accelerate growth and gain loyal customers by offering easy and flexible payments online and in stores.
Tabby generates over $18 billion in annual transaction volume for its partner brands and is the highest-rated, most-reviewed, largest, and fastest-growing FinTech in the GCC region.
Tabby launched in 2019 and has since raised +$1 billion in equity and debt funding from global and regional investors, and is now valued at $6,5 billion.
ServiceDesk is the L1 layer between frontline support and engineering. Frontline agents escalate complex customer cases to us; we resolve them or route them to the right engineering team, and we own the whole path a ticket takes: from intake and classification to SLA, escalation and closure. We build our own tools for it: an in-house analytics platform, automations in CRM and Jira, and AI-assisted handling of tickets. You will help us make that path faster, clearer and easier to measure.
Key Responsibilities:
Own and improve the ticket flow between CRM and Jira: statuses, routing, escalation rules between L1, L2 and engineering teams;
Keep ticket classification and SLA targets accurate (issue types, categories, responsible teams) and fix gaps in the data;
Find where tickets get stuck, bounce back or breach SLA, and turn findings into process changes or clear tasks for engineering;
Work with frontline and engineering teams on intake quality: what a good escalation looks like and how to give feedback;
Automate routine steps in CRM procedures and Jira (automation rules, scripts);
Contribute to our internal tools and services (TypeScript / Node.js, Go): features, fixes and integrations, through merge requests and code review;
Help roll out and check AI-assisted ticket handling: what it gets right, where it fails, what to change;
Measure the effect of every change with data, and report it in a clear, short form;
Prepare and maintain documentation and playbooks for L1 and L2.
What you’ll bring:
2+ years in technical support, support operations or a similar role with tiered support (L1/L2/L3) and SLAs;
Solid experience with Jira: workflows, JQL, automation rules, dashboards;
Experience with a CRM or helpdesk system (ticket lifecycle, queues, routing);
SQL for your own analysis: joins, aggregations, working with large tables;
Working with logs and monitoring tools to investigate issues (Datadog, Grafana, Kibana);
Hands-on coding in at least one of: TypeScript / JavaScript, Go, Python (Google Apps Script counts for automation);
Working with Git, merge requests and code review;
Understanding of HTTP, REST APIs and webhooks;
Process thinking: you can map a flow, spot the weak step and change it without breaking the rest;
Clear writing in English (B2): instructions, task descriptions, short reports;
Ownership and autonomy: you drive a change to the end, including agreeing it with other teams.
Nice to have:
Production experience with Node.js / TypeScript or Go services, and Postgres;
Jira administration, Jira Service Management or Assets;
Understanding of ITIL processes;
Google Cloud and BigQuery;
Experience with LLM tools or agents in support: prompts, evaluation, guardrails;
Experience at a fintech company and/or a startup.
What we offer:
Full-time B2B contract
Fully remote setup
Up to 20% tax allowance
22 paid leave days annually
Stock options (ESOP) in a fast-scaling, pre-IPO company
Flexi benefits you can use for wellness, travel, or learning
Work alongside a high-performing, international engineering team in a global fintech unicorn
Location: Poland, Remote/Poland
Workplace: remote
Tabby creates financial freedom in the way people shop, earn and save by reshaping their relationship with money. Over 25 million users choose Tabby to stay in control of their spending and make the most out of their money.
The company’s flagship offering allows shoppers to split their payments online and in-store with no interest or fees. Over 70,000 global brands and small businesses, including Amazon, Noon, IKEA, and SHEIN use Tabby to accelerate growth and gain loyal customers by offering easy and flexible payments online and in stores.
Tabby generates over $18 billion in annual transaction volume for its partner brands and is the highest-rated, most-reviewed, largest, and fastest-growing FinTech in the GCC region.
Tabby launched in 2019 and has since raised +$1 billion in equity and debt funding from global and regional investors, and is now valued at $6,5 billion.
ServiceDesk is the L1 layer between frontline support and engineering. Frontline agents escalate complex customer cases to us; we resolve them or route them to the right engineering team, and we own the whole path a ticket takes: from intake and classification to SLA, escalation and closure. We build our own tools for it: an in-house analytics platform, automations in CRM and Jira, and AI-assisted handling of tickets. You will help us make that path faster, clearer and easier to measure.
Key Responsibilities:
Own and improve the ticket flow between CRM and Jira: statuses, routing, escalation rules between L1, L2 and engineering teams;
Keep ticket classification and SLA targets accurate (issue types, categories, responsible teams) and fix gaps in the data;
Find where tickets get stuck, bounce back or breach SLA, and turn findings into process changes or clear tasks for engineering;
Work with frontline and engineering teams on intake quality: what a good escalation looks like and how to give feedback;
Automate routine steps in CRM procedures and Jira (automation rules, scripts);
Contribute to our internal tools and services (TypeScript / Node.js, Go): features, fixes and integrations, through merge requests and code review;
Help roll out and check AI-assisted ticket handling: what it gets right, where it fails, what to change;
Measure the effect of every change with data, and report it in a clear, short form;
Prepare and maintain documentation and playbooks for L1 and L2.
What you’ll bring:
2+ years in technical support, support operations or a similar role with tiered support (L1/L2/L3) and SLAs;
Solid experience with Jira: workflows, JQL, automation rules, dashboards;
Experience with a CRM or helpdesk system (ticket lifecycle, queues, routing);
SQL for your own analysis: joins, aggregations, working with large tables;
Working with logs and monitoring tools to investigate issues (Datadog, Grafana, Kibana);
Hands-on coding in at least one of: TypeScript / JavaScript, Go, Python (Google Apps Script counts for automation);
Working with Git, merge requests and code review;
Understanding of HTTP, REST APIs and webhooks;
Process thinking: you can map a flow, spot the weak step and change it without breaking the rest;
Clear writing in English (B2): instructions, task descriptions, short reports;
Ownership and autonomy: you drive a change to the end, including agreeing it with other teams.
Nice to have:
Production experience with Node.js / TypeScript or Go services, and Postgres;
Jira administration, Jira Service Management or Assets;
Understanding of ITIL processes;
Google Cloud and BigQuery;
Experience with LLM tools or agents in support: prompts, evaluation, guardrails;
Experience at a fintech company and/or a startup.
What we offer:
Full-time B2B contract
Fully remote setup
Up to 20% tax allowance
22 paid leave days annually
Stock options (ESOP) in a fast-scaling, pre-IPO company
Flexi benefits you can use for wellness, travel, or learning
Work alongside a high-performing, international engineering team in a global fintech unicorn
Location: Belgrade, Remote
Workplace: remote
Tabby
creates financial freedom in the way people shop, earn and save by reshaping their relationship with money. Over 25 million users choose Tabby to stay in control of their spending and make the most out of their money.
The company’s flagship offering allows shoppers to split their payments online and in-store with no interest or fees. Over 70,000 global brands and small businesses, including Amazon, Noon, IKEA, and SHEIN use Tabby to accelerate growth and gain loyal customers by offering easy and flexible payments online and in stores.
Tabby generates over $18 billion in annual transaction volume for its partner brands and is the highest-rated, most-reviewed, largest, and fastest-growing FinTech in the GCC region.
Tabby launched in 2019 and has since raised +$1 billion in equity and debt funding from global and regional investors, and is now valued at $6,5 billion.
ServiceDesk
is the L1 layer between frontline support and engineering. Frontline agents escalate complex customer cases to us; we resolve them or route them to the right engineering team, and we own the whole path a ticket takes: from intake and classification to SLA, escalation and closure. We build our own tools for it: an in-house analytics platform, automations in CRM and Jira, and AI-assisted handling of tickets. You will help us make that path faster, clearer and easier to measure.
Key Responsibilities:
Own and improve the ticket flow between CRM and Jira: statuses, routing, escalation rules between L1, L2 and engineering teams;
Keep ticket classification and SLA targets accurate (issue types, categories, responsible teams) and fix gaps in the data;
Find where tickets get stuck, bounce back or breach SLA, and turn findings into process changes or clear tasks for engineering;
Work with frontline and engineering teams on intake quality: what a good escalation looks like and how to give feedback;
Automate routine steps in CRM procedures and Jira (automation rules, scripts);
Contribute to our internal tools and services (TypeScript / Node.js, Go): features, fixes and integrations, through merge requests and code review;
Help roll out and check AI-assisted ticket handling: what it gets right, where it fails, what to change;
Measure the effect of every change with data, and report it in a clear, short form;
Prepare and maintain documentation and playbooks for L1 and L2.
What you’ll bring:
2+ years in technical support, support operations or a similar role with tiered support (L1/L2/L3) and SLAs;
Solid experience with Jira: workflows, JQL, automation rules, dashboards;
Experience with a CRM or helpdesk system (ticket lifecycle, queues, routing);
SQL for your own analysis: joins, aggregations, working with large tables;
Working with logs and monitoring tools to investigate issues (Datadog, Grafana, Kibana);
Hands-on coding in at least one of: TypeScript / JavaScript, Go, Python (Google Apps Script counts for automation);
Working with Git, merge requests and code review;
Understanding of HTTP, REST APIs and webhooks;
Process thinking: you can map a flow, spot the weak step and change it without breaking the rest;
Clear writing in English (B2): instructions, task descriptions, short reports;
Ownership and autonomy: you drive a change to the end, including agreeing it with other teams.
Nice to have:
Production experience with Node.js / TypeScript or Go services, and Postgres;
Jira administration, Jira Service Management or Assets;
Understanding of ITIL processes;
Google Cloud and BigQuery;
Experience with LLM tools or agents in support: prompts, evaluation, guardrails;
Experience at a fintech company and/or a startup.
What we offer:
Full-time B2B contract
Fully remote setup
Up to 20% tax allowance
22 paid leave days annually
Stock options (ESOP) in a fast-scaling, pre-IPO company
Flexi benefits you can use for wellness, travel, or learning
Work alongside a high-performing, international engineering team in a global fintech unicorn
Основной стек: JavaScript, TypeScript, Angular 20+, CSS, NodeJS, Electron, Git Задачи: Разработка и поддержка клиентских компонентов Разработка и поддержка админок Разработка и поддержка сервисов и микро сервисов Разработка клиентской части Требования: Опыт коммерческой разработки web-приложений на Angular актуальных версий;
Location: Москва
MarketRiskCalculator — корпоративная система расчета рыночных рисков, такая как VaR/CVaR, дельта-вега-ро чувствительность, сценарии анализа и стресс-тестирования. Система обрабатывает портфели из 40+ различных финансовых инструментов, включая акции, облигации, фьючерсы, опционы, свопы, структурированные продукты, паевые инвестиционные фонды.
Обязанности
Чем предстоит заниматься:
• разработка ядра расчетов VaR на C++17 с использованием Boost, QuantLib, Eigen, Ceres Solver;
• реализация финансовых моделей: state-space модели с Kalman-фильтрацией, GBM, Gaussian Vasicek term structure;
• оптимизация производительности: распараллеливание через C++ REST SDK (Casablanca), OpenMP, векторизация Eigen;
• работа с кривыми доходностей, поверхностями волатильности, риск-факторами proxy;
• написание unit-тестов (gtest, более 1000 уже существует);
• управление зависимостями через Conan, сборка через CMake+Ninja.
Backend (~20–25% времени):
• разработка Python-сервисов (Tornado, Celery, MongoDB, PostgreSQL);
• интеграция с внешними системами;
• работа с RabbitMQ, Kafka, LDAP, REST API;
• создание AI-ассистента на основе GigaChat + LangChain/LangGraph.
Frontend (~10–15% времени):
• поддержка и развитие веб-интерфейса на React 17 + TypeScript + Bootstrap;
• взаимодействие с REST API, обработка данных, визуализация.
Инфраструктура (~5–10% времени):
• настройка и поддержка CI/CD (Jenkins, SonarQube);
• миграции PostgreSQL (Alembic, более 100 миграций)
• контейнеризация, деплой.
Требования
Мы ждём что ты:
• уверенно пишешь на C++17 (опыт от 2 лет);
• готов разбираться в Python-бэкенде и вносить небольшие изменения во frontend;
• можешь самостоятельно понять незнакомый код;
• интересуешься вопросами оптимизации производительности: профилированием, параллелизмом, оптимизацией кода.
**Будет плюсом:**
• опыт работы с QuantLib, MLlib или аналогичными численными библиотеками;
• понимание финансовых инструментов: облигации, акции, деривативы, yield curves;
• знание линейной алгебры и численных методов (матричные операции, оптимизация, стохастические модели);
• понимание риск-менеджмента (VaR, стресс-тесты, чувствительность);
• опыт работы с Celery, Tornado, MongoDB;
• умение работать с React/TypeScript на уровне поддержки и модификации интерфейсов;
• опыт настройки CI/CD (Jenkins, SonarQube);
• знакомство с принципами микросервисной архитектуры и event-driven систем.
Условия
Что мы предлагаем:
• гибридный график работы: два дня в офисе, три дня удалённо (после испытательного срока);
• ежегодный пересмотр зарплаты и возможность получения годовой премии;
• доступ к образовательным программам СберУниверситета для твоего профессионального и карьерного роста;
• расширенная медицинская страховка, скидки и специальные условия для членов семьи, корпоративная пенсия;
• особые условия ипотеки, скидка на подписочные сервисы;
• возможность получать бонусы за рекомендации.
We are looking for a Product Owner to lead that team: a small, senior, fully remote squad of engineers that takes new product concepts from idea to a working MVP in customers' hands, then hands proven products to a product line and moves on to the next concept.
Location: Canada
Workplace: Remote
ABOUT THE TEAM
Most providers make customers migrate their data to them. We're doing the opposite: bringing ClickHouse Cloud into the environments our customers already trust, so their data stays useful right where it lives.
Those environments come in a few shapes. Some are major cloud data platforms that run ClickHouse as a native service, so customers get it without leaving the tool they already use. Some are BI and visualization tools that need ClickHouse to show up as a fast, first-class data source behind their dashboards. And some are developer and data platforms we connect through marketplaces and identity federation with a couple of clicks or agentic calls. Every integration is unique, but the goal is the same every time: ClickHouse should feel like a first-class citizen in every environment.
The craft is finding the patterns underneath different integrations. As one of the first backend engineers, you'll help shape the technical defaults for this team. You'll have end-to-end ownership, but you'll also work inside the constraints of platforms you don't own: thin documentation, unfamiliar deployment topologies, and timelines governed by partner approval cycles. A lot of the challenge is engineering across trust boundaries you don't fully control.
You won't be doing it alone. You'll work closely with your engineering manager, the product manager, a growing team, and experienced engineers across the broader org. If that sounds like your kind of challenge, let's talk.
WHAT YOU'LL DO
You'll own an integration end to end: the design, the code, and the production system that keeps running after launch. The patterns you set there become defaults the rest of the team builds on.
Day to day, that looks like:
- Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production
- Running what you build. Which means owning the infrastructure, CI, deployment, observability behind it and on-call
- Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't
- Partnering closely with the internal teams whose services you depend on: iterating on product requirements, agreeing on interfaces and protocols, and proactively finding ways to keep moving
ABOUT YOU
These are the attributes of someone who will perform well in this role:
- 8+ years building software, with a good chunk of it on data-heavy or integration-flavored systems
- Preferably proficient in TypeScript or Go or comfortable contributing to each
- Solid backend and systems instincts. You can reason about deployment topology, multi-tenancy, and data movement, and you're comfortable owning architectural tradeoffs you'll have to live with later
- You've worked with modern auth protocols, service principals, and identity federation, and you know how to get it right across a trust boundary
- You've built on someone else's platform and know what that's actually like: incomplete docs, unintended breaking changes, etc.
- You're comfortable in ambiguity. You can ship before the spec is finished, make sensible calls under uncertainty, and flag the decisions that'll be hard to undo to your team before we bake them in.
- You're good with other engineers. Much of the work runs through teams you don't own, and you earn their trust by how you think, not just what you commit.
- You're mainly a backend engineer, but you're comfortable enough to touch a modern React app
- You use AI tools well and honestly. Reach for Claude Code, Cursor, Copilot, or whatever helps, and be clear about where you did and didn't
- You write well. Most of how we coordinate happens async in chats, design docs and RFCs
NICE TO HAVE
None of these are required, but any of them would be a bonus:
- Close familiarity with a major cloud data or analytics platform ecosystem
- Real depth in auth and identity federation, or experience building to a partner's security review, marketplace requirements or certification requirements
- Hands-on experience designing multi-tenant SaaS platforms, or the isolation and deployment topology behind them
- Working knowledge of ClickHouse, or another columnar / OLAP engine
PERKS
- Flexible work environment - ClickHouse is a globally distributed company and remote-friendly. We currently operate in over 25 countries.
- Healthcare - Employer contributions towards your healthcare.
- Equity in the company - Every new eligible team member who joins our company receives equity.
- Time off - Flexible time off in the US, generous entitlement in other countries.
- A USD$500 Home office setup if you’re a remote employee.
- Global Gatherings – We believe in the power of in-person connection and offer opportunities to engage with colleagues at company-wide offsites.
CULTURE - WE ALL SHAPE IT
As part of a rapidly scaling start-up, you will be instrumental in shaping our culture.
Are you interested in finding out more about our culture? Learn more about our values here https://clickhouse.com/company/careers. Check out our blog posts https://clickhouse.com/blog or follow us on LinkedIn https://www.linkedin.com/company/clickhouseinc/life/0c1ee7f4-2129-488d-b413-e7f6270659fd/?viewAsMember=true to find out more about what’s happening at ClickHouse.
EQUAL OPPORTUNITY & PRIVACY
ClickHouse provides equal employment opportunities to all employees and applicants and prohibits discrimination and harassment of any type based on factors such as race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state or local laws.
Please see here https://clickhouse.com/legal/applicant-privacy-notice for our Privacy Statement.
Требования:
— 2-4 года коммерческого опыта с C# и .NET (ASP.NET Core)
— Уверенное понимание ООП, SOLID, паттернов проектирования и чистой архитектуры
— Опыт работы с реляционными базами данных SQL Server или PostgreSQL и ORM EF Core
— Опыт разработки frontend-приложений на React или Angular с использованием TypeScript
Местоположение: Весь мир
Формат работы: Удаленно
Location: Bangalore - Engineering
Workplace: OnSite
LIFE AT UIPATH
The people at UiPath believe in the transformative power of automation to change how the world works. We’re committed to creating category-leading enterprise software that unleashes that power.
To make that happen, we need people who are curious, self-propelled, generous, and genuine. People who love being part of a fast-moving, fast-thinking growth company. And people who care—about each other, about UiPath, and about our larger purpose.
Could that be you?
Your Mission
We are looking for a Software Engineer II who operates as a Builder — an engineer with an
unusual bias to ship, an eye for craft, and a comfort running toward ambiguity instead of waiting for it to be solved for you.
- Be immersive in the 'why' of what we're building — not just the ticket.
- Validate with real users and teammates early; fail fast and iterate faster.
- Operate AI-forward and hands-on; let modern tools expand what you can ship on your own.
And the core technical chops of a strong frontend-leaning full-stack engineer.
At UiPath we are enabling enterprises to transform via Business Orchestration and modernize their core business processes. The frontend is where customers feel whether the product is world-class. We are a global team that collaborates like a startup and protects the pace and autonomy that lets engineers grow fast.
What you'll do at UiPath
- Ship Frontend, End-to-End: Build features from empty Figma (or no Figma at all) through
production — interactive, accessible, fast, and on-brand.
- Builder Mindset: Pick up loosely defined problems and turn them into working product. Prefer a scrappy shipped v1 over a polished plan.
- AI-Forward Development: Use Codex, Claude Code, and similar tools as part of your daily loop for coding, refactoring, testing, and debugging. Share what works with the team.
- Talk to Users: Join customer calls, review feedback, and watch real people use the thing. Let what you see change what you build.
- Touch the Stack When Needed: Write the API, add the column, ship the endpoint —
whatever unblocks your feature. Frontend is home base, not a ceiling.
- Raise the Craft Bar: Care about spacing, type, motion, loading states, empty states, and edge cases. Modern, delightful UI is the job, not a bonus.
What you'll bring to the team
- Shipping experience: 3–7 years of professional experience (or equivalent) shipping
production software, with a frontend center of gravity.
- Modern frontend fundamentals: TypeScript, React (or equivalent), component composition, state management, responsive design, accessibility, and web performance awareness.
- Enough backend to unblock yourself: You've written REST/GraphQL endpoints, worked with a database, and handled auth — or you're hungry to learn.
- Taste: You notice when a UI is well-crafted and can articulate why. You can produce
something clean without a designer holding your hand.
- AI-forward habits: You already code with AI tools and have opinions about how to get more leverage from them.
- Ownership and time management: You break work down, ship small, communicate early, and finish what you start. Write automated tests for multi-tier systems, debug cross-service issues, and take deep ownership during incidents.
- Customer curiosity: You'd rather watch one user try the product than read ten pages of
spec.
Nice to have
Experience with LangChain/Langraph, OCR/large-document pipelines, or LLM evaluation
frameworks.
#LI-VR1
Maybe you don’t tick all the boxes above—but still think you’d be great for the job? Go ahead, apply anyway. Please. Because we know that experience comes in all shapes and sizes—and passion can’t be learned.
Many of our roles allow for flexibility in when and where work gets done. Depending on the needs of the business and the role, the number of hybrid, office-based, and remote workers will vary from team to team. Applications are assessed on a rolling basis and there is no fixed deadline for this requisition. The application window may change depending on the volume of applications received or may close immediately if a qualified candidate is selected.
We value a range of diverse backgrounds, experiences and ideas. We pride ourselves on our diversity and inclusive workplace that provides equal opportunities to all persons regardless of age, race, color, religion, sex, sexual orientation, gender identity, and expression, national origin, disability, neurodiversity, military and/or veteran status, or any other protected classes. Additionally, UiPath provides reasonable accommodations for candidates on request and respects applicants' privacy rights. To review these and other legal disclosures, visit our privacy policy https://www.uipath.com/legal/trust-and-security/privacy-policy.
Освоить бэкенд целиком и понимать фронт настолько, чтобы чинить его без посторонней помощи. от трёх лет коммерческой бэкенд-разработки, в том числе сервисы на LLM в продакшене.
Управление командой: выполнение бизнесовых и технических целей, соблюдение высокого качества продукта, разработка системной архитектуры. Участие в разработке продукта: написание кода, ревью, релиз.
leadГеография найма не уточнена
УдалённоPoland, Remote/Poland
УдалённоBelgrade, Remote
Не хотите искать каждый день?
Настройте подбор один раз, и подходящие вакансии будут сами приходить в Telegram.
Настройте подбор, и подходящие вакансии будут приходить в Telegram.