Technical Writing Projects

opportunity

MERN Developer

We are looking for a senior developer to help us finalise and consolidate a number of projects which are 75% complete. We expect this to be an ongoing, monthly paid role and so the budget is on that basis. We have a legacy system that, whilst functional, is outdated and needs the functionality migrating/replicating in our new environment. The work will include refactoring, adding routes and connecting multiple interfaces to complete the job. You will need to have an understanding of complex data structures to ensure that migration and CRUD functionality is accurate to serve various interactions of the project. Lastly, the platform has a companion application that is built and compiled in EXPO. This will need attaching to the new migration, rebuilding and deploying to the stores appropriately. Therefore the following experience is necessary **Key Responsibilities:** - Develop new features and enhance existing functionality for our directory website using the MERN stack (MongoDB, Express.js, React.js, Node.js, Next.js). - Utilise trunk-based development practices to ensure smooth and timely integration of code into the main branch. - Work collaboratively with other developers to resolve conflicts and merge changes efficiently. - Perform regular performance and bug-fixing tasks to ensure optimal website performance. - Write clean, maintainable, and efficient code, following best practices and industry standards. - Participate in code reviews to maintain code quality and provide constructive feedback. - Continuously improve and upgrade the software to keep up with the latest advancements in technology. **Required Skills and Experience:** - Proven experience as a MERN Stack Developer. - Strong understanding of trunk-based development and its best practices. - Prior experience working in an agile environment with regular sprints. - Proficiency in MongoDB, Express.js, React.js, and Node.js. - MUST MUST be proficient with Docker and build architectures. - Familiarity with version control systems, particularly Github and Github Actions. - Excellent problem-solving skills and attention to detail. - Strong communication skills and the ability to work collaboratively in a team environment. - Ability to manage multiple tasks and deadlines effectively. **Nice to Have:** - Experience with DevOps practices and tools. - Knowledge of serverless architecture and cloud platforms. - Familiarity with continuous integration and continuous deployment (CI/CD) pipelines. - Typescript experience. If you're after a easy going developer role where there's more work then we can get through then please let me know. No agencies and please only apply if you're used to throwing code out from ticket reference branches - we want to be pushing/building multiple times a day in some situations. Please please please do not apply if you're a junior or mid dev - this requires an individual to undergo a steep learning curve and drive the migration to finalisation. Also - the individual needs to work on the project full time until complete - this is not something that can be done in an hour a day.

Data Annual Form 10-k

Overview Accountants must be familiar with the amount of data required in the Annual Form 10-K filing and the Annual Proxy filing for publicly traded companies because they will use the data from these filings to research a company’s competitors. Accountants can even use the data from these filings in their personal life to research investment opportunities. Scenario In this milestone, you will prepare a valuation for a 1% minority shareholder on the assumption that your company is a “going concern” company, meaning that the company will be able to pay its financial obligations as needed for the foreseeable future. Directions In this milestone, you will provide a brief history and overview of the company you selected. Use your company’s most recent Form 10-K filing and SEC Annual Proxy filing from The Securities and Exchange Commission’s (SEC) website to gather the information described in the rubric criteria. You will also provide a brief summary of your findings for your valuation team members and include a visualization in the summary. Note: Refer to this module’s Discussion for the list of companies to choose from. Specifically, you must address the following rubric criteria: Links Provide the most recent SEC Form 10-K filing link for the company. Provide the most recent SEC Proxy filing link for the company. History and Overview Provide a brief company history overview based on external research of the company. Consider the following questions to guide your response: How long has the company been in business? Who was the original founder of the company? What significant changes to company leadership have occurred? How has the company changed since its beginning? Consider expansion of locations or products/services, etc. Identify all of the company’s major locations for their facilities and/or other properties. Identify all of the customers recognized by the company. List all of the names of the executive management team of the company. Identify all of the competition recognized by the company. Identify all of the major shareholders of the company. Describe business risks recognized by the company. Explain how the company is committed to environmental, social and governance (ESG) efforts and sustainability. Describe the company’s leadership in energy and environmental design (LEED) status. Consider the following questions to guide your response: Is the company currently LEED certified? If the company is not currently LEED certificated, is it working toward becoming LEED certified? Summary Summarize your findings for the valuation team. Include the following details in your response: Explain what you learned as you researched the company. Identify the key points the valuation team needs to be aware of. Create at least one effective visualization that supports key points. Include the following detail in your response: Provide appropriate labels for the visualization(s). If you need writing support, access the Academic Support module of your course. What to Submit Submit the Business Valuation Template with the Milestone One: Introduction section completed. The Introduction section should be an additional 4- to 6-page Microsoft Word document with double spacing, 12-point Times New Roman font, and one-inch margins in addition to the current page count. Sources should be cited according to APA style. Note: You will be using this same file throughout all the milestones and your project. Supporting Materials The following resources support your work on this assignment: Website: U.S. Securities and Exchange Commission This website allows users to search for a publicly traded company and find their published financial statements. Use this website to find your company’s 10-K filing.

opportunity

Build Integration to send IONOS Web Orders to Kipos POS

We run a food takeaway and need a developer to build an integration so that orders placed on our IONOS webstore are automatically sent into our Kipos account (https://app.kipos.uk/) and print straight to our kitchen/printer setup with no manual re-entry. This must be production-ready: fast, reliable, and built to handle busy service periods. What the integration must do 1) Capture new online orders from IONOS Detect new orders as soon as they’re paid/confirmed (or the correct “ready for kitchen” status) Pull all relevant order data: Order ID, timestamp Customer name + phone/email Delivery vs collection Address (delivery) / pickup details (collection) Requested time: ASAP vs scheduled (time slot if applicable) Customer notes (allergies, “no onions”, etc.) Items, quantities, variants Modifiers / add-ons / extras (e.g., “extra cheese”, “no sauce”, spice level) Discounts / delivery fee / tips (if present) Payment method/status 2) Create the order in Kipos exactly as the kitchen needs it Push the order into Kipos so it lands in the correct screen/queue as an online order Map all the required fields Ensure delivery/collection is correctly set and visible on print tickets Include requested time clearly (especially for scheduled orders) 3) Auto-printing to kitchen printers Orders arriving in Kipos should auto-print to our configured printer(s), or be inserted into the correct Kipos workflow/status that triggers printing. Key requirements (takeaway-specific) Modifier & note handling (critical) Must support multiple modifiers per item, and multiple items each with their own notes Preserve formatting so the ticket is easy to read during service Handle edge cases like: “No X” and allergy notes Duplicate prevention + reliability No duplicate tickets/orders if a webhook retries or the sync is re-run Retry + failure handling: Automatic retries Clear error logs Optional alert (email) if an order fails to sync Operational timing Webhook/event-driven preferred (near-instant) Polling acceptable only if webhooks aren’t available, but it must still be reliable and efficient Security Secure credential storage (environment variables/secret store) HTTPS, least-privilege access Preferred technical approach We’re open to the best implementation, but we expect this to be either: Middleware service (recommended): listens for IONOS orders and posts to Kipos or Direct plugin/integration if IONOS supports it. Deliverables Working live integration: IONOS → Kipos order creation + printing workflow Configuration options: Which order status triggers sending Item/modifier mapping method Logging dashboard or structured logs (success/failures, retries, duplicates) Documentation: Setup steps How to update menu/mappings Troubleshooting guide Test evidence: At least 10 varied test orders (modifiers, delivery/collection, scheduled/ASAP) Source code + handover (Git repo or zip) Short post-launch support period (bug fixes) Acceptance criteria A new IONOS order appears correctly in Kipos within an agreed time (e.g., under 60 seconds if webhook-based) Ticket prints automatically (or via correct Kipos status trigger) without staff interaction Items, modifiers, notes, times, and delivery/collection details are accurate and readable No duplicates under retries/network issues Clear logs for each order’s sync status To include in your proposal Your recommended approach (webhooks vs polling, architecture, hosting) Relevant experience (POS integrations, online ordering, printers/kitchen workflows) Estimated cost + timeline (phased: build → test → deploy) What you need from us (API access, sample menu, Kipos printer workflow details) Info we can provide to speed things up Sample orders (with modifiers/notes) Our current IONOS product list/menu structure Screenshot/video of our Kipos order screen + print output requirements Printer setup details inside Kipos (single printer or multiple stations)