Full-Stack Engineer

Initial arrangement

• The relationship begins on a project or milestone basis.
• Each project will have a written scope, delivery requirements, milestones, deadline, budget, payment schedule, and acceptance process.
• Project or milestone compensation will be proposed by Blaron and finalized through mutual discussion before work begins.
• The initial arrangement is not a monthly salaried employment commitment.
• Early engagements may be divided into smaller paid milestones so both parties can evaluate compatibility and delivery quality.

Scope changes

• Minor clarifications that remain inside the agreed scope do not automatically change the budget.
• Material additions or major changes outside the approved scope will be reviewed separately.
• When a scope change is substantial, Blaron will provide additional compensation and may extend the deadline.
• No additional work should begin until the revised scope, budget, and timeline are approved in writing.

Long-term progression

After the engineer understands Blaron's workload, delivery standards, communication style, project volume, and operating pressure, either party may propose a different arrangement. Possible progression includes part-time monthly employment, full-time monthly employment, or a permanent technical leadership position. Progression is based on performance, compatibility, ownership, reliability, and business requirements. It is not automatic or guaranteed.

Requirement analysis and research

• Read and clarify business and technical requirements.
• Identify missing information, risks, dependencies, and edge cases before development.
• Research suitable technologies, APIs, libraries, architecture patterns, and implementation constraints.
• Translate non-technical briefs into actionable engineering plans.

System architecture and mapping

• Design system architecture before implementation.
• Produce workflow maps, service boundaries, database models, API contracts, data flows, security boundaries, and failure-handling plans.
• Select technologies based on maintainability, security, scalability, cost, and delivery speed.
• Explain architectural decisions clearly to Blaron's internal team.

Estimation and milestone planning

• Break work into practical milestones and deliverables.
• Identify assumptions and exclusions.
• Provide realistic time and resource estimates.
• Raise risks early rather than after a deadline is affected.

Development

• Build maintainable, production-ready software.
• Work on both new and existing codebases.
• Follow clean coding, modular design, version control, review, and documentation practices.
• Integrate external services, databases, queues, caches, storage, APIs, and automation tools when required.

Testing and quality assurance

• Test functionality, edge cases, error handling, data integrity, security, and performance.
• Use appropriate unit, integration, end-to-end, regression, and manual testing methods.
• Review AI-generated code with the same standard as manually written code.
• Resolve defects found during Blaron's review of an agreed milestone.

Deployment and operations

• Prepare applications for deployment.
• Configure environments, containers, CI/CD pipelines, secrets, logs, metrics, and alerts as required.
• Support deployment, rollback planning, monitoring, and incident diagnosis.
• Work within Blaron-controlled repositories, infrastructure, and project accounts.

Documentation and handover

• Document architecture, setup, deployment, configuration, dependencies, APIs, database structures, known limitations, and maintenance instructions.
• Keep README files, environment examples, migration steps, and operational notes current.
• Ensure another qualified engineer can understand and continue the work.

Maintenance and support

• Diagnose and fix defects covered by the project agreement.
• Provide monitoring, maintenance, or post-delivery support when included in the scope.
• Warranty and maintenance periods will be agreed separately for each project.

Systems engineering

• Excellent system architecture, workflow design, technical mapping, and component planning
• Strong understanding of scalability, reliability, maintainability, data integrity, access control, and failure recovery
• Ability to evaluate tradeoffs and justify engineering decisions

Python development

• Strong production-level Python skills
• Experience with APIs, background workers, automation, data processing, testing, packaging, and debugging
• Ability to work with relevant Python frameworks and libraries based on project needs

CRM development

• Proven experience developing CRM systems from scratch, extending existing CRMs, or building complex CRM integrations
• Understanding of pipelines, contacts, activities, permissions, dashboards, automations, reporting, and third-party synchronization

AI, agents, RAG, and LLM systems

Required practical knowledge includes:

• AI agents and multi-step agent workflows
• Prompt design and reusable prompt systems
• RAG architecture and knowledge bases
• Embeddings and vector databases
• Tool and function calling
• Structured outputs and workflow loops
• Evaluations, guardrails, validation, and monitoring
• LLM and AI-service integrations
• OpenAI, Claude, Gemini, or suitable open-source models
• Fine-tuning and traditional machine-learning experience are preferred but not mandatory. Training foundation models from scratch is not required.

Web scraping and browser automation

• Strong experience with tools such as Playwright, Selenium, Scrapy, or equivalent technologies
• Ability to design reliable scraping, extraction, validation, deduplication, scheduling, retry, and monitoring systems
• Experience handling dynamic sites, sessions, rate limits, proxies, and CAPTCHA services when authorized and required
• All work must follow applicable law, authorization, platform rules, and project-specific compliance requirements

APIs and backend systems

• Design and development of secure APIs, services, webhooks, workers, and integrations
• Authentication, authorization, validation, rate limiting, error handling, logging, and API documentation
• Strong backend development is required. Node.js backend experience is helpful but not mandatory.

Frontend development

• Ability to deliver or supervise professional, responsive, production-ready interfaces
• Familiarity with JavaScript or TypeScript and suitable frontend frameworks such as React, Next.js, Vue, Tailwind CSS, or equivalents
• AI-assisted frontend development is acceptable, but the engineer must review, test, debug, secure, and maintain the final output

Databases and data systems

• Experience with relational and non-relational databases as required
• Data modeling, migrations, indexing, query optimization, backups, consistency, and access control
• Familiarity with queues, caching, search, storage, and data pipelines

DevOps, cloud, and observability

• Docker, Linux, Git, CI/CD, environment management, and deployment workflows
• Cloud infrastructure and production-service configuration as required
• Logs, metrics, traces, dashboards, alerts, health checks, and incident diagnosis
• Network monitoring, API debugging, production debugging, and infrastructure troubleshooting

Security engineering

• Secure development practices, secret management, access control, dependency review, hardening, monitoring, and safe deployment
• Ability to identify and reduce common application and infrastructure risks
• Deep penetration-testing specialization is not required unless a project explicitly requires it

Experience

• Eight or more years of professional system-development or coding experience is preferred.
• General software-development experience counts when it demonstrates relevant engineering depth.
• An exceptional engineer with fewer years may qualify if their architecture, code quality, delivery history, and judgment are strong.

Education

• No formal degree or educational qualification is mandatory.
• Skill, maturity, proof of work, technical reasoning, and accountability are more important than academic credentials.

Location and language

• Bangladesh-based engineers are strongly encouraged to apply.
• Dhaka is preferred because occasional in-person meetings may be required.
• Remote applicants may still be considered after an online meeting.
• Strong written and spoken English is required for briefs, documentation, updates, and technical discussion.

Professional maturity

The engineer must:

• Understand the seriousness of production and client work
• Take ownership instead of waiting for constant supervision
• Communicate blockers, risks, and delays early
• Learn new skills quickly when projects require them
• Work carefully under pressure without sacrificing security or quality
• Protect confidential information and client trust
• Provide accurate progress updates and realistic commitments

Agreements

Before receiving project access, the engineer must sign a non-disclosure agreement, a project or contractor agreement, and any project-specific security, confidentiality, or access terms.

Intellectual property

• Development must take place in Blaron-controlled repositories and accounts unless otherwise approved.
• Ownership of work completed and paid for transfers to Blaron or its client, as defined in the project agreement.
• Approved open-source components and pre-existing tools remain subject to their original licenses and ownership terms.
• The engineer may not publish project details, screenshots, source code, client information, or portfolio material without written permission.

Optional but strongly useful evidence

Applications missing mandatory information may not be reviewed.

• GitHub profile
• Portfolio or personal website
• LinkedIn profile
• Architecture or system-mapping sample
• CRM case study
• Python code sample
• Two brief descriptions of relevant systems previously built
• Examples of AI-agent, RAG, scraping, automation, backend, or infrastructure work