Infosys Appian Interview Experience

Practice this interview

Answer each question in your head first, then open the guide and mark how you did.

1. Ever worked on Appian Administration?

   How to answer

   The interviewer is checking whether you have handled environment-level tasks beyond building applications.

   • Describe Admin Console work you have done, such as managing users and groups, authentication settings and Third-Party Credentials.
   • Mention running Health Check, reading its findings and fixing flagged design risks.
   • Cover deployments across environments, import customization files and handling missing dependencies.
   • Include process monitoring, such as finding failed nodes, fixing paused processes and tuning archiving.

   Tip: Give one concrete incident you resolved and its outcome rather than listing every admin page.

   Knew it Need review

2. How to start a process from an email?

   How to answer

   The interviewer is checking whether you know how Appian receives inbound email and turns it into a process instance.

   • Configure an email trigger on the process model start event so the model gets its own receiving address.
   • Inbound email must be enabled by an administrator for the environment.
   • Map sender, subject and body into process variables, and store attachments as documents in a target folder.
   • Validate the sender and handle malformed emails so unwanted messages do not start processes.

   Tip: Mention a fallback, such as polling a mailbox through an integration, if inbound email is not allowed.

   Knew it Need review

3. How will you configure related actions in record type. What happens if context is not added.

   How to answer

   The interviewer is checking whether you understand how record actions pass record data into a process.

   • In the record type, add a related action, select the process model and set the title, description and icon.
   • Pass context by mapping rv!identifier or rv!record fields to process parameters.
   • Use a visibility expression so only authorized users see the action for the right records.
   • Without context, the process starts with null parameters, so the form opens empty, fails to load data, or creates a new row instead of updating.

   Tip: The process variables must be marked as parameters, or the context mapping will not appear.

   Knew it Need review

4. What are the integration you worked on?

   How to answer

   The interviewer is checking the depth and variety of your real integration experience.

   • Name the external systems, the direction of data flow and the protocol, such as REST, SOAP or file transfer.
   • Explain the Appian objects you used: Connected System, Integration objects called from interfaces or the Call Integration smart service, and Web APIs for inbound calls.
   • Cover authentication, such as OAuth 2.0, API keys or basic auth, and where credentials were stored.
   • Describe error handling, retries, logging and timeout handling.

   Tip: Walk through one integration end to end, including a production issue you fixed.

   Knew it Need review

5. What are the objects you feel comfortable working with

   How to answer

   The interviewer wants to see the breadth of your hands-on experience and where you can work without guidance.

   • Group objects by layer: data (record types, data types, data stores), logic (expression rules, constants, decision objects), process (process models, smart services) and UI (interfaces, sites, reports).
   • For each group, give one real example of something you built.
   • Mention integrations, connected systems and web APIs if you have used them.
   • Say honestly which objects you know less well.

   Tip: Name only objects you can defend with detailed follow-up answers.

   Knew it Need review

6. What are the Security types in Record Type

   How to answer

   The interviewer is checking whether you understand the different security layers on record types.

   • Record type object security: roles such as Administrator and Viewer control who can see or edit the record type itself.
   • Record-level security: rules that limit which rows each user or group can see, often based on group membership or field values.
   • Field-level security on synced record types: hides sensitive fields from some users.
   • Record action security, controlled by the action's visibility and the security of the underlying process model.

   Tip: Explain that security also needs to be enforced on the data source and in processes, not only on the record type.

   Knew it Need review

7. What is pass by Value and pass by reference

   How to answer

   The interviewer is checking whether you know how data moves between parent and child objects in Appian.

   • Pass by value: the child gets a copy, so changes in the child do not affect the parent.
   • In process models, a synchronous subprocess can map a process variable by reference, so the child's changes show up in the parent at once.
   • In interfaces, a child interface can update the parent's local variable when that variable is passed in and saved into through the rule input.

   Tip: Mention that Pass as reference is set on the subprocess Setup tab, and a CDT passed by reference must exactly match the parent's CDT.

   Knew it Need review

8. What is synchronous and asynchronous process model

   How to answer

   The interviewer is checking whether you know how parent and child processes run and how that affects design and performance.

   • Synchronous subprocess: the parent waits for the child to finish and can receive output variables.
   • Asynchronous subprocess: the parent continues right away and the child runs on its own, with no outputs returned.
   • Activity chaining continues into a synchronous subprocess, which keeps the user flow seamless.
   • The Start Process smart service and a!startProcess start a new process without the parent waiting for it to finish.

   Tip: Give an example such as an asynchronous child for sending notifications.

   Knew it Need review

9. What is the use of service account in Appian?

   How to answer

   The interviewer is checking whether you know how external systems authenticate to Appian securely.

   • A service account is a non-human user type that cannot sign in to the Appian interface.
   • It is mainly used with API keys so external systems can call Appian Web APIs.
   • Its security comes from group membership, so it only sees the objects and data those groups allow.
   • Create a separate account and key for each consuming system so access can be revoked independently.

   Tip: Mention least privilege and key rotation, not just how to create one.

   Knew it Need review

10. What should we use to trigger a process model when an email is sent to appian?

    How to answer

    The interviewer is checking whether you know how Appian can start a process from inbound email.

    • Appian can start a process from an incoming email. Incoming mail is configured in the Admin Console, and the process model start event is set to receive a message.
    • Map the sender, subject, body and attachments into process variables, and store attachments in a document folder.
    • Validate the sender and handle security on who is allowed to start the process.
    • On cloud, check whether inbound email is available. A scheduled poller against a mail API is a common alternative.

    Tip: Describe the parsing and error handling you built, not only the trigger.

    Knew it Need review

11. When synced records types are opted, when data is added into db Directly, how can we see data in record type

    How to answer

    The interviewer is checking whether you understand how synced record types refresh and when they go stale.

    • Writes made through Appian, such as the Write Records smart service, sync automatically. Direct database inserts do not.
    • You can trigger a manual sync from the record type's data sync settings, or rely on the scheduled full sync.
    • For near real time, call the Sync Records smart service with the changed identifiers after the external load.
    • Know the sync row limits and the fact that failed syncs show errors on the record type.

    Tip: Explain how you coordinated sync with an external ETL job.

    Knew it Need review

12. Where do you find performance of query

    How to answer

    The interviewer is checking whether you can diagnose slow queries and pinpoint where the time goes.

    • In the interface or expression rule designer, the performance view breaks down evaluation time per rule and query.
    • Application server performance logs, such as the data store and expression detail files, record query timings.
    • Appian Health Check reports flag slow queries and expressions across the environment.
    • At the database level, use the execution plan and indexes to fix the root cause.

    Tip: Mention paging with a!pagingInfo and filtering at the source, not in memory, as the usual fixes.

    Knew it Need review

13. Which one is more efficient

    How to answer

    The interviewer is checking whether you can compare design options on performance and justify the choice.

    • Clarify what is being compared, commonly a!forEach versus MNI, or looped queries versus one batched query.
    • Expression logic like a!forEach runs in memory and is usually cheaper than creating process node instances.
    • One filtered query beats repeated queries inside a loop.
    • Back claims with evidence, such as the interface designer performance view or Appian Health Check findings.

    Tip: Never give a one-word answer. State when each option wins.

    Knew it Need review

14. Why do we use MNI , instead of foreach()?

    How to answer

    The interviewer is checking whether you know when per-item process execution is needed and what it costs.

    • a!forEach runs inside an expression and returns a list. It cannot spawn a user task or subprocess per item.
    • MNI repeats a process node, such as a user input task or subprocess, once per list item, one at a time or all at once.
    • Many smart services, like Write Records, accept lists, so MNI is often unnecessary.
    • MNI adds node instances, memory use, and a per-node instance limit.

    Tip: Say you use MNI only for per-item tasks or subprocesses.

    Knew it Need review