ATA SLD

Slavic Languages Division (American Translators Association)

American Translators Association: The Voice of Interpreters and Translators

  • Home
  • About Us
  • Blog
    • Comments Policy and Disclaimer
  • SlavFile
  • Resources
    • Slavic Languages Presentations Archive
  • Contact Us
  • SLD Podcast

2024 SLD Annual Meeting Minutes

October 30, 2024

Minutes of the Annual Meeting of the Slavic Languages Division

of the American Translators Association

September 29, 2024, 2:00 EDT

Held online via Zoom

Steven McGrath, Administrator; Natalia Postrigan, Assistant Administrator

  1. Short introductions were exchanged (attendees’ locations and specializations) before the meeting was called to order.
  2. The meeting was called to order at 2:03 PM EDT.
  3. The minutes from the annual meeting of 2023 were shared in the chat for the attendees to review, and it was mentioned that the minutes were also previously published in the Slav File.
  4. The agenda for the current meeting was also shared in the chat. Eugenia Tietz-Sokolskaya seconded to approve. The 2024 agenda was accepted with no changes.
  5. Division members presented an overview of Division events in the past year:
  6. Blog update: Eugenia shared an update on the SLD Blog. There have been challenges this year related to the changes in the content regulations for ATA division blogs. Also, currently there is no way to subscribe to the blog, leaving no way to let members know about new posts: the only way at present is to request a broadcast to all through ATA communications. Steven said that he would bring up this issue in the quarterly report to the ATA board.
    • Eugenia will be at the conference in Portland inviting people to submit reviews of the conference sessions for publication in the blog.
    • Aleksandr Lukoff asked what input would be wanted from the conference. Eugenia explained that members would be invited to share reviews of the conference sessions.
    • Steven expressed appreciation for Eugenia’s work, and for Viktoryia Baum for contributing an article to the blog.
    • Viktoryia commented about her willingness to share reviews on the sessions, if possible.
    • Steven added that in addition to Slavic track sessions, because in the blog format we don’t have a page limit anymore, anyone is welcome to submit reviews of sessions in other tracks, as well as other content.
  7. Website update: Eugenia shared an update about the website. Eugenia would like to build the resource page on the website, and she invited everyone to supply links and resources.
  8. SLD podcast: Halla Goins was not present to report progress. Steven reported that the podcast is going well. Steven mentioned that there had been two episodes this year and that a new episode is coming soon. Steven expressed appreciation for Viktoryia for participating in the podcast.
  9. Facebook, LinkedIn, and the online forum: The volunteers in this area were not present to report. Steven expressed appreciation for the volunteer effort to grow our social media: Anna Livermore for Facebook, Julia Thornton for the Google forum, and Mikhail Yashchuk for LinkedIn.
  10. Steven asked if anyone would be interested in managing the division’s X (formerly Twitter) account. There was no interest expressed.
  11. New business for 2024:
    • Next year, an election is coming up for the administrator and assistant administrator. Steven called for volunteers for the nominating committee (at least two members). Eugenia and Shelley Fairweather-Vega volunteered.
    • ATA’s 66th Annual Conference will be held in Boston, MA, October 22-25, 2025.
    • Steven invited suggestions for speakers, in particular, for a Distinguished Speaker. Eugenia encouraged members to send proposals to present on their specialization, because the Slavic track usually is slow to fill up. Language-specific sessions are of particular interest. Eugenia said that we are all experts in something and great in what we do, and it would be interesting for all to hear these presentations. Steve joined this call for proposals, sharing that presenting is a good experience and helps you think about your specialization in a new way. Aleksandr commented that interpreting for worker compensation cases appears to be an area of high demand at the moment.
    • Eugenia reminded attendees that Nora Favorov had suggested literary translator Robert Chandler on several occasions, and Boston would be a logistically easier destination for him traveling from England. Shelley commented that if someone like Robert Chandler is recruited, the Literary Division might join SLD to have a joint Distinguished Speaker. The Literary Division also needs to find a distinguished speaker for the next year.
    • Eugenia mentioned immigration lawyer Jan Albrecht as another potential distinguished speaker. Aleksandr mentioned that a colleague of late Ukrainian émigré linguist Sviatoslav Karavanskyi could be a good speaker, but he would need to research a suitable candidate.
    • Steven mentioned that distinguished speaker suggestions would be reviewed by Paul Gallagher.
  12. Call for feedback and suggestions from the members
    • Eugenia spoke about the survey for her and John Riedl’s upcoming presentation at the conference. The survey was sent by the ATA in the past month. The subject was “SLD survey request,” and the email went out on September 25th. The survey is primarily on the topic of Russian>English translation.
    • Viktoryia expressed appreciation for the work of SLD administrator and assistant administrator and mentioned being nominated for ATA president-elect.
  13. Call for newcomers to introduce themselves
    • Anna Kostorna made her introduction. She is looking to expand her business in translation and interpreting work in Ukrainian and Russian.
    • Steven encouraged attendees to share their contact information in the chat.
  14. Annual dinner: Natalia reported on signups for the annual dinner in Portland and encouraged people to sign up soon, as we are getting close to capacity. Viktoryia suggested that next year SLD and LTD consider a joint dinner.
  15. ATA election: Steven mentioned that the ballots for the ATA election should be going out tomorrow.
  16. The meeting was adjourned at 2:46 PM EDT.

Filed Under: SLD Tagged With: Administrative, SLD

ATA65 – One Month Away!

October 1, 2024

One Month until ATA65 in Portland, OR

Just one month until the 65th ATA Annual Conference in Portland, Oregon (October 30 – November 2, 2024)! Early bird registration rates have been extended until October 7, so if you haven’t already, register now to lock in that good deal. Standard registration will be available October 7-14, and late registration rates apply after October 14.

Already registered? Wondering what to do on Thursday evening? Join SLD at our annual dinner at 8 PM at the Eastern European restaurant Kachka. Seats are limited and they’re filling up! Check your inbox for information from ATA HQ, or contact Natalia Postrigan to reserve your spot.

Filed Under: ATA Networking, ATA65, SLD Networking Tagged With: annual dinner, ata65, networking, SLD

Don’t Miss SLD’s Annual Meeting 9/29/24

September 20, 2024

The Slavic Language Division’s annual meeting is on Sunday, September 29, from 2:00 PM to 3:00 PM (ET).

Don’t miss out on the chance to share your common interests and shape upcoming division initiatives! Find out what the division has been up to in the past year, provide input, and welcome newcomers to the division and our profession.

How to attend:
The Zoom link was sent out in a broadcast from ATA Headquarters to SLD members on Friday, September 6. Check your ATA member email inbox and join us!

Conference registration is not required. All members are welcome!

Filed Under: SLD Tagged With: Administrative, ATA

Job Opportunity: Ukrainian Intermittent Language Specialist Position (USCIS)

August 29, 2024

Glenn Carstens via Unsplash

The Language Services Section with U.S. Citizenship and Immigration Services currently has a job announcement for an intermittent (as-needed/project-based) language specialist for several languages, including Ukrainian.


Language Specialist, GS-11/12

Office: Public Services Division, Language Services Section

Closing Date: Friday September 6, 2024

Note: This job will close when we have received 200 applications which may be sooner than the closing date.

Area of Consideration: U.S. Citizens – Any position utilizing this announcement will be filled through Direct Hire Authority.

Languages:  Dari, Pashto, Farsi, Ukrainian

Work Schedule: Intermittent

Location: Remote

Job Opportunity Announcement: USAJOBS – Job Announcement

What should I include on my resume?

Announcement shared by:

Steven A. Miller | Language Specialist / Trainer

DHS | USCIS | EXA | OAIS | Language Services Section

Filed Under: Job Opportunities Tagged With: Ukrainian

Two New Slovo Episodes!

August 9, 2024

microphone

The latest episode of Slovo, the SLD’s podcast, digs into probably the hottest and most contentious topic in T&I right now, AI, with guests Daniel Sebesta and Bridget Hylak. Whether you think you love it or hate it, you can’t escape it, so let’s talk about it!

In case you missed it, check out the previous episode profiling SLD member Viktoryia Baum, tracing her route through the language industry from starting a Bachelor’s in teaching ESL to finishing a Master’s of Conference Interpreting, adventures interpreting in the aerospace sector, and helping implement New York’s language access law.


You can find these and past episodes on the Slovo page on SoundCloud, or through Google Play, Apple Podcast, and Spotify. Follow Slovo on SoundCloud or subscribe through a podcast platform so you never miss an episode!

Filed Under: Podcast Episodes Tagged With: advocacy, AI, interpreting, translation

Generative AI and What It Means for Translators and Interpreters. Part I.

July 29, 2024

By Viktoryia Baum

Over the past year and a half, the world has been thrown into the hype (or pain?) of artificial intelligence, with the advancement of many products, and the race between the companies to create their own, unique and individual intelligent chatbots capable of many ordinary human tasks. I have been hearing from many colleagues of different ages how this is becoming an existential threat to the profession as a whole, for both translators and interpreters alike. But the real question remains: is it?

I’m a firm believer that if there’s a will, there’s a way. Meaning that I don’t think any of these “robots” will eliminate the need for the profession and the professionals, or somehow bring about our total and ultimate demise. If anything, they can be trained to help us in any imaginative way or method possible. Such opinions of mine have been met with frustration and disbelief by many of my colleagues, yet welcomed and shared by another many.

Recently, Eugenia Tietz-Sokolskaya invited and encouraged me to consider writing for the SLD blog on any subject and anything at all (thank you, Eugenia!), and although I don’t do much writing in any capacity, I figured I might as well give it a try. I usually have a lot to say about things, so why not do it here? Hopefully, the readers will not have a plate of rotten tomatoes handy to smash against the monitor as they read these lines. Maybe, just by sharing some of my experiences I may help alleviate some technology fears, or help someone learn something new. I will probably anger some colleagues and make them reach for their plate of rotten tomatoes, but that’s where technology is in my favor—unlike 200 years ago, I don’t have to deliver this speech in front of you (thank you, industrial civilization!), and I can hide behind the screen.


Let’s start with some basics and try to break down the concept of generative AI, its purpose, and what it can do. Basically, generative AI refers to artificial intelligence systems capable of generating new data and producing content. It can create not just text, but also images or even audio and video files. Here are some examples of generative AI:

  • Language models (GPT-4) that can generate human-quality text on almost any subject based on a prompt
  • Image generators used to create novel images from text descriptions (DALL-E 2 and Stable Diffusion)
  • Music generators that can compose new songs, musical compositions, or other audio using training data (MuseNet)
  • Video generators that can make video clips by processing and synthesizing existing data (Sora)

The capability behind generative AI is machine learning models, especially large neural networks. They can analyze thousands of datasets and learn the patterns and representations within that data. Having learned and captured those patterns, the models are then capable of generating new content that is similar to the training data statistically, yet differs from it in a new way. One type of machine learning model is large language models (a phrase everyone in the industry has been hearing more and more); those are built on neural architecture, and they are referred to as large because they use huge datasets. There has been a boost and a rapid increase in research and development of large language models in big tech, with any major player buckling up and racing to develop their own models and tools. The now very infamous ChatGPT is a large language model, or LLM. In simple terms, this is a computer program that has received and analyzed enough data that it is now capable of generating its own responses. The quality of the responses always depends on the quality of the datasets the LLM has been fed. The more they know, the better they are at producing content.


I’ve been experimenting with AI chatbots for quite some time now. When I said they can be trained to help us in any imaginative way or method possible, that’s because I’ve tried and largely succeeded on some level, achieving the objective I set out for myself. A few months ago, for example, I chatted with one of the publicly available chatbots (not ChatGPT) about building up a glossary specifically for use in interpretation, and I’d like to share the outcome.

The background for this experiment was fairly simple. I wear both hats of being a translator and an interpreter. In my state, I am a certified per diem court interpreter, but I live in an area with not a lot of need for court interpreting in my language combination. If anything, it’s approximately 4-5 calls a year plus a few depositions. This means that enough time passes between court appearances that my skills and language databanks typically grow rusty and need a solid refreshment before assignments. Preparing for any court appearances can be daunting due to lack of information and/or materials. If all I know is that tomorrow I am heading over to family court, how should I prepare? What should I look for?

I started with a relatively easy prompt, asking my new AI friend (let’s call him Sam) to help me put together a Russian to English legal glossary to use for interpreting purposes. In a few seconds, the system produced a glossary with some common legal terms, roughly 20 to 25, including terms like lawsuit/claim, indictment, defendant, and court order. The chatbot then asked me if I wanted to know any other specifics to be added “for my translation purposes,” to which I happily said yes, also requesting a set of legal terms in Latin, giving an example prompt of “amicus curiae.” The result was a compilation of another 25-30 terms including bona fide, nolo contendere, ex parte, pro se, inter alia, etc.

For the third part of the conversation, I congratulated Sam on providing me with the definitions of Latin legal terms in the English language, then asking if he could take these same Latin terms and give me their Russian equivalents. He obliged. It is important to note here that the glossary was provided to me in the LATIN to RUSSIAN variant, although for some reason I expected Sam to use the English translations he pulled for the Latin and only then give me the Russian equivalents. I was wrong. Sam was smart, even if my prompt was quite poorly written.

Next, I asked for more terminology, the more advanced, the better. The resulting table included terms like defamation, pre-trial agreement, acquittal, and statute of limitations. I felt that it could have been a bit more advanced, but ok. The next query asked for terms used in family and traffic courts. Then I made another query, and another, and another. But I think I made my point already. Perhaps the best glossary (in my humble opinion) was produced when I asked for terminology specifically used in an arraignment hearing. This turned up terms like request for leniency, motion to suppress evidence, own recognizance release, and recusal motion.

The entire encounter and the prompts along with their results took me approximately 5-7 minutes. The end of the conversation was quite comical, since I asked for all of the terms to be exported to Excel and sent to me via email. Sam happily agreed, took down my email address, and nothing happened. When told that no email had come, he apologized profusely for letting me down and leading me to believe he had the capability of exporting and sending emails. He said that by design he actually did not have that capability, but in his inherent desire to please me, he misrepresented his abilities. The apologetics went on for a few more rounds, much to my amusement and comic relief. It was clear that I wasn’t speaking with a human, but I got amused as if I really were.

Overall, I found the quality of the glossaries produced by AI very high. I did not find any incorrect translations, nor did I find any inconsistencies (some terms were repeated with each of the prompts, and the output was the same). If you ask me personally, I believe that for a real assignment, this approach would have saved me hours of googling terminology and trying to think about all the possible terms I could encounter. Of course, if I were unfamiliar with any of the terms or translations produced, I would have double-checked everything and cross-referenced items using regular old-fashioned dictionaries. For example, if I were to go and interpret at a mining conference, or any other completely foreign subject, like rare and valuable gemstones, I would follow up on what the AI told me.

I forgot to mention that I went into this experiment with very low expectations. I can’t say that I wanted the AI to give me erroneous translations of the terms, to prove that humans and only humans are capable of creating a glossary, but I did think there would be errors. AI proved me wrong, at least for that exercise. I intend to keep practicing and conversing with it regarding my needs in the profession. If you are given the tool, why not use it? And if you are skeptical, I would invite you to try for yourself. Or you can reach for that plate of rotten tomatoes……just kidding. In short, you don’t have to love it or hate it, endorse it or promote it. It’s just a tool. If it can help you save time and do a better job, why not. If anything, you will definitely get some comic relief from experimenting.

If you have any comments or feedback regarding this blog post, I invite you to reach out directly to me via email at vbaum00@gmail.com. In the meantime, I’ll work on Part II of this series over the next weeks. Thanks for reading, and stay tuned!


Viktoryia Baum is an avid technology buff and skilled researcher who spends at least part of her spare time studying new and existing language tools. Having started as an aerospace interpreter many years ago, she discovered she was equally good at translation, so she does both, working with Eastern European languages and specializing in technical, legal, and medical translation and interpreting. She lives in upstate New York and can be contacted at vbaum00@gmail.com.

Filed Under: Interpreting, Legal, Tools Tagged With: artificial intelligence, interpreting, Russian

Achieving High-Quality Translation: The Final Step

June 24, 2024

High-quality translation requires in-depth domain knowledge, meticulous attention, and a series of well-defined steps. In this article, I’ll focus on the last stage of a standard translation project: automated Quality Assurance (QA).

QA ensures that hard-to-spot and easy-to-miss errors are eliminated. Common issues include source and target inconsistencies, capitalization errors, incorrect spacing around punctuation marks, numerical mistakes, missing or extra tags, incorrect quotation marks, terminology mistakes, measurement unit discrepancies, etc.

Below are the steps I use when doing QA.

  1. Built-in CAT tool QA:

Most computer-assisted translation (CAT) tools (e.g., Trados Studio or memoQ) offer built-in QA functionality. Enable the relevant options in the CAT tool menus and run QA.

  1. Export to Word and use Word’s proofing features:

If your CAT tool allows it, export the translation to Microsoft Word. Press F7 to check for additional mistakes that the CAT tool may have missed. Ensure that Word’s proofing options (grammar, repeated words, uppercase words, etc.) are activated.

  1. Standalone QA tools:

Use standalone QA tools for comprehensive checks. Xbench, Verifika, and QA Distiller are some of the oldest and most popular ones.

QA Distiller is completely free, Xbench has a free limited-functionality version, and Verifika (my personal favorite) has a fully functional free web version, provides language-dependent checks, and covers numerous mistake categories. Take the time to configure Verifika with the options you need—it’s worth the effort.

  1. Double-check and run QA again:

Correct any mistakes the tool found and run another round of QA to catch any overlooked errors or newly introduced mistakes.

  1. Use multiple QA tools:

If you’re doing a test translation or working on a particularly important project, consider running QA using multiple tools. It’s better to spend time reviewing false positives than to miss an embarrassing error.

  1. Impress the client:

Go the extra mile by exporting a final QA report containing only false positives. Demonstrating your commitment to quality will leave a positive impression.

Let no mistakes slip through into your translations!


This is the third and final post in a series of posts on translation quality. The first post can be found here, and the second here.

headshot of Mikhail YashchukMikhail Yashchuk is an industry veteran. In 2002, he received his university degree in English, and six years later he founded a boutique agency where he gained experience in linguist recruitment, project management, translation, editing, and quality assurance. He has recently been admitted as a sworn translator to the Belarusian Notary Chamber.
In 2018, Mikhail joined the American Translators Association and is now working as an English-to-Russian translator, actively sharing knowledge with younger colleagues. He is the moderator for the
SLD LinkedIn group. He may be contacted at mikhail@lexicon.biz.

Filed Under: Tools, Translation Tagged With: CAT tools, series, translation

Navigating Translation Tests: Tips for Success

June 10, 2024

by Mikhail Yashchuk

As a former boutique agency owner, I was responsible for linguist selection for 15 years. That meant that part of my routine was checking test translations. Here are some tips I can give test-takers.

✅Before taking a test, agree on rates, payment methods and other terms with the client.

You don’t want to pass a test only to find out the client can only pay you half of your regular rates, 90 days after the invoice, or using a payment method you can’t accept.

✅Leave comments if you want to clarify anything or support your linguistic choices.

Not all tests are ideal—some have ambiguities, some are out of context, some have inconsistent terms and some even contain mistakes.

Don’t be afraid to ask the client to clarify certain things. Asking relevant questions doesn’t mean you don’t know what you’re doing. On the contrary, it shows that you are attentive to detail and don’t translate blindly.

Linguistic choices can be very subjective; there are usually many correct ways of saying the same thing in the target language. So, if you think your choice of a word or term is not obvious and might be considered a mistake, leave a comment for the reviewer. Your reasoning, supported by a link to an acknowledged website or an industry standard, will be appreciated by the reviewer.

✅Use correct quotation marks (e.g. «» for Russian).

Whether you translate your test piece using Microsoft Word, a CAT tool or an online environment that may not directly support all punctuation, make sure you use correct quotes.

You can use keyboard shortcuts (e.g. Alt+0171 and Alt+0187), tick Replace straight quotes with smart quotes in Trados or simply copy and paste correct quotation marks into the translation.

✅Use a spell checker and make sure the UPPERCASE option is turned on.

Make sure the spell checker is turned on and all relevant options are ticked. If you work in Chrome, choose Enhanced spell check in Settings-Languages so that Chrome shows your mistakes in words in uppercase.

✅If you work in a CAT tool, run automated quality assurance (QA) in Xbench, Verifika, etc.

The test translation must be spot-on, so it may be a good idea to use as many QA tools as possible, because not all of them are able to find the same types of mistakes. While such tools often produce lots of false positives, it’s better to spend time checking them than to miss an embarrassing error.

✅Check your text several times.

If time permits, leave the translated piece aside, then come back and check it against the source for meaning. Then leave it aside again and check it later without looking at the source, correcting typos, punctuation, grammar and style. Repeat the last step at least twice.

✅Rephrase sentences that don’t sound natural.

If a sentence is correct in meaning but sounds awkward, try to change it—split a long sentence into two, merge two short sentences into one, use a verb instead of a verbal noun, change word order, etc.

✅Check the translation for double spaces.

Run this check (by pressing CTRL+F and typing 2 spaces) several times to find all double and triple spaces and be careful with extra or missing spaces around tags—sometimes they need to be searched for manually.

❌Don’t use hyphens (-) instead of n-dashes (–) and m-dashes (—).

Know the rules for your language (compound words, minus signs, number ranges, complex sentences, etc.) and use the correct dashes, even if the tool you work in doesn’t directly support them.

❌Don’t blindly copy source grammar structures.

That’s what Google Translate is for 😊. Human translations need to sound natural, and that often entails changing the original grammar and word order.

❌Don’t try to hand in the test ASAP.

I came across an agency once that required completing test translations within 30 minutes. But most clients expect quality and not speed, so take your time to provide your best translation ever, since there may not be a second chance.

❌Above all, don’t take a test in a domain of which you have no knowledge.

This is the last tip, but it should probably be the first on the list.

Good luck with passing your tests and finding good clients!


This is the second in a series of posts on translation quality. The first post can be found here, and the third and last, on ensuring quality by using QA tools, here.

headshot of Mikhail YashchukMikhail Yashchuk is an industry veteran. In 2002, he received his university degree in English, and six years later he founded a boutique agency where he gained experience in linguist recruitment, project management, translation, editing, and quality assurance. He has recently been admitted as a sworn translator to the Belarusian Notary Chamber.
In 2018, Mikhail joined the American Translators Association and is now working as an English-to-Russian translator, actively sharing knowledge with younger colleagues. He is the moderator for the
SLD LinkedIn group. He may be contacted at mikhail@lexicon.biz.

Filed Under: Business Practices, Translation Tagged With: editing, series, translation

Tips for Self-Checking Your Translations

May 28, 2024

by Mikhail Yashchuk

In our industry, everyone talks about quality. But how do you achieve it?

Education, experience, specialization, attention to detail, etc. go without saying. But today I’d like to share a simple and proven step-by-step workflow to make your translations sound natural. I have been using this workflow for 15 years and hope you find it useful.

The first step after translating a text is to set it aside for some time. When you’ve been working on a translation for a long time, you can become “blind” to errors or awkward phrasing. By stepping away from the text, you allow your brain to reset and approach the text with fresh eyes when you return to it.

Next, compare the translation against the source. This is where you carefully check for major issues such as meaning, terminology, and consistency. It’s important to ensure that the translated text accurately reflects the original meaning and that the correct terminology has been used consistently throughout. This stage also involves checking for any omissions or additions that shouldn’t be there.

After this, if possible, set the translation aside for some more time. This additional break allows you to return to your text with an even fresher perspective and with less memory of the source.

The final step is to read the translated text without looking at the source. This is a critical step that should never be skipped.

Since meaning mistakes have been fixed at the previous stage, you can forget about the original and focus solely on the translated text. Reading it from your target-language reader’s perspective allows you to spot issues with punctuation, grammar, and flow. During this step I focus on style and make many changes that result in a high-quality target text that reads naturally, as if it was originally written in the target language and not translated. To achieve such quality, sometimes I need to repeat this step several times.

This step is particularly effective for spotting sentences that don’t flow well. I’m not only talking about creative or marketing translations here. Technical, IT, healthcare, and other specialized translations need to sound natural too. They need to be concise and not use unnecessary words that make sentences longer without conveying any useful meaning. One of the few exceptions I can think of is legal translations where there may be limitations on combining or breaking up sentences.

If a sentence seems awkward or unnatural, it’s a sign that it needs to be reworked—you can change word order or sentence structure, split one sentence into two, combine two sentences into one, transform passive voice into active voice, use verbs instead of verbal nouns, etc.

P.S. These steps should not replace standard editing by a second person. To err is human; even the most experienced and careful translators can make mistakes, whether they are minor stylistic errors or major issues in meaning. Having a second person review the translation can help catch these errors and ensure the highest quality output.


This is the first in a series of posts on translation quality. Keep reading to learn about ensuring quality when doing translation tests and using QA tools.

headshot of Mikhail YashchukMikhail Yashchuk is an industry veteran. In 2002, he received his university degree in English, and six years later he founded a boutique agency where he gained experience in linguist recruitment, project management, translation, editing, and quality assurance. He has recently been admitted as a sworn translator to the Belarusian Notary Chamber.
In 2018, Mikhail joined the American Translators Association and is now working as an English-to-Russian translator, actively sharing knowledge with younger colleagues. He is the moderator for the
SLD LinkedIn group. He may be contacted at mikhail@lexicon.biz.

Filed Under: Translation Tagged With: editing, series, translation

Reminder: Don’t Miss SLD’s Spring 2024 Networking Meetup!

May 13, 2024

ATA SLD Networking MeetupDon’t miss our next quarterly gathering on Zoom this Sunday, May 19, 2024. Come chat with Slavic Languages Division colleagues about what’s going on in life and in business. The past meetups have offered members a valuable chance to catch up with each other. We hope that this one will give attendees a sense of connection and motivation going forward.

Grab something from the fridge and meet us on Zoom from 2–4 PM EDT on Sunday, May 19. Come when you can, leave when you must!

To ensure you get a link for the event, register here. For questions, please email SLD Assistant Administrator Natalia Postrigan (postrigann09@gmail.com) before the meetup. We hope to see you there!

Filed Under: SLD, SLD Networking Tagged With: networking, SLD

  • « Previous Page
  • 1
  • 2
  • 3
  • 4
  • …
  • 16
  • Next Page »

Recent Posts

  • Turkic Languages SIG: Seeking Moderator
  • ATA65 Review: On Interpreting for Russian-Speaking LGBTQ+ Individuals
  • ATA65 Review: I Can’t Place the Accent
  • SLD Announcements: Networking Zoom and ATA66 Deadline Extended
  • Speak at ATA66 – Proposals Due March 3

SLD on Twitter

My Tweets

SLD on Social Media

Facebook: ATA Slavic Languages Division LinkedIn: Slavic Languages Division of the American Translators Association

Tags

Administrative AI annual dinner ATA ATA58 ATA59 ATA60 ATA61 ATA63 ATA64 ata65 ATA66 audiovisual AVT business CAT tools certification ceu watch conference editing events feedback interpreting interview legal literary localization marketing medical member profile networking podcast Polish professional development project management Russian series session review SlavFile SLD specializations survey translation webinar workshop

SLD Blog Categories

Search This Website

Copyright © 2025 · American Translators Association

 

Loading Comments...