Best Java Jobs & Projects

I am an active real estate wholesaler looking for an experienced Real Estate Virtual Assistant to help grow my lead pipeline.

I personally handle acquisitions, negotiations, offers, and contracts. Your job is to find potential sellers, contact them, qualify their interest, organize leads in our CRM, and help build our cash buyer database.

We are currently targeting Evansville, IN; Newburgh, IN; Indianapolis, IN; and Louisville, KY. We will target both houses and vacant land.

Responsibilities:
• Use PropWire to build targeted property-owner lists
• Find vacant land, absentee owners, high-equity owners, vacant properties, tired landlords and other motivated-seller opportunities
• Skip trace/find owner phone numbers and contact information
• Cold call and/or conduct approved outreach to property owners
• Determine whether owners are interested in selling
• Ask basic qualifying questions: motivation, property condition, timeline and asking price
• Enter and organize every lead in our CRM
• Maintain follow-up dates and detailed seller notes
• Hand qualified/interested sellers directly to me for acquisitions
• Research cash buyers, landlords, flippers, builders and land investors
• Contact buyers and collect their buying criteria
• Maintain an organized cash-buyer database

You WILL NOT be responsible for negotiating contracts or making final offers. I handle acquisitions.

Requirements:
• Previous experience working for a U.S. real estate wholesaler or investor
• Experience with PropWire, PropStream or similar property-data software
• Experience skip tracing property owners
• Experience cold calling motivated sellers
• Experience using a real estate CRM
• Good spoken and written English
• Comfortable speaking with U.S. property owners
• Organized and able to follow a daily process
• Experience building cash-buyer lists is strongly preferred

Schedule & Pay:
• Starting at 3 hours per day
• 5 days per week
• $5/hour
• Approximately 15 hours/week
• Opportunity for increased hours and responsibilities if performance is strong

I am looking for someone long-term. This is not a one-time data-entry project.

When applying, answer these questions:
1. How long have you worked for U.S. real estate wholesalers?
2. Which lead-generation platforms have you used?
3. Have you personally used PropWire?
4. Which CRMs have you used?
5. How do you build and skip trace a motivated-seller list?
6. Have you cold called homeowners before?
7. How do you qualify an interested seller before sending the lead to acquisitions?
8. Have you built cash-buyer lists? Explain how you found the buyers.
9. Have you worked with vacant-land leads?
10. Please submit a short voice recording introducing yourself and explaining your previous wholesaling experience.

Seeking an expert developer to build a multi-user trading bot for stocks (Interactive Brokers) and crypto (Bybit or similar), with signals from two Telegram channels and access controlled by an active Whop.com subscription. The project includes webhook integration, three risk profiles, emergency stop logic, fractional share support, take profit safety nets, latency-tolerant execution, and secure credential management. Security is critical: NDA required, no hardcoded secrets, paper trading tested first, and full IP/code ownership transferred. Start with a small paid test task, with milestone payments tied to completed modules. Please apply with relevant API experience, a code sample or project link, and a timeline/rate estimate.

Description:

We are seeking a Senior Full-Stack Engineer to support the development and maintenance of modern, production-grade software applications.

This role requires strong hands-on experience across backend and frontend development. You will work with Python and Java services, Angular-based web applications, APIs, cloud-native deployments, and AI-enabled features.

Required skills — must have:

Strong production experience with Python
Strong working experience with Java
Strong experience building web applications with Angular
Experience designing and integrating REST APIs and microservices
Experience with Docker and Kubernetes
Familiarity with CI/CD, code reviews, testing, and production deployments
Professional English communication skills
Experience with AI/ML or LLM integrations is highly preferred

Responsibilities:

Build and maintain backend services using Python and Java
Develop and enhance Angular frontend applications
Integrate APIs and services across distributed systems
Help implement AI/LLM-powered features where applicable
Write maintainable, tested, production-ready code
Collaborate with remote engineering team members and participate in code reviews

Availability requirement:

Must be available full-time from 9:00 AM to 6:00 PM CST
Remote position
Long-term opportunity

Compensation:

USD $600 per month
Monthly payment

When applying, please include:

Your years of experience with Python, Java, and Angular
A brief summary of relevant projects
Your English level
Confirmation that you are available 9:00 AM–6:00 PM CST
Your resume or Upwork profile link

Job Title:Interactive "Draw, Scan, Play" Unity System (Computer Vision + Dynamic Sprite Ingestion)Project OverviewWe are looking for a developer or small agency to build a custom interactive educational system for our makerspace. The goal is to create a seamless hardware-software pipeline where a student draws a character or object on a physical sheet of paper, places it under a fixed overhead webcam, and presses a button to scan it. The system must automatically isolate the drawing and dynamically inject their physical artwork as the playable character inside a custom Unity game template.The final system will be a standalone desktop application (running on Windows or macOS) attached to a connected touchscreen monitor and overhead USB camera. It must also generate a QR code so users can take their web-based games home.Technical Scope & WorkflowThe software pipeline must execute the following steps seamlessly:1. Image Capture & Processing (Computer Vision)Input: Capture a high-resolution image from a fixed overhead USB webcam or document camera.Segmentation: Use computer vision (OpenCV or standard C# thresholding scripts) to automatically detect paper boundaries, correct perspective distortion, perform thresholding to completely erase the white paper background, and isolate the drawing.Output: Save the isolated drawing as a transparent .png sprite into a designated directory.2. Game Customization & Asset Mapping (Unity Engine)Templates: Build three (3) simple, pre-coded 2D game templates (e.g., an Infinite Runner, a Platformer, and a Flappy Bird/Jumper clone).Asset Mapping: The selected template must dynamically fetch the newly generated .png sprite from the local directory at runtime and map it as the main playable character with a fitted 2D box/capsule collider.Customization Dashboard Screen: Before the game launches, a touchscreen dashboard menu must allow the user to select modular customization variables that alter the template:Accessories: Choose a digital sticker sprite overlay (e.g., a hat, sunglasses, or cape) that automatically anchors to the top bounds of the scanned character.Audio: Select from 3 pre-loaded background music tracks.Variables: Toggle between basic movement modifiers (e.g., Speed: Normal vs. Fast).3. Deployment & Portability (QR Code Output)Local Play: The game must launch instantly in full-screen mode for immediate local arcade-style gameplay.Mobile Portability: Upon game completion, the system must generate a unique QR code. When scanned by a smartphone, this QR code must open a mobile-optimized WebGL version of the exact game played, hosted on a cloud server (using a free-tier hosting framework like Firebase or GitHub Pages to minimize running costs).Key DeliverablesFully functional local application managing the camera control, image processing pipeline, and touchscreen arcade UI dashboard.Three (3) completed Unity game templates fully integrated into the dynamic asset pipeline.Cloud web-hosting pipeline configuration for serving compiled WebGL builds via QR codes.Clean, well-commented Unity project files and source code with full intellectual property ownership handed over to us upon project completion.Multi-language support architecture (Structured text data files for English and Thai; designed so Spanish text can easily be added by us later).

We are seeking a skilled web developer to assist with our ongoing project. The ideal candidate will have experience in web development, CSS, and JavaScript. Responsibilities include developing and maintaining web applications, ensuring responsive design, and optimizing performance. If you have a passion for creating seamless user experiences and are detail-oriented, we would love to hear from you.
i have an active website that i need the following changes on it:
1. Change the home page- give a rebrand feel(should be more modern/dynamic)
2. Cange the descriptions on the website- we will provide
3. Coupons and discount in the home and the order page
4. Redesign the career page - but still allow us to be able to upload images and job descriptions
5. Colour and contrast within chats
6. Redesign our landing pages (ensure color and contrast work well)
7. Change the number of orders completed and the ratings on the home page

Hi
, I’m looking to develop a complete online multiplayer Ludo game based on a reference APK that I can share with you.

Main requirements: Flutter app, 2/4-player real-time multiplayer, private rooms with 8-digit room codes, matchmaking, complete Ludo gameplay, reconnect system, leaderboard, player profiles, game history, notifications, backend/server, admin panel and secure server-side game validation.

I also need the complete source code for the mobile app, backend and admin panel, with the project maintained in my GitHub repository.

Please let me know if you have experience building similar real-time multiplayer games, and share your previous work, estimated development time and total cost.

We need a developer to help build and improve a ROS2-based robot system. The work includes setting up the development environment, integrating sensors and actuators, and improving system performance. You should be comfortable working with existing code, debugging issues, and collaborating with the team to deliver reliable updates. Experience with robot software development and a strong understanding of ROS2 workflows are important for this role.

We need a full stack software engineer to help us build multiple projects securely, include backend buildout and API.

Mid Level Full Stack Developer (PHP / Java / JavaScript)

​Role Overview
We are seeking an experienced Full Stack Developer to design, build, and maintain high-performance web applications and API integrations. In this role, you will take part on end-to-end software development projects- from conceptual architectural design to deployment—delivering tailored digital solutions that optimize operational efficiency and business workflows.
​Key Responsibilities
​Architect, build, and deploy scalable front-end interfaces and robust back-end systems using JavaScript, PHP, Java (Spring Framework), and WordPress.
​Design, implement, and maintain RESTful APIs and database queries to ensure seamless data integration and high system performance.
​Manage the complete software development lifecycle (SDLC), driving projects independently from initial client concept to final delivery.
​Conduct database management and data/query analysis to identify operational risks, optimize backend performance, and recommend strategic improvements.
​Administer and configure deployment environments in Linux (GNU/Linux), ensuring application stability, security, and uptime.
​Collaborate closely with cross-functional teams and clients to translate complex requirements into clean, scalable, and maintainable code.
​Qualifications & Requirements
​Education: Bachelor’s Degree in Computer Engineering or related technical field.
​Backend Expertise: Proven hands-on experience with Java (Spring / Spring Boot), PHP, and database querying/analysis.
​Frontend Expertise: Core proficiency in JavaScript, modern UI practices, and custom WordPress integration/development.
​System Administration: Strong background in GNU Linux environment configuration, troubleshooting, and system management.
​Analytical Skills: Solid background in database risk analysis, performance optimization, and problem-solving.
​Languages: Advanced English and Native Spanish proficiency (written and spoken).
​Soft Skills: High creative capacity, self-motivated, strong independent project management skills, and a collaborative team mindset.

I need help building a trading bot for cryptocurrency trading. The project involves developing a system that can analyze market data, execute trades, and manage risk. I’m looking for someone who can create a reliable, scalable solution and work closely with me to refine the strategy over time. Experience with trading systems and automation is important. Please share relevant examples of similar projects and your approach to building and improving a trading bot.

Title: Developer Needed for a Small, Secure, Web-Based Expense-Tracking Application

I am looking for an experienced and dependable full-stack web developer to create a small, simple, user-friendly expense-tracking application.

The application will initially be used by a small group of authorized users. It should work through a regular web browser on computers, tablets, and mobile phones.

Main requirements:

Secure login for multiple users
Administrator and regular-user roles
Ability to create and manage approximately 8 companies and 16 projects
Companies and projects may be marked active, inactive, or archived
Users can select a company and related project when entering an expense
Entry of amount, date, notes, payment method, bank or credit-card category, and expense type
Date, time, and user identity automatically recorded with every transaction
Ability to save and edit entries
Deleted or modified entries must remain preserved in an administrator audit record
A user requesting deletion must provide an explanation
Administrator should receive notice of important changes or deletions
Search and filter expenses by company, project, user, payment method, and date range
Printable and downloadable reports
Secure database, backups, and an easy-to-use interface
Possibility of expanding the program later

This is an original proprietary project. The selected developer must sign a confidentiality/non-disclosure agreement and an intellectual-property assignment agreement before receiving the complete workflow and detailed specifications.

All source code, database structure, designs, documentation, administrator credentials, and project-specific work must become my exclusive property after payment. Development must take place in a private repository and hosting accounts controlled by me. No subcontracting or disclosure to another person will be permitted without my written approval.

I prefer an individual developer or a very small, clearly identified team. Please provide:

Examples of similar web applications you have personally developed.
Your recommended technology and hosting arrangement.
Your approximate fixed-price estimate and expected completion time.
The number of revisions and post-delivery support included.
Confirmation that you will sign the NDA and intellectual-property agreement.
Confirmation that you will provide complete source code, deployment instructions, database documentation, and administrator access.
Confirmation that you will not use confidential project information or screenshots in your portfolio.

The project should be divided into milestones:

Requirements review and screen mockups
Working prototype
Main functions and reports
Security testing and corrections
Final deployment, source-code transfer, documentation, and training

Please begin your proposal with the words “Secure Expense Application” so I know that you have read the complete posting. Please do not send a generic proposal.

Budget: Please submit a reasonable fixed-price quotation based on the above preliminary requirements. Complete details will be provided to shortlisted candidates after confidentiality arrangements are completed.

I'm looking for Senior developer who can migrate Python project code + PostgreSQL which generates ISO 8583 messages to Java code using Quercus framework + PostgreSQL

AI can be used but manually the generated code must be very carefully revied and compatibility should be 100%

B.Tech Fresher to join us as a Full-Stack Java Developer for a local website project in Hyderabad to gain hands-on, real-world development experience, build their portfolio, and work

Need help creating a 123 sheet for a play class that includes a budget and a schedule. The work should be completed within 1 day. Please share your experience with similar projects and your availability for quick turnaround.

We need a developer to build a bot that automates appointment booking for VFS Global from India to Latvia. The work includes setting up the booking process, handling login and form submission, and ensuring the system can manage appointments efficiently. You should be able to create a reliable solution that supports recurring bookings and provides a smooth user experience. Experience with similar automation projects is important for this role.

CRM Developer — Long-Term Opportunity

Fresh View Business Solutions is looking for an experienced CRM developer to join our growing team. We design and build custom CRM dashboards for service businesses, helping them manage leads, customers, appointments, estimates, jobs, payments, follow-ups, automations, and reporting within one organized system.

This is not a one-time project. We are looking for a dependable developer who wants to build a long-term working relationship and contribute to multiple client CRM projects as our company grows.

Responsibilities:

* Build responsive, production-ready CRM dashboards
* Develop lead pipelines, customer records, calendars, estimates, jobs, invoices, and reporting tools
* Create secure database structures and reliable backend workflows
* Build email, SMS, calendar, payment, and lead-source integrations
* Implement user authentication, permissions, and multi-company data separation
* Troubleshoot bugs without disrupting existing functionality
* Write clean, reusable, well-documented code
* Test features thoroughly before production deployment
* Communicate progress, blockers, and technical recommendations clearly
* Help maintain and improve existing client systems over time

Preferred qualifications:

* Strong experience with React, Next.js, TypeScript, and modern frontend development
* Experience with Supabase, PostgreSQL, database migrations, authentication, and row-level security
* Experience deploying and maintaining applications through Vercel and GitHub
* Strong understanding of APIs, webhooks, email services, SMS providers, OAuth, and third-party integrations
* Experience building CRM, SaaS, admin-dashboard, or business-management software
* Knowledge of responsive design, data security, testing, version control, and production deployment
* Ability to understand a company’s workflow and translate it into functional software
* Strong attention to detail and respect for existing production functionality

The ideal candidate:

* Takes ownership of their work
* Communicates consistently and meets deadlines
* Tests changes instead of assuming they work
* Can work independently while collaborating with a growing team
* Understands the difference between creating a visual demo and building reliable production software
* Is interested in ongoing projects and a long-term role

To apply, please include:

* A brief introduction
* Your location and availability
* Relevant CRM, SaaS, or dashboard experience
* Links to previous projects, GitHub, or portfolio
* Your experience with Next.js, Supabase, Vercel, APIs, and integrations
* Your preferred hourly rate or project-based pricing
* Confirmation that you are interested in long-term work

We are building a strong development team for ongoing CRM projects and are looking for someone who can grow with Fresh View Business Solutions.

We are seeking an experienced Full Stack Developer to assist with ongoing structural and design updates for our consumer directory platform. The ideal candidate will have strong expertise in custom PHP development, database management, and responsive front-end styling using Bootstrap.

Key Responsibilities

Implement modifications to the core directory layout, page hierarchy, and site setup.

Adjust and refine the listing scheme and dynamic display options for consumer listings.

Customize front-end user workflows, forms, and directory search results.

Ensure full responsiveness, fast load times, and cross-browser compatibility.

Troubleshoot existing PHP scripts and database queries to ensure smooth functionality.

Required Qualifications

PHP: Advanced hands-on experience with native PHP (or common directory frameworks).

Front-End: High proficiency in Bootstrap (CSS/JS), HTML5, and JavaScript/jQuery.

Database: Strong SQL skills for managing directory categories, custom fields, and listing data.

Directory Systems: Prior experience building, customizing, or maintaining business or consumer directory platforms is strongly preferred.

Project Details & Application

Type: Freelance / Project-based (Contract)

Location: Remote

To Apply: Please submit a brief cover letter highlighting your experience with PHP and Bootstrap directory projects, along with links to relevant portfolio examples or past work.

Detailed functional specifications and project scope will be provided to eligible candidates upon initial review.

# Senior Full-Stack Developer / Architect — Restaurant Equipment E-Commerce Platform (iOS, Android, Web, Admin)

We're building an e-commerce platform for a commercial restaurant equipment and supplies business — mobile apps (iOS + Android), a web storefront, and an admin dashboard, all backed by one central system.

**This is not a "build me an app" project.** We need someone who can architect this properly, not just wire up screens.

## The core requirement

The app must never have hard-coded products, prices, or inventory. Everything — products, prices, images, categories, stock — lives in a central database and gets managed through an admin dashboard by non-technical staff. When someone changes a price in the admin panel, it should show up in the app automatically, with no new app release needed.

```
Customer App / Website → API → Central Database → Admin Dashboard
```

## What we're building

**Customer-facing:** iOS app, Android app, responsive web storefront (same backend/catalog as the apps — we don't want two databases to maintain).

**Business-facing:** Admin dashboard for managing products, inventory, orders, customers, promotions, and reporting.

**Backend:** REST API, PostgreSQL database, auth, search, payments, image storage, notifications.

## Tech preferences (open to pushback)

- **Mobile:** Flutter, one codebase for iOS/Android. Open to React Native if you can make the case.
- **Backend:** Node.js/TypeScript (NestJS or similar). Open to .NET, Java/Spring, or Python with good reason.
- **Database:** PostgreSQL, properly normalized, built to grow.
- **Search:** Postgres search is fine to start, but the architecture should let us move to OpenSearch/Elasticsearch/Algolia later.
- **Images:** Object storage (S3, R2, Azure Blob, GCS) — not in the database.
- **Payments:** Stripe or another Canadian-friendly provider. Card data should never touch our database directly.

## The tricky part: the product catalog

Products vary wildly. A fryer has oil capacity, BTU, gas type, number of baskets. A fridge has capacity, temperature range, door config, compressor type. We don't want to redesign the database every time we add a new category.

We also need product variants — e.g., a work table in 24"×48", 24"×60", or 30"×60", or an oven in gas/propane/electric — each with its own SKU, price, and inventory.

Tell us how you'd model this.

## Search

Customers should be able to type something like *"48 inch stainless steel table"* and get relevant results — not just exact name matches. Typo tolerance, filters (category, brand, price, availability), sorting.

## Other things that matter

- **Pricing security:** the server calculates final prices — never trust what the app sends.
- **Future inventory integration:** we'll likely connect a POS/ERP/warehouse system down the road. Design for it now.
- **Roles/permissions:** Admin, Manager, Product Manager, Order Manager — regular staff shouldn't touch sensitive settings.
- **Environments:** dev/staging/production, proper Git workflow, CI/CD, tests for critical paths (checkout especially), error monitoring (Sentry or similar).
- **Ownership:** we own the code, repo, database, cloud accounts, App Store/Google Play accounts — everything. Nothing lives under a personal freelancer account.
- **Documentation:** architecture, database, API, deployment, and setup docs thorough enough that another developer could take over.

## Phase 1 (MVP)

Apps + storefront with: browsing, search/filters, product pages with variants, cart, checkout, payment, order history, wishlist, push notifications. Admin with: product/category/brand management, inventory, orders, customers, basic promotions and reporting.

## Later phases (design for these, don't build them yet)

B2B accounts and bulk/custom pricing, real-time inventory sync, freight/shipping calculators, product comparison, reviews, loyalty programs, analytics.

## Answer these in your proposal — generic pitches will be skipped

1. What architecture would you recommend, and why?
2. Flutter, React Native, or native — and why?
3. What backend stack, and why?
4. How would you structure a catalog with thousands of products across very different specs? Give an example.
5. How would you model variants (size, voltage, configuration, separate SKUs)?
6. How would you implement fast, typo-tolerant search and filtering?
7. How do you stop a customer from manipulating price via the app?
8. How would you design this so we can plug in an external inventory system later?
9. What would you use for the admin dashboard?
10. Walk through what happens end-to-end when we change a price in admin and it shows up in the app.
11. How does your architecture hold up at 10,000 / 50,000 / 100,000+ products?
12. What are the biggest security risks here, and how would you handle them?
13. What payment provider would you recommend for a Canadian business, and why?
14. AWS, Azure, GCP, or something else — and why?
15. How would a non-technical employee actually maintain this day to day?
16. Confirm: we own the code, repo, database, infrastructure, and store accounts.
17. What documentation do you hand over at the end?
18. Share 2–3 real e-commerce projects you've built — your role, stack, database, product count, whether payments were live, whether you built the admin system.

## Proposal format

1. Recommended architecture
2. Tech stack
3. Relevant experience
4. Product catalog approach
5. Search approach
6. Payment approach
7. Inventory integration approach
8. Security approach
9. Timeline estimate
10. Cost estimate
11. Risks/challenges you see
12. Questions you have for us

## How we're deciding

Not going with the lowest bid. We're looking for strong architecture and database skills, real e-commerce/backend experience, security awareness, clean code, good documentation, and someone who can clearly explain *why* they're making the choices they're making. If you think there's a better approach than what's outlined here, tell us — that counts in your favor, not against you.

Bonus points for experience with: restaurant equipment or B2B e-commerce, Shopify/WooCommerce, Stripe, PostgreSQL, Flutter or React Native, NestJS, AWS/Azure, Elasticsearch/OpenSearch/Algolia, POS/ERP integrations, or Canadian tax/e-commerce requirements.

We want this built as a real long-term platform — one we can keep adding products, suppliers, features, and integrations to for years, not a one-off app.

i have a specific job im looking to get done, i need someone to create a calibration report for me with certian cars and information for the report i can provide an examplem, i need someone consistent. i need it to be a ltitle different everytime so they dont look the same if it is somerthing you are interested in please let me know as soon as possible. i am going to attach an actual calibration report

We need a short, focused anatomy program for a Pilates Certification course. The work includes creating clear, concise content that supports the certification curriculum and helps students understand key anatomy concepts related to Pilates. This is a small project for someone who can deliver accurate, easy-to-follow material and collaborate closely with the course team. Please share relevant experience with educational content creation or anatomy-related instruction.

Here's the message for Chad:

---

Hi Chad,

I'm building a Bubble.io app called GAU Hub — a kids' companion mobile app for a book/animation franchise. It's built page-by-page from a design mockup, mostly complete. I have two pieces of work I'd like you to quote together.

**1) Bug fix — character movement / detail page data handoff**
I have a Bubble app where a specific element ("Porky Georgey") is supposed to move across 5 slot positions when two buttons are tapped, and where tapping a character tile is supposed to open a detail page with that character's data. Both have had persistent tap/workflow issues over an extended debugging period, including:
- One button's workflow was completely empty (no click action wired at all)
- Fruit catch-detection was comparing two incompatible value scales, so it could never register a catch
- A "game_running" flag was gating button actions but wasn't reliably being set true, silently blocking movement
- A z-index/overlap issue between two layered groups was intercepting taps before they reached the buttons underneath
- Bubble support closed the related ticket claiming it's resolved, but testing still shows the movement doesn't work reliably

I need someone to get into the editor, verify each of these issues end-to-end (not just theoretically), and confirm the character reliably moves and the detail page reliably populates on tap.

**2) New mini game — fruit catching game**
Porky Georgey stands under a tree; fruit (apples, pears, etc.) drops from the tree and the player catches it in a basket.

Requirements:
- 30 second timer per round, with a working countdown
- Target age group: 7 to 10 years old
- Layout: points counter on the left, timer in the middle, basket display on the bottom right
- Caught fruit accumulates in the basket on the right; points accumulate on the left
- No fail state / no penalty for misses — keep it positive and encouraging for young kids
- Show final fruit count when time runs out

Can you review the app and give me a combined fixed price and turnaround time for both pieces?

Thanks,
Chef Jack

---

Want any changes before you send it?

I'm looking for an experienced Solana trading bot developer to act as a technical advisor while I build a bot for scalping newly launched meme coins. I'll write all the code myself. What I need is your practical knowledge: the architecture and theory behind it, what actually works in live trading and what doesn't, and the details that only come from experience, such as RPC node choices, priority fees, Jito tips, latency, and handling failed transactions.

I already have two trading bots running and a solid understanding of trading and how bots work, so I'm not looking for hand-holding. The format would be an initial overview call on how to structure the bot, then occasional check-ins where you review my progress and give pointers along the way.

Proven experience building and running on-chain trading bots on Solana is required. In your proposal, please describe a bot you've built or run live, and one lesson you learned the hard way.

We are looking for an experienced Technical Recruiter who can help us source, screen, and hire qualified Software Engineers for our open positions.

The ideal recruiter should have strong experience in technical recruitment and be comfortable finding software engineering talent through LinkedIn Recruiter, job boards, GitHub, Boolean search, and other sourcing platforms.

What You’ll Do
Source qualified Software Engineers based on our hiring requirements
Search for candidates using LinkedIn Recruiter, GitHub, job boards, and other sourcing tools
Build targeted candidate lists based on skills, experience, location, and role requirements
Review and screen resumes and profiles
Conduct initial candidate screening and qualification
Contact candidates and explain the opportunity
Manage candidate communication and follow-ups
Present qualified candidates for interviews
Coordinate with us throughout the hiring process
Help move candidates from sourcing through interview and offer stages
Maintain accurate candidate tracking and recruitment records
Roles We May Hire For

Depending on our current hiring needs, positions may include:

Software Engineer
Full Stack Developer
Backend Engineer
Frontend Engineer
.NET Developer
Java Developer
Python Developer
React Developer
Software Engineering Consultant
Other technical/software engineering positions
Requirements
2+ years of experience in technical/software engineering recruitment
Proven experience sourcing Software Engineers
Strong understanding of technical skills, technologies, and engineering roles
Experience with LinkedIn Recruiter or similar sourcing platforms
Strong Boolean search and candidate research skills
Ability to identify qualified candidates rather than simply collecting profiles
Strong communication and candidate engagement skills
Experience with US/Canada hiring is a strong plus
Ability to work independently and consistently deliver qualified candidates
What We’re Looking For

We want someone who can understand our requirements, identify the right talent, approach candidates professionally, and help us get qualified Software Engineers into the interview and hiring pipeline.

Please include examples of the types of Software Engineers you have recruited previously, the markets you have worked in, and the sourcing tools you regularly use.

To apply, please briefly share:

Your technical recruiting experience
The types of Software Engineers you have recruited
Your primary sourcing tools
The countries/markets you have recruited for
Your availability and preferred working arrangement

We are looking for a recruiter who can build a reliable pipeline and help us make successful technical hires.

Core Stack: Java 21, Spring Boot, Angular 17–21, TypeScript, PrimeNG, Oracle, SQL Server
Language: French C1/Expert + Professional English
Work Environment: Agile / Scrum
Availability: Remote

We are looking for a Senior Java Full-Stack Developer to join a multidisciplinary Agile team working on enterprise applications across transaction processing, compliance, KYC, distribution, asset management, and life insurance.

The role involves both new development and application maintenance, including bug fixing, change requests, testing, technical documentation, troubleshooting, and production deployments.

Key Responsibilities
You will analyse user requirements, contribute to functional specifications, and develop and test both backend and frontend applications. You will maintain and continuously improve existing solutions while collaborating across Agile squads based on business priorities.

The role also includes preparing technical documentation, deploying applications to production and non-production environments, troubleshooting technical issues, and ensuring application stability and reliability.

Requirements
Strong hands-on experience with Java 21, Spring, and Spring Boot is required, along with practical experience in Angular 17–21, PrimeNG, HTML, CSS, and TypeScript.

You should have experience with Hibernate, Lombok, Liquibase, Maven, Git, Jenkins, and DevOps toolchains, as well as strong experience working with SQL Server and Oracle databases.

Solid web application development experience and knowledge of SOAP and REST web services are essential. Experience working in Agile/Scrum environments is also required.

Familiarity with AI-assisted development or vibe coding is expected. Candidates must have French at C1/Expert level and professional English communication skills.

Nice to Have
Experience in life insurance, banking, compliance, KYC, or asset management will be an advantage. Knowledge of Jira and Solife is also desirable.

Ideal Candidate
The ideal candidate is a senior, hands-on developer who can work across both frontend and backend technologies, maintain complex enterprise applications, troubleshoot production issues, and collaborate effectively with multidisciplinary Agile teams.

We are seeking a skilled developer to create an AI-powered chatbot for our website. The project involves designing and implementing a chatbot that can handle customer inquiries, provide relevant information, and improve user engagement. The ideal candidate should have experience with AI chatbot development and be able to deliver a functional, user-friendly solution. This is a part-time project with a budget of $19 to $40 per hour.

We are looking for an experienced Full Stack Developer for AI/LLM Integration with strong expertise in healthcare, life sciences, and regulated environments.

The ideal candidate has hands-on experience taking AI features to production in healthcare platforms: integrating LLM APIs, migrating workloads to HIPAA-eligible infrastructure, and ensuring compliance, security, and operational reliability under real user volume.

Requirements:

- 8+ years of software engineering experience
- Strong TypeScript and Node.js expertise (Express, tRPC, REST APIs)
- Python for AI/ML workflows where needed
- Experience with AWS Bedrock, Anthropic, OpenAI, or similar AI platforms
- AI API integration and LLM implementation experience (streaming, prompt/output validation, cost and latency tuning)
- Healthcare, payer, pharma, or clinical technology background
- Experience working with HIPAA-compliant systems (BAA-covered data flows, audit logging, session security)
- Strong API architecture and backend development skills
- Experience stabilizing and extending existing production codebases, including AI-generated code

Nice to Have:

- CMS-regulated healthcare experience (prior authorization, utilization management, claims, risk adjustment, care management)
- Clinical trials, pharmacovigilance, or GxP-validated systems
- RAG systems, embeddings, and document extraction pipelines
- React frontend experience
- AWS (RDS, S3, Secrets Manager), Docker, CI/CD
- MySQL or PostgreSQL with ORM migrations (Drizzle, Prisma)

Responsibilities:

- Design and implement AI-powered healthcare workflows
- Integrate LLM APIs into existing software platforms and migrate off non-compliant vendors
- Build secure and scalable backend services and APIs
- Advise on AI architecture, HIPAA data flows, and production deployment
- Implement audit logging, access controls, and regression test coverage
- Ensure reliability, compliance, and maintainability of AI solutions

Please include examples of healthcare AI, clinical technology, payer systems, or other regulated-industry projects you have worked on.

We need a developer to build an AI-powered chatbot for our website. The project includes designing the chatbot flow, integrating it with our site, and ensuring it provides a smooth user experience. You should be able to work independently, communicate clearly, and deliver a reliable solution on time.

The mission

Take Parinita Enclave and Parinita Almanac through a tightly controlled four-day launch sprint and establish a production-grade path that is technically defensible.

The four-day objective is a controlled production launch of a defined surface, not an artificial claim that every roadmap feature has reached GA. We will cut optional scope before weakening tenant isolation, durability, authorization, evidence, recoverability, or RAG grounding.

By the end of the sprint, the team must be able to show what is:

LIVE / ACCEPTED — exercised against real dependencies and cleared for the controlled launch surface.

INTEGRATION-GATED — implemented but still waiting on a real service, environment, test, benchmark, or acceptance condition.

ROADMAP / DESIGNED — intentionally not represented as production functionality.

What we are building

Parinita Enclave — Object Trust Runtime

Enclave is not intended to reinvent disk-level distributed storage. Ceph/RADOS/RGW is the Tier-0 durable object-storage substrate. Parinita's differentiation sits above it.

Stratum is the governed object transaction and trust layer. It owns the logical object lifecycle, tenant scope, object/version identity, policy envelope, Object Trust Contract, Object Passport, retention/legal-hold extensions, trust inheritance, capability leases, evidence state, and the point at which an object becomes visible as committed Enclave state.

Flash is the object-intelligence layer. It enriches objects with AI-driven classification and analysis while failing safely if AI dependencies are unavailable.

Witness establishes identity, authority, delegation, and scoped capability.

Secure evaluates whether the proposed action is permitted in the current context.

Chrysalis provides the evidence/finality integration for consequential state transitions.

The intended high-assurance object flow is conceptually:

Client → Enclave API / Stratum → Witness → Secure → Ceph durable object → Chrysalis evidence → Stratum COMMITTED/VISIBLE

If evidence or policy requirements are not satisfied, the object must not be prematurely represented as a successful high-assurance Enclave commit. The implementation must use explicit durable states and recovery semantics rather than pretending Ceph and Chrysalis share a single distributed ACID transaction.

Parinita Almanac — Sovereign, Verifiable RAG

Almanac is first and foremost a production RAG platform. It is not being repositioned away from RAG.

The core path is:

Authorized Enclave source → extract → chunk → classify → embed → hybrid retrieve → rerank → assemble grounded context → approved model generation → claim/evidence validation → answer + provenance/evidence

The 10/10 Almanac features strengthen that RAG pipeline:

Knowledge Passport — lineage for a retrieved entry/chunk back to the exact source object/version and transformation state.

Knowledge Release — a versioned corpus/index release so a consultation can identify the exact knowledge state used.

Consultation Contract — principal, purpose, corpus scope, policy, jurisdiction, model/use constraints, freshness and evidence requirements for a RAG request.

ProofRAG — material claims are mapped to authorized source evidence; insufficiently supported claims must be flagged or withheld rather than disguised by decorative citations.

Answer Passport — query fingerprint, knowledge release, retrieved evidence, ranking/reranking context, model/version, output hash, claim/evidence map, and evidence references.

Trust inheritance — applicable Enclave restrictions follow the source into chunks and derived RAG artifacts.

Contradiction handling — conflicting authoritative sources are surfaced rather than silently resolved by similarity score alone.

Knowledge recall / replay foundations — identify downstream RAG artifacts affected by a corrected or revoked source and reconstruct historical consultation state where evidence exists.

The product relationship is simple:

Enclave governs the source object and what it is allowed to become. Almanac retrieves the right authorized evidence and produces traceable RAG answers from it.

Target production architecture

Layer

Primary technology / service

Responsibility

Durable object substrate

Ceph / RADOS / RGW

S3-compatible object storage, versions, replication/EC, scrub/recovery, Object Lock where applicable

Enclave transaction plane

Stratum services + PostgreSQL

Governed object state, tenant/version identity, trust contract, passport, leases, evidence state, visibility

Object intelligence

Flash

Classification, sensitivity/secret signals, content intelligence, anomaly/ransomware signals, enrichment

Identity / authority

Witness + OIDC/JWT/JWKS

Principal identity, delegation, scoped authority, short-lived capabilities

Runtime policy

Secure

Contextual allow/deny and policy decision for protected actions

Evidence

Chrysalis

Consequential-event submission, finality state, verification reference

RAG metadata / retrieval

PostgreSQL + pgvector or approved equivalent

Corpora, entries, embeddings, full-text/vector indexes, retrieval state

Almanac RAG

Almanac / Tracker services

Ingest, chunk, embed, hybrid retrieval, rerank, context, grounded generation, ProofRAG

Model execution

Denizen Blu / approved model endpoint

Embeddings, reranking and/or generation as configured and accepted

Deployment

Kubernetes + Helm or approved target

Scheduling, rollout, secrets integration, network controls, scaling, health

Observability

Prometheus/OpenTelemetry-compatible stack or approved equivalent

Metrics, traces, logs, SLO evidence, alerting

The exact production dependency endpoints and credentials must be supplied and validated in the deployment environment. The team must not substitute local mocks and then label the result “production.”

Open roles

We expect to engage multiple people. Senior, Staff and Principal-level candidates are welcome across the roles below. Strong engineers can own more than one workstream, but nobody is expected to be expert in every layer.

1. Technical Launch Lead / Staff-Principal Distributed Systems Engineer

Mission

Own the end-to-end launch architecture and force clarity at every boundary between storage, object state, identity, policy, evidence, RAG and operations.

Responsibilities

Audit the current Enclave and Almanac repositories, deployment manifests, database migrations, tests and runbooks.

Convert ambiguous cross-service behavior into explicit contracts, state machines and failure semantics.

Define the launch surface and decide what is accepted, gated or removed from scope.

Own the object state progression across Stratum, Ceph and Chrysalis without false atomicity claims.

Own service-to-service dependency contracts between Enclave, Almanac, Witness, Secure, Chrysalis and model endpoints.

Review authorization boundaries and make sure backend/internal calls cannot silently bypass the external trust model.

Establish idempotency, retry, timeout, circuit-breaker and reconciliation rules for cross-system operations.

Drive architecture decisions quickly; reject unnecessary rewrites that endanger the four-day target.

Coordinate technical owners, unblock dependencies, run daily go/no-go checkpoints and maintain the acceptance matrix.

Lead the final launch review and issue a clear GO / CONDITIONAL GO / NO-GO with evidence.

Day-4 deliverables

Approved architecture and dependency contract map.

Cross-product state/failure model.

Closed list of critical blockers for the launch surface.

Reproducible deployment path and acceptance report.

Explicit inventory of live vs integration-gated vs roadmap capabilities.

Must have

Production distributed-systems experience across multiple stateful services.

Strong PostgreSQL/data-consistency background.

Experience designing idempotent workflows and recovery after partial failure.

Ability to read Python quickly; Go or Rust experience is highly valuable.

Experience making production launch decisions under real time constraints.

2. Ceph / RGW Storage Platform Engineer

Mission

Make Tier-0 storage boring, recoverable and measurable, so Parinita engineering can concentrate on the trust and AI layers above it.

Responsibilities

Deploy or validate the target Ceph cluster and RGW topology.

Configure buckets/pools, versioning, replication or erasure coding, placement rules and Object Lock/retention capabilities where required.

Validate S3 behavior required by Enclave, including multipart, range requests, metadata, version IDs and error semantics.

Define and test the no-bypass topology: protected Enclave namespaces must not be exposed to users/services in a way that allows them to write around Stratum policy.

Validate capacity, headroom, recovery behavior, scrub/deep-scrub, rebalance behavior and expected failure domains.

Exercise disk/OSD/node failure and recovery rather than relying on documentation.

Establish metrics/alerts for cluster health, degraded PGs, recovery pressure, capacity thresholds and RGW errors/latency.

Document operational procedures for expansion, replacement, recovery and maintenance.

Work with the backend engineer to align Ceph object/version semantics with Enclave logical transaction state.

Day-4 deliverables

Working target RGW endpoint with documented storage classes/pools.

S3 contract validation for the launch surface.

No-bypass storage/network design and test evidence.

At least one tested storage failure/recovery scenario.

Ceph health/alert dashboard requirements and operator runbook.

Must have

Hands-on production Ceph/RADOS/RGW administration.

Real experience with OSD failure, PG recovery, EC/replication, scrub and cluster performance.

S3 semantics beyond simple PUT/GET demos.

Understanding of WORM/Object Lock and retention behavior.

Strong plus

Large NVMe Ceph clusters, multisite RGW, Kubernetes/Rook-Ceph, performance tuning, backup appliances or regulated storage environments.

3. Backend / Enclave Object Trust Engineer

Mission

Make Stratum the enforceable object trust boundary above Ceph.

Responsibilities

Implement/harden Stratum object APIs and durable state transitions.

Ensure object/version identity is stable and cryptographically bound to the stored content and metadata required by policy.

Implement Object Trust Contracts and Object Passports as real persisted, versioned data structures.

Implement short-lived Object Capability Leases scoped to principal, object/version, action, purpose, expiry and relevant restrictions.

Enforce retention/legal-hold behavior without depending only on application convention.

Implement evidence-gated visibility using explicit states such as PREPARED/PENDING/DURABLE/ATTESTED/COMMITTED/FAILED/QUARANTINED as appropriate.

Ensure retries cannot double-commit, lose evidence links or surface an object prematurely.

Build reconciliation workers for partial success: e.g., Ceph write succeeded but Chrysalis or metadata transition failed.

Implement trust inheritance hooks for downstream Almanac ingestion and derived artifacts.

Eliminate unsafe development fallbacks from production paths.

Write negative and concurrency tests around state transitions.

Day-4 deliverables

Tested governed PUT/GET/version flow over the real Ceph/RGW dependency.

Persisted Object Trust Contract + Object Passport lifecycle.

Evidence-gated commit/recovery behavior.

Capability-lease enforcement for at least the controlled launch surface.

Negative tests proving direct invalid transitions are rejected.

Must have

Strong backend engineering in Python, Go, Rust, Java or equivalent.

PostgreSQL transactions, locking, migrations, concurrency and idempotency.

Durable workflow/state-machine design.

Secure API design and tenant isolation.

Strong plus

S3 integrations, cryptographic metadata, policy engines, audit/evidence systems, distributed transaction patterns, event/outbox architectures.

4. RAG / Retrieval / AI Engineer — Almanac

Mission

Ship a production RAG path that is retrieval-first, evidence-aware and precise about what it knows.

Responsibilities

Harden source ingestion from authorized Enclave objects.

Implement reliable extraction for the accepted launch document types and record parser/version metadata.

Design chunking appropriate to source type and preserve exact source coordinates needed for citations.

Build and validate embedding generation, version pinning and index compatibility.

Operate PostgreSQL/pgvector or the accepted retrieval backend with tenant/corpus isolation.

Implement hybrid retrieval (vector + lexical/filtering), candidate generation, reranking and deterministic evidence packaging.

Create/version Knowledge Passports and Knowledge Releases.

Implement Consultation Contracts that constrain corpus, purpose, principal, policy, model, freshness and evidence requirements.

Harden prompt-injection/content-poisoning handling so retrieved document text is treated as untrusted evidence, not executable instruction.

Implement ProofRAG at the claim/evidence level, not merely by checking whether the LLM emitted [1] or [E3] tokens.

Require abstention/insufficient-evidence behavior when material claims are unsupported.

Surface contradictory source evidence where confidence/authority cannot safely resolve it.

Generate Answer Passports linking the answer to source versions, retrieval state, model/version, claim/evidence map and evidence references.

Build evaluation cases for retrieval quality, citation precision, answer grounding, contradiction handling and negative authorization.

Day-4 deliverables

Working Enclave-source-to-RAG-answer flow against real dependencies.

Versioned source/chunk/embedding/retrieval lineage for the launch corpus.

Hybrid retrieval + reranking evaluation report.

Claim-level citation/grounding tests with abstention cases.

Answer Passport for every accepted controlled-launch RAG answer.

Must have

Production RAG experience beyond prompt demos.

Embeddings, vector search, lexical retrieval and rerankers.

pgvector, Elasticsearch/OpenSearch, Vespa, Qdrant, Milvus or equivalent hands-on experience.

Document ingestion/extraction and chunking trade-offs.

RAG evaluation: recall/precision, ranking quality, citation quality, answer grounding and failure analysis.

Strong plus

Enterprise/regulated RAG, provenance, temporal/versioned retrieval, multimodal retrieval, knowledge graphs, secure RAG, red-team testing for prompt injection.

5. Security / Identity / Policy Engineer

Mission

Ensure every protected action has a real identity, scoped authority and deny-by-default policy path.

Responsibilities

Integrate/validate OIDC/JWT/JWKS authentication in production mode.

Integrate Witness authority/delegation decisions for customer, agent and service principals.

Integrate Secure runtime policy checks for protected operations.

Define service identities and least-privilege permissions across Enclave, Almanac, Ceph/RGW, PostgreSQL, Chrysalis and model endpoints.

Remove development tenant-header/default-token behavior from the production path.

Design capability-lease verification and anti-replay/expiry behavior.

Validate secrets handling and KMS/HSM integration contracts; do not embed long-lived secrets in images/config maps.

Establish mTLS/service-authentication requirements where appropriate.

Lock down network egress/ingress so “sovereign” does not mean a NetworkPolicy that still permits unrestricted outbound traffic.

Build negative tests for cross-tenant access, privilege escalation, invalid delegation, expired capability, bad issuer/audience, policy-denied operations and internal-service bypass.

Review audit logs to ensure sensitive payloads/secrets are not leaked.

Day-4 deliverables

Production auth path exercised with the real identity endpoint or explicitly gated if unavailable.

Witness/Secure decision matrix for launch operations.

Service-to-service identity map and secrets plan.

Negative-security test results.

Network/egress policy appropriate to the launch environment.

Must have

OIDC/OAuth2/JWT/JWKS and service identity.

RBAC/ABAC/capability/delegation patterns.

API and microservice threat modeling.

Secrets/key management; KMS/HSM integration patterns.

Network segmentation and deny-by-default controls.

6. Platform / SRE / Kubernetes Engineer

Mission

Turn the code into a repeatable, observable, recoverable production service.

Responsibilities

Harden Docker images and Helm/Kubernetes manifests or the approved deployment target.

Implement production configuration validation and fail-closed startup for required dependencies.

Manage PostgreSQL/pgvector deployment assumptions, migrations and upgrade/rollback safety.

Configure readiness/liveness/startup probes that reflect real dependency state without causing restart storms.

Define resource requests/limits, autoscaling, disruption budgets and rollout policy.

Implement secrets integration and immutable image/version promotion.

Establish CI/CD checks: lint, tests, dependency/security scan, migration check, image scan and deploy validation.

Instrument metrics, traces and structured logs for Enclave and Almanac critical paths.

Build dashboards/alerts for object state backlog, failed evidence submissions, Flash/AI queue health, ingestion failures, index freshness, RAG latency, retrieval quality signals and dependency health.

Execute backup/restore for PostgreSQL state and document Ceph recovery dependencies.

Exercise rollout, rollback and restore before customer exposure.

Create a launch-day runbook and incident escalation path.

Day-4 deliverables

One-command or documented reproducible deployment from approved prerequisites.

Immutable image/version manifest.

Monitoring/alerting baseline.

Exercised DB backup/restore and application rollback.

Production runbook with dependency failure actions.

Must have

Kubernetes/Helm or equivalent production operations.

Stateful workloads and PostgreSQL operations.

CI/CD, containers, secret management and observability.

Real incident/recovery experience.

7. QA / Performance / Resilience Engineer

Mission

Prove the launch surface by trying to break it.

Responsibilities

Build a cross-product acceptance matrix covering functionality, isolation, security, recovery, performance and evidence.

Create deterministic integration fixtures for Enclave + Almanac.

Test cross-tenant/cross-corpus denial paths.

Exercise retries, duplicate requests, stale tokens, expired leases and partial dependency failures.

Test service restart during object commit, evidence submission, ingestion and RAG consultation.

Validate no object becomes visible before its required Enclave commit state.

Validate no Almanac answer can retrieve from an unauthorized corpus.

Validate ProofRAG behavior on supported claims, unsupported claims, conflicting sources and malicious prompt-injection content.

Establish baseline throughput/latency for the launch surface and record the test method rather than publishing unmeasured SLA claims.

Exercise Ceph failure/recovery with the storage engineer and DB restore/rollback with SRE.

Produce a final release-evidence pack with test inputs, results, failures, residual risks and rerun instructions.

Day-4 deliverables

Release acceptance matrix with PASS/FAIL/GATED status.

Functional + negative-security + tenant-isolation suite.

Dependency-outage/restart/recovery evidence.

Initial performance baseline with methodology.

Final critical/high defect list and retest status.

Must have

Production integration/acceptance testing across distributed services.

Negative security and tenant-isolation testing.

Load/performance testing with reproducible methodology.

Failure injection and recovery validation.

8. Optional: AI/RAG Evaluation & Red-Team Specialist

We may also engage a dedicated evaluator if the RAG engineer should remain focused on implementation.

Focus

Build a gold evaluation set for retrieval and grounded answer quality.

Measure retrieval recall, ranking quality, source attribution, unsupported-claim rate and abstention quality.

Adversarially test indirect prompt injection, conflicting documents, stale/superseded content and poisoned sources.

Review Answer Passports and claim/evidence maps for false confidence.

Define regression gates for model, embedding, reranker and chunking changes.

Day 0 — prerequisites before the four-day clock starts

The sprint is only meaningful if the team has access to real dependencies. Before Day 1, Parinita and the selected team should confirm availability of:

Current Enclave and Almanac repositories and issue/acceptance lists.

Target deployment environment and sufficient cluster privileges.

Ceph/RGW endpoint and administrative contact/credentials required for setup.

PostgreSQL/pgvector or authority to deploy it.

OIDC/JWKS issuer and test principals.

Witness, Secure and Chrysalis integration endpoints or a written statement that a specific dependency remains gated.

Approved model/embedding/reranking endpoints for Almanac.

Required DNS/TLS/secrets/KMS/HSM integration details for the launch environment.

A representative but safe test corpus and tenant matrix.

Named Parinita decision-maker for rapid architecture/scope decisions.

A missing external dependency does not justify a fake local substitute being called production. It becomes an explicit integration gate.

Four-day execution plan

Day 1 — Establish truth, deploy foundations, freeze contracts

Morning

Repository and deployment audit.

Re-run existing tests and classify what they actually prove.

Identify critical defects and stale/hallucinated assumptions.

Freeze launch scope and assign workstream owners.

Validate Ceph, DB, identity, policy, evidence and model endpoints.

Afternoon

Deploy/validate Ceph RGW + PostgreSQL/pgvector + application namespaces.

Apply DB migrations and seed controlled test tenants.

Establish service identities/secrets/network boundaries.

Define Stratum object-state and Almanac consultation-state contracts.

End-of-day exit criteria

All required dependencies are either reachable and tested or explicitly GATED.

Critical architecture decisions are closed.

The team can deploy all in-scope services in the target environment.

No one is still assuming a mock/local service is equivalent to the production dependency.

Day 2 — Enclave governed object lifecycle

Morning

Prove governed PUT/GET/version/list flow through Stratum over Ceph.

Persist object/version identity, hash, trust contract and passport.

Validate tenant boundaries, retention/legal hold and no-bypass topology.

Afternoon

Integrate Witness/Secure on protected actions.

Exercise Chrysalis submission/finality states for evidence-gated operations.

Validate partial-failure reconciliation and idempotent retry.

Validate Flash enrichment state and safe failure behavior.

End-of-day exit criteria

A controlled launch tenant can write/read a governed object.

Direct policy bypass is demonstrably blocked for the protected namespace.

Object state survives process restart and dependency failure.

A failed evidence/AI dependency does not silently produce a false successful state.

Day 3 — Almanac source-to-answer RAG lineage

Morning

Ingest authorized Enclave objects.

Extract/chunk supported documents with exact source coordinates.

Generate embeddings with pinned model/version and build a Knowledge Release.

Validate tenant/corpus isolation and retrieval filters.

Afternoon

Exercise hybrid retrieval + reranking against a representative evaluation set.

Apply Consultation Contracts before retrieval/generation.

Generate grounded answers through the approved model endpoint.

Enforce claim/evidence mapping and abstention.

Produce Answer Passports tied to exact object versions and Knowledge Release.

End-of-day exit criteria

The team can trace an accepted answer from claim → retrieved passage → chunk → source object/version.

Unauthorized corpus retrieval fails.

Unsupported questions demonstrate safe insufficient-evidence behavior.

Prompt-injection content is treated as untrusted evidence rather than higher-priority instruction.

Day 4 — Break it, recover it, measure it, launch only what passes

Morning

Cross-tenant negative tests.

Kill/restart critical services during object write and RAG consultation.

Simulate identity/policy/evidence/model dependency outage.

Exercise DB backup/restore and application rollback.

Run controlled load/performance baseline.

Afternoon

Close critical/high launch blockers or remove affected surface from launch.

Run final acceptance suite.

Review security, data isolation, recovery and observability evidence.

Publish live/gated/roadmap matrix.

Issue GO / CONDITIONAL GO / NO-GO.

Launch rule: no deadline overrides a failed trust, tenant-isolation, durability, authorization, evidence or grounded-RAG gate.

Non-negotiable acceptance requirements

Enclave

Protected writes go through the governed Stratum path.

Production tenant identity is not taken from a caller-controlled development header.

Object Trust Contract and Object Passport are durable and tied to the exact object version.

Required evidence state is distinguishable as submitted/finalized/failed; an arbitrary ID is not assumed to prove finality.

Partial failure is recoverable and idempotent.

Retention/legal hold behavior is negative-tested.

Flash failure is visible and does not silently fabricate semantic output.

Ceph degradation/recovery behavior is understood and observable.

Almanac RAG

Authorization and corpus scoping happen before retrieval.

Exact source object/version lineage survives extraction, chunking and indexing.

Embedding/rerank/generation model/version are recorded where needed for reproducibility/audit.

Retrieval uses the accepted combination of vector, lexical and structured filtering appropriate to the launch corpus.

Material claims have source evidence or are explicitly unsupported/abstained.

Contradictory sources are not silently disguised as a single fact where the system lacks authority to resolve them.

Answer Passport records the accepted consultation lineage.

An LLM's own “evidence analysis” is never treated as independent proof that the answer is true.

Platform / security

No default secrets, dev auth, mock tenants or permissive production fallback.

Egress/ingress rules are explicit and testable.

Backups restore; rollbacks work.

Dashboards/alerts expose queues, dependency failures and degraded states.

The exact deployed image/build can be identified.

Production claims are tied to acceptance evidence, not architecture diagrams.

Engineering rules for this sprint

1. Do not rewrite Ceph. Use the mature storage substrate unless a specific launch-blocking defect proves otherwise.

2. Do not hide partial failure. Persist explicit state and reconcile it.

3. Do not call local mocks “production integrations.” Mark the dependency gated.

4. Do not make RAG look grounded by decorating answers with citations. Prove claim-to-source mapping for the accepted surface.

5. Do not let AI-generated analysis become the root of trust. Cryptographic evidence can prove what happened, not whether an LLM's reasoning was correct.

6. Do not publish unmeasured performance/SLA claims. Record methodology, then publish accepted measurements.

7. Do not bypass policy for internal services. Service-to-service authority is still authority.

8. Do not trade isolation, durability or recoverability for the four-day deadline. Reduce scope instead.

What strong candidates look like

You have personally operated systems where failure mattered. You can describe what broke, how you found it, what state was left behind, how you recovered it, and how you prevented recurrence.

We value engineers who are comfortable saying “this is implemented but not yet production-accepted” rather than turning roadmap intent into claims.

Strong candidates typically have several of the following:

Stateful distributed systems under real load.

Ceph/RADOS/RGW, object storage, S3 or storage control planes.

PostgreSQL transactions/migrations/HA and pgvector or comparable retrieval systems.

Production RAG with measurable retrieval and grounding evaluation.

OIDC/JWT/JWKS, policy engines, capability/delegation systems.

Kubernetes/Helm and production SRE.

Evidence/provenance/audit pipelines.

Cryptographic service integrations, KMS/HSM or signing systems.

Multi-tenant security architecture.

Incident response and disaster recovery.

Current services are heavily Python-oriented. Strong Go or Rust experience is valuable, particularly for systems/performance work.

Who should not apply

This role is not a fit if your relevant experience is primarily:

Building chatbot demos around managed APIs.

Running local Docker Compose and calling it production.

Writing architecture documents without owning deployment/failure behavior.

Assuming Kubernetes automatically solves security/reliability.

Treating a vector database as a complete RAG system.

Recommending a new framework/database/storage engine before understanding the existing code.

Avoiding operational responsibility after merge.

Selection process

We want a fast, high-signal process because the work is immediate.

Step 1 — written response. Answer the role-specific questions below and include links or concise descriptions of relevant production work.

Step 2 — technical discussion. 30–45 minutes focused on one real system you owned and one failure scenario relevant to your workstream.

Step 3 — repo/architecture fit. Selected candidates review the launch brief/repository and identify the first changes they would make. We are evaluating judgment, not presentation theater.

Step 4 — engagement and sprint start. Confirm scope, rate/commercial terms, availability, owner and Day-1 deliverables.

Application questions

Answer the general questions plus those relevant to your role.

General

1. Which role(s) are you applying for? State Senior / Staff / Principal level if useful, but emphasize what you can personally own.

2. What can you commit to delivering in the next four days?

3. Describe one production system you personally built or operated that is directly relevant. What failed in production and what did you do?

4. What timezone are you in, what hours can you overlap, and when can you start?

5. Do you prefer hourly, daily or fixed-scope commercial terms? Provide your rate/proposal.

6. Are you applying individually or as part of a team? If a team, list each person, role and concrete deliverable.

Storage / Ceph

7. Describe a real Ceph/RGW incident you handled: what failed, what did cluster state look like, how did you recover it, and what did you change afterward?

8. How would you prevent users and internal services from bypassing Stratum while still allowing Stratum/RGW to scale?

9. For a high-assurance bucket, how would you combine Ceph Object Lock/retention with an application-level governed state machine without creating contradictory sources of truth?

Backend / distributed systems

10. Design an evidence-gated Enclave PUT where Ceph can succeed and Chrysalis can time out. What durable states, idempotency keys, retry rules and reconciliation jobs do you use?

11. How do you prevent a retry from producing two logical Enclave versions or exposing a PENDING object as COMMITTED?

12. What belongs in the Object Trust Contract vs the Object Passport vs operational metadata?

RAG / retrieval / AI

13. How would you evaluate whether hybrid retrieval + reranking actually improved Almanac instead of merely changing scores?

14. How would you enforce claim-level evidence and abstention rather than checking that an answer contains citation markers?

15. How would you represent versioned corpus/index state so a historical Answer Passport can identify what was searchable at consultation time?

16. How would you handle two authoritative source documents that materially contradict each other?

17. Describe your defense against indirect prompt injection contained inside retrieved enterprise documents.

Security / policy

18. How would you model authority for a human, an AI agent acting under delegation, and an internal service without giving any of them blanket storage credentials?

19. What claims must you validate in JWT/OIDC tokens and how do you handle key rotation, issuer/audience errors and clock skew?

20. What would you test to prove service-to-service policy cannot be bypassed through an alternate internal endpoint?

Platform / SRE

21. What must pass before you permit production traffic to a new Enclave/Almanac release?

22. How would you deploy DB migrations safely with multiple application replicas and a required rollback path?

23. What are the first ten metrics/alerts you would require across Ceph, Stratum, Flash and Almanac?

24. Describe a backup/restore or disaster-recovery test you personally executed rather than merely documented.

QA / resilience

25. List the first ten failure/negative tests you would run against Enclave + Almanac together.

26. How would you demonstrate that a tenant can never retrieve another tenant's object or RAG chunk, including through caches/indexes?

27. How would you build a repeatable performance baseline without turning a four-day benchmark into an unsupported SLA promise?

What the team receives

Selected candidates will receive the current code repositories, architecture/white-paper packet, build/operate material, hallucination/overclaim audit, acceptance requirements, and the credentials/environment information Parinita is able to provide for the launch sprint.

You are expected to challenge contradictions in those materials. The code, the deployed environment and repeatable tests determine technical truth.


Detailed Recruiting Brief v3 | September 2026 | Page

PARINITA AI EDGE | ENCLAVE + ALMANAC ENGINEERING LAUNCH TEAM

ENGAGEMENT • IMMEDIATE START

Build the trusted data + RAG path with us.

Four-day controlled-launch sprint first. Ongoing production engineering and operations work available for strong performers and teams.

Apply for the workstream you can own. We are willing to hire multiple specialists rather than force one person to cover every domain.

ENCLAVE

Make object trust enforceable.

ALMANAC

Make RAG evidence precise.

PRODUCTION

Make failure recoverable.

What to send in your first response

The role(s) or workstream(s) you want to own.

One directly relevant production system you personally built or operated, including a failure you handled.

Your earliest start, timezone and realistic availability across the four-day sprint.

Your hourly, daily or fixed-scope commercial proposal.

Answers to the role-specific technical questions in this brief; if applying as a team, map each person to a concrete deliverable.

If you can make storage boring, object trust enforceable, authorization fail closed, RAG evidence precise, and production failures recoverable, we want to hear from you.

We are looking for a detail-oriented tester to test our basketball score web app and identify bugs, incorrect information, and usability issues. You will test game scores, schedules, live and completed games, game details, navigation, buttons, links, filters, and overall functionality.

You will also check the app on desktop and mobile, identify any errors or unexpected behavior, and provide clear feedback with screenshots where necessary. The goal is to make sure the app works smoothly and provides accurate information to users.

Previous experience with manual web or app testing is preferred. You should have good attention to detail, be able to clearly report issues, and have good written English. Basic basketball knowledge is a plus but not required.

We’re looking to implement ChatGPT Business as a central AI environment across the company, with data security being a key priority. We’d like to connect our Microsoft/SharePoint files and company knowledge to ChatGPT, and create dedicated AI projects/workspaces for each department – Sales, Finance, Marketing, Operations and Production.
Beyond this central knowledge base, we’d like each department’s AI to integrate with the tools they use every day to automate and simplify tasks. For example, Sales uses Zoho CRM, and we’d like AI to access relevant CRM data, assist with reporting and potentially update records. Finance uses Sage, where we’d like to explore automating tasks such as invoice capture and entry, with appropriate approval controls.
Ideally, we’re looking for someone who can help us design the architecture, build the integrations and then work with each department to implement and train the teams.
Do you have experience integrating ChatGPT/OpenAI with Sage, Zoho and Microsoft environments?

We run automated beverage stations. The phone app, the customer backend and the fleet operations tool are built and tested. The one thing that does not work yet is the machine, and that is the whole job.

THE HARDWARE
An embedded Android 7.1.2 board, Rockchip RK3288, API 25, rooted, no Google Play Services. Two serial lines. The drink controller speaks 38,400 baud 8N1 with an XOR checksum and an ACK of command + 0xA0. The payment peripheral is MDB on a separate line, a cashless card reader. Both protocols are already reverse engineered and documented, and you get the documentation on day one.

A Java bridge on the board is the only component permitted to actuate. It is fail closed today: canBrew, PREPARE_QUALIFIED and COMMIT_QUALIFIED are all false in source, so no dispense is reachable from any code path. That is deliberate, and it stays that way until the work below proves it is safe to change.

THE WORK, IN THREE WAVES
1. Read-only port qualification. Open the ports, read what is actually on the line, and show us evidence of what the controller says and when. Nothing actuates.
2. Bench actuation, one recipe family at a time, with the owner physically at the machine.
3. Supervised hardware in the loop, until one settled payment produces exactly one dispense.

THE ACTUAL HARD PART
An ACK is not proof of dispense. A lost reply, a crash mid action or a restart must never produce a second drink. If the controller does not deduplicate a stable order id, or expose a dispense result we can query before a retry, then the order stops for reconciliation rather than guessing. Sending a command is the easy half.

HOW WE WORK
You drive from your keyboard. The owner is physically at the machine for every session and performs every physical action. No hardware ships to you. Every task ends in a command anyone can run and output anyone can read. A suite made green by editing an assertion, adding .skip or loosening a check is not green.

WHAT TO PUT IN YOUR REPLY. Applications that skip these will not be read.
1. A device you have driven over a serial line from Android or Linux. What the protocol was, what you had to work out yourself, and how you proved it worked.
2. A time you had to make an operation happen exactly once across a link that could drop. What you keyed it on, and what your system did when the response was lost after the action had already happened.
3. Your read on this: on a line where the only reply is an ACK, how would you establish whether a drink was actually poured before allowing any retry?

Skip the portfolio paragraph. Answer the three.

WHAT COMES AFTER
There is a Kotlin kiosk application driving a 32 inch on-machine screen with MDB card payment behind this, and a fleet of machines after that. This is a runway, not a one-off.

First engagement is a small paid task on the read-only qualification, before any longer commitment.