<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://charlesm93.github.io/feed.xml" rel="self" type="application/atom+xml" /><link href="https://charlesm93.github.io/" rel="alternate" type="text/html" /><updated>2026-04-06T17:41:42-07:00</updated><id>https://charlesm93.github.io/feed.xml</id><title type="html">Charles Margossian</title><subtitle>personal description</subtitle><author><name>Charles Margossian</name><email>cmargossian@flatironinstitute.org</email></author><entry><title type="html">💭 One of my favorite papers (that I have written)</title><link href="https://charlesm93.github.io/posts/2025/09/blog-post-3/" rel="alternate" type="text/html" title="💭 One of my favorite papers (that I have written)" /><published>2025-11-15T00:00:00-08:00</published><updated>2025-11-15T00:00:00-08:00</updated><id>https://charlesm93.github.io/posts/2025/09/blog-favorite_paper</id><content type="html" xml:base="https://charlesm93.github.io/posts/2025/09/blog-post-3/"><![CDATA[<p>During my academic job search, I was sometimes asked what my favorite paper was.
I liked this question because it is an invitation to discuss not just the paper
itself but also the story behind it—most likely, a story that dives into the
inevitable setbacks of doing research and the struggle to overcome these
setbacks, usually with the fortuitous help of some great colleagues.
Chances are, you can relate: maybe you just finished a difficult proof; or
maybe you’ve just realized a piece of code doesn’t work; or maybe you’ve been
stuck on that mathematical argument for a while and you just can’t quite
figure out that one detail that keeps resisting you.</p>

<p>Today, I’d like to share a paper and a story that made me go through many
(emotional) phases of research.
The paper is <a href="https://arxiv.org/abs/2403.13748">Variational Inference for Uncertainty Quantification</a>,
written with Lawrence Saul and Loucas Pillaud-Vivien.</p>

<p><strong>Disclaimer:</strong> During the job search, this was <em>not</em> the paper I spoke about :)
My favorite paper (that I’ve written) is probably still the <a href="https://arxiv.org/abs/2110.13017">nested $\widehat R$ paper</a>.
But when I got home from an interview, I started thinking, the VI for uncertainty
<em>could’ve</em> also been a good paper to discuss and I drafted this blog post way
back in February 2025.</p>

<p>The paper has now appeared in the <em>Journal of Machine Learning Research</em>.
Here’s the abstract:</p>

<p><em>Given an intractable distribution $p$, the problem of variational inference (VI) is to find the best approximation from some more tractable family $\mathcal Q$. Commonly, one chooses $\mathcal Q$ to be a family of factorized distributions (i.e., the mean-field assumption), even though $p$ itself does not factorize. We show that this mismatch can lead to an impossibility theorem: if $p$ does not factorize and furthermore has a non-diagonal covariance matrix, then any factorized approximation $q \in \mathcal Q$ can correctly estimate at most one of the following three measures of uncertainty: (i) the marginal variances, (ii) the marginal precisions, or (iii) the generalized variance (which for elliptical distributions is closely related to the entropy). In practice, the best variational approximation in $\mathcal Q$ is found by minimizing some divergence $D(q,p)$ between distributions, and so we ask: how does the choice of divergence determine which measure of uncertainty, if any, is correctly estimated by VI? We consider the classic Kullback-Leibler divergences, the more general $\alpha$-divergences, and a score-based divergence which compares $\nabla \log p$ and $\nabla \log q$. We thoroughly analyze the case where $p$ is a Gaussian and $q$ is a (factorized) Gaussian. In this setting, we show that all the considered divergences can be ordered based on the estimates of uncertainty they yield as objective functions for VI. Finally, we empirically evaluate the validity of this ordering when the target distribution p is not Gaussian.</em></p>

<p>(February 9th 2025)</p>

<h2 id="a-textbook-question">A textbook question</h2>

<p>A little over two years ago, I started working on variational inference (VI).
As I read the literature, I kept coming across the comment that “VI
underestimates uncertainty” and I wanted to convince myself of this fact with
a simple example. Say I approximate a non-factorized Gaussian with a factorized
Gaussian, can I show that the approximation always underestimates the marginal
variances? So I scribbled and scribbled, and I didn’t get anywhere.
No problem: VI legend Lawrence Saul was down the hall
(at the <a href="https://www.simonsfoundation.org/flatiron/center-for-computational-mathematics/">Flatiron Institute</a>),
and I submitted this textbook problem to him. He agreed the result seemed elementary.
In fact, many books and review papers proved the claim in 2-D, and it seemed
straightforward to generalize it to higher dimensions.</p>

<p>So we went to the black board, and we tinkered, and tinkered, and… hmmm…
could this problem be harder than we thought?</p>

<p>We did eventually write a proof: it was short but unintuitive. (I didn’t like
this proof.) (The excellent paper by <a href="https://www.gatsby.ucl.ac.uk/~maneesh/papers/turner-sahani-2010-ildn.pdf">Turner &amp; Sahini (2011)</a>
has a statement of the result, albeit without a proof.)
Then we derived more results on variance estimation and wrote a <a href="https://proceedings.mlr.press/v216/margossian23a/margossian23a.pdf">precursor</a> to our paper on VI uncertainty.</p>

<h2 id="a-fleeting-shadow">A fleeting shadow</h2>

<p>Lawrence felt strongly that in addition to variance we should also analyze entropy
as a measure of uncertainty. And we did find that VI also underestimates entropy.
But when I ran numerical experiments, something surprising
transpired. As dimension increased, I found that estimates of the variance
became worst, while estimates of the entropy improved. This contradicted our
visuals: the volume of the approximating sphere was clearly much smaller than
the volume of the target ellipsoid. For entropies to match, you would need
the volumes of the two objects to be the same.</p>

<p><br /><center>
<img src="/images/ellipse.png" alt="hi" class="inline" style="width:100;height:150px;" />
</center><br />
Fig1. <em>Factorized Gaussian approximation of an $n$-dimensional Gaussian. The target
has a covariance matrix with constant off-diagonal element $\varepsilon$.</em></p>

<p>I checked and double-checked my code, and I couldn’t find an error. And then I
had a happy thought. The two dimensional picture we were looking at was
misleading. The sphere was not smaller than the ellipsoid, even though its shadow was.
Each time we “added” back a dimension, the sphere would grow in every direction, while the
ellipsoid would only grow a little bit. Until eventually, the volume of the
two objects nearly matched.</p>

<p>Here’s another way to understand the result. Setting correlations to 0 (as one
does with the factorized/mean-field approximation) increases entropy. If our
goal is to match the entropy of the target, the increase in volume caused by
the null correlation must be compensated by a shrinkage in the marginal variances.
Conversely, matching the variances means overestimating the entropy of the target. The two
measures of uncertainty therefore compete with one another. This fact is
elegantly captured by an equation we termed the <em>shrinkage-delinkage trade-off</em>.
Here it is, without any proper definition of the terms but just to highlight its simplicity:
<br /><center>
$$ \Delta \mathcal H = \frac{1}{2} \log |S| - \frac{1}{2} \log |C|^{-1}. $$
</center><br />
This late result became the main character of our precursor paper.</p>

<p>I <a href="https://www.youtube.com/watch?v=2q5azatd-Ko">presented this result at the UAI conference 2023</a> in Pittsburg. It was a fun
conference, mostly because I met some amazing PhD students and postdocs to
hang out with. I should now mention that all the work Lawrence and I did was
based on minimizing the reverse Kullback-Leibler divergence,
<br /><center>
$$
\text{KL}(q||p) = \int (\log q(z) - \log p(z)) q(z) \text d z,
$$
</center><br />
which is the usual
objective function we minimize in VI. Many people asked me if I had thought
about what would happen if I minimized other divergences
and I figured this would be a straightforward extension.
It would also allow me to address a question that had long pre-occupied me,
namely what is the best way to compare probability distributions?</p>

<h2 id="thanksgiving-break">Thanksgiving break</h2>

<p>So back to the blackboard (we have beautiful blackboards at the Flatiron
Institute). I looked at a few divergences and even some metrics. Did you
know there is not analytical expression for the total variation distance
between two multivariate Gaussians? It turned out the KL-divergence was
particularly easy to manipulate, with other divergences posing additional
challenges. Still, we made progress, one divergence at a time.</p>

<p>I had another small breakthrough on Thanksgiving. I remember I was taking the
bus to Pennsylvania. I had missed my original bus and then, I received an email,
telling me another paper of mine had gotten rejected. I read the reviews and
felt absolutely gutted. I can still see it: the overcrowded bus terminal, the
endless waiting, the phone call I made to a close one, the reviews I read and
re-read and re-read. It was a sunny day. I was fortunate to be with family that
day. And the next morning, I woke up early and felt the need to make amends
for my “failure”. I sat in the kitchen and extended the shrinkage-delinkage
trade-off to a three-way impossibility theorem between precision, variance,
and entropy.</p>

<h2 id="loucas-napkin">Loucas’ napkin</h2>

<p>I had intended to submit a manuscript by the end of November, with the hope
that within a year, my paper would be reviewed and accepted, and that this
would strengthen my application for my next job. (None of this happened.) Some
of the results resisted us. Lawrence and I had an incredibly difficult time
proving an “ordering” of the Renyi $\alpha$-divergences. We felt close: each
week, we believed we would finish the proof; and each week, the last piece
of the puzzle eluded us.</p>

<p>One day, I was working at the white board, messing around with the terms of
an equation. My then fellow post-doc Loucas Pillaud-Vivien walked by and asked
me what I was working on. So I explained the problem. He then grabbed a marker
and began working in his corner of the white board. He shared his ideas, his
perspective as a theorist and a probabilist. He spoke about “agreeable facts”,
he dug out results from linear algebra that I wasn’t familiar with. It was also
fun for me to revisit the topic in French, somehow it gave me a fresh
perspective. (Loucas was also French.)</p>

<p>And so, Loucas joined forces with Lawrence and I. I remember the day when we
finally cracked the proof. It was a Friday. We  felt close (as always) and it
was getting late. Another one of our colleagues brought beers and we drank
them in front of the white board. Now we were one or two details away from
the contradiction that would complete the proof. But I had a ballroom dance
practice and I left the office.</p>

<p>Later that night, while I was warming up at the dance studio, I got a message
from Loucas: “I think I got it. You can dance in peace.” Dance in peace?? No,
I had to see the proof for myself before being “at peace”. Right after practice,
Loucas and I met at the usual Mexican bar and he completed the proof on a napkin, which is
a cliche, but we had ran out of paper.</p>

<p>After that, it took me quite a bit of time to check all the proofs, scattered
in my notebooks, and patch together the missing details. And of course,
Lawrence made an heroic effort editing the manuscript and making sure it lived
up to his very high writing standards.
I suppose the story is far from finished, since the paper is still under review…!</p>

<h2 id="afterthought">Afterthought</h2>
<p>(November 11th)</p>

<p>I don’t believe there’s anything extraordinary about this project. It’s a
typical good research story and illustrates one of the happy collaborations I
had as a postdoc. Some of the results seem elementary, or to use a more
flattering word, fundamental. (A reviewer criticized results I had in another
paper as “elementary” and it had never occurred to me that this word could
have a negative connotation.) I trust we will see the results we derived in
upcoming textbooks. With time, I was able to simplify several of the proofs.
At this point, I am aware of four proofs to show VI underestimates variance,
each offering its particular perspective.</p>

<p>p.s. The paper was desk-rejected from a first journal. We then revised it quite
a bit and sent it to JMLR. After a few months, we got requests for some
minor revisions and the paper was published another few months later.</p>]]></content><author><name>Charles Margossian</name><email>cmargossian@flatironinstitute.org</email></author><category term="research" /><category term="variational inference" /><summary type="html"><![CDATA[During my academic job search, I was sometimes asked what my favorite paper was. I liked this question because it is an invitation to discuss not just the paper itself but also the story behind it—most likely, a story that dives into the inevitable setbacks of doing research and the struggle to overcome these setbacks, usually with the fortuitous help of some great colleagues. Chances are, you can relate: maybe you just finished a difficult proof; or maybe you’ve just realized a piece of code doesn’t work; or maybe you’ve been stuck on that mathematical argument for a while and you just can’t quite figure out that one detail that keeps resisting you.]]></summary></entry><entry><title type="html">🗺️ The Job Market Campaign</title><link href="https://charlesm93.github.io/posts/2025/06/blog-post-1/" rel="alternate" type="text/html" title="🗺️ The Job Market Campaign" /><published>2025-11-10T00:00:00-08:00</published><updated>2025-11-10T00:00:00-08:00</updated><id>https://charlesm93.github.io/posts/2025/06/blog-job_market</id><content type="html" xml:base="https://charlesm93.github.io/posts/2025/06/blog-post-1/"><![CDATA[<p>“Ce fut au milieu de ces pensées généreuses, et dans cette disposition d’esprit,
qu’il traversa l’Hellespont.”
(“<em>It was amidst these generous thoughts and with this mindset that
he crossed the Hellespont.</em>”)<br />
– Maurice Druon, <em>Alexandre le Grand</em> (1958)</p>

<p>Last fall, I went on the academic job market and applied for tenure-track
faculty positions primarily in Statistics. I’m happy to
report I received multiple offers and accepted a position at the
<a href="https://www.stat.ubc.ca/">University of British Columbia</a> in Vancouver 🇨🇦</p>

<p>I’ve benefited a lot from the guidance of mentors and peers,
and the occasional blog post. A blog post is no substitute for the
advice of a seasoned academic, still it may provide unexpected tips and
it can make the job search feel like a less lonely endeavor. With that in mind,
I’ll contribute my brick to the edifice and describe my personal experience.</p>

<h2 id="summary-of-tips">Summary of tips</h2>
<ul>
  <li>Set abstract goals—e.g. conduct impactful research, educate the next
generation—as opposed to fixating on a particular school or location.</li>
  <li>Don’t go on the job market just to try it out (the “dip your toe” approach).</li>
  <li>Wait until the end of the summer to start working on application material.</li>
  <li>Only apply to places where you might accept an offer.</li>
  <li>Keep your application material short and informative for the recruiting
committee.</li>
  <li>Use the same CV, research statement and teaching statement
for every institution.</li>
  <li>It’s ok to use a generic cover letter. However, if there is something that
makes you particularly excited about one school, this is the place to mention it.</li>
  <li>The job talk is the most important part of the on-site interview, so put
in the time to prepare it and do a few practice runs with an audience. Then
put in more time. Be a perfectionist!</li>
  <li>In your job talk, privilege clarity. Resist to urge to impress with technical
details—unless you can make them intelligible! People outside your particular
subfield should understand what you’re doing and where you’re going.</li>
  <li>During the job talk, encourage people to ask questions. It will make things
more interesting for your audience and for you.</li>
  <li>The job market campaign is long. Take care of yourself: exercise, travel with
good books, and have people with whom you can discuss your journey.</li>
</ul>

<h2 id="when-should-the-job-search-begin">When should the job search begin?</h2>

<p>I like to call the job search the <em>job market campaign</em>. Because it will take
up a lot of your time and energy. It’ll be the proverbial full-time job.
And so, here are two advice I received and I’m happy to pass on:</p>
<ul>
  <li>Don’t apply on a year just to try it out and see what happens. Some people
argue it doesn’t hurt to try and you might get lucky. But it does hurt. It
takes up your time and eats up your mental bandwidth. In my view, there is no
point dipping your toe in the job market. If there is an exceptional
opportunity, pursue it, otherwise, wait until the end of your PhD or
postdoc.</li>
  <li>If applications are due in the fall, wait until the end of the summer to
work on your application material. Because once you do, it’ll be very hard
to focus on anything else and the presumably important work you’re doing.
I waited until October. In September, I finished a paper and attended a
conference I was co-organizing.</li>
</ul>

<p>Don’t get me wrong: you still need to lay the groundwork before hand.
That means doing research, attending conferences, advertising that you will
be applying for positions (that takes courage but do it; you want to hear
about opportunities.) And working out who your three/four letter writers will
be—keep in mind that some institutions require someone to write about your
teaching.</p>

<p>Another good piece of advice is start acting like a professor (this is
pretty much the one thing I remember from reading <a href="https://books.google.com.sg/books/about/The_Professor_is_in.html?id=XTZEBQAAQBAJ&amp;source=kp_book_description&amp;redir_esc=y">The Professor is in</a>
when I was a PhD student). That can mean several things but essentially:
take charge. Organize conference sessions, invite seminar speakers, lead
your research.</p>

<h2 id="where-do-you-apply">Where do you apply?</h2>

<p>Here’s some wisdom from my advisor: only
apply if there is a chance you would accept an offer. Otherwise, you’re wasting
their time and your time.  That said, you should keep an open-mind.
The chance of accepting the offer need not be high. Think about your hard
constraints and your soft constraints. For example, a hard constraint might
be living with a significant other. A soft constraint might be: you prefer a
city to a small town. If something doesn’t meet your soft constraints,
that shouldn’t prevent you from applying to an otherwise good department.</p>

<p>The other thing is that you’ll learn a lot about yourself while you’re applying:
as you visit universities, as you (fingers crossed!) consider multiple offers,
as your personal situation evolves, heck even as geopolitics change…
You’ll learn what your priorities are as you go through the process.</p>

<p>I first made a list based on universities I was a familiar with, mostly because
I knew at least one good professor there. If I was in good terms with that
professor, I would reach out to ask them about the job opening and whether they
thought I would be a good fit. (Often, I had already had this conversation
with the professor at a conference or seminar.)</p>

<p>Then, I added research universities in locations that I liked and where I
could imagine myself living. I looked at listings such as
<a href="https://careerconnect.amstat.org/jobs/">asa career</a>,
<a href="https://jobs.imstat.org/jobs/">imstat jobs</a>, and
<a href="https://forms.stat.ufl.edu/statistics-jobs/">statistics jobs</a>.</p>

<p>Once I compiled the list, I went over it with my letter writers and got some
additional recommendations. Then I put together a big XL sheet, wrote down
deadlines, and unconventional requirements.</p>

<p>I applied to about 50 places. Some people think it’s not enough, others
that it’s too much. I was applying to different countries, so that increased
the number of places I was willing to consider. What’s more, many institutions
require the same documents, so you can streamline the process.</p>

<h2 id="application-material">Application material</h2>

<p>The standard requirements are: a CV, a cover letter, a research statement,
a teaching statement, sometimes a diversity statement, and at least three
letters of recommendation.</p>

<p>Here are some recommendations:</p>
<ul>
  <li>Keep it informative. No need for generic statements that any applicant can
write, i.e. “we live in a golden age of Computational Statistics…”. (For most
people, this means deleting the first paragraph of the cover letter and
research statement.) You want the admissions committee to learn about what
distinguishes you.</li>
  <li>Find the place that imposes the shortest length constraint on each document
and use that as your template. It turned out my four-page research statement
was just as good as my five-page one, and writing shorter statements is often
more effective.</li>
  <li>I used the same CV, research, teaching and diversity statements for almost
every institution I applied to. Sometimes I would tweak the teaching statement
depending on whether I was applying to a stats or CS program.</li>
  <li>The research statement should send a clear message to a reader who only
reads the first paragraph and one who only reads the first page. If someone
is motivated to read the whole thing, great. Make sure you talk about your
work and your future work over the coming years. (Let’s be honest, you won’t
stick to your five-year plan but people expect you to have a direction…)</li>
  <li>Ask peers who recently landed positions if they could share their material
with you. It will give you a compass.</li>
  <li>General writing advice: you’re writing for your reader. Make it as easy
as possible for them, make sure there always have all the information they
need to understand what you’re saying, what you’re showing in a figure, etc.</li>
</ul>

<p>Regarding the cover letter, I received two contradictory advice, which I’m
compelled to share:</p>
<ul>
  <li>Nobody reads the cover letter so put as little effort into it as possible.
Really, all you need is: “Dear committee, enclosed is my application.
Sincerely, Charles Margossian.” 😂</li>
  <li>The cover letter is the one place where you get to talk about the institution
you’re applying to. You shouldn’t sell yourself (the rest of your application
already does that). You should explain why you would accept an offer, if you
got one.</li>
</ul>

<p>I really like this last advice. I find it considerate. However, given the volume
of places I was applying to, I couldn’t do it for every university. But they
were a handful of places, where I felt a particular affinity and I wrote down
why. (In the end, I got interviews at both places that received a custom cover
letter and ones that got a generic letter.)</p>

<p>Final advice: proof-read, read your statements out loud, and have two/three
friends or colleagues proof-read your application. I was incredibly
lucky in that respect. I had great writers read my material with patience
and kindness. If you ask for more feedback, you’ll start getting contradicting
advice. And also: no advice is sacred. Write in your own voice.</p>

<h2 id="the-job-talk">The job talk</h2>

<p>If you’re fortunate enough, you’ll get interviews and you’ll need to hold a
seminar. There are a lot of advice on how to give a good talk and
often academics blatantly disregard them. I believe that, as a
community, we should all invest more time into preparing good talks. Think
about how much better conferences would be! But until that happens, you have
an opportunity to distinguish yourself as a competent speaker 🎉</p>

<p>To me, the most valuable resource has been
<a href="https://www.youtube.com/watch?v=Unzc731iCUY">this lecture</a>
by Patrick Winston. I would try and implement every piece of advice,
at least as an exercise. You can then adjust to your style.</p>

<p>Beyond that:</p>
<ul>
  <li>Privilege clarity. I realize sometimes it feels like we need to impress our
audience and convince them that our work is super hard and non-trivial,
especially for a job talk. But in the end, you want the audience
to be on board with you and feel like they’re taking something away from your
presentation, other than “this is not my field or this went too fast for
me”. Trust that the audience values your work: they’re mostly professors who
liked your application enough to invite you. Some of the coolest feedback I got
during interviews was: “this wasn’t my field but I understood everything you
were doing and I always knew where you were going.” Also, remember there will
be graduate students in the audience: make it worth their time!</li>
  <li>Your title should be short but informative. It should give the committee an
easy way to label you. I didn’t do an outstanding job here, but my job talk
was titled “Markov chain Monte Carlo and Variational Inference in the age
of parallel computation”. Ok, so I’m the MCMC and VI guy who cares about
modern hardware.</li>
  <li>Be a perfectionist. There shouldn’t be any slide or figure that can be
improved in an obvious way. Put in the hours.</li>
  <li>Don’t use beamer: keynote or google slides.</li>
  <li>Practice your talk a few times and get feedback. I did a few practices on my
own, one practice at my institution, and one at my alma matter. Suffer through
the feedback. Use it. Again, put in the hours.</li>
  <li>Pause. Control your tempo. Silence builds suspense and gives the audience a chance to
catch their breath.</li>
  <li>If you give your talk several times, you might lose the enthusiasm you
initially had. It can be good to freshen up the talk. In my case, I invited
people to ask questions during the talk. This made for more lively conversations.
(You should know your material well enough to engage in these discussions.)</li>
  <li>Beware that, while most questions will be genuine, you’ll occasionally get the
“let me grill the candidate” question. Do your best, but I wouldn’t worry too
much about it. It’s more important to answer the curiosity-driven questions.</li>
</ul>

<h2 id="the-interviews">The interviews</h2>

<p>Part of the on-campus visit will be one-on-one interviews. I don’t have too
much advice here. Did I know everyone who was going to interview me? No. In
fact, the job search made me realize I didn’t know the vast majority of people
in my field.</p>

<p>Most professors prepare the interview and have a set of topics they want to
discuss. When that happens, roll with that. The chair will usually cover
the big topics (funding, tenure, etc.). Professors you knew beforehand and
young faculty are people who can give you the inside-scoop.</p>

<p>If you’re interviewing in the winter, bring some cough drops. You and your
interviewer might need them.</p>

<p>I had one or two tough interviews and one or two what-should-we-tak-about
awkward meetings. But overall, interviews were straightforward and pleasant.
People were nice, interesting and interested.</p>

<p>I also really liked the dinner. Yes, don’t get drunk, don’t be a slob, this is
still part of the interview, blah blah blah. But relax. Be yourself. If you
don’t BS them, they won’t BS you. They want to know if you would be a good
colleague to hang out with. Everyone at this table wants to have a
pleasant dinner. I’d think of it as a small celebration: both you and them
put in a lot of hard work for the interview. As a reward you get a three-course
meal and a glass or two of wine.
(I don’t know if they do it for every candidate or just because I’m French,
but I was consistently asked to pick a wine for the table, so maybe I have
some elementary notions of wine pairing.)</p>

<h2 id="well-being">Well-being</h2>

<p>The job market campaign is long. If you’re like me, you’ll mostly stop doing
anything else at work to focus on it. Still: your colleagues will ask for
your help on a project, you’ll get a damming review that requires a response…
and more than that, life won’t stop. You’ll probably be going through
your own set of personal challenges.</p>

<p>Of course, the market itself will be trying. For some time, I wondered why I
wasn’t hearing from some places. Then I freaked out about scheduling interviews
scattered across the world. I questioned whether I had the right priorities:
should I move back to Europe to be close to family? Should I stay in New York
where I had lived for eight years? Should I…?</p>

<p>When I got my first job offer, I broke down crying. Not tears of joy. I had
just finished a full day interview and was prepping
a “future job talk” for my next university visit (I really procrastinated
on that one and stayed up until 2 am). I was completely depleted.
Of course, I was happy about the offer itself.
But not relieved: the offer came with an exploding deadline
and it seemed likely I would have to turn it down.
At that point, I experienced total mental overload. Also, I was sad,
because I always imagined that I would be surrounded by people I love
to celebrate, if I one day I got a faculty job offer. Not alone in a hotel,
exhausted and preparing the next interview.</p>

<p>In a both good and bad way, the job market campaign keeps you busy and forces you to
move forward. Traveling gives me a lot of peace: this is where I meditate,
look out of the window, and sometimes chat with other travelers (who will find
it super exciting that you’re trying to become a professor).</p>

<p>Here’s my last set of advice. This one is more personal, so obviously only
take what’s useful for you:</p>
<ul>
  <li>Take good books with you. For me, it was <em>Alexandre, le grand</em> by
Maurice Druon: a fictionalized account of Alexander the great, narrated by
his seer, and so with an emphasis on the religious aspect of his journey.
Captivating and emboldening. And then, the complete work of
Antoine de Saint-Exupéry, who mostly wrote about the early days of aviation.
Poetic, meditative, and filled with nostalgia. Something to appease the mind
amidst the turmoil of traveling.</li>
  <li>Exercise: go on long walks, run around the campuses you’re visiting, work out
at the gym of your hotel. Clear your mind. Blast that music. Motivate yourself.
Each interview is a marathon and you’ll want to rise to the occasion.</li>
  <li>Have a few close ones with whom you can speak. Tell them what’s going on.
No one will fully get it, because no one will at once understand your academic,
personal and emotional aspirations. That’s ok. Even if someone doesn’t fully
get it, they’re still rooting for you. Thank you to those who were there for
me and put up with a few months of insanity.</li>
</ul>

<h2 id="perspectives">Perspectives</h2>

<p>The outcome of the job search does not define you. A lot of it is outside of
your control and this seems more true today than before. After I received
my offers, many university began hiring freezes. This meant that some of the
offers I turned down did not go to the next candidate, as would’ve been the
case in a less chaotic year.</p>

<p>When I signed my offer at UBC, a colleague wrote to me: “Well deserved,
but the process doesn’t always work the way it should, so glad to hear that
it worked out.”</p>

<p>Some of the best researchers I know did not get faculty positions and still
went on to do influential work.</p>

<p>And here’s one more small set of fun facts: the first time I applied to
grad school, I got no offers. I was the only one in my PhD cohort to fail
their qualifying exam at the end of my first year, meaning I had to take it
again. At the end of the PhD I applied
to a few universities for professor positions and got zero interviews
(the toe dipping I don’t recommend).
When I applied this year, I attended seven in-person interviews,
which resulted in five offers.</p>]]></content><author><name>Charles Margossian</name><email>cmargossian@flatironinstitute.org</email></author><category term="academia" /><summary type="html"><![CDATA[“Ce fut au milieu de ces pensées généreuses, et dans cette disposition d’esprit, qu’il traversa l’Hellespont.” (“It was amidst these generous thoughts and with this mindset that he crossed the Hellespont.”) – Maurice Druon, Alexandre le Grand (1958)]]></summary></entry><entry><title type="html">📚 Reading “The Armor of Light”</title><link href="https://charlesm93.github.io/posts/2025/07/blog-post-2/" rel="alternate" type="text/html" title="📚 Reading “The Armor of Light”" /><published>2025-07-09T00:00:00-07:00</published><updated>2025-07-09T00:00:00-07:00</updated><id>https://charlesm93.github.io/posts/2025/07/blog-armor_light</id><content type="html" xml:base="https://charlesm93.github.io/posts/2025/07/blog-post-2/"><![CDATA[<p>This morning, I finished reading <em>The Armor of Light</em> by Ken Follett, which is
the latest novel in the Kingsbridge series. I recommend the novel and I’d like
to share my enthusiasm. There won’t be any spoilers in this post but there will
be hints, so if you haven’t read the book and you plan to, you might as well
wait before reading the post.</p>

<p>I’m a fan of historical novels and this is not my first book by Follett.
(I’ve read <em>A Column of Fire</em>, <em>Fall of the Giants</em> and <em>Winter of the World</em>.)
His
books are extremely well-written and captivating: I find them to be wonderful
companions when I travel. I’ve also recommended them to a few friends, including
ones who are less in the habit of reading, and they’ve gone on to read
several books by Follett.</p>

<p>A quality I enjoy in Follett’s books is that he lets us witness historical
events through the eyes of ordinary folks. Sometimes these characters end
up playing an instrumental role (in <em>Column of Fire</em>, one of the main
antagonists essentially causes the
<a href="https://en.wikipedia.org/wiki/St._Bartholomew%27s_Day_massacre">St. Bartholomew’s Day massacre</a>).
Often times, the characters merely endure events that surpass them. They have
little agency in the unfolding of these events and yet they fully experience
their consequences. <em>The Armor of Light</em>, more so than other books I’ve read
by Follett, emphasizes this point.</p>

<p>The book mostly focuses on the town of Kingsbridge and how its habitants deal
with the impact of the Napoleonic wars (higher taxes, inflation, conscription,
and anti-union laws for fear of seeing the sparks of the French revolution
spread in Great Britain). The book doesn’t go too deep into how the characters
feel about the french revolution–some express sympathy for the uprise against
aristocracy and the book often questions the competence of leaders who have
inherited their positions rather than earn them; others feel they have a
patriotic duty to defend their country against a potential French invasion.
But the characters mostly focus on how to improve their livelihood.
They fight either to give more rights to workers or deprive them of it;
they seek to educate or be educated; they struggle to feed their children;
or they compete to earn an army contract to supply uniforms for the army.</p>

<p>Another major theme in the book is the introduction of machinery in the
weaving industry. Naturally, the benefits of the technology are hardly
distributed: the business owners—who granted, invest and take the risk—reap
most of the benefits; the workers on the other hand are ruthlessly sacked,
lose their employment, and find themselves impoverished by the new
technology. The more reasonable employers, who care about the well-being of
their employees, are forced to follow suit in order to stay competitive
and keep their business afloat. The book introduces an unusual character (a working
class child in the first act of the book) who becomes an able engineer, earns his keep
selling machines and later finds himself at odds with his step father, who lost
his position at a mill.</p>

<p>A notable choice is that the book almost exclusively focuses on people
in Kingsbridge. This is to be contrasted with <em>A Column of Fire</em>, the previous
volume in the Kingsbridge series, whose characters are scattered across England,
France, Spain and more. I went into <em>Armor of Light</em> expecting the same.
When I saw the book started in 1792, I hoped to read about the rise of a working
class Frenchmen in the ranks of the revolutionary army—one whose perspective
would contrast with the British experience of the war; or perhaps a pupil of
Beethoven in Vienna, at first enthusiastic about the French republic and later
disappointed by the French empire. But Follett’s decision to only gives us
Kingsbridge’s perspective is effective: it portrays the war as a distant,
almost intangible thing that still completely disrupts the daily life of the
protagonists.</p>

<p>One reservation I had while reading the first half of the book is that the novel
clearly tells us which characters to root for and which ones to dislike.
There is nuance of course: some
characters have tragic backgrounds; others are flawed but the novel
signals that they are good-hearted and that we should not judge them too
harshly. But some characters seem simply there to be disliked. The first chapter
already depicts one such characters as absolutely despicable. He becomes
a formidable adversary to one of the protagonists. Emotionally, this is
effective: it makes us root for a character, it creates suspense and a
conflict whose resolution we care about. But it also makes the antagonist seem
flat. A mediocre and yet incredibly destructive being. An unrelatable person.
I prefer it when the characters can be understood and we can have some
sympathy for them—even if we ultimately disagree with their actions.
This bothered me a bit but it certainly did not stop me from reading.
Which is good because most of the characters <em>do</em> eventually change, undergo their arcs,
even though it takes many pages or many years in the story.
Sometimes, the arc carries out across generations,
with the children refusing to live as their parents did, which is always a
powerful theme. All in all, the novel reminded me that life is long, very long,
and that many things will change as the decades march by.</p>

<p>In conclusion, it was a very enjoyable and thought-provoking read. Even
though the novel is set in a historical period, much of its topics seem
particularly relevant to today’s society. I like remembering that some of the
challenges we face are not as new as they might seem. And of
course, the book takes us into the innermost worlds of its characters: it
is fascinating to see their perspectives on historical events and
even more so to simply witness their humanity.</p>]]></content><author><name>Charles Margossian</name><email>cmargossian@flatironinstitute.org</email></author><category term="reading" /><summary type="html"><![CDATA[This morning, I finished reading The Armor of Light by Ken Follett, which is the latest novel in the Kingsbridge series. I recommend the novel and I’d like to share my enthusiasm. There won’t be any spoilers in this post but there will be hints, so if you haven’t read the book and you plan to, you might as well wait before reading the post.]]></summary></entry></feed>