Python Django Developer Internship

This is a backend role. You won't build screens, and you don't need frontend experience. The mobile team will add a language picker and pass a locale to the backend. Everything behind that is yours: the data model, content pipelines, LLM generation, retrieval, audio, notifications, and making sure all of it holds up in production.

What you'll build

1. The language data model

• Design how language lives in the database: user language preference, per-story translations, fallback chains (e.g. pt-BR → pt → en), and versioning so a translation is marked stale when its English source changes.
• stories.translations (jsonb) already exists and nothing reads it yet. Decide whether it stays, or whether we move to a dedicated story_translations table, and write down why.
• Everything ships as new, reversible migrations. We never edit an existing migration.

2. The content translation pipeline

• Our library has already been translated into several languages using the Anthropic Batch API, with a two-pass generate-then-review process. Move this into the repo so it's idempotent, re-runnable and cheap, and so it handles only the stories that changed.
• Build a glossary and style layer: Hebrew terms, names of sages and sources, and terms that must never be translated. Add automated QA checks (completeness, glossary adherence, length drift, broken formatting) plus a sampling workflow for native-speaker review.

3. Generation in the user's language

• Reflections, bridge text, the three practices (Echo, Naming, Walking) and Path arcs are generated by Claude through shared prompt modules in our Supabase edge functions. Make them produce native, natural output in the target language. That means writing in the language directly, not translating English after the fact. Our existing rules must still hold, e.g. each practice carries a Hebrew term with its meaning explained, now explained in the user's language.
• Build a per-language evaluation harness so we can check quality before a language goes live and catch regressions when prompts change.

4. Multilingual matching

• Today, language-validation detects the language of the user's input and blocks anything that isn't English. Replace that gate with detection and routing.
• Story matching uses OpenAI text-embedding-3-large over pgvector. Measure how well non-English input retrieves the right English-indexed stories. Then decide between cross-lingual matching, per-language embeddings, or a hybrid, and back the decision with numbers.

5. Audio

• Stories and reflections are read aloud by ElevenLabs voices. Audio is currently stored per voice (audio_urls), so it has to become per voice and per language. Pick voices for each language, and plan batch pre-rendering, storage, cost and backfill.

6. Server-side copy

• Move push notification copy (including our Shabbat-aware scheduling), transactional and lifecycle emails, and database-driven home-screen messages out of the code and into a locale-aware string system with proper plurals and date formats.

7. Safe rollout

• Several app versions are live at the same time, and older builds can't be changed. Every change you make must stay backward compatible: English stays the default, current RPC signatures stay the same, and each language can be switched on independently behind a flag.
• Track cost and quality for each language: tokens, TTS credits, fallback rate and generation failures.

Our stack

• Backend: Supabase: Postgres (RLS, RPCs, pgvector, jsonb, pg_cron) and 50+ Deno/TypeScript edge functions
• AI: Anthropic Claude (Messages and Batch APIs, prompt caching), OpenAI embeddings, ElevenLabs TTS
• Data/scripts: Python and Node
• Other: RevenueCat, Resend, Expo Push/FCM. The app is Expo/React Native, but you won't need to work in it.

You'll be a fit if you have

• 5+ years of backend engineering, with strong PostgreSQL: schema design, migrations on live data, RLS, stored functions, and performance tuning.
• Production TypeScript (Deno or Node) and solid Python for data pipelines.
• Shipped LLM features to production, beyond prototypes: prompt design, structured output, batch processing, cost control, and above all evaluation. You know how to tell whether output in a language you don't speak is good.
• Built backend internationalization before: locale negotiation, fallback chains, ICU/CLDR plurals and dates, and translation workflows with versioning.
• Worked with embeddings and vector search, and can design a retrieval evaluation.
• Care about keeping production running: backward compatibility, feature flags, and rollouts that can be undone.
• Write clearly. Decisions here get written down before they get built.

Nice to have

• Experience with ElevenLabs or other TTS pipelines.
• Supabase-specific experience.

Job description

Tech Stack: C#, .NET Core, XUnit, Entity Framework Core, MS SQL Server, PostgreSQL, Git, JIRA, Confluence

Senior (Lead) .NET Developer Responsibilities: -

Interface with product owners and software architects to review and finalize requirements

- Participate in the full SDLC including analysis, design, development, testing, deployment, and support of new features and applications

- Actively lead and participate in agile ceremonies (Standups, Refinements, Retrospectives, Planning, and Requirement’s discussions)

- Communicate effectively, clearly, and thoroughly with the Scrum Team and Stakeholders - Provide innovative solutions to complex problems

- Design, develop and modify software applications/systems according to specifications

- Develop technical documentation including services, object, and data model

- Create high quality code and perform code reviews

- Create unit and integration tests to ensure the code quality and functionality

- Proactively learn and share knowledge of technology and compare advantages and disadvantages of alternative solutions/technologies

- Identify areas needing process improvements and see them through to resolution

- Support and coach other Developers, provide technical guidance

- Help onboard new team members

Job Type: Full-time

Ventura Securities is establishing its fintech team - a remote-first, work from anywhere team with highly talented individuals who come from diverse backgrounds and looking to solve real client problems at scale. Ventura has been in the stockbroking business for 20+ years and it is a robust and profitable franchise with 1000+ employees currently. We are looking for passionate techies with skills primarily around AWS and Python who are aspiring for a fast-track career.

Your Key Responsibilities: 

1. Build out of the Ventura cloud-based backend platform from scratch

2. Ownership and monitoring of our D2C backend

3. Robust documentation skills and desire to share information with others

4. Desire and ability to prototype ideas quickly, and be willing to experiment and learn

Basic Requirements:

·  Very strong python, lambda, sql, general aws

· Clean coding skills around Python or Go and SQL

· Demonstratable experience around writing testable code, working with git, doing peer-level code review, daily standups, and generally championing software excellence

· What you get: 

1. Chance to build out a next-gen fintech product from ground 0

2. Opportunity to influence the design of the product

3. Flexible and work anywhere environment running out of Slack

Flat org structure

Must have 1+ Years of experience.

Location: Apart from the East Indian States it will be permanent work from home.

We are having an immediate requirement for a Python web developer.

You have:

• At least 2 years of experience developing web applications with Django/Flask/FastAPI
• Familiarity with Linux
• Experience in both SQL and NoSQL databases.
• Uses Docker and CI/CD
• Writes tests
• Experienced in application deployments and scaling them on AWS or GCP

You are:

• Eager to work independently without being watched
• Easy going.
• Able to handle clients on your own

Location: Remote (in India)

We are looking for experienced Odoo Developers with good development skills in Python. Candidates should have hands-on experience in end to end implementation of the custom modules in Odoo.

RESPONSIBILITIES:

• Develop and deploy ERP/ web applications using OpenERP/ Odoo.

• Customize/ develop various modules such as Accounting, POS Sales & CRM, inventory, Purchasing, , Invoice, Website, Google map, Warehouse, MRP, HR, etc.

• Customize various modules and integrate services/ products ranging from payment gateways to hardware devices with Odoo.

• Understand Functional requirements from clients. Provide GAP analysis and transform them into technical requirements.

• Functional knowledge of ERP modules like Accounting, Stock, CRM, Inventory, HR, Sales, Purchasing, Manufacturing, E- Commerce, and Payment gateway.

• Experience in Migrations, Odoo end user training.

• Knowledge of OOP concepts, SQL, HTML and JavaScript.

• Experience in hosting on AWS or other cloud service providers

• Ability to understand client requirements and translate them into business solutions.

• Develop and deploy ERP modules from scratch

• Adopt new and emerging technologies to provide solutions to client needs. Cater to time difference need

• Identify technical issues and provide solutions

• Testing support.

• Develop and customize reports based on client s specifications in the modules like Accounting, Inventory, Manufacturing and HR. Work on Odoo's internal BI reporting tool for live reports

• Skills

• Strong familiarity with the Odoo framework is mandatory.

• Should have a solid knowledge of Python and programming concepts. Contribution for Open Source Projects will be advantageous.

• Good problem solving and analytical skills

Education:

• Bachelor's (Preferred)