Jobs at Djinni

Job Description

We are looking for a detail-oriented and proactive Junior Trading Risk Officer to join our Trading Risk management team. This is an entry-level position ideal for someone interested in financial markets and risk control. You will assist in monitoring trading activities, analyzing exposures, and ensuring adherence to internal risk policies and legal requirements. This is a great opportunity for an individual with a passion for financial markets and a keen interest in the Forex industry.
 

Responsibilities

• Manage order flows and ensure accurate execution of trades on electronic platforms.
• Support the process of updating quotes and tracking market movements.
• Help monitor company FX exposures and ensure compliance with internal risk management rules.
• Observe key developments in FX markets and report important changes or opportunities to the team.
• Assist in analyzing client positions to identify potential risks.
• Prepare basic reports on trading activity, exposures, and performance metrics.
• Stay informed about major macroeconomic events and news impacting currency markets.
• Collaborate with IT and other departments to help improve trading platforms and client experience.
• Continuously learn about market structure, trading strategies, and analytical tools.
   

Requirements

• Bachelor’s degree in Finance, Economics, Mathematics, or a related field (or final-year student).
• Basic understanding of financial markets and FX trading concepts.
• Strong analytical and numerical skills with attention to detail.
• Good knowledge of Excel and interest in data analysis or automation tools.
• Ability to work under pressure and make quick, accurate decisions.
• Strong communication skills and eagerness to learn from experienced team members.
• English proficiency (both written and spoken).
   

Nice to have

• Familiarity with trading platforms (e.g., MT4/MT5, cTrader, or similar).
• Some experience or coursework in financial analysis, risk management, or quantitative methods.
• Basic programming or scripting knowledge (Python, VBA, or similar).
   

Benefits

• Competitive and attractive compensation
• Remote work schedule
• Proper rest time and sick leaves.
• Challenging and unique tasks in the FinTech field
• Funding for gym memberships, fostering a healthy work-life balance
   

Interview Stages

1. Interview with Recruiter (1 hour)
2. Interview with Hiring Manager (1.5 hours)
3. Final Interview (45 minutes)

Mandatory Skills
- Minimum 3+ years of hands-on Python backend development experience in production environments
- Strong Python fundamentals (clean code practices, typing discipline (where used), debugging, and performance awareness)
- Experience building web APIs with a modern framework (FastAPI) and designing maintainable endpoints
- Strong understanding of API patterns (authentication/authorization basics, input validation, pagination, versioning, consistent error contracts)
- Solid database experience (PostgreSQL preferred - schema design, migrations, indexing, query optimization, transaction basics
- Experience with asynchronous/background processing and handling retries
- Experience writing tests (pytest or similar): unit + integration tests, mocking, test data strategy
- Familiarity with production-grade practices (logging, monitoring basics, configuration management, secure secrets handling)
- Ability to detect, analyze, and resolve issues in production systems
- Comfortable doing root-cause analysis
- Ability to work independently in a remote setup with proactive, clear communication.

Responsibilities:
- Build and ship backend features for Obriy AI / SURE platform - APIs, services, and workflow components that power automation, integrations, and knowledge modules
- Design, implement, and maintain clean, well-documented REST APIs (and internal service interfaces) with strong validation and error handling
- Integrate with external systems (CRMs, support tools, messaging channels) using stable adapters, retries, and safe failure handling
- Implement background processing and asynchronous workflows (queues, schedulers) for long-running tasks and integrations
- Maintain and improve data models and persistence: schema changes, migrations, query performance, data consistency
- Improve reliability and observability: structured logging, metrics, tracing, alerts, and practical runbooks
- Troubleshoot production issues, perform root cause analysis, and deliver robust fixes with minimal regression risk
- Write and maintain automated tests (unit/integration) and support QA with clear test scenarios and reproducible cases
- Participate in code reviews, contribute to backend best practices, and keep engineering documentation up to date
- Collaborate closely with Frontend, DevOps, and Product teams to refine requirements, estimate work, and deliver iteratively.

Nice to have: 
- Experience with LLM/GenAI integrations (OpenAI-compatible APIs), prompt orchestration, tool-calling patterns, and safety considerations
- Familiarity with RAG pipelines (embeddings, vector databases, document chunking, retrieval quality evaluation)
- Experience designing integration connectors 
- Knowledge of event-driven architecture (Kafka/RabbitMQ/NATS) and distributed systems concepts
- Experience with Docker and Kubernetes-based deployments (understanding runtime constraints and observability)
- Familiarity with security best practices: OAuth/OIDC, RBAC/permissions modeling, audit logs, data protection principles
- Experience with performance tuning: profiling, caching strategies (Redis), async I/O optimization
- Experience working in B2B SaaS / enterprise environments with reliability and compliance expectations.

We are looking for an AI/ML Research Scientist.

Requirements:

• PhD with 1+ years of research experience in Electrical Engineering, Computer Science, Information Systems, or a STEM-related field
• 1+ years of experience with modern machine learning architectures including Transformers, Graph Neural Networks, and Diffusion models
• Strong coding skills in Python and C++
• Experience with machine learning frameworks like PyTorch
• At least 1 publication in top machine learning conferences (NeurIPS, ICML, ICLR, etc.)
• Experience with deep learning on graphs (general graphs, circuit graphs, molecular graphs, or trees)
• Familiarity with classical search and optimization techniques (Genetic Algorithms, Monte-Carlo Tree Search, Dijkstra's Algorithm, etc.)
• Experience with EDA tools, either commercial or open-source
• Publications in top-tier venues focusing on AI for chip design or AI for materials science. 

CreditBooster.ai’s mission is to help every American understand, build, and own their credit. We’re an AI-native credit platform, live on the App Store and Google Play, with real paying customers and a small remote team across the US, Europe, and now the Americas.

About the role

This is the seat that anchors our engineering day in the Americas.

Our backend runs on European hours today. We want the product covered across a much longer working day, so that a production issue at 3pm Chicago has an owner who is awake, and so that work moves while the other half of the team sleeps. You’d own that side of the clock.

That means real autonomy, not a night shift. For most of your day you’ll be the senior backend engineer on duty: you’ll make the call, ship it, and hand off cleanly. We’re looking for someone comfortable being the most senior person online for a stretch of the day, who writes things down well enough that the handoff actually works.

It also means a platform flavor, not just feature work. Centralized logging, monitoring, alerting, and notification infrastructure are part of this seat. We are past the point where a small team can run on hope and a message in chat.

AI is not a slogan here, it’s how we build. Our designer shipped the referral page that’s live in production working with an agent. Our CPO built one of our web apps the same way. The standard is not handing a ticket to an agent and approving the result: you plan with it, read the plan properly, push back, iterate, and stay responsible for what ships.

We move fast and we’re deliberately not over-gated, even in fintech. Freedom to move, judged on results.

The kind of problems this seat owns

Long-running processes that have to survive. Significant parts of our backend are not request and response. They are processes that run for weeks, depend on outside parties answering on their own schedule, and where the outcome of one step determines the next. They have to be resumable, idempotent, and survive a deploy in the middle. We orchestrate this on AWS Step Functions. If your instinct for “this takes three weeks and can fail at any step” is a cron job and a status column, this role will be uncomfortable.

Third-party integrations where the vendor is the unreliable part. We depend on external providers for regulated data and for delivery into the physical world. Payloads are messy, contracts change under you, and failures are quiet rather than loud. Building the layer that makes an unreliable dependency safe to build on is a large and permanent part of this seat: error taxonomies you can act on, reconciliation between our state and theirs, and detection when something silently never completed. This is the thing we talk about most.

Centralized logging, monitoring, and alerting. We’re consolidating observability onto PostHog, with Sentry on errors, and building out alerting properly: service outages, volume anomalies, and the silent failures that today only surface when a customer writes in. Making those loud is part of the job.

Notification infrastructure. A real event model with types, priorities, batching, and dedup, across push, email, and in-app. This is infrastructure, not a feature.

LLM work with an actual job to do. We run on AWS Bedrock, replacing deterministic logic with model-backed logic where it earns its place. This is not chat: it’s structured output, validation, and evaluation on data that has to be right, in a regulated domain where a fabricated claim is a compliance problem rather than a polish bug.

Payments and subscriptions. RevenueCat across the App Store and Google Play, entitlement webhooks, and the reconciliation nobody enjoys. Billing bugs are the ones users notice first and forgive least.

Email that actually arrives. Resend, with deliverability treated as an engineering problem: bounce rates, sender warm-up, segmentation.

Our stack

• Core: Node.js 22, Fastify, TypeScript, PostgreSQL 17
• AWS: Step Functions, Bedrock, EC2, RDS, S3, ECR, ALB
• Payments: RevenueCat, App Store and Google Play server-side
• Observability and analytics: PostHog, Sentry
• Email: Resend
• Voice: LiveKit
• CI/CD: GitLab

We would rather you know a few of these deeply than list all of them.

Responsibilities

• Own backend services end to end: Node.js, Fastify, TypeScript, and PostgreSQL, from schema design to the endpoint to whether it holds up in production
• Design and own long-running workflows: transitions, retries, idempotency, and what happens when a step fails on day nineteen of thirty
• Build out centralized logging, monitoring, and alerting so failures are loud instead of quiet
• Own the notification infrastructure: event model, priorities, batching, dedup, across push, email, and in-app
• Own our integrations with external data and delivery providers, including the resilience layer around them
• Own subscription and entitlement flows through RevenueCat, including reconciliation
• Work on LLM-backed features where the output has to be structured, validated, and defensible
• Anchor the Americas working day. Diagnose and fix a production problem during US business hours without waiting for Europe to wake up
• Cross the boundary rather than filing a ticket at it. Our web app, landing site, and internal admin are within reach when the surface you own needs them
• Use Claude Code, MCP servers, and your own agents to compress engineering work that used to take days into hours, while staying responsible for everything that merges
• Write the handoff. Async is not a nice-to-have on a team split across nine time zones, it’s the job

What we’re looking for

• You’ve owned something, not just contributed to it. You can point at a service and say it was yours, describe what would have gone wrong without you, and separate what you owned from what your team delivered. This is the single thing we’re screening hardest for
• You’ve built something that had to survive time. A long-running, resumable process: a state machine, a durable workflow engine, a saga, an orchestrator, or a job pipeline with real retry and idempotency semantics. Step Functions specifically is a bonus, the thinking is the requirement
• You have a platform instinct. You’ve owned logging, monitoring, or alerting somewhere and you have opinions about what deserves a page and what deserves a dashboard. You treat an outage nobody noticed as the worse outage
• You’ve made an unreliable dependency safe to build on. Retries, backoff, idempotency, reconciliation, and knowing which failures are recoverable and which are not
• You’re comfortable outside the backend. Node.js and PostgreSQL are the centre of gravity, but you can work in a web codebase and ship something a user can touch without a handoff
• You’re effective alone. For much of your day nobody senior will be online with you. You need to unblock yourself, make a defensible call, and write down enough that the next person picks it up cleanly
• You’re AI-native in how you build. Claude Code or an equivalent agentic CLI is part of your daily workflow. You’ve built your own skills, agents, or MCP servers that automate real engineering work, and you can tell us about a time one was confidently wrong and how you caught it
• You debug for real. Symptom to root cause to verification, and you know the difference between a bug that stopped reproducing and a bug that got fixed
• You ship without waiting for a spec. Often there’s a problem and an owner, not a written specification

You may be a good fit if you have

• 5+ years building product software, with deep Node.js and TypeScript in production
• A backend area you owned in production. Be ready to walk us through it: what it was supposed to do, what broke, what you changed, and how you knew things got better. This is the most important part of your application
• Strong PostgreSQL and API fundamentals: schema design, migrations, async flows, and a feel for what gets slow
• Real experience with long-running or event-driven systems: queues, workflows, webhooks, retries, idempotency
• Enough DevOps to own your own observability: you can set up the logging and the alert, not just read the dashboard
• TypeScript strict-mode discipline (no any)
• Working English at B2 or above, written and spoken. Our team works in Russian and Ukrainian internally, but Linear, code, and customer-facing copy are English
• A working day on Americas hours that overlaps Chicago business hours

Bonus

AWS Step Functions in production, or an equivalent durable workflow engine (Temporal, Airflow, Camunda, or one you built). AWS Bedrock, or serious LLM work in a regulated context. Payments and subscription billing: RevenueCat, Stripe, App Store and Google Play server-side receipts, and the reconciliation that comes with them. Email deliverability as an engineering problem. Fintech, lending, KYC, or other regulated-domain work. Experience being the on-call owner for a service that mattered. A public Claude Code skill, MCP server, or contribution to an open-source agent harness. Founding engineer or first-few-hires experience at a small company, where owning the whole thing was the default.

Logistics

Fully remote, contractor or self-employed. Open to anyone working on Americas hours: Mexico, Colombia, Brazil, Argentina, Chile, or elsewhere in a compatible time zone. Equipment provided.

How to apply

Tell us about one bug you fixed in production: what the symptom was, what the cause actually turned out to be, and how you knew it was really fixed. Short is fine. This is the part we read first. First step is a 30-minute conversation where we’ll ask you to walk us through how you work with an agent, live.

CreditBooster.ai’s mission is to help every American understand, build, and own their credit. We’re an AI-native credit platform, live on the App Store and Google Play, with real paying customers and a small remote team across the US and Europe. Our users work on improving their credit, learn how credit actually works, and find credit products matched to their profile. We grew 2,211% in six months.
 

The problem you’d own

Credit improvement has the slowest feedback loop in consumer fintech.

Improving a credit score is a long journey, and it moves in long cycles. Reports refresh once a month. Real change takes many months more. Between those moments a user’s score does not move and nothing visible happens. Every product in this category inherits that silence. Most of them fill it with noise, or with numbers they cannot stand behind. We would rather fill it with something true, and that is the design problem you would own.

The second half of it is comprehension. Credit is genuinely confusing, and most people arrive without a clear model of how it works or what to do first. Building that understanding, and making it feel like real movement long before the outcome arrives, is as much of this role as the mechanics are.

Your job is to design the system that fills that gap: a motivation and education layer that makes a 30-day wait feel like forward movement, without ever lying to the user about their score.

That last clause is the hard part, and it’s why this role needs a specialist. We operate under CROA and app-store rules. We cannot promise a score outcome, we cannot imply a guaranteed result, and we cannot reward users for taking on debt. Every mechanic you design has to create genuine momentum inside those constraints. If you’ve only ever gamified things where you could dangle the outcome, this will be a harder and more interesting problem than you’re used to.
 

Where you might come from

We’re as interested in game designers as in product people. If you’ve built progression systems, quest structures, meta systems, or in-game economies, and you want to point that craft at something that changes a person’s financial life rather than their score in a match, this is that job. The discipline transfers. The subject matter is what changes.

To be direct about one thing: this is not an iGaming or casino retention role, and that experience is not what we’re looking for. Bonus mechanics, lootboxes, and win-back offers are the opposite of the playbook here.
 

What you’d own

You’d work alongside our product manager.

• The engagement model. Define the progression system end to end: what counts as progress between report pulls, how it’s earned, how it’s shown, what it unlocks. We have an internal brainstorm covering XP, credit-health levels, streaks, and quest-framed progress. Treat it as raw material to argue with, not a spec to implement.
• Notifications and lifecycle messaging. Our push and email today are functional and forgettable. We want a messaging system built on a metaphor a user can hold in their head, delivered on a cadence that earns attention instead of burning it.
• First-run and education. Design what a new user sees in their first ten minutes and their first month. This is the single biggest lever we have on how a new user starts.
• The retention instrument panel. Decide what we measure, instrument it with our PM and engineers, and hold yourself to it. You should be able to say which mechanic moved which cohort, and kill the ones that didn’t.
• Experiment design. Set up the tests, call them honestly, and write down what we learned. We have PostHog, Amplitude, and RevenueCat in place.
   

What we’re looking for

• You’ve shipped a real system that survived contact with users. Progression, levels, quests, missions, streaks, meta systems, in-game economies, habit loops. In a game or in a product, it doesn’t matter which, as long as it went live and you can talk about what it changed using numbers. Not a case study, not a concept deck.
• You can write the document. A GDD, a systems spec, an engagement model, whatever your discipline calls it. You define the rules, the balance, and what the system refuses to do, clearly enough that designers and engineers can build from it.
• You reason from behavioral science, not from a pattern library. Self-determination theory, the Fogg behavior model, variable reward, loss aversion, the difference between a habit and a compulsion. You can explain why a mechanic works, and you can tell when the honest version of it is weaker than the manipulative version and choose the honest one anyway.
• You are comfortable being the person who says no. Half of good gamification is deleting mechanics. Points for their own sake, leaderboards that shame people, streaks that punish a missed day during a hard month. You’ve killed features like these before and you can explain why.
• You work in the constraint, not around it. Regulated, compliance-bound, or safety-critical product experience is a strong signal. Health, education, finance, insurance.
• You’re hands-on. We’re a small team. You will write the specs, sit with the designers in Figma, brief the engineers, read the dashboards, and argue with the CEO. There is no team under you and no one to delegate to.
   

You may be a good fit if you have

• 4+ years in game design, product design, behavioral design, or learning design, with at least 2 owning a progression, economy, or engagement system end to end
• Evidence a system you built changed how people behaved, and the honesty to also describe something you shipped that didn’t work
• Fluency with analytics and experimentation tooling, and the confidence to design a test that can actually fail
• A plus, not a requirement: experience at a company known for doing this well, such as Duolingo, SoFi, Noom, Headspace, Chime, Credit Karma, Peloton, Babbel, or Strava, or on a live game with real progression and economy systems
• Working English at C1 or above. Our team speaks Russian and Ukrainian internally, but all product artifacts, tickets, and customer-facing copy are in English
   

Nice to have

Consumer subscription experience, especially where the value takes weeks to arrive. Formal background in psychology, behavioral economics, or instructional design. Game design or live-ops experience. Experience in credit, lending, or another product where the user’s outcome is partly out of the product’s control.
 

How we work

Fully remote. You’ll need overlap with Chicago mornings, roughly 8 to 11am CT, for standups and demos. We’re open to full-time and to a focused fractional engagement if that’s how you work best. Tell us which you want and we’ll talk.
 

How to apply

Send us one system you shipped. Tell us what it was supposed to change, what it actually changed, and one mechanic you removed and why. First step is a 30-minute conversation. No take-home before that.

We run a large fleet of Android devices driven by a Python/ADB automation script. Currently 240 physical devices, managed by 2 employees.

What you'll own:

• Reliability of the automation script (crash detection, auto-restart, logging)
• Proxy routing and failover across the fleet
• Per-instance device configuration
• Migration from physical devices to LDPlayer
• Simple status reporting so operators can see fleet health at a glance

• Proactive optimization

   

Requirements:

• Strong Python
• ADB and Android device automation
• Windows Server and virtualisation
• Networking basics: proxies, routing, iptables

• Experience running 20+ concurrent instances

   

Nice to have: Docker, monitoring tooling, experience with device farms

Paid trial task before we commit either way. 

🚀 About Kilona.io

At Kilona.io, we build high-quality, high-speed web and mobile applications. We work with global startups to create cutting-edge products that are fast, precise, and beautifully engineered.

We are looking for an experienced Unity Developer to adapt an existing Unity game for the Skillz platform.

This is not a full game port or a project built from scratch. The main task is to prepare a dedicated version of the existing game, integrate the required Skillz functionality, and ensure that it meets the platform’s technical requirements.

✅ Requirements

• 4+ years of hands-on experience with Unity and C#
• Practical experience working with the Skillz platform and Skillz SDK
• Experience working with existing Unity projects and codebases
• Experience integrating third-party SDKs and APIs
• Strong understanding of mobile game development for iOS and Android
• Ability to debug, optimize, and resolve integration-related issues
• Experience preparing mobile games for release
• Good communication skills in English, at B2 level or higher

✨ Nice to Have

• Experience with multiplayer, competitive, or skill-based mobile games
• Understanding of authentication, analytics, payments, and tournament systems
• Experience publishing games on the App Store and Google Play
• Familiarity with CI/CD pipelines for Unity projects
• Experience using AI-powered development tools such as ChatGPT, Cursor, or similar tools

🧑‍💻 Responsibilities

• Review the existing Unity game and its technical structure
• Prepare a separate version of the game for the Skillz platform
• Integrate and configure the Skillz SDK
• Adapt the existing game flow according to Skillz requirements
• Test and debug the integration on iOS and Android
• Ensure stable performance and compatibility across supported devices
• Collaborate with the team throughout development, testing, and release

🧑‍💻 Working Conditions

• Hourly-based payment model — overtime is always paid
• Fully remote — work from anywhere
• Flexible schedule — we appreciate team overlap, but you manage your own time
• Easy time-off policy — take days off when you need them, with no unnecessary bureaucracy
• Work on an international mobile gaming project in a fast-paced and supportive environment

🔍 Hiring Process

• Video introduction or a quick screening call — 20–30 minutes
• Technical interview — up to 1 hour
• Final interview, if needed
• Offer 🎉

Interested? Let’s talk! 📨 Drop us a message — we’re always open to meeting like-minded people.

🚀 About Kilona.io

At Kilona.io, we build high-quality, high-speed web and mobile AI applications. We work with top global startups to create cutting-edge products that are fast, precise, and beautifully engineered. 

We’re looking for an experienced Performance Marketing Manager to help scale VibeMeal — an AI-powered calorie tracking app 
 

VibeMeal allows users to log meals through photos, voice, or text.

We’re actively scaling paid acquisition and looking for someone who understands subscription-based mobile apps and can take ownership of Meta Ads performance.

✅ Requirements

• 4+ years of experience in Performance Marketing / User Acquisition
• Strong hands-on experience with Meta Ads
• Experience scaling mobile subscription apps
• Deep understanding of:
  • Web-to-App funnels
  • In-App funnels
  • Onboarding optimization
  • Paywalls
  • Trial conversion optimization
  • Subscription metrics: ROAS, CAC, LTV, Payback
• Experience with:
  • AppsFlyer
  • RevenueCat
  • Meta Ads Manager
  • Firebase / Analytics tools
• Strong analytical mindset and data-driven decision-making

✨ Nice to have

• Experience in Health & Fitness apps
• Experience with calorie tracking, nutrition, or weight loss apps
• Experience managing budgets above $50k/month
• Experience working with AI-powered consumer apps

🧑‍💻 Responsibilities

• Manage and scale Meta Ads campaigns
• Improve acquisition efficiency and profitability
• Analyze funnel performance and identify bottlenecks
• Work closely with the founder, product, and design teams
• Generate and test new creative angles and growth hypotheses
• Optimize onboarding, paywalls, and subscription conversion

 🤝 What We Offer

• Long-term collaboration
• Hourly-based payment model (overtime is always paid)
• Fully remote — work from anywhere
• Flexible schedule — we appreciate team overlap but you manage your own time
• Easy time-off policy — take days off when you need, no bureaucracy
• Opportunity to make a significant impact on a fast-growing mobile product 🚀

If interested, please send:

• Your LinkedIn profile
• Relevant mobile app experience
• Apps you’ve worked on
• Your salary expectations
• Brief description of your biggest growth achievement

Position overview

As a Middle .NET Developer, you will join our engineering team to design, develop, and maintain high-performance backend systems for a modern fintech platform built on a microservices architecture.

You will take ownership of implementing scalable, secure, and reliable backend solutions, delivering new product functionality, and resolving complex technical challenges. Working closely with Solution Architects, Product Owners, QA Engineers, and DevOps specialists, you will contribute to architectural decisions, improve system performance, and ensure high code quality across the platform.
 

This role is ideal for an engineer with strong commercial .NET experience who enjoys building robust backend systems, writing clean and maintainable code, and delivering reliable solutions from the ground up. Experience with distributed systems, asynchronous communication, and modern cloud-native technologies will be a strong advantage.

Your Background

• 3+ years of commercial experience with .NET / C# development
• Strong experience with ASP.NET Core and REST API development
• Good understanding of microservices architecture
• Experience with Entity Framework Core and SQL databases
• Hands-on experience with PostgreSQL
• Experience working with Redis
• Good understanding of asynchronous communication patterns
• Experience writing clean, maintainable, and testable code
• Strong knowledge of software design principles (SOLID, Clean Code, YAGNI)
• Ability to analyze requirements, estimate tasks, and deliver features independently
• English level: B1+
   

Nice to have

• Experience with Kubernetes
• AWS experience
• Experience with gRPC
• Experience with RabbitMQ
• Experience with banking or fintech products
• Mentoring or code review experience
  
  Responsibilities
• Develop, maintain, and enhance backend services using .NET Core
• Design and implement new product features
• Resolve complex technical issues and optimize application performance
• Estimate development tasks and contribute to project planning
• Conduct technical investigations and propose effective solutions
• Contribute to architectural decisions and engineering best practices
• Write clean, maintainable, and testable code

• Collaborate with cross-functional teams, including QA, DevOps, and Product
  
  Technologies

  .NET Core, ASP.NET Core Web API, Entity Framework Core, PostgreSQL, Redis, RabbitMQ (MassTransit), gRPC, Docker, Kubernetes, AWS, GitHub Actions, Git
  
  What we offer

• 20 billable days off during the first year of cooperation, 25 billable days off from the second year
• Fair and competitive compensation
• Friendly team and supportive working environment
• Flexible working schedule
• Remote work opportunities
• Well-established business processes
• Regular company updates and Q&A sessions with management
• Ability to transfer unused vacation days to the next year
• Opportunities for professional growth and participation in large-scale fintech projects

About Us

DNSai LLC is an independent technology company focused exclusively on building practical, high-performance tools for understanding and working with the Domain Name System (DNS). We are not an email security company. DNSai is a Cyber Security DNS Utility, a purpose-built set of utilities that make DNS data easier to access, interpret, and apply to real-world workflows across IT, security operations, research, and digital operations.

We are looking for a highly skilled and motivated Senior C#/.NET Full Stack Engineer with extensive experience across the C#/.NET ecosystem, AWS, Azure, Docker, and Kubernetes to join our growing team. You will play a key role in developing and maintaining both frontend and backend systems behind our DNS utilities — services that must stay fast, accurate, and reliable while processing large volumes of DNS data.

Responsibilities

• Design, develop, and maintain scalable and secure applications and DNS utilities using C# and .NET technologies.
• Build and maintain cloud-based infrastructure on AWS and Azure for high-throughput, low-latency DNS data processing.
• Develop and implement RESTful APIs that expose DNS lookup, enrichment, and analysis capabilities to internal and external consumers.
• Collaborate with product, research, and design teams to turn complex DNS data into clear, usable tooling.
• Utilize Docker and Kubernetes to containerize applications and ensure smooth deployment pipelines.
• Troubleshoot, debug, and optimize applications for performance and reliability at scale.
• Write efficient, maintainable, and testable code following best practices.
• Participate in code reviews and ensure adherence to coding standards.
• Implement CI/CD pipelines to streamline deployments using AWS and Azure services.
• Ensure security and data protection across applications and services, in line with the expectations of a cyber security utility.
• Stay up-to-date with DNS standards, security trends, and platform technologies to enhance development practices.
•  

Requirements

• Proven experience as a Full Stack Developer, with a focus on C# and .NET technologies.
• Solid understanding and hands-on experience with AWS and Azure cloud services.
• Expertise in containerization technologies such as Docker and Kubernetes.
• Strong experience with SQL and NoSQL databases (e.g., SQL Server, MongoDB).
• Familiarity with frontend technologies (e.g., JavaScript, React.js, Angular) is a plus.
• Experience in building and consuming RESTful APIs.
• Knowledge of version control systems like Git.
• Strong problem-solving skills and the ability to debug complex issues.
• Familiarity with agile methodologies and CI/CD processes.
• Excellent communication and collaboration skills to work with cross-functional teams.

Preferred Qualifications

• Working knowledge of DNS concepts and protocols (record types, resolvers, zone data, DNSSEC, passive DNS), or a strong interest in learning them quickly.
• Experience with microservices architecture and serverless computing.
• Familiarity with DevOps practices and infrastructure-as-code tools (e.g., Terraform).
• Understanding of security best practices and cloud-native security services.
• Experience with high-volume data pipelines or network/telemetry data.
• Experience with testing frameworks (unit, integration, and UI testing).

Why DNSai?

• Competitive salary and flexible payment method.
• Deep, focused work in a single problem domain — DNS — rather than scattered consulting projects.
• Opportunities for growth and professional development.
• Flexible working hours and full remote work opportunity.
• Work in a collaborative, innovative and inclusive environment.

About the Role

We are looking for a skilled Full Stack Developer to join our engineering team and build modern, high-performance web applications. You will work across both frontend and backend, designing scalable solutions, implementing new features, and optimizing system performance.

Responsibilities

• Develop and maintain frontend applications using Next.js 14, React 18, and TypeScript
• Build responsive and reusable UI components with Tailwind CSS 
• Design and develop REST APIs using FastAPI and Starlette
• Design, optimize, and maintain PostgreSQL and TimescaleDB databases 
• Implement caching and performance optimizations with Redis 
• Collaborate with product managers, designers, and engineers to deliver high-quality features
• Write clean, maintainable, and well-tested code
• Participate in code reviews and technical discussions
• Troubleshoot, debug, and optimize application performance

Required Skills

Frontend

• Next.js 14
• React 18
• TypeScript
• Tailwind CSS 

Backend

• FastAPI 0.111
• Starlette

Database & Infrastructure

• PostgreSQL
• TimescaleDB
• Redis

Nice to Have

• Experience with Docker and containerized deployments
• Experience with CI/CD pipelines
• Familiarity with cloud platforms (AWS, GCP, or Azure)
• Knowledge of authentication (JWT, OAuth)
• Experience building scalable, high-load applications

What We Offer

• Opportunity to work with a modern technology stack
• Challenging technical projects
• Flexible work environment
• Professional growth and learning opportunities 
• Collaborative and supportive engineering culture

Expected results during the first 1–3 months

• Resolve outstanding technical debt across the codebase.
• Design and develop an AI-powered chatbot.
• Fix existing bugs and improve overall platform stability.

Red Flags

• Drug use.
• Disruptive, aggressive, or unstable behavior.
• Abusive or disrespectful communication.

Working Conditions

• Fully remote.
• Monday–Friday (Monday–Saturday is available if preferred).
• Compensation: $1,500–4,000/month.
• Salary depends on experience and technical level.

Probation Period

• 3 months

About the Role

We're looking for an experienced SEO Copywriter who can create high-quality, SEO-driven content for competitive niches. You'll be responsible for writing commercial and informational articles, optimizing content for search engines, and adapting materials for multiple GEOs and language versions.

If you have a strong understanding of SEO, can write directly in English, and know how to create content that ranks and converts, we'd love to hear from you.

What You'll Do

• Write high-quality SEO content manually (without AI-generated texts).
• Create long-form commercial and informational articles.
• Build clear and logical article structures, including headings and content blocks.
• Optimize content for target keywords (Title, H1–H3, Meta Description, Alt tags).
• Work with semantic core and LSI keywords.
• Create and localize content for multiple GEOs and language versions.
• Develop SEO-focused commercial content that meets search engine guidelines.
• Ensure content quality, originality, and consistency.

• Collaborate with the marketing team to deliver content aligned with business goals.

   

What We're Looking For

Must-have

• 5+ years of commercial copywriting experience.
• At least 2 years of SEO copywriting experience.
• Experience writing directly in English (B2 level or higher), without translating from Russian or Ukrainian.
• Strong understanding of SEO principles and content optimization.
• Experience working with semantic core, keyword clustering, and LSI keywords.
• Ability to create well-structured long-form content.
• Understanding of meta tags and their purpose.
• Experience building commercial article structures.
• Strong logical thinking and attention to detail.
• Ability to work independently and meet deadlines.

A big advantage

• Experience in Forex, Crypto or Trading.
• Experience working with gray niches.
• Understanding of search engine restrictions and trigger words within the Forex niche.
• Experience creating multilingual content for different GEOs.

What We Offer

• Fully remote work.
• Monday–Saturday schedule.
• Competitive salary based on experience and skills.
• Three-month probation period.
• Opportunity to work on challenging international projects.
• Professional and supportive team with opportunities for growth.

Red Flags

We won't move forward with candidates who demonstrate:

• Insufficient English proficiency.
• Lack of motivation or initiative.
• Poor work ethic or inability to meet deadlines.
• Dependency on AI as the primary content creation tool instead of writing independently.
• Addiction-related issues that affect work performance.

About RiskSeal
RiskSeal is an innovative startup focused on providing cutting-edge risk management solutions in the fintech industry. Trusted by top fintech providers globally, RiskSeal is dedicated to developing highly scalable data collection and data processing tools that drive smarter and faster credit risk decisions. As a growing company, we thrive on creativity, collaboration, and the excitement of tackling new challenges.

Job Description
This is a remote position with a shifted working schedule, starting at 2:00 PM Kyiv time. We are looking for a Middle+ TechOps Engineer to oversee the smooth operation of our data collection and processing pipelines. The ideal candidate will have experience managing large-scale automated data gathering systems, ensuring seamless deployments, and maintaining system efficiency across a complex microservices environment.

Responsibilities
● RiskSeal data collection platform support & maintenance
● Configuration of new environments, clients, data sources
● Troubleshoot data harvesting issues
● Optimize system performance & minimize downtime of data collection algorithms
● Monitoring the state of integrations of data collection
● Take part in production deployments ensuring continuous operation and no customer impact

Requirements
● 2+ years of experience in a technical support or engineering role in a
data-intensive environment.
● Experience working with automation tools, web data collection workflows.
● Experience working with databases such as MySQL, ClickHouse, etc.
● Experience with monitoring and logging tools such as Grafana, LogChef, or similar.
● Strong problem-solving skills and ability to troubleshoot operational bottlenecks.

● Ability to collaborate with cross-functional teams, including developers and DevOps engineers.
 

What We Offer
● A high-impact role in a fast-growing fintech startup.
● The opportunity to optimize and scale an advanced data collection system.
● A flexible remote work environment with a focus on results.
● Competitive salary and benefits package.
● A chance to work with a team of passionate professionals in a rapidly evolving space.

We are looking for an experienced Wikidata / Wikipedia consultant with proven expertise in creating and editing company pages in compliance with Wikipedia's policies and guidelines.

What we're looking for:

• Hands-on experience with Wikidata and Wikipedia editing, particularly for companies and organizations.
• Strong understanding of Wikipedia's notability requirements and sourcing policies.
• Knowledge of paid editing disclosure requirements and experience working within Wikipedia's conflict-of-interest guidelines.
• Ability to write in a neutral, encyclopedic tone without promotional language.
• Good understanding of Wikidata structure, including properties, items, statements, and entity relationships, to correctly build and maintain a company record.

The goal is to create a properly structured, policy-compliant, and sustainable Wikidata entry for our company based exclusively on existing independent and reliable sources. 

The specialist should:

• Review available third-party publications and assess whether they meet Wikipedia/Wikidata requirements.
• Create or update the company's Wikidata item using the appropriate properties and references.
• Ensure all information complies with Wikipedia and Wikidata policies.

• Advise on whether the company currently meets notability requirements and recommend any improvements if necessary.

   

Requirements

• Portfolio with relevant Wikidata/Wikipedia projects.
• Demonstrated knowledge of Wikipedia policies and editorial standards.
• Excellent attention to detail and ability to work with structured data.

• Experience with corporate profiles is highly preferred.

   

When applying, please share examples of Wikidata items or Wikipedia pages you have worked on and briefly describe your role in those projects.

About the company

Turning marketing into a market-domination weapon, we created a new category - the marketplace for future customers. Businesses shop for leads as they shop for products in e-commerce: you see everything about a lead before you buy - full transparency, control, and predictable outcomes. We're the #1 lead marketplace in the USA, and we're accelerating.

Role overview

We are looking for a Product Owner to ensure that the most valuable product decisions are executed efficiently, shipped quickly, and delivered in the right order. You will own the "how and when" of the product, turning direction into reality while maintaining speed, clarity, and high delivery quality. You will work in close partnership with a Product Manager, who owns direction ("what and why"), while you own delivery flow, backlog quality, and release readiness.

Requirements

2+ years as a Product Owner making real scope decisions, on a team of 8+ engineers.

You optimize for value shipped, not tickets closed, and can explain calls where you shipped less to deliver more.

You can reason about cost of delay and effort vs value out loud, not just in story points.

You read API contracts and talk about service boundaries without a translator; Node.js / microservices is a plus.

Your specs are praised by engineers; we will ask to see real tickets you wrote.

English B1/B2+.

AI-first by default — if you are not already using AI to 3x your output, you will be behind our engineers.

What You'll Be Doing

Take product briefs and decompose them into shippable increments. A 3-week ticket is a planning failure, and it is yours.

Own the backlog end-to-end: acceptance criteria, edge cases, definition of done, all in place before an engineer touches anything.

Weigh every increment against its cost: engineering effort vs expected value and cost of delay. Cheap and high-value ships first; expensive and speculative waits.

Prioritize with a visible score, not a feeling. Anyone can challenge it; you defend it with numbers.

Own communication outward: founders, sales, support, and the PM always know what's shipping, what's next, and what changed, without anyone interrupting the team to ask.

Keep the team unblocked and own the delivery numbers (cycle time, predictability, carryover, QA flow) as tools to spot problems early. Hygiene, not the mission.

Push back on the PM when a brief is not buildable. That friction is the system working.

This is not for you if

You see yourself as a delivery manager who moves tickets. The "what ships" decisions are yours to make, not yours to receive.

Your main skill is running ceremonies.

You sequence by gut rather than by value and cost.

You want to own product direction. That is a different role.

What we expect from you (first 3 months)

We don't do long onboarding. Access on day one, context in days, a real problem in week one. We hire people who create value with incomplete information, because that is the job every day after probation too.

End of month 1: you know the codebase map and the team; the queue is fully yours, continuously ordered with a visible score; baseline flow metrics captured (cycle time and WIP), because you cannot improve what you did not measure.

End of month 3 (the bar): cycle time visibly better than your month-1 baseline with before/after to show; founders fully out of the delivery loop (prioritization, scope, and ship decisions run without us); briefs turning into shipped product, in the right increments, without anyone pushing.

How we work with you: honest checkpoints at 2 weeks, 1 month, 2 months. We judge trajectory, not perfection. Wrong fast and corrected beats slow and safe. If the fit is wrong, we both know by month 2 and say it out loud.

What We Offer

Impact: Direct influence on how fast and effectively product decisions reach users.

Autonomy: Ownership over delivery processes and prioritization decisions.

Flexibility: Remote-first setup with async-friendly communication.

Compensation: Competitive salary above market benchmarks.

Team: Skilled, fast-moving team focused on execution and results.

Time Off: Three weeks paid vacation plus 5 paid sick days annually.

Growth: Unlimited learning opportunities and resources.

AI-Heavy Environment: Advanced tooling and automation across workflows.

Ownership: Full responsibility for delivery outcomes and team efficiency.