We source, vet, and manage hiring so you can meet qualified candidates in days, not months. Strong English, U.S. time zone overlap, and compliant hiring built in.
.svg){kind=logo}
LotusScript is the embedded scripting language for IBM's Lotus Notes and Domino platforms, the enterprise messaging and collaboration suite that powers document management, workflow automation, and business process execution in large organizations. It's an event-driven, object-oriented language that runs on both client (Notes) and server (Domino) sides, enabling developers to build sophisticated applications within the Notes/Domino ecosystem without leaving the platform.
While LotusScript occupies the legacy end of the technology spectrum, it remains deeply entrenched in enterprise organizations, particularly in regulated industries like finance, insurance, pharmaceuticals, and government. Thousands of organizations run critical business processes through Notes/Domino applications that were built 10-15 years ago and remain stable and productive today. The installed base is enormous, creating steady demand for developers who can maintain and extend these systems.
LotusScript combines elements of BASIC, JavaScript, and Java, making it approachable for developers transitioning from VB6 or other legacy languages. The language is tightly integrated with the Notes/Domino object model, giving developers direct access to documents, views, agents, and the messaging framework through familiar APIs. New development in LotusScript is rare, but maintenance, enhancement, and migration work is common.
Hire a LotusScript developer when you're maintaining or extending an existing Notes/Domino application. Common scenarios include adding features to existing databases, fixing bugs in legacy applications, modernizing user interfaces, integrating Notes with newer backend systems, or managing the gradual migration of Notes applications to cloud platforms.
You should also hire LotusScript developers if you're operating a Domino infrastructure that requires custom agents, scheduled tasks, or integration logic. Many organizations run recurring processes powered by Domino agents that handle email routing, database replication, data synchronization, or compliance reporting. These agents are often written in LotusScript and need ongoing maintenance as business requirements evolve.
Building new applications in LotusScript from scratch is rare and generally not recommended unless you're deeply committed to the Notes/Domino ecosystem. If you're starting a new project, explore modern alternatives like web-based applications, cloud collaboration platforms, or other frameworks. LotusScript is primarily a maintenance and enhancement language for existing investments.
Team composition typically pairs a LotusScript developer with a Notes/Domino administrator who manages the infrastructure, and often with Java or C# developers handling integration with external systems. Migration projects frequently involve architects planning the transition strategy alongside implementers.
The strongest LotusScript candidates have deep experience with the Notes/Domino object model and understand the nuances of client-side versus server-side development. Must-haves include solid LotusScript syntax knowledge, familiarity with Notes document design, understanding of view and form development, and experience with agents and scheduled tasks. Nice-to-haves include knowledge of XPages (Domino's modern web UI framework), integration experience with external systems, and background in Notes infrastructure or administration.
Look for developers who've actually shipped and maintained production Notes applications, not just written simple scripts. Someone who can discuss performance tuning in Domino, optimizing view indexes, or handling large databases demonstrates practical production experience. This matters because poor LotusScript practices can cripple a Domino server.
Red flags include claiming LotusScript expertise without demonstrable Notes/Domino experience, inability to explain the difference between client-side and server-side execution, or suggesting LotusScript for new application development. Also be cautious of developers who only know LotusScript and lack familiarity with integration technologies or modern web frameworks, as they may struggle with modernization projects.
Junior (1-2 years): Understands LotusScript syntax, can write simple agents and form scripts, knows the basic Notes object model (Document, View, Database), and can modify existing applications. Should be comfortable with Notes Designer and debugging tools but may lack experience with complex business logic or performance optimization.
Mid-level (3-5 years): Writes production-quality LotusScript for complex applications, understands client-side and server-side tradeoffs, has optimized performance for large databases, can design workflows, and integrates Notes with external systems (REST APIs, JDBC, etc.). Can troubleshoot subtle issues and mentor junior developers.
Senior (5+ years): Architects large-scale Notes/Domino solutions, understands the entire Domino infrastructure, can plan migrations to cloud or modern platforms, has shipped mission-critical applications, and understands advanced techniques like lotus script optimization, replication, and security. Often involved in strategic decisions about Notes investments versus alternatives.
For remote work: Communication matters because much LotusScript work involves understanding legacy application logic and business context. Seek developers comfortable asking questions, documenting their work, and explaining their approach to non-technical stakeholders. Time zone overlap is valuable for pairing on complex troubleshooting.
1. Describe a complex LotusScript application you've maintained. What were the biggest challenges in understanding and modifying it? Listen for real-world experience with legacy code. Strong answers discuss the challenge of reverse-engineering logic, dealing with incomplete documentation, and managing risk when modifying critical systems. Weak answers sound like they've only done simple script modifications.
2. Tell us about a time you had to integrate a Notes application with an external system. What was the integration approach and how did you handle data synchronization? Testing practical integration knowledge. Strong answers discuss API calls, error handling, data transformation, and how they verified data integrity. They understand the complexity of keeping systems in sync.
3. Have you worked on Notes/Domino infrastructure projects? What's your experience level with administration, replication, and deployment? This filters for developers with broader Domino ecosystem experience. Senior candidates can discuss infrastructure decisions, not just application code.
4. What's the most critical performance issue you've debugged in a Notes/Domino application? How did you identify and fix it? Testing understanding of Domino performance fundamentals. Strong answers discuss view indexing, server process profiling, or database design issues. They show knowledge of tradeoffs between functionality and performance.
5. Describe your experience with modernization or migration projects. Have you moved applications away from Notes/Domino to other platforms? For senior hires, understanding their perspective on legacy platform transitions. Honest assessment of when to stay vs. when to move demonstrates strategic thinking.
1. Explain the difference between client-side and server-side LotusScript execution. When would you choose each approach, and what are the performance implications? This is fundamental to LotusScript development. Strong answers explain security boundaries, scalability, and the tradeoff between distributing logic and centralizing it on the server.
2. You're building an agent that processes documents in a large database (millions of records). How would you approach this to avoid performance problems? Testing understanding of Domino scalability. Strong answers discuss chunking data into batches, using NotesSession.Evaluate to server-side filter, understanding view limitations, and measuring performance. They know that naive iteration over millions of documents is career-limiting.
3. What is a replication conflict in Notes/Domino, and how would you handle it in LotusScript? Tests knowledge of Domino's fundamental architecture. Strong answers explain how replication creates conflicts, discuss resolution strategies, and know when to programmatically handle conflicts versus letting the system manage them.
4. Design a workflow application in LotusScript that routes documents through an approval chain. How would you track the workflow state and handle rejections? This is a practical design question. Look for clear thinking about document state, transitioning between states, and handling edge cases like manager being unavailable. They should discuss both data storage and process logic.
5. Compare LotusScript agents with Domino scheduled agents. When would you use each, and what are the resource implications? Testing understanding of Domino execution contexts. Strong answers discuss the difference between user-triggered, form-triggered, and scheduled agents, and understand when each is appropriate.
Build a document approval workflow in LotusScript. Create a form with a document routing mechanism that sends documents through an approval chain, tracks approver history, and routes rejections back to the originator. Requirements: (1) documents must track their current approver, (2) approval history must be maintained, (3) rejection must route back with comments, (4) completed approvals must be logged. Scoring rubric: correctness of workflow logic, proper use of Notes object model (Document, NotesSession, NotesDatabase), clear code structure, and error handling.
LotusScript is a legacy skill with a shrinking but experienced talent pool. Salaries reflect the specialized nature and decreasing demand for new development.
US rates for comparable LotusScript experience typically run 2.5x to 3x these figures. LatAm has pockets of strong LotusScript talent, particularly in Brazil and Argentina where many organizations still run Notes/Domino infrastructure from the 2000s era outsourcing boom.
All-in staffing through South includes salary, equipment, compliance, and payroll management. Direct hires would add employer contributions and benefits on top of the salary ranges shown.
Latin America has mature LotusScript communities, particularly in Brazil, Argentina, and Mexico, where Notes/Domino was historically deployed widely in government, banking, and large enterprises. Many organizations in these countries still run critical systems on Domino infrastructure, creating steady demand for developers who understand the platform.
Time zone alignment is excellent: most LatAm LotusScript developers work UTC-3 to UTC-5, overlapping 6-8 hours with US East Coast teams. This is valuable for maintenance work and troubleshooting production systems where real-time collaboration accelerates problem-solving.
English proficiency among LatAm LotusScript developers is generally strong, particularly those who've worked on international projects or in multinational organizations. Cultural alignment is natural; they understand enterprise software development, compliance requirements, and the need for stability and documentation.
Cost efficiency is substantial. A senior LotusScript developer in Latin America operates at 40-60% of comparable US talent, making modernization and maintenance projects economically feasible where they might otherwise be prohibitively expensive.
South identifies qualified LotusScript developers from our vetted network based on your specific needs. If you're maintaining a healthcare Notes/Domino system, we find developers with healthcare domain knowledge and production system experience. If you're planning a migration, we identify architects familiar with exit strategies and modern platform alternatives.
Our technical screening for LotusScript focuses on production experience, understanding of the Domino ecosystem, and ability to troubleshoot complex issues. We verify past project outcomes and validate their knowledge through practical assessments.
You interview the shortlisted candidates directly, assessing team fit and depth of expertise for your specific system. We've already verified their skills, so you can focus on whether they understand your business context and architecture.
Once selected, South manages the contract, equipment, payroll, compliance, and ongoing HR support. If the hire doesn't work out, our 30-day replacement guarantee protects you with a cost-free backfill.
Ready to find a LotusScript developer for your project? Describe your needs at https://www.hireinsouth.com/start.
LotusScript builds applications within the IBM Notes/Domino platform for document management, workflow automation, collaboration, and enterprise messaging. It's used to create forms, agents, views, and business logic that execute within the Notes/Domino ecosystem.
Yes, for organizations that have invested heavily in the platform. Thousands of companies still run mission-critical applications on Domino, particularly in regulated industries. However, new development in LotusScript is extremely rare. Most organizations are planning migrations to modern platforms rather than expanding Domino investments.
If you already have a Notes/Domino investment and need to maintain it, LotusScript is your only option. If you're starting new development, avoid it. Modern alternatives like web applications, cloud platforms, or RPA often provide better paths forward for the problems Notes/Domino traditionally solved.
Mid-level developers run $35,000-$48,000/year, senior developers $52,000-$70,000/year. These are market rates; all-in staffing through South includes salary, compliance, and equipment. Get a quote at https://www.hireinsouth.com/start for your specific project.
For maintenance and enhancement roles, 2-3 weeks. For specialized needs (healthcare compliance, financial system expertise), 3-4 weeks as we identify candidates with relevant domain knowledge. Urgent timelines are possible for well-defined roles.
For maintaining existing applications, mid-level developers (3-5 years) are typically sufficient. For complex systems, architectural decisions, or migration planning, senior developers are essential. Avoid juniors for critical production systems.
Yes. South supports contract, part-time, and project-based arrangements. Describe your timeline and engagement model when you reach out.
Most work UTC-3 to UTC-5 (Brazil, Argentina, Paraguay), giving you 6-8 hours of overlap with US East Coast teams. Ideal for troubleshooting production systems and collaborative maintenance work.
We verify Notes/Domino experience through technical screening, validate knowledge of the object model and best practices, and check past project outcomes. We also assess their understanding of when to maintain versus modernize.
South's 30-day replacement guarantee covers you. If the hire doesn't work out, we'll identify and onboard a replacement at no additional cost.
Yes. South manages salary processing, tax compliance, benefits, and all HR administration. You pay one invoice to South; we handle the rest.
Absolutely. If you need infrastructure expertise, application development, or a mixed team, we can coordinate multiple hires. Describe your team composition when you reach out.
