Senior Python Developer

About the role 

This role supports the BuyerLink business, which runs a lead marketplace across automotive, home services, HVAC, and insurance. Every day the platform matches consumer intent to the businesses that can act on it, at volume, in near-real time. The systems that do this are Python: the services that route and score leads, the pipelines that move data between our marketplace and our partners, and the internal tools our operators use to run the business. 

We are hiring a senior engineer to own a meaningful piece of that. This is a broad platform role rather than a narrow one. In a given quarter you might design an API a partner integrates against, rebuild a pipeline that has outgrown its original design, and ship an AI-backed feature that removes manual work from an internal workflow. If you want deep ownership of systems that carry real revenue, and you would rather make a decision than wait for one, this will suit you. 

You will be based in Yerevan, working alongside our Armenia engineering team and with colleagues in the United States, Canada, Guatemala, and Ukraine. Most of your day runs on your own schedule, with an afternoon overlap window for the people you work with in North America. That structure gives you long stretches of uninterrupted build time, and it puts a premium on clear written communication. Decisions here get made in writing so that they survive the time difference. 

On structure: you will report to a manager in Armenia, and your day-to-day technical direction, priorities, and sprint work come from our Python team in Ukraine, specifically their technical lead and project manager. In practice you are a full member of that Python team, in a time zone close enough that real-time collaboration works without anyone bending their day around it. 

What you will do 

• Design, build, and operate Python services and APIs that carry production traffic, with performance, reliability, and security as first-order concerns rather than afterthoughts. 

• Own data pipelines end to end: ingestion, transformation, validation, and the monitoring that tells you when something has gone wrong before a partner does. 

• Make architecture decisions and defend them. You will be the person in the room with the strongest opinion on how a system should be shaped, and you will be expected to have one. 

• Build AI-assisted features into internal and customer-facing products where they earn their place, working with LLM APIs, retrieval, and structured extraction. 

• Review code with real rigor, and raise the standard of the code around you by doing it. 

• Diagnose production issues under time pressure, fix the cause rather than the symptom, and write down what happened. 

• Mentor mid-level engineers and give them the context to make good calls without you. 

• Work as part of our Ukraine-based Python team, taking technical direction from their lead and coordinating daily on sequencing, code review, and handoffs. 

• Work directly with product, data, and operations partners to turn a business problem into a scoped technical one. 

Working with AI 

Every developer here has Claude and GitHub Copilot, and they are part of how the work gets done rather than an optional extra. The engineers getting the most from them are shipping meaningfully more, and we would like you to be one of those engineers. 

What matters to us is judgment. Knowing which tasks to hand to a model and which to write yourself, giving it enough context to return something usable, and reviewing what comes back as carefully as you would review any other engineer's pull request. You should be able to explain every line you merge. 

The more important thing to know is where this is heading. Over the next six to twelve months we expect to move substantially toward agentic development, with agents taking on larger and more autonomous portions of the build and test cycle. That will change our tooling, our workflow, and what the day-to-day job looks like. We are not asking you to have done this before, because very few people have. We are asking you to be genuinely interested in figuring it out with us, and comfortable working in an environment where the way we build is still being reshaped. 

If you would rather join a team with a settled toolchain, this is an honest reason to look elsewhere. If that prospect is the interesting part, we should talk. 

What you will do 

• Design, build, and operate Python services and APIs that carry production traffic, with performance, reliability, and security as first-order concerns rather than afterthoughts. 

• Own data pipelines end to end: ingestion, transformation, validation, and the monitoring that tells you when something has gone wrong before a partner does. 

• Make architecture decisions and defend them. You will be the person in the room with the strongest opinion on how a system should be shaped, and you will be expected to have one. 

• Build AI-assisted features into internal and customer-facing products where they earn their place, working with LLM APIs, retrieval, and structured extraction. 

• Review code with real rigor, and raise the standard of the code around you by doing it. 

• Diagnose production issues under time pressure, fix the cause rather than the symptom, and write down what happened. 

• Mentor mid-level engineers and give them the context to make good calls without you. 

• Work as part of our Ukraine-based Python team, taking technical direction from their lead and coordinating daily on sequencing, code review, and handoffs. 

• Work directly with product, data, and operations partners to turn a business problem into a scoped technical one. 

Working with AI 

Every developer here has Claude and GitHub Copilot, and they are part of how the work gets done rather than an optional extra. The engineers getting the most from them are shipping meaningfully more, and we would like you to be one of those engineers. 

What matters to us is judgment. Knowing which tasks to hand to a model and which to write yourself, giving it enough context to return something usable, and reviewing what comes back as carefully as you would review any other engineer's pull request. You should be able to explain every line you merge. 

The more important thing to know is where this is heading. Over the next six to twelve months we expect to move substantially toward agentic development, with agents taking on larger and more autonomous portions of the build and test cycle. That will change our tooling, our workflow, and what the day-to-day job looks like. We are not asking you to have done this before, because very few people have. We are asking you to be genuinely interested in figuring it out with us, and comfortable working in an environment where the way we build is still being reshaped. 

If you would rather join a team with a settled toolchain, this is an honest reason to look elsewhere. If that prospect is the interesting part, we should talk. 

What you bring 

• 5 to 8 years building and operating production Python systems, including time as the senior engineer others turned to. 

• Depth in at least one modern web framework (Django, FastAPI, or Flask) and the judgment to know when the framework is the wrong tool. 

• Strong API design instincts across REST and GraphQL, including versioning, authentication, and the boring parts that decide whether a partner integration succeeds. 

• Real database skill: schema design, query optimization, and index strategy in PostgreSQL or MySQL, plus working knowledge of a NoSQL store. 

• Production experience on a major cloud. We run primarily on GCP with Azure in the mix, so either is a strong signal, and AWS experience transfers. 

• Comfort with Docker, container orchestration, and modern CI/CD. 

• Git fluency and disciplined testing habits, including the automated coverage that lets you refactor without fear. 

• Ability to work effectively inside a distributed team where your technical lead and your manager are in different places. Seniority here means raising questions early and keeping people informed without being asked. 

• Comfort working through change. Our stack and our development practices are actively evolving, and you should find that energizing rather than unsettling. 

• Professional English, written and spoken. You will be in design discussions and code reviews with colleagues across four countries. 

• Clear written communication. Distributed teams run on writing. 

Nice to have 

• Hands-on work with LLM APIs, retrieval-augmented generation, or agentic frameworks. 

• Experience in lead generation, ad tech, marketplaces, or another high-volume transactional domain. 

• Familiarity with data warehousing (Snowflake, BigQuery) and analytics workloads. 

• Exposure to privacy and compliance requirements such as TCPA, CCPA, or the California Delete Act. 

• Open-source contributions, or a second language you are productive in. 

• Agile delivery experience in a distributed team. 

Why work with us? 

You will have room to make decisions. Our engineering organization is deliberately lean and distributed, which means senior engineers here carry real scope rather than a slice of someone else's plan. Our Armenia team owns production systems outright, not overflow work handed down from somewhere else. We invest ahead of the curve on tooling, we retire what no longer serves us, and we would rather ship and learn than deliberate indefinitely.