Backend and Frontend service on Node.js/TypeScript with Solana + Jito integration

Für ein Kundenprojekt im Bereich Microsoft 365 Modern Workplace suchen wir erfahrene Freelancer (m/w/d) mit Schwerpunkt Microsoft Places. Im Mittelpunkt steht die Beratung, Konfiguration und Optimierung einer Microsoft-365-Umgebung zur Unterstützung moderner Hybrid-Workplace-Konzepte. Aufgaben Beratung bei der Einführung und dem Betrieb von Microsoft Places Analyse bestehender Microsoft-365-Umgebungen und Erarbeitung geeigneter Lösungskonzepte Konfiguration von Gebäuden, Stockwerken, Meetingräumen und Arbeitsplätzen Einrichtung und Optimierung von Desk-Booking- und Room-Booking-Szenarien Integration von Microsoft Places in Microsoft Teams, Outlook und Exchange Online Unterstützung bei Lizenzierungsfragen sowie Best-Practice-Empfehlungen Durchführung von Workshops und Know-how-Transfer für Anwender und IT-Teams Unterstützung bei Troubleshooting sowie im laufenden Betrieb Anforderungen Mehrjährige Erfahrung im Microsoft-365-Umfeld Praktische Erfahrung mit Microsoft Places Sehr gute Kenntnisse in Microsoft 365, Microsoft Teams, Exchange Online und Outlook Erfahrung mit Microsoft Entra ID (Azure AD) Kenntnisse moderner Hybrid-Workplace- und Modern-Work-Konzepte Wünschenswerte Kenntnisse Microsoft Teams Premium PowerShell für Microsoft-365-Administration Erfahrung mit Arbeitsplatz- und Raumbuchungslösungen Microsoft-Zertifizierungen im Bereich Modern Workplace oder Microsoft 365 Erfahrung in der Konzeption und Einführung moderner Arbeitsplatzkonzepte Start: asap Dauer: ca 3 Monate mit Option auf + Einsatzort: Remote / nach Absprache Auslastung: Nach Absprache Interesse? Da sich das Projekt aktuell in der Vorbereitungsphase befindet, möchten wir frühzeitig passende Experten kennenlernen. Bitte senden Sie uns an contract (AT) advergy de : CV Verfügbarkeit Stundensatz (Remote / Onsite) Dreizeiler, wieso Sie besonders gut auf das Projekt passen Vielen Dank und liebe Grüße Seda

The website is developed on: Backend: Java + Spring Boot Database: MySQL Frontend: JavaScript, HTML, CSS Template Engine: Thymeleaf Server: VPS (Linux Ubuntu) Reverse Proxy: Apache2 Architecture: Monolithic application Currently, the website has implemented: A blog with an admin panel. The ability to create and edit articles through the admin panel. The ability to add HTML markup and content through a visual interface. Static pages of the site, which are currently created by the developer manually. ⸻ Task Objective It is necessary to implement the ability to create and manage new commercial service pages through the existing admin panel similarly to how blog articles are currently created. After implementation, the administrator should be able to independently create new SEO service pages without the involvement of the developer. ⸻ Current State Currently, only blog posts can be created through the admin panel. Example: Article 1 Article 2 Article 3 Each article has: Title URL (slug) Content SEO parameters Images ⸻ What Needs to be Implemented 1. New content type "Services" Create a separate section in the admin panel: "Services" It should be independent of the blog section. Example structure: Blog Services ⸻ 1. Creating a service page The administrator should be able to create a new service page through the interface. Commercial service pages consist of 13 blocks, of which 4 blocks are dynamic and 9 are static. Fields: Service name URL (slug) H1 SEO Title Meta Description SEO Keywords Main content of the page Image Publication status (Draft / Published) ⸻ 1. Page content The content should support: HTML markup Text formatting Headings H2-H6 Lists Images Links It is preferable to use the existing editor that is already applied in the blog. ⸻ 1. URL generation Each service should have its own URL. Examples: /visa/usa/business-visa-usa /visa/usa/business-visa-uk /visa/usa/business-visa-canada ⸻ 1. Display on the site After publication, the page should: automatically become available at its URL; use the existing service page template or a new template; display correctly on all devices. ⸻ 1. SEO For each service, it is necessary to provide the ability to configure: Title Description H1 Canonical URL (preferably) Open Graph (preferably) Pages should be indexed by search engines similarly to blog pages. ⸻ 1. List of services In the admin panel, implement: a list of all services; search; editing; deletion; changing publication status. ⸻ 1. Important Implement the ability to create new types of SEO pages without code modifications in the future. through a unified content management mechanism. ⸻ What is Expected from the Developer It is necessary to analyze the existing implementation of the blog and maximize the reuse of the current architecture to create the new "Services" section. When responding, please indicate: How the task will be implemented. What changes will be required in the database. Time estimate. Cost of work. What technologies should the performer know Mandatory: Java Spring Boot MySQL Thymeleaf HTML/CSS JavaScript Working with Linux Ubuntu Desirable: Spring Security SEO optimization of server pages Experience with CMS and CRUD modules Experience supporting monolithic Spring Boot projects

A separate CRM system needs to be developed for the centralized processing of all retail orders from various sales channels (Prom, Rozetka, own websites, and manual orders). Main requirements: A unified order registry from all sources, preserving information about the source and its status. A separate internal CRM status that operates independently of the status on the marketplace or website, with two-way synchronization of statuses where supported. Flexible integration with 1C: for each source, the administrator can separately enable or disable automatic order export. Integration with carriers for automatic creation of shipping documents, saving their numbers in the CRM, and transmitting the shipping document numbers to Prom and Rozetka. Integration with Checkbox for creating receipt projects, using customizable payment method matching, with subsequent fiscalization control. Support for manual order creation (phone, Viber, Telegram, Direct, etc.) with a complete subsequent processing cycle through the CRM. All API keys and integration settings must be managed by the administrator through the CRM interface without the involvement of a programmer. A complete action log and integration logging for system operation control. Main goal The manager must be able to fully process orders in one CRM interface — from receiving the order to creating a document in 1C, shipping document, receipt project, and completing the order, without the need to access the cabinets of Prom, Rozetka, websites, carriers, or Checkbox.

We have synchronization of two data sources with the CRM. The system as a whole is stable. However, there remains a part that becomes desynchronized. The main hypothesis is that in one of the sources, the data changes after the initial synchronization, and these changes are not always pulled into the CRM. + the data in the two sources have different names/identifiers even though they represent the same entities.

Task: deploy an LLM service that knows all the company's documentation and answers questions from the sales department managers. Current situation: the client has independently assembled a prototype (a separate project with uploaded company information, hosted on a server), but the information from the database is not transmitted to the model — likely, there is an issue with the API. We will provide the code and access. The first step is an audit: fix the existing setup or justifiably rebuild from scratch. Required functionality: Upload all company documentation: description of each service, regulations, FAQ, pricing (all materials will be provided). Answers strictly based on the uploaded documents (RAG). The model does not invent facts; if the answer is not in the database — it honestly informs about it. Access for managers via a link (web interface), with authorization. Scenarios: the manager asks any question about the company's work; inserts the client's question "as is" and receives a ready answer for sending; finds the necessary regulation/report by request. Knowledge base updates without a developer (uploading files through the interface or a connected folder). English language. History of requests for quality control. Technical expectations: LLM via API (Claude/OpenAI — propose with a cost calculation for tokens), RAG pipeline (vector database, embeddings), hosting on our server or in the cloud, HTTPS. The architecture should allow for future connection of the assistant to the analytical data warehouse (parallel project). In the response, indicate: examples of similar RAG projects, stack, timeline, cost of work, and estimated monthly ownership cost (tokens + hosting).